this post was submitted on 04 Nov 2023
57 points (98.3% liked)

Arch Linux

8539 readers
93 users here now

The beloved lightweight distro

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 2 years ago (1 children)

Ah that's what it is. Of course!

[–] [email protected] 18 points 2 years ago* (last edited 2 years ago) (3 children)

I recommend switching to nvidia-dkms which will auto rebuild the module for every kernel and lets you update them independently of each other.

[–] [email protected] 4 points 2 years ago (2 children)

Does it work with modesetting, where Nvidia is the only video driver?

[–] [email protected] 8 points 2 years ago

It's a drop-in replacement for the nvidia package. AFAIK there are zero differences in functionality. The only change is it being built locally by DKMS instead of coming pre-built.

[–] [email protected] 1 points 2 years ago

It builds the kernel module for your specific kernel. It's not different from the nvidia package, that's just the same thing pre-build for the default kernel (in fact if you install both nvidia-dkms will build the module locally, then realize the exact same thing it just build is already there and move on...).

[–] [email protected] 2 points 2 years ago

Perfect -- this solved the issue completely for me

sudo pacman -Sy linux-lts nvidia-dkms
## removes nvidia
[–] fhoekstra 1 points 2 years ago (1 children)

I know my Pop!_OS install pulls Nvidia drivers and modules using flatpak. I don't know the pros and cons of this method, but I've assumed it's more robust due to decoupling of dependencies.

What is your opinion on flatpak vs pacman for proprietary Nvidia drivers?

[–] [email protected] 4 points 2 years ago

I am philosophically against duplicating similar libraries, so I don't use flatpak. Insufferable, I know