Arch + Gnome + Wayland + nvidia-dkms 530.41.03-1 cannot boot

Graphics / Linux Linux
1

Can’t boot into Arch + Gnome + Wayland with 530.41.03-1.

I have a 1080TI and I have 60Hz monitor. I am stuck after the GNOME Display Manager (GDM) login and have to switch to Xorg.

I had to downgrade to use Wayland.

warning: downgrading package nvidia-utils (530.41.03-1 => 525.89.02-2)
warning: downgrading package nvidia-dkms (530.41.03-1 => 525.89.02-2)

journalctl -b | grep wayland result

Apr 01 14:35:53 username /usr/lib/gdm-wayland-session[599]: dbus-daemon[599]: [session uid=120 pid=599] Activated service ‘org.freedesktop.systemd1’ failed: Process org.freedesktop.systemd1 exited with status 1
Apr 01 14:35:59 username systemd[1089]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV
Apr 01 14:35:59 username systemd[1089]: org.gnome.Shell@wayland.service: Failed with result ‘core-dump’.
Apr 01 14:35:59 username systemd[1089]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
Apr 01 14:36:07 username systemd[1089]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV
Apr 01 14:36:07 username systemd[1089]: org.gnome.Shell@wayland.service: Failed with result ‘core-dump’.
Apr 01 14:36:07 username systemd[1089]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
Apr 01 14:36:21 username systemd[1571]: org.gnome.Shell@wayland.service: Skipped due to ‘exec-condition’.
Apr 01 14:36:24 username gnome-shell[610]: Connection to xwayland lost

2

Have you set DRM kernel mode setting and early loading?
First go to: NVIDIA - ArchWiki
Read the following:
1.3 DRM kernel mode setting
1.3.1 Early loading
1.3.1.1 mkinitcpio
If you are still having issues visit: GDM - ArchWiki

3

Duplicate of Can't boot into KDE WAYLAND session with 530.30..02

4

Hello,

Thanks for your reply, sorry for the late answer.

I am loading the following modules and haven’t touched them :

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

I also have the nvidia_drm.modeset=1 as a kernel parameter.

5

Dont forget to sudo mkinitcpio -P after you added the modules to mkinitcpio.

Also are you using grub or systemd-boot? if you’re using grub you need to sudo grub-mkconfig -o /boot/grub/grub.cfg after adding the kernel parameter to grub. If you are using systemd-boot there is no further action taken.

If you did all that and cant get into wayland try sudo ln -s /dev/null /etc/udev/rules.d/61-gdm.rules

I always had to use that when I was using NVIDIA as my primary GPU.

6

I did not add them, the modules have been there since the beginning. I did not need to regenerate anything. I have a pacman hook to regenerate mikinitcpio -P. I can get into Wayland, just not with the new 530.41.03-1.

7

Oh okay. I misunderstood then. I thought it was a new install. Hopefully, the issue will get resolved soon!

8

