Have used Qubes for around 8 years but since kernel 6.1.62-1 have been getting boot process stopping with message “starting plymouth-quit-waiting-until boot process finshes up”.
Have resolved this to date by going into Advanced option at boot - and selecting the above kernel - ignoring later ones.
With update to Qubes 4.2.4 have found the same boot problem irrespective of kernel. Can get round this by keying “e” at screen where I can choose which kernel to use and this gives the opportunity to edit the file which appears.
If I edit out “quiet splash nomodeset” and then press F10 - then it boots fine - irrespective of kernel choice.
Grateful if someone can advise if there is a way to edit this out permanently (not sure what the file name is - or whether edit would be permanent)
If there is a better solution - I would be grateful for advice.
You can remove the quiet splash nomodeset options from your GRUB configuration by editing the file /etc/default/grub. Look for the line starting with GRUB_CMDLINE_LINUX= and delete those options. Then, regenerate your GRUB configuration using the appropriate command for your system:
sudo grub2-mkconfig -o /boot/grub/grub.cfg # for BIOS systems
sudo grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg # for UEFI systems
Alternatively, another option to work arround the error might be by disablng plymouth with the option plymouth.enable=0
While these workarounds might be enough for you, it could still be beneficial to investigate the origin of the error for the sake of learning as well as because others might encounter the same issue.
You can remove the quiet splash nomodeset options from your GRUB configuration by editing the file /etc/default/grub. Look for the line starting with GRUB_CMDLINE_LINUX= and delete those options. Then, regenerate your GRUB configuration:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Alternatively, you might work around the error by disabling plymouth with the option plymouth.enable=0
While a work around might be enough for you, it could be worthwhile to investigate the root cause of the error for the sake of learning as well as to help others who might encounter a similar issue.
Edit: Fixed typo
Many thanks for comments.
Amending the default kernel gave no success.
I tried the “plymouth.enable=0” approach and no success here but possibly I included the code at the wrong point.
The suggestion of editing the /etc/default/grub file and deleting the “quiet splash nomodeset” options WAS SUCCESSFUL.
It did not work when following the “sudo” code (as in the above note) to regenerate the GRUB - but I followed the QUBES DOCS note on managing kernels - where it suggested using
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
(ie inserting grub2 instead of grub after /boot/ )
I assume this is OK as it seems to work.
Further point here - in the /etc/default/grub file and the line starting with GRUB_CMDLINE_LINUX - my system included the option “plymouth.ignore-serial-consoles 6.1.62-1.qubes .fc37.x86_64”.
It may be that instruction which has previously allowed me to boot with the old kernel.
Maybe I could have tried a similar instruction with the latest kernel reference also to overcome the problem - but I’m happy for the moment with the fix as mentioned above.
As to the cause of the problem in the first place - I have no idea at the moment - but if I do get to understand the issue I will add to this note.
For the moment - thanks again for comments - and I can again have a simple boot procedure which uses the latest kernel and does not require me to enter advanced mode and worry about system updates possibly removing the old kernel which has worked to date.
Yes, this was a typo of mine. grub2 instead of grub is correct.