Arch Linux

rek2

Member

Registered: 2015-02-12

Posts: 44

[SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

[I read a similar post to this before posting but is related only to open drivers not propietary]
Hello 2 weeks a go I did the upgrade and broke my system, so I reverted to "560.35.03-4" and kernel "linux-6.11.3.arch1-1 since then I have been trying every minor release like 560.35.03-5 560.35.03-6 560.35.03-10(latest one on testing) etc. all the same, it boots and gets stuck right after systemd-udevd (something like this)
and there is no way, I go into edit mode and remove nvidia_drm.modeset=1 and no luck I have tried combinations of older kernels with newer drivers, no luck. Anyway, with the same problem? Any idea? a workaround?
my setup:
I am using the dkms driver
systemd-boot
wayland
sway
NVIDIA GTC1080ti (is why I need to still use proprietary drivers )

Thank you

Last edited by rek2 (2024-10-14 17:17:40)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,333

Re: [SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

You can't just mix and match nvidia packages and kernels like that. You're using a binary module, it must match the kernel exactly. If you want to mix and match, you need to use the dkms version.

rek2

Member

Registered: 2015-02-12

Posts: 44

Re: [SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

You can't just mix and match nvidia packages and kernels like that. You're using a binary module, it must match the kernel exactly. If you want to mix and match, you need to use the dkms version.

My bad I did not add that part, I am using dkms and even if I did not I know how to downgrade been using linux since 1995 if I am asking here is because I have really tried most things, fair to say systemd is new, so I am not as experienced as I was with initd.
Updated the og post to say I am using DKMS

Last edited by rek2 (2024-10-14 16:49:47)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,333

Re: [SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

OK, so pkgrel 4 works and 5 doesn't. The change there was https://gitlab.archlinux.org/archlinux/ … 2115ec3e22, so disabling fbdev will probably fix it.

rek2

Member

Registered: 2015-02-12

Posts: 44

Re: [SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

OK, so pkgrel 4 works and 5 doesn't. The change there was https://gitlab.archlinux.org/archlinux/ … 2115ec3e22, so disabling fbdev will probably fix it.

This will be great, but if is at boot I do not have it, only `nvidia_drm.modeset=1`
you mean to disable it also somewhere else?
On my mkinitcpio.conf I have
```
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
```
HOOKS on same file:
```
HOOKS=(base udev autodetect modconf block keymap filesystems keyboard encrypt fsck consolefont)
```
May as well paste it since is where boot breaks

Last edited by rek2 (2024-10-14 16:58:55)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,333

Re: [SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

As the link says, nvidia_drm.modeset=1 is now default, so you don't need it. Unfortunately nvidia_drm.fbdev=1 is also default and is experimental and needs to be turned off (set to 0) in some cases.

rek2

Member

Registered: 2015-02-12

Posts: 44

Re: [SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

Awesome! that did the trick, weird do because I did removed the entry at boot with edit but doing it this way with nvidia_drm.fbdev=0 got me to boot.
this is how I ended up configuring for anyone else that have missing the git changelog like I did.
```
options <device info etc etc>   root=/dev/mapper/luksdev zswap.enabled=0 rw intel_pstate=no_hwp rootfstype=ext4 nvidia_drm.fbdev=0
```
Now that at least I booted I can fix some other issue I have now with greetd I had to ctrl+alt+f2 and login that way instead but this is something I can fix.

Thank you!

Last edited by rek2 (2024-10-14 17:18:26)

rek2

Member

Registered: 2015-02-12

Posts: 44

Re: [SOLVED][nvidia propietary driver] upgradin from 560.35.03-4 to ...

I wanted to add in case someone else have this issue, I ended up adding again the nvidia_drm.modeset=1 and also nvidia_drm.fbdev=0  if I remove modeset=1 from boot then vulkan does not work on sway, and vulkaninfo gives errors, when I added it back all works perfectly so the issue here is fbdev=1  that needs  to be changed to fbdev=0 since it got enable by default I had to disable it when before I did not even had it.
Hope this helps someone else.