last year I tried upgrading dom0 kernel from 4.* to 5.* and Qubes became unstable after that (randomly hang after a few minutes). I tried bios tweaks and such back then but to no avail, so I reverted to the older kernel and all was well.
Yesterday I ran the auto updater tool and forgot to uncheck dom0, so I accidentally updated the dom0 kernel, and the system was again unstable after rebooting.
So I wanted to revert to the old dom0 kernel to for stability. Unfortunately, my first action to was to edit the xen.cfg file and change [default] to the older 4.* kernel listed in that file.
The GUI hanged before I was able to actually reinstall that older kernel in the system, and upon hard reset, qubes booted into a red-text emergency shell. Hoping for a miracle, I rebooted again, and this time not even the emergency shell came up and the EFI boot no longer found an OS.
What Iāve tried so far:
I used the 4.03 USB install disk to boot via UEFI, and then mounted the EFI partition. xen.cfg was empty, so manually entered the parameters shown in the qubes documentation UEFI Troubleshooting example, and set the kernel values to the newly auto-installed version.
That didnāt change anything (still no boot device found) so I backed up the xen.efi into a different name, and copied the latest available xen-* in the EFI/qubes directory to xen.efi, and the OS still did not boot.
Next I tried the efibootmgr trick as listed on the UEFI Troubleshooting page, changing the drive from ādev/sda -p 1ā to ā/dev/nvme0n1 -p 1ā and the new entry shows up in efibootmgr -v as active, but the BIOS does not show it as one of the available EFI boot options. I changed the boot order in efibootmgr, putting the new one first but the BIOS still doesnāt see it.
I tried listing the drive as ā/dev/nvme0n1p1ā using efibootmgr without the ā-p 1ā and it created a boot entry that did show up in the BIOS, but it was incorrect and said MBR with a bunch of zeros instead of GPT with a nice string of numbers like the previous working xen efi boot entry.
Then I tried going into my Dellās BIOS to use its boot manager to create an EFI boot entry by pointing it directly to /EFI/qubes/xen.efi. An entry is created, but does not find a boot device either. (and appears different from the efibootmgr created entries).
Any help here would be greatly appreciated.
Is there some location that might contain a backup of my previous xen.cfg which I edited from within the OS to cause this mess? Or should the generic values from EFI Troubleshooting page simply work after substituting the example with my currently installed dom0 kernel? (I noticed another personās xen.cfg has some LUKS info/numbers specific to their system)
I saw that another potential solution on on the UEFI Troubleshooting page is to create an /EFI/BOOT/ folder with the xen.efi and xen.cfg renamed to BOOTX64.efi and BOOTX64.cfg. Would this help when my system was already booting previously with /EFI/qubes/xen.efi anyway?
Thanks in advance!