i just installed qubes on a new system with a nvidia dGPU and an AMD iGPU. After a dom0 update, i rebooted and now lightdm will not start. After typing in my FDE password, i get a black screen with white text, stopping at
Failed to start lightdm.service
I have tried
‘sudo qubes-dom0-update kernel-latest’
rd.qubes.hide_pci to hide the nvidia gpu
nomodeset
modprobe.blacklist=nouveau
but nothing had any effect. Next step is removing the GPU but is there something else i need to do to get this working?
So i checked /var/log/Xorg.0.log and it seems like the error is happening because /dev/dri/card0 is missing. EDIT: actually idk what the real cause is.
Maybe there is a problem with newer kernel version that was installed during update.
Try to boot with the older kernel version that worked for you before.
Also, what Qubes OS version do you have and what kernel versions old/new do you have?
Very nice, changing the kernel version worked. In the grub menu, i selected “Advanced options for Qubes (with xen hypervisor)” → “Xen hypervisor, version 4.17.5” and i was given three options:
Qubes with xen 4.17.5 and Linux 6.6.77-1.qubes.fc37.x86_64
Qubes with xen 4.17.5 and Linux 6.12.47-1.qubes.fc37.x86_64
Qubes with xen 4.17.5 and Linux 6.15.10-1.qubes.fc37.x86_64
I tried each of them but only 6.6.77 allows me to boot into the OS as normal (lightdm launches fine).
I tried to set 6.6.77 as my default kernel using the method described in this guide, but it has no effect.
Seems like I’m still booting into 6.15 by default even after i follow the instructions and select 6.6 once.
Woops! All good, i have the old kernel set as default in grub now. My problem was just that i was misspelling one of the grub env variables in /etc/default/grub.
So what should i do now? My system now runs fine with the 6.6 kernel, but how should i report this kernel incompatibility so it can be fixed upstream?
Did you test your kernel versions with NVIDIA GPU removed?
You can try to boot from some other Linux OS (e.g. Fedora Live) and check if you’ll have the same issue with the same kernel versions there.
If it’s not an issue specific to Qubes OS or Xen, then it should be reported to the kernel mailing list or to Fedora.