Talk:GDM

From ArchWiki

Steps for enabling Wayland for proprietary Nvidia driver is incomplete

I am using Gnome. Steps in section 4.1 to enable Wayland for proprietary Nvidia driver is incomplete. Below post in the Manjaro forum listed all the necessary steps. I think the missing step in the Arch wiki is the third step with a gsettings call. After I did that step, I successfully entered Wayland session with my Nvidia 1660 Ti gpu.

https://forum.manjaro.org/t/howto-use-wayland-with-proprietary-nvidia-drivers/36130

Alphanci (talk) 16:36, 20 March 2023 (UTC)Reply

I don't know what exactly was missing for you, but for me the section is missing information about what the effect of the 61-gdm.rules regarding the Nvidia drivers and Wayland. After a night of fighting with gdm and the Nvidia driver, this is what I found out:
Among other things, 61-gdm.rules checks if the Nvidia driver is configured in a certain way, probably to avoid unwanted or unstable behavior. It basically checks for the configuration described in NVIDIA/Tips and tricks#Preserve video memory after suspend (the kernel parameter and the 3 Nvidia services). So rather than suggesting overriding 61-gdm.rules, users should configure the driver as mentioned before. I think overriding should be the last option.
I'm planning on updating the section accordingly, by making clear that NVIDIA/Tips and tricks#Preserve video memory after suspend is mandatory for GDM.
The important lines of 61-gdm.rules for reference: https://gitlab.gnome.org/GNOME/gdm/-/blob/81ee658c11381912131dd4a29e84190f7f9cd039/data/61-gdm.rules.in#L48-56 Mastercaution (talk) 00:40, 15 June 2024 (UTC)Reply
There is a Template:Note about it since 2022, did you skip past it or should we improve it so that it's clearer?
-- Erus Iluvatar (talk) 06:57, 15 June 2024 (UTC)Reply
I read it but I thought I had a different issue with GDM, so I mistakenly thought it was not relevant. My situation was that GDM didn't start at all (because for some reason it was unable to start the fallback X server). At that time, I didn't know that it was trying to use the fallback. The note describes the issue that GDM starts but doesn't show the Wayland option.
I guess if GDM had been able to successfully start the fallback X server, I would have the issue described in the note. I don't know why GDM failed to do that, but maybe I messed up somewhere. The symptoms were a black screen with a blinking cursor that freezes after a few seconds (consuming all ttys), but starting a gnome-session manually worked fine.
I still think the note could be clearer in case I'm not the only one encountering this issue. Maybe we can alternatively add a subsection for the issue I've encountered? Mastercaution (talk) 12:07, 15 June 2024 (UTC)Reply
I see... Did you manage to find what was preventing X to start ? The message in the logs might be a good starting point to create a new Troubleshooting entry. IMO your description sounds like there were two separate issues at the same time which might create more confusion for other readers.
-- Erus Iluvatar (talk) 13:49, 15 June 2024 (UTC)Reply