LightDM fails to start after dom0 update with Xen upgrade and NVIDIA driver installation #9501
Labels
affects-4.2
This issue affects Qubes OS 4.2.
C: Xen
diagnosed
Technical diagnosis has been performed (see issue comments).
hardware support
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
r4.2-host-stable
r4.3-host-cur-test
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Comments
ghost
added
P: default
ghost
changed the title
|
Can you say exactly which version works and which doesn't? |
|
Sure. |
andrewdavidwong
added
C: Xen
hardware support
needs diagnosis
|
As suggested by the Xen Matrix channel, I manually compiled Xen from source with the debug option enabled. Below is the output of |
marmarek
added a commit
to marmarek/qubes-vmm-xen
that referenced
this issue
Oct 14, 2024
It looks like this workaround is still needed, at least for the nvidia driver. This reverts commit 394e018. Fixes QubesOS/qubes-issues#9501
|
Running |
andrewdavidwong
added
diagnosed
|
@xGlasi Can you file a bug report with Nvidia? The update causes Xen to use Linux’s PAT, which isn’t a configuration supported by upstream Xen. A correctly-written Linux driver will not need this. |
|
Done. |
Thanks! I would add that this is PV dom0. PVH and HVM guests will not be affected by this bug. |
|
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Qubes OS release
Qubes release 4.2.3 (R4.2)
Brief summary
I installed the NVIDIA driver following the tutorial from the forum. Additionally, I always need to run
sudo ./nvidia-installerto get the nvidia_drm kernel module. I'm not sure why this step is necessary, but it has worked for a long time. I follow this process whenever there's a new kernel release and have been doing so for quite some time now.After a recent update to dom0 via the Qubes Updater, which included a Xen update, my setup broke. Upon restarting Qubes OS, I encountered the usual error associated with driver issues: LightDM failed to start. However, there was an unusual aspect this time: the Plymouth splash screen animation is still displayed correctly. Normally, when there is an issue with the NVIDIA driver, the Plymouth animation is not shown, and instead, I see the terminal-based view with a blue background for entering the LUKS password.
(Update: I just tried it again and it seems like I imagined it. The plymouth plash screen animation is not displayed after all.Second Update: I don't think it was imagination. I tried it again, and while the Plymouth splash screen wasn't shown at login this time, it appeared at shutdown.) After entering my LUKS password, the error LightDM failed to start occurs.The cause of the issue appears to be in
/var/log/Xorg.0.log:Running
lspci -k | grep -EA3 ‘VGA|3D|Display’shows that the kernel driver in use isnvidia, and the loaded kernel modules are nouveau, nvidia_drm, and nvidia.I've tried reinstalling everything several times, but it doesn't resolve the issue. I also tested with older NVIDIA driver versions and Linux kernels.
The only solution that seems to work is downgrading xen:
sudo qubes-dom0-update --action=downgrade python3-xen xen xen-hypervisor xen-libs xen-licenses xen-runtimeSteps to reproduce
Expected behavior
LightDM (or the graphical user interface) should start successfully.
Actual behavior
LightDM fails to start, and the graphical user interface does not appear.
The text was updated successfully, but these errors were encountered: