Boot Loop After Latest Dom0 Update

After updating dom0 and restarting I can no longer boot. It loads GRUB then after that the screen turns black and it restart the computer

What should I do?

1 Like

OMG I just updated dom0 (kernel update) too… do I dare to reboot now? :scream:

Qubes OS Repository for Dom0                                                  2.9 MB/s | 3.0 kB     00:00    
Dependencies resolved.
==============================================================================================================
 Package                  Architecture    Version                           Repository                   Size
==============================================================================================================
Installing:
 kernel                   x86_64          1000:6.6.74-1.qubes.fc37          qubes-dom0-cached            12 M
 kernel-devel             x86_64          1000:6.6.74-1.qubes.fc37          qubes-dom0-cached            14 M
 kernel-modules           x86_64          1000:6.6.74-1.qubes.fc37          qubes-dom0-cached            72 M
 kernel-qubes-vm          x86_64          1000:6.6.74-1.qubes.fc37          qubes-dom0-cached            18 M
Removing:
 kernel                   x86_64          1000:6.6.63-1.qubes.fc37          @qubes-dom0-cached           40 M
 kernel-devel             x86_64          1000:6.6.63-1.qubes.fc37          @qubes-dom0-cached           65 M
 kernel-modules           x86_64          1000:6.6.63-1.qubes.fc37          @qubes-dom0-cached          427 M
 kernel-qubes-vm          x86_64          1000:6.6.63-1.qubes.fc37          @qubes-dom0-cached          518 M

Transaction Summary
==============================================================================================================
Install  4 Packages
Remove   4 Packages

Total size: 116 M
Is this ok [y/N]: y
1 Like

My Librem 14v1-01 boots just fine after the latest update.

1 Like

Can I undo the update from chroot?

1 Like

Search for “Boot Troubleshooting” in the documentation and here on the forum.

1 Like

There should be a grub entry to boot an older kernel version.

4 Likes

none of them work, I can boot other linux distros

1 Like

does qubes have a live environment where I can test it?

can I backup my qubes from rescue environment?

1 Like

Hi bootl - and welcome to Qubes OS

It’s still unclear to me, which steps you have tried (in order to narrow down the cause of the problem you see - can you describe them in more details?

:slight_smile:

1 Like

I updated dom0 then continued using the computer - no problem. Later after rebooting, it reaches the screen where I can edit GRUB boot option. I select one and it shows that it’s loading the OS but the gray screen where you enter the password never shows up, instead it turns completely blank and reboots the computer in a loop

What have I tried?

  • I tried all available boot entry in GRUB, including choosing advanced and the past kernels which existed

  • There are 2 boot entries for Qubes in UEFI boot menu, I tried both but no difference

  • booting other Linux distribution, works fine only Qubes OS has issues

I am technical enough to chroot or troubleshoot with Linux, but I see no error message so i am stumped

What have I not tried?

Why? Because it did not seem relevant since it worked until today should I try it?

2 Likes

Please provide kernel version(s) and Xen version you see on the GRUB menu. Also please provide brief hardware specification. And the Qubes OS version.

p.s. Since you say you were able to chroot, I assume that the local installation was successfully mounted and the filesystem is intact.

2 Likes

Could you try and add:

console=vga vga=,keep loglvl=all guest_loglvl=all noreboot=1 earlyprintk=xen

to the Xen kernel line and remove quiet from the Kernel line in GRUB and boot?

:slight_smile:

4 Likes

Yes no problems there. Will respond with versions and hardware after trying the suggestion by @ChrisA

2 Likes

Xen 4.17.5
Kernel 6.6.74-1, 6.6.68-1 and 6.6.65-1

Latest Qubes stable version
AMD CPU
AMD GPU

1 Like

What happens, if you boot with:

dom0_mem=1G,max:1G dom0_max_vcpus=1 dom0_vcpus_pin=1 console=vga vga=,keep loglvl=all guest_loglvl=all noreboot=1 earlyprintk=xen

?

:slight_smile:

2 Likes

New result, image looked broken to me on forum so I put it on imgur

1 Like

Managed to boot by setting dom0_mem=4G,max:4G after looking up solution online. Thank you @ChrisA for showing me how to find the error. Don’t know why it happened but now it’s fixed

4 Likes