Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Black screen with blinking cursor with GDM runit after gdm 40 upgrade (Read 2083 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Black screen with blinking cursor with GDM runit after gdm 40 upgrade

After GDM upgraded to version 40 gdm stopped working, only way to login with gdm is now with automatic login. If I logout from my session I get black screen with blinking cursor.

System
Artix linux with runit
Kernel:  5.11.14-artix1-1
Nvidia driver 465.24.02
Login manager gdm
 

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #2 –
I'd be inclined to think this is some problem with gdm and the proprietary nvidia driver. It should default to using xorg, but make sure you're not somehow trying to use wayland.

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #3 –
Quote from: Dudemanguy – on
I'd be inclined to think this is some problem with gdm and the proprietary nvidia driver. It should default to using xorg, but make sure you're not somehow trying to use wayland.

I tried this from /etc/gdm/custom.conf  WaylandEnable=false , Still doesn't work. :(
I'm not sure if there any other way to make sure that it uses xorg instead of wayland.
I wonder if other gdm users had same problem with nvidia drivers after update.

Edit: also  /usr/lib/udev/rules.d/61-gdm.rules  has this line.
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm-runtime-config set daemon WaylandEnable false"

Edit2: https://pastebin.com/Lh2vCgys Also gdm log files had errors

Edit3: seems like the problem is with nvidia drivers.  with Nouveau drivers gdm worked just fine.

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #4 –
Quote
xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted

Yeah that line would lead me to believe that there's a driver bug somewhere in there since it doesn't happen with the free drivers.

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #5 –
Same problem with GDM after upgrade to gnome 40, any update for nvidia drivers?

I using now LIGHTDM, but screen lock don't work...  :'(

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #6 –
Same problem with gdm-openrc and NVIDIA driver. However to me with the GNOME automatic login you start, you must enter "AutomaticLoginEnable=true" and "AutomaticLogin=yourusername" in /etc/gdm/custom.conf, but if you finish the session instead of the GDM screen you only have the black screen with the flashing cursor.

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #7 –
Hello I got gdm working with nvidia 470 driver just enabled wayland /etc/gdm/custom.conf  WaylandEnable=true
and if you are using grub set kernel parameter in /etc/default/grub nvidia-drm.modeset=1 and then  sudo grub-mkconfig -o /boot/grub/grub.cfg , reboot and after that my gdm is working with wayland. Gnome on wayland is buggy still tough with nvidia drivers so you should select gnome-xorg from login screen if you are using gnome.

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #8 –
Quote from: ankkax – on
Hello I got gdm working with nvidia 470 driver just enabled wayland /etc/gdm/custom.conf  WaylandEnable=true
and if you are using grub set kernel parameter in /etc/default/grub nvidia-drm.modeset=1 and then  sudo grub-mkconfig -o /boot/grub/grub.cfg , reboot and after that my gdm is working with wayland. Gnome on wayland is buggy still tough with nvidia drivers so you should select gnome-xorg from login screen if you are using gnome.

That's weird. Wayland doesn't work well with Nvidia proprietary drivers in general due to different API set used in Nvidia.

Re: Black screen with blinking cursor with GDM runit after gdm 40 upgrade

Reply #9 –
Actually, a NVIDIA guy merged some code into Mesa that allows for alternative backends to be used with the API. Presumably, they will have said alternative backend in their proprietary blob. Now, I didn't think the new nvidia 470 driver was supposed to have actual good wayland support (I.E. use GBM not EGLStreams) yet so it is kind of weird that it works for that guy. In any case, it's nice that NVIDIA seems to actually be working with Mesa for once. That's a real rarity and goes completely against their history.