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…).
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.
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?
Just wait for the kernel module to arrive in the repositories.
Ah that’s what it is. Of course!
I recommend switching to
nvidia-dkmswhich will auto rebuild the module for every kernel and lets you update them independently of each other.Perfect – this solved the issue completely for me
Does it work with modesetting, where Nvidia is the only video driver?
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…).
It’s a drop-in replacement for the
nvidiapackage. AFAIK there are zero differences in functionality. The only change is it being built locally by DKMS instead of coming pre-built.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?
I am philosophically against duplicating similar libraries, so I don’t use flatpak. Insufferable, I know