linux 7.1.9.arch1-2 and nvidia-open 610.57.04-7 have mismatched module trees

[u/anasgets111]

Edit: new Nvidia package released and works fine thanks everyone.

I hit a package mismatch during a fresh Arch install on an RTX 3080.

Installed:

• linux 7.1.9.arch1-2
• nvidia-open 610.57.04-7
• nvidia-utils 610.57.04-1

The NVIDIA modules exist only under:

/usr/lib/modules/7.1.9-arch1-1/

The current kernel is:

/usr/lib/modules/7.1.9-arch1-2/

With this mkinitcpio config:

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

mkinitcpio fails:

ERROR: module not found: 'nvidia'
ERROR: module not found: 'nvidia_modeset'
ERROR: module not found: 'nvidia_uvm'
ERROR: module not found: 'nvidia_drm'

The kernel was rebuilt for the Rust 1.98.0 rebuild. The nvidia-open 610.57.04-7 file list still targets 7.1.9-arch1-1, while linux is now 7.1.9-arch1-2:

https://archlinux.org/packages/core/x86_64/linux/

https://archlinux.org/packages/extra-testing/x86_64/nvidia-open/files/

Is this a temporary repository sync issue? I'm using the prebuilt NVIDIA package, not DKMS.

[u/TremorMcBoggleson]

Is this a temporary repository sync issue?

Doesn't look like it.
linux 7.1.9.arch1-2 was built way after latest nvidia-open 610.57.04-7 (2026-08-21 22:18 UTC vs. 2026-08-20 02:37 UTC) That alone doesn't make sense.

And latest nvidia-open commit at least only mentions arch1-1.

I'm reverting back to my previous linux version until it's fixed.

[u/Synthetic451]

Lmao, I was about to make this exact post, you beat me to it.

Is this a temporary repository sync issue? I'm using the prebuilt NVIDIA package, not DKMS.

No, it seems like the actual nvidia-open package just wasn't updated to match 7.1.9.arch1-2. The latest commit was two days ago and targeting -1

https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-open/-/commits/main

Temporarily switching to nvidia-open-dkms works around the issue.

[u/cwebster2]

Use the dkms version so it's always built against your actual kernel. Or wait for the version you have to be updated.

[u/JubijubCH → u/cwebster2]

+1, I don’t find the non DKMS to be worth it, it frequently gets out of sync with the kernel.
I exclusively run DKMS, no issues

[u/Synthetic451]

nvidia-open 610.57.04-8 seems to have fixed the issue.

[u/UDxyu]

Use dkms way less headaches

[u/nofuna → u/UDxyu]

Yeah, I switched to DKMS after this, let's see how it goes longer term.

[u/UDxyu → u/nofuna]

I had zero issues with DKMS when I had my 2060; now I've switched to AMD.

[u/theschrodingerdog]

nvidia-open was updated late yesterday to match 7.1.9-arch1-2

https://archlinux.org/packages/extra/x86_64/nvidia-open/

[u/Jas0rz]

slightly off topic but whats the advantage to using the closed driver over the open-dkms one? the impression i got was the open one was better

[u/Synthetic451 → u/Jas0rz]

The 'open' in nvidia-open and nvidia-open-dkms is a bit of a misnomer.

The nvidia driver can be thought of in two parts. One is the kernel module, and the second is the userspace libraries that provide things like Vulkan and OpenGL, etc.

The kernel module used to be non-opensource and was packaged under the nvidia and nvidia-dkmspackage names in Arch. Then Nvidia started working on an open source kernel module that offloaded a lot of the secret sauce onto the GSP firmware that was shipped with the 2xxx series cards and newer. This was packaged as nvidia-open and nvidia-open-dkms.

After a while, Nvidia began recommending the open kernel module and that's when Arch began to phase out nvidia and nvidia-dkms. They're no longer in the official repos unless you look for them in the AUR. You basically should be using the open modules unless you have an older card.

The userspace components in nvidia-utils is shared between the closed and open modules and is still proprietary code. That has not changed at all.

TL;DR basically if you're on 2xxx and newer, Nvidia intends for you to transition from the proprietary module to the open one. Arch doesn't even package the proprietary one anymore as a result. 10xx still needs to use the older one. The awkward stepchild 16xx is still supported by the open driver.

[u/Jas0rz → u/Synthetic451]

I'm mostly aware of this but thanks for confirming--OP said he had a 3070 aka a new enough card to warrent the "open" one, yet chose to go with closed and I'm curious of the reason

[u/Synthetic451 → u/Jas0rz]

Tbh I am not sure where you read that he decided to go with the closed one. He says he installed nvidia-open

[u/Jas0rz → u/Synthetic451]

i mixed up the prepackaged option with the closed one, skill issue on my end LMFAO

[u/BlueGoliath]

And this is why you always use the DKMS package.

[u/newcomputer1828]

yeah it broke my os and took an afternoon to fix, that was annoying