You are not logged in.
Pages: 1
VBox 7.0.8 from originator on Daedalus amd64 on X570/Ryzen 5900/6700XT hardware. VMSVGA video driver selected.
netinstall previews dated May 8th, 22nd and 27th do start in EFI mode, install and expert install and end in a grey screen where I would expect the language selection screen. Same isos work fine in legacy mode and and real HW.
Tried to get to some screen with useful debug info and failed ...
Somebody with some more knowledge should look into this issue. If I can help with some more input, please let me know.
Thanks, rolfie
Online
Well, definitely there is a kernel dump on console 4 related to the graphics (after I found out how to switch consoles in a VBox window). Have no idea how to copy this.
Last edited by rolfie (2023-05-29 21:03:23)
Online
In that case you might switch to a console with C-A-F2, push newline, mount a target filesystem (which you have to prepare beforehand, eg with qemu-image etc), then copy /var/log/syslog to it, unmount and mount that to somewhere accessible, and finally copy out that syslog ... easy peasy
EDIT: btw, if you want to explore that vbox UEFI startup it's also possible to make it use a special "disk composite" where you single out grub.cfg as an editable byte block.
(eg for preview 20230522 that file starts at byte 3033088 and ends before byte 3037172 )
If that sounds useful and fun for you I can give some more detail instructions...
EDIT 2 : corrected ending 3037642 to be 3037172
Online
Also, a similar issue turns up with EFI in qemu ... I can explore that myself
Online
@rolfie, the cause for me was that qemu EFI emulation actually requires the ISO to be writable. I believe it's part of the EFI emulation which will want the EFI partition to be writable so it's likely the same for you on vbox.
Online
No my issue was different.
I'm not sure what it is, @rolfie, but it all seems to work on virtualbox if you add 'nopat' to the boot command line (push 'e' at the startup splash, then add 'nopat' to the 'linux' line and boot with '^x').
This is regardless of whether the ISO file is writable or not.
Afaict that 'pat' feature is something new for the kernel's memory management and apparently some module(s) are not fully revised and tested with respect to it. Using the 'nopat' option presumably makes the kernel use different code paths that get around this.
Online
@Ralph: thank you. Can confirm that the 'nopat' option works. The installer boots into a VBox VM and you can select a language.
But: when trying to set up an encrypted LVM in expert mode, the installer stumbles, I get a red screen past entering the passphrase twice. On console 4 I see the message "partman-crypto: libgcc_s.so.1 must be installed for pthread_exit to work"
Last edited by rolfie (2023-05-31 20:23:03)
Online
Thanks.
Yes, that installer is missing libgcc_s.so.1 (due to an undeclared dependency).
New ISOs are in progress that should be better in that, though you still need to add nopat by hand; that issue seems to be limited to virtualbox with EFI and it's not yet confirmed to be a universally useful fix.
Online
@Ralph: just for completion, also the legacy mode throws the same libgcc error on the May 27th version.
Last edited by rolfie (2023-06-01 18:42:25)
Online
ok. thanks. So far limited to virtualbox; i.e. it's not a problem with qemu. I haven't seen it reported from other use cases.
Online
Well, the encryption problem is fixed with the netinstall iso dated June 1st. The nopat issue still exists.
Thank you for your attention.
Online
Pages: 1