In the latest update 20251210 I noticed zypper installed nvidia-open-driver-G07-signed-kmp-default
I have never used any repository for Nvidia drivers or installed one
My card is too old (750ti) for open drivers
G07 (590 driver) doesn’t support my legacy card (Maxwell chip)
I install the hard way from the .run file
Did anyone else notice this? I don’t see any bugreports on it. If not I guess I’ll just call it a glitch in the matrix and see if it happens on the next update.
Good news: Nvidia has a new run file out in the 580 series
NVIDIA-Linux-x86_64-580.119.02.run … XFCE taskbar panel didn’t like it (or the DUP) but that’s a whole nother can-o-bugs … KDE-X11 is working fine
Same problem here with the same card. But I had installed via Nvidia repo and zypper.
And because I had blacklisted nouveau, I ended up with neither Nvidia nor nouveau loading…
Well it seems like that rpm thinks it’s very important … would be nice to know if both G06 and G07 are installed or G06 was replaced … bedtime for me … I’ll check bug reports in the morning
Looks like there is no nvidia-open-driver-G07-signed-kmp-metawhich should filter the supported chips, like you would see for the proprietary driver for your card:
LT-B:~ # zypper info --supplements nvidia-driver-G06-kmp-meta | grep pci:v000010DEd00001380
(kernel-default and namespace:modalias(pci:v000010DEd00001380sv*sd*bc03sc0[02]i00*))
(kernel-longterm and namespace:modalias(pci:v000010DEd00001380sv*sd*bc03sc0[02]i00*))
LT-B:~ #
Created a useraccount at OpenSUSE bugzilla and they said they sent an email to verify but I don’t see it in the inbox or spam folders Guess I’ll just wait a little while and try to verify again if I don’t see it … Meanwhile I did see another similar bug here:
I simply uninstalled G07 immediately after the DUP before I even rebooted and then installed Nvidia drivers “the hard way” like usual … working fine but I’m more concerned with people who use the repository drivers and are wondering why their machine has a blank screen
You can get in with the same username and password used on the Forums, no need for another account. Anyway Stefan Dirsch knows about the problem and a fix is underway apparently.
Passing by . . . hit this problem probably back at the beginning of the year on my '12 Mac Pro with Nvidia 680??? (aging memory) . . . where the G07 did not “support” my card, and simultaneously it “blacklisted nouveau” . . . had to lock the G06 package in YaSt to keep it from reinstalling the G07 . . . and find the file that contained the two word script “blacklist nouveau” and trash it.
lsmod would show what modules are being used in video . . . . I preferred nouveau because of the problems that showed up running proprietary . . . like “not resuming from suspend” . . . . hours and hours went into dealing with the care and feeding of the Nvidia card. Finally went for a homebuilt in June . . . Ryzen cpu with onboard graphics . . . not as “crispy” rendering as with the Nvidia card, but so far, no headaches for a daily driver . . . .
Can’t say that I’ve ever had that problem(s) but at any rate zypper attempting to install GO7 apparently has been sorted out because it hasn’t happened since … I’m calling this fixed … thanks to Stefan, maintainers and anyone else involved
I need to understand what happened exactly I haven’t done that yet.
Guess I’ll just wait a little while and try to verify again if I don’t see it … Meanwhile I did see another similar bug here:
Hopefully it’ll get sorted soon