Update to 4.2 - Kernel 6.6.54 does not boot

User Support
1

I updated a LUKS-encrypted Qubes OS 4.1 to 4.2, following the official documentation.
This also included an update of the Linux kernel from 6.1.75 to 6.6.54.
After STAGE 3 of qubes-dist-upgrade, the system should be rebooted.
Unfortunately, this newer Kernel (6.6.54) does not boot properly and I am unable to enter the decryption passphrase.
Once I manually select the old kernel (6.1.75) in the grub menu, I am able to boot again.
This way, I finished the upgrade to 4.2 (STAGES 4-6) using the older kernel version.
However, the Kernel 6.6.54 seems to be properly installed, as it can successfully be used for different VMs.

I already tried the following:

  • Removed rhgb and quiet from and added plymouth.enable=0 to the kernel command line options in grub config: This shows some output when trying to boot 6.6.54, but it is way to fast to capture anything useful as it is interrupted by textual gibberish
  • Installed kernel-latest via qubes-dom0-update: This installed kernel 6.10.10, but this one doesn’t boot either

Did anyone encounter similar issues or can anyone think of a way to properly debug (or even fix) this behavior?

The full kernel names for reference:

  • 6.1.75-1.qubes.fc32.x86_64 (kernel used with 4.1) boots properly with 4.2
  • 6.6.54-1.qubes.fc37.x86_64 (installed during upgrade to 4.2) does not boot
  • 6.10.10-1.qubes.fc37.x86_64 (manually installed as kernel-latest) does not boot

Edit: I just now found this post. Seems somewhat related!?

2

Did you try using kernel 6.6.42?
What’s your CPU/GPU?

3

Yes, I am successfully running on 6.6.42-1.qubes.fc37.x86_64 now.
My CPU is an AMD, but since my GPU is also an NVIDIA GTX 1070, it seems similar.
So probably not an issue with the update to 4.2 (or with Qubes for that matter), but with the kernel.