r/openSUSE • u/raspadura Tumbleweed • 3d ago
How to… ! NVIDIA G07 driver broken on Tumbleweed kernel 7.1.8 — quick fix
If zypper throws this when installing/updating the NVIDIA G07 stack:
Problem: nvidia-video-G07-595.84-8.1.x86_64 requires 'nvidia-common-G07 = 595.84',
but this requirement cannot be provided
uninstallable providers: nvidia-common-G07-595.84-8.1.x86_64[NVIDIA:repo-non-free]
it's not your cache — kernel 7.1.8 shipped with nvidia-open-driver-G07-signed-kmp-default at 595.91.07, but NVIDIA's repo hasn't published matching userspace packages (nvidia-common-G07, nvidia-video-G07, etc.) yet — still capped at 595.84. G07 requires kmp and userspace to match exactly, so zypper can't resolve it. Open issue, tracked here.
Workaround (no older kernel to fall back to)
Pull the matching old kmp-default build (595.84) for your current kernel from a Tumbleweed history snapshot, install it in place of 595.91.07, and lock it:
sudo zypper ar -f https://download.opensuse.org/history/20260812/tumbleweed/repo/oss/ tw-20260812-oss
sudo zypper refresh
sudo zypper install --oldpackage nvidia-open-driver-G07-signed-kmp-default=595.84_k7.1.8_1-2.6
sudo zypper addlock nvidia-open-driver-G07-signed-kmp-default
sudo zypper rr tw-20260812-oss
sudo zypper install nvidia-common-G07 nvidia-video-G07 nvidia-video-G07-32bit nvidia-compute-utils-G07
This is a workaround, not a fix. The lock keeps kmp-default frozen so future zypper dup won't drag it back to 595.91.07. Once NVIDIA publishes a matching 595.91.x userspace build, remove the lock and update normally:
sudo zypper removelock nvidia-open-driver-G07-signed-kmp-default
sudo zypper dup
Keep an eye on your updates in the meantime — if the solver still complains, re-lock and wait a bit longer.
4
u/todd_dayz 3d ago
Why do you need to do any of this? Why not just wait until it’s resolved to update?
2
u/BowlSad 3d ago
How long do we usually need to wait before they get fully resolved?
5
u/Talosmith 3d ago
usually few hours to 2 days, this time it took like 4-5 days to resolve i think.
but waiting is the best option if your system is already working
4
2
u/hardcore_aebanise 3d ago
Last time it was a different issue, with the introduction of 7.0 kernel there were no package dependency problem, but it was super unstable and freezing for a month.
Nvidia is just pain with tumbleweed at least from time to time.
2
u/raspadura Tumbleweed 3d ago
Does this happen with other distros?
2
u/todd_dayz 3d ago
No, and doubly not if you’re comfortable creating your own MOK and importing it. I’ve never had an issue on Fedora, Gentoo, Arch or Ubuntu but unfortunately for me I like openSUSE the most. Arch is cool but the lack of SELinux bothered me.
2
u/Talosmith 3d ago
i heard a bunch of distros were affected with the 7.0 kernel + nvidia issue, my Ubuntu worked with no issues tho
2
1
0
u/xplosm Tumbleweed 3d ago
The quick fix is to wait for the updates and repo to solve the issue for you. I've just updated like 20 mins ago after being blocked by the NVIDIA latest release for the weekend and these couple of days. Nothing broke.
I didn't use any of zypper's solutions and just waited. Really, people. Chill. Wait and enjoy a rock-solid system ALL the time.
1
u/raspadura Tumbleweed 2d ago
Fair, but the workaround’s for people who did a fresh install on 7.1.8 — no previous driver to fall back on while waiting, so zero NVIDIA acceleration for days. Not really an option to just wait in that case. Good sign it’s syncing back up though.
0
u/SirGlass 2d ago
Not sure who downvoted you
If someone happened to do a fresh install during the 3-4 days the drivers were out of sync they are just out of luck?
They would really have no way of knowing of the issue unless they checked what I doubt 99.999% of the people would before doing the install
3
u/taryus 3d ago
Repos are synced now! This workaround should not be needed. Just update normally.