I hope so too. I edited my pacman.conf to IgnorePkg` for the time being, but I hope it’ll be resolved soon

9

ARCH + KDE+X11+NVIDIA-DKMS 530.41.03 HDMI 4k120 GSYNC

Same issue for me.

I can boot into the new driver if I delete the line:
/etc/X11/xorg.conf

   Option         "metamodes"  ...

As soon as you use nvidia-settings again, your system will fail to hit graphical mode next time you reboot it.

What’s going on NVIDIA?

10

I don’t have a /etc/X11/xorg.conf

I had to revert to use Xorg, I still can’t log in Wayland.

I upgraded my packages, it upgraded my kernel which broke my install because the kernel depend on the latest nvidia-dkms 530 module. I had to arch-chroot to fix it.

11

Hello guys and gals.

Any news ?

journalctl -b | grep nvidia

Apr 15 20:30:43 username kernel: Command line: initrd=\amd-ucode.img initrd=\initramfs-linux-zen.img root=“PARTUUID=82c00610-c1fe-4daa-99b0-372fa551d152” nvidia-drm.modeset=1
Apr 15 20:30:43 username kernel: Kernel command line: initrd=\amd-ucode.img initrd=\initramfs-linux-zen.img root=“PARTUUID=82c00610-c1fe-4daa-99b0-372fa551d152” nvidia-drm.modeset=1
Apr 15 20:30:43 username kernel: nvidia: loading out-of-tree module taints kernel.
Apr 15 20:30:43 username kernel: nvidia: module license ‘NVIDIA’ taints kernel.
Apr 15 20:30:43 username kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Apr 15 20:30:43 username kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 237
Apr 15 20:30:43 username kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
Apr 15 20:30:43 username kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 530.41.03 Thu Mar 16 19:23:04 UTC 2023
Apr 15 20:30:43 username kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Apr 15 20:30:43 username kernel: nvidia-uvm: Loaded the UVM driver, major device number 235.
Apr 15 20:30:43 username kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Apr 15 20:30:43 username kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
Apr 15 20:30:43 username (udev-worker)[338]: nvidia: Process ‘/usr/bin/bash -c ‘/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \ -f 1) 255’’ failed with exit code 1.
Apr 15 20:30:43 username (udev-worker)[338]: nvidia: Process ‘/usr/bin/bash -c ‘for i in $(cat /proc/driver/nvidia/gpus/*/information | grep Minor | cut -d \ -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontend /proc/devices | cut -d \ -f 1) ${i}; done’’ failed with exit code 1.
Apr 15 20:30:44 username gnome-shell[573]: Added device ‘/dev/dri/card0’ (nvidia-drm) using atomic mode setting.
Apr 15 20:30:58 username gnome-shell[1144]: Added device ‘/dev/dri/card0’ (nvidia-drm) using atomic mode setting.
Apr 15 20:30:58 username kernel: gnome-shell[1144]: segfault at 0 ip 00007ff2f521556b sp 00007ffd86543410 error 4 in libnvidia-allocator.so.530.41.03[7ff2f5200000+1f000] likely on CPU 2 (core 2, socket 0)
#0 0x00007ff2f521556b n/a (nvidia-drm_gbm.so + 0x1556b)
#1 0x00007ff2f5215838 n/a (nvidia-drm_gbm.so + 0x15838)
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: Kernel command line: initrd=\amd-ucode.img initrd=\initramfs-linux-zen.img root=“PARTUUID=82c00610-c1fe-4daa-99b0-372fa551d152” nvidia-drm.modeset=1
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (**) OutputClass “nvidia” ModulePath extended to “/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) Applying OutputClass “nvidia” to /dev/dri/card0
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: loading driver: nvidia
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (==) Matched nvidia as autoconfigured driver 0
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) LoadModule: “nvidia”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) Module nvidia: vendor=“NVIDIA Corporation”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) Applying OutputClass “nvidia” options to /dev/dri/card0
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) Loading sub module “glxserver_nvidia”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) LoadModule: “glxserver_nvidia”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) Module glxserver_nvidia: vendor=“NVIDIA Corporation”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) NVIDIA(0): “DFP-3:nvidia-auto-select,DFP-1:nvidia-auto-select”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (WW) NVIDIA: ‘/var/run/nvidia-xdriver-d9ce177d’ Permission denied
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) NVIDIA(0): Setting mode “DFP-3:nvidia-auto-select,DFP-1:nvidia-auto-select”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) NVIDIA(0): Setting mode “DP-0: nvidia-auto-select @1920x1200 +0+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
Apr 15 20:31:09 username /usr/lib/gdm-x-session[1290]: (II) NVIDIA(0): Setting mode “DP-0: nvidia-auto-select @1920x1200 +1920+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”

That seems interesting

Apr 15 20:30:58 username kernel: gnome-shell[1144]: segfault at 0 ip 00007ff2f521556b sp 00007ffd86543410 error 4 in libnvidia-allocator.so.530.41.03[7ff2f5200000+1f000] likely on CPU 2 (core 2, socket 0)
#0 0x00007ff2f521556b n/a (nvidia-drm_gbm.so + 0x1556b)
#1 0x00007ff2f5215838 n/a (nvidia-drm_gbm.so + 0x15838)

I have a 1080 TI and a Ryzen 7 7600X.

12

@BubuGagaGugu
Are you seeing this issue on higher refresh rates only or at all refresh rates ?
We had similar issue reported on below thread but it was having only at higher refresh rates.

13

Hello,

I have this issue at 60Hz, my screens can’t go higher.

First screen :

image

Second, an older one :

image

I switched to Xorg for the time being.