[SOLVED] Wayland doesn't start after installing NVIDIA drivers

barish · 2024-06-07 06:08:47

Hi all, hoping that everyone's doing well. I am trying to install NVIDIA drivers on my new desktop with discrete graphics (i7 14700F + RTX 4070 Super) but having no luck -- after a few hours of hacking, I figured that I need another set of eyes on this.

I am using linux kernel version 6.9.3-arch1-1. I have followed the steps from NVIDIA installation page on the wiki and enabled DRM as well:

Jun 07 00:25:08 archlinux kernel: Kernel command line: initrd=\initramfs-linux.img root=PARTUUID=684b33e5-07a4-4f3b-94ed-69e08f2f54f7 zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs nomodeset nvidia_drm.modeset=1 nvidia-drm.modeset=1 nvidia_drm.fbdev=1

I am trying to boot into GDM with Wayland. My system is up to date, and I have linux-headers installed as well. I made sure to set GBM_BACKEND variable just in case. My /etc/mkinitcpio.conf also contains "nvidia nvidia_modeset nvidia_uvm nvidia_drm" modules.

If this makes any difference, I am using DisplayPort 1.4 with 165Hz monitor. Deleting NVIDIA drivers and switching to Nouveau works (with some suspend/resume bugs), but I am certain it's not hardware related issue since I plugged in a Windows drive and it worked as expected.

Here are possible issues with the boot from the logs, I'd appreciate if anyone could help me understand why they come up or if they are important:

Jun 07 00:25:08 archlinux kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Jun 07 00:25:08 archlinux (udev-worker)[542]: nvidia_modeset: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidia-modeset c $(grep nvidia /proc/devices | cut -d \  -f 1) 254'' failed with exit code 1.
Jun 07 00:25:08 archlinux (udev-worker)[554]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia /proc/devices | cut -d \  -f 1) 255'' failed with exit code 1.
Jun 07 00:25:08 archlinux (udev-worker)[554]: 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 /proc/devices | cut -d \  -f 1) ${i}; done'' failed with exit code 1.
Jun 07 00:25:08 archlinux (udev-worker)[593]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia /proc/devices | cut -d \  -f 1) 255'' failed with exit code 1.
Jun 07 00:25:08 archlinux (udev-worker)[593]: 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 /proc/devices | cut -d \  -f 1) ${i}; done'' failed with exit code 1.

Last edited by barish (2024-06-07 17:38:33)

seth · 2024-06-07 06:44:43

https://wiki.archlinux.org/title/GDM#Wa … DIA_driver

I plugged in a Windows drive and

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Here are possible issues with the boot from the logs

Which are all irrelevant. Grepping only works if you precisely know what you're looking for, not "some problems".
If it's not the GDM pecularities, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Edit: looking at "some things I've done", enabling KMS does not seem to be part of it?
Enable https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!) to also kill the simpledrm device.

Last edited by seth (2024-06-07 06:46:07)

barish · 2024-06-07 17:08:44

Thanks for the suggestions here! I did indeed disable fast boot (the "bios fast boot" is also disabled) and it didn't help (my Windows and Linux don't share EFI partition too).

I do actually have "nvidia_drm.modeset=1" in my kernel parameters, and "/sys/module/nvidia_drm/parameters/modeset" contains "Y" on boot.

Here's my full journalctl -b logs: http://0x0.st/XbuR.txt

V1del · 2024-06-07 17:23:46

Did you read seths link for the GDM peculiarities? It's not sufficient to enable modesetting for GDM, you'd also have to set up the suspension hooks for properly restoring VRAM on suspend/hibernation -- or disable the udev rule GDM uses to check this. .

barish · 2024-06-07 17:38:03

Hi V1del, I had the suspension hooks set up, but just in case I tried disabling the udev rule using

ln -s /dev/null /etc/udev/rules.d/61-gdm.rules

from the GDM link. I thought it'd only be relevant for older drivers, but it solved my problem!

Thanks to you both.

Arch Linux

#1 2024-06-07 06:08:47

[SOLVED] Wayland doesn't start after installing NVIDIA drivers

#2 2024-06-07 06:44:43

Re: [SOLVED] Wayland doesn't start after installing NVIDIA drivers

#3 2024-06-07 17:08:44

Re: [SOLVED] Wayland doesn't start after installing NVIDIA drivers

#4 2024-06-07 17:23:46

Re: [SOLVED] Wayland doesn't start after installing NVIDIA drivers

#5 2024-06-07 17:38:03

Re: [SOLVED] Wayland doesn't start after installing NVIDIA drivers

Board footer