Since the last system updates QubesOS doesn’t boot anymore with the new default Linux. After showing GRUB, instead of starting the boot process, the screen simply shows the blinking underline character and nothing else.
When I’m interrupting GRUB, I can navigate to the alternative boot entries and at least the second entry is still working (Linux 6.6.42).
Not booting: Qubes, with Xen 4.17.4 and Linux 6.6.48-1.qubes.fc37.x86_64
Still correctly booting: Qubes, with Xen 4.17.4 and Linux 6.6.24-1.qubes.fc37.x86_64
On the one hand it indeed sounds logical. On the other hand it felt more severe than “just” a GPU issue because I couldn’t even reach another TTY during the blinking underline (e.g. by pressing CTRL + ALT + F2). I would expect that this should still be possible with such GPU issues.
Let’s see what will happen with the next update then. I’m planning to report back here.
Thanks for testing and reporting this here, @quantum .
Does anyone have a suggestion on how to troubleshoot this? Are there some kind of log files that we could check?
It seems to me that the OS is not started at that point yet but that the error occurs when GRUB tries to initiate the startup of the OS. So maybe we should try to collect some GRUB logs?
Building recent kernels with the reverted commit works for me.
I’m not sure when this will be fixed, for now I’ve been including a revert commit patch in my kernel builds and it’s worked perfectly on all recent releases.