About nVidia proprietary driver software

Support
, , ,
62

My boot log is very long, so I will paste here only the most relevant parts of it.
I am not sure, but it seems that the wrong nvidia driver rules which start early at boot create display problems with plain shell.
Please let me know if I should search for something more specific.

gen 18 20:05:36 Sharky systemd-udevd[680]: Reading rules file: /usr/lib/udev/rules.d/60-nvidia.rules
gen 18 20:05:36 Sharky systemd-udevd[680]: /usr/lib/udev/rules.d/60-nvidia.rules:2 Invalid value "/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) 255'" for RUN (char 61: invalid substitution type), ignoring.
gen 18 20:05:36 Sharky systemd-udevd[680]: /usr/lib/udev/rules.d/60-nvidia.rules:3 Invalid value "/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'" for RUN (char 28: invalid substitution type), ignoring.
gen 18 20:05:36 Sharky systemd-udevd[680]: /usr/lib/udev/rules.d/60-nvidia.rules:4 Invalid value "/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidia-modeset c $(grep nvidia-frontend /proc/devices | cut -d \  -f 1) 254'" for RUN (char 66: invalid substitution type), ignoring.
gen 18 20:05:36 Sharky systemd-udevd[680]: /usr/lib/udev/rules.d/60-nvidia.rules:5 Invalid value "/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidia-uvm c $(grep nvidia-uvm /proc/devices | cut -d \  -f 1) 0'" for RUN (char 62: invalid substitution type), ignoring.
gen 18 20:05:36 Sharky systemd-udevd[680]: /usr/lib/udev/rules.d/60-nvidia.rules:6 Invalid value "/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidia-uvm-tools c $(grep nvidia-uvm /proc/devices | cut -d \  -f 1) 1'" for RUN (char 68: invalid substitution type), ignoring.
[...]
gen 18 20:05:37 Sharky systemd-logind[766]: VT changed to 1
gen 18 20:05:37 Sharky sddm[809]: Failed to read display number from pipe
gen 18 20:05:37 Sharky sddm[809]: Attempt 1 starting the Display server on vt 2 failed
[...]
gen 18 20:05:39 Sharky systemd-logind[766]: VT changed to 2
gen 18 20:05:39 Sharky systemd-logind[766]: VT changed to 1
gen 18 20:05:39 Sharky sddm[809]: Failed to read display number from pipe
gen 18 20:05:39 Sharky sddm[809]: Attempt 2 starting the Display server on vt 2 failed
[...]
gen 18 20:05:42 Sharky systemd-logind[766]: VT changed to 1
gen 18 20:05:42 Sharky sddm[809]: Failed to read display number from pipe
gen 18 20:05:42 Sharky sddm[809]: Attempt 3 starting the Display server on vt 2 failed
gen 18 20:05:42 Sharky sddm[809]: Could not start Display server on vt 2
63

This is just a guess, but maybe worth a try. If you go into edit mode in grub2 menu (press e), and change nvidia-drm.modeset=1 to 0 and see if it boots into a tty?

64

I donā€™t have ā€œnvidia-drm.modesetā€ in my grub2 menu; only ā€œrd.driver.blacklist=nouveauā€ is there.
I deleted that part in console mode and booted. System logs showed something different (the other log was from recovery mode). Looks like my system regularly loaded nvidia drivers and no display issues were reported, but I couldnā€™t use any shell anyway.

gen 19 10:53:42 Sharky kernel: nvidia: loading out-of-tree module taints kernel.
gen 19 10:53:42 Sharky kernel: nvidia: module license 'NVIDIA' taints kernel.
gen 19 10:53:42 Sharky kernel: Disabling lock debugging due to kernel taint
gen 19 10:53:42 Sharky kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
gen 19 10:53:42 Sharky kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241
gen 19 10:53:42 Sharky kernel: 
gen 19 10:53:42 Sharky kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[...]
gen 19 10:53:42 Sharky kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  525.78.01  Mon Dec 26 05:58:42 UTC 2022
gen 19 10:53:42 Sharky systemd-udevd[691]: event19: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
gen 19 10:53:42 Sharky kernel: nvidia_modeset: no symbol version for nvidia_register_module
gen 19 10:53:42 Sharky kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  525.78.01  Mon Dec 26 05:38:56 UTC 2022
[...]
gen 19 10:53:43 Sharky systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions...
gen 19 10:53:43 Sharky systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
gen 19 10:53:43 Sharky systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions.
gen 19 10:53:43 Sharky systemd[1]: Starting plymouth-quit-wait.service - Hold until boot process finishes up...
gen 19 10:53:43 Sharky systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen...
gen 19 10:53:43 Sharky systemd[1]: Finished plymouth-quit-wait.service - Hold until boot process finishes up.
gen 19 10:53:43 Sharky systemd[1]: Started getty@tty1.service - Getty on tty1.
gen 19 10:53:43 Sharky systemd[1]: Reached target getty.target - Login Prompts.
gen 19 10:53:43 Sharky systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen.
65

Hmmmā€¦ Thatā€™s odd, as I have nvidia-drm.modeset=1 in my grub entries, and I thought that was added when installing the dkms drivers, but maybe I added that line myself as I know itā€™s needed in Hybrid gfx situations.

I also have rd.driver.blacklist=nouveau as without that, Iā€™ll either not boot correctly, or the system will freeze shortly after.

If you add nvidia-drm.modeset=0 or 1 , are you able to get into a TTY? That setting alters the way that nvidia cards handle the tty, afaik. Understanding nvidia-drm.modeset=1 (NVIDIA Linux driver modesetting) - Linux - NVIDIA Developer Forums has some more info. It could be related to the 60-nvidia.rules errors in udev, but Iā€™m out of my depth on that one. :frowning:

66

I added the command you suggested, but nothing changed.
Here is the grub2 boot line I used:

gen 19 13:43:25 omv dracut-cmdline[283]: Using kernel command line parameters: rd.driver.pre=btrfs rd.driver.pre=ehci_hcd BOOT_IMAGE=/boot/vmlinuz-6.1.4-desktop-1omv2301 root=UUID=4bd79bf4-8abd-4b45-b273-c52b69077cd2 ro rd.driver.blacklist=nouveau nvidia-drm.modeset=0 scsi_mod.use_blk_mq=1 quiet splash logo.nologo acpi_osi=Linux "acpi_osi=!Windows 2012" acpi_backlight=vendor audit=0 rd.timeout=120

67

Just to let all know that the issue I reported has been solved with the latest kernel updates.
Currently I am running the kernel 6.3.5-desktop-3omv2390 and my system wakes up regularly from suspend mode.