[SOLVED] nvidia GPU and gnome on wayland

wilcomir · 2024-08-15 16:15:37

Hello,

I just did a fresh arch install on my system today. I have an RTX 4080, after I installed the whole system, including gnome, everything was working fine.

I followed the instructions here to install the proprietary drivers, but after several trials, whenever I try "systemctl start gdm.service", I am simply stuck at a blinking cursor. I get a warning from zsh, as it tells me "1 job SIGHUPPED". While that happens, I can still switch to a different tty, but after a while the cursor stops blinking and the only thing I can do is physically reboot the machine.

I have tried several steps of the various pages of the wiki, to no avail.

currently the status is as follows:

#mkinitcpio.conf
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
...
HOOKS=(... removed kms from here...)[\code]

#/boot/loader/entries/arch.conf
...
options ... nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nomodeset module_blacklist=nouveau

lspci -k
...
VGA compatible controller: ...
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia

I am unable to find anything interesting inside dmesg or the journal. It does complain about the tainted kernel because I am loading an out of tree module, but I believe that to be expected.

At this point I am at a loss, as I do not know how to further debug this problem. It is also very probable that I forgot some silly step here or there, but it does not look like it...

As a side note: is there any way to copy stuff like log files and the like from my system to elsewhere? i copied manually what is above, but certainly there are other ways

Thanks to anyone who might respond!

Solution:
I had to disable a udev rule as described here.

Cheers,
V

Last edited by wilcomir (2024-08-15 21:07:24)

V1del · 2024-08-15 18:44:39

Get rid of nomodeset, you're basically undoing the modeset you're setting up again. module_blacklist=nouveau is also unnecessary the nvidia-utils package blacklists that already.

And for GDM in particular, see the checks it tries to do https://wiki.archlinux.org/title/GDM#Wa … DIA_driver and either set all of that up or disable the udev rule.

wilcomir · 2024-08-15 19:39:03

Hello V1del,

thanks for your help.

I fixed my kernel parameters removing nomodeset and blacklist_module=nouveau, as you suggested.

Regarding the link you have sent, the first portion - let's say the three steps - I have already done. I tried to override the udev rule, but it lead to some odd behavior - moreover I have installed gdm 46.2-2 and nvidia 555.58.02-15 - basically the latest versions at the time of writing - therefore the udev rule thing should not apply to my case, as it seems to me it applies for older versions of the packages.

Let me also add that my processor is an intel K variant - so there is no integrated graphics therefore I cannot disable it, as the link subsequently suggests.

Thanks,
V

seth · 2024-08-15 19:58:34

I tried to override the udev rule, but it lead to some odd behavior

And what /is/ "odd behavior"?

therefore the udev rule thing should not apply to my case

Yes "should" … in reality the entire thing is so fragile that you'll better apply all mentioned steps.
Then please post your complete system journal for the boot:

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

wilcomir · 2024-08-15 20:39:36

Ok I tried the symlink again and it effing worked.

I swear the only thing that I changed is that I have added a few environment variables inside /etc/environment

I had what I found on the wiki:

GBM_BACKEND=nvidia-drm
__GLX_VENDOR_LIBRARY_NAME=nvidia

but from some random site linked in a thread similar to this one link I found also these additional variables:

ENABLE_VKBASALT=1
LIBVA_DRIVER_NAME=nvidia
WLR_NO_HARDWARE_CURSORS=1
QT_QPA_PLATFORMTHEME="wayland;xcb"

Can any of that have actually made a difference?

At any rate, for the record, the odd behavior I experienced is some serious delay in switching between tty1 and tty2 - it happened only that time. At this point, I can accept I imagined that. So weird.

seth · 2024-08-15 20:42:15

nvidia is/can be notoriously slow at switching framebuffers, you probably did not hallucinate that.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

And I hope you watched the shouldland video and learned something important from it

wilcomir · 2024-08-15 21:05:37

Thanks Seth - I did watch it.

marking as solved, you guys are legends.

Arch Linux

#1 2024-08-15 16:15:37

[SOLVED] nvidia GPU and gnome on wayland

#2 2024-08-15 18:44:39

Re: [SOLVED] nvidia GPU and gnome on wayland

#3 2024-08-15 19:39:03

Re: [SOLVED] nvidia GPU and gnome on wayland

#4 2024-08-15 19:58:34

Re: [SOLVED] nvidia GPU and gnome on wayland

#5 2024-08-15 20:39:36

Re: [SOLVED] nvidia GPU and gnome on wayland

#6 2024-08-15 20:42:15

Re: [SOLVED] nvidia GPU and gnome on wayland

#7 2024-08-15 21:05:37

Re: [SOLVED] nvidia GPU and gnome on wayland

Board footer