nvidia driver broken after update to 5.12.4-1-default
Greetings: This morning I recently updated my Tumbleweed to the latest (5.12.4-1-default kernel) and when I boot into it, my resolution is stuck on 1024x768. I did some sleuthing and it looks like the Nvidia drivers are in a weird state (see below). I did some looking around and couldn't find a bug or forum entry for this so I thought I'd start here. Does anyone have any suggestions? Thank you for your help with this. {{{
nvidia-smi Failed to initialize NVML: Driver/library version mismatch }}}
Kind regards, Anthony
On Sunday, 23 May 2021 1:15:42 AM ACST Anthony Agelastos wrote:
Greetings:
This morning I recently updated my Tumbleweed to the latest (5.12.4-1-default kernel) and when I boot into it, my resolution is stuck on 1024x768. I did some sleuthing and it looks like the Nvidia drivers are in a weird state (see below). I did some looking around and couldn't find a bug or forum entry for this so I thought I'd start here. Does anyone have any suggestions? Thank you for your help with this.
{{{
nvidia-smi
Failed to initialize NVML: Driver/library version mismatch }}}
Kind regards, Anthony
My system ended up broken, too. I have always installed mine from the nvidia installer, rather than from the repos, because the drivers from the repos have always left me with a black screen. Well, after installing 5.12.4-1-default, no graphical desktop (as expected). Attempted to re-install 460.67 drivers - failed. Same with 460.80 and 465.31. All failed with the same error - compiler warnings/errors about implicit function declarations and unused variables. Nothing I did (even setting EXTRA- CFLAGS to silence those warnings) would get them to install on 5.12.4-1- default. Even after they built, all I got was a heap of "Symbol undefined" errors. So, I uninstalled them and tried the versions from the repos - no X11 at all. Removed them and tried nouveau - got a mouse cursor on a black screen. Nothing else. Eventually rebooted to 5.11.15-1-default, tried again with the nvidia installer for 465.31, and got an immediate fail due to the compiler version being different from that which compiled the kernel. Tried bypassing that by using the --no-cc-version-check and, hooray! Back in business with a fully- functional graphical desktop again. Only took 5 hours. Still can't build/install the kernel modules for 5.12.4-1-default using dkms, though - same errors occurring. Looks like we'll have to wait for another update from Nvidia. I also checked the Nvidia dev forums and could not find any clues or discussions there - maybe it's too soon. 465.31 reportedly builds OK with kernel 5.31-RC1 though, so not sure what's going on with 5.12, unless maybe its something to do with the gcc version update - maybe some warnings have now been changed to errors that cause the compilation to fail. Regards, Rodney. -- ================================================================================================================== Rodney Baker rodney.baker@iinet.net.au ==================================================================================================================
Also, I am new to openSUSE. In general, what is this community's preference for when a question is posed to the mailing list versus forums versus a bug at bugzilla? I have now used all 3 (all for different issues) and I want to make sure I'm creating things appropriately.
Hello Anthony, Am Samstag, 22. Mai 2021, 18:47:37 CEST schrieb Anthony Agelastos:
Also, I am new to openSUSE.
First of all - welcome :-)
In general, what is this community's preference for when a question is posed to the mailing list versus forums versus a bug at bugzilla? I have now used all 3 (all for different issues) and I want to make sure I'm creating things appropriately.
Well, thats mostly up to your preference. Mailings list have a certain purpose, which can mostly be derived from the name, same for forums. The discussions in there may or may not end up in a bug report - in this case someone will advise you to create a bug report HTH Axel
I was able to overcome this issue by reinstalling the Nvidia drivers with the following command. {{{ sudo zypper in --force `rpm -qa "nvidia-gfx*kmp*"` }}} Is this something I will need to do going forward or is this something that should be triggered for the next time a kernel update occurs?
Hello Anthony, Am Samstag, 22. Mai 2021, 22:46:27 CEST schrieb Anthony Agelastos:
I was able to overcome this issue by reinstalling the Nvidia drivers with the following command.
{{{ sudo zypper in --force `rpm -qa "nvidia-gfx*kmp*"` }}}
Is this something I will need to do going forward or is this something that should be triggered for the next time a kernel update occurs?
In general not, but exceptions occur (see e.g. https://bugzilla.opensuse.org/show_bug.cgi?id=1182666 describing a similar issue) To quote a statement on Nvidia: https://www.youtube.com/watch?v=i2lhwb_OckQ&t=85s I can fortunately switch off the nvidia part in the Optimus chipset of my laptop, that keeps those issues away from me Cheers Axel
participants (3)
-
Anthony Agelastos -
Axel Braun -
Rodney Baker