Running openSUSE 13.1 (Bottle) (x86_64) KDE Platform Version 4.14.10
Graphics: GF114 [GeForce GTX 560]
Patch update today included kernel update from standard Update-Oss repository. After rebooting the installed nVidia driver [x11-video-nvidiaG03 340.96-41.1] is no longer loaded and screen defaults to 1,024 x 768 pixels.
Progress update … and thanks for reading
This is my daily desktop and there is work to be done.
tried updating nvidia drivers to G04 version - problem persists
tried downgrading to previous kernel version - problem persists
tried uninstalling all nvidia drivers, re-booting and reinstalling - problem persists
uninstalled all nvidia drivers, reverted to nouveau - screen resolution 1920 x 1200 (normal)
so back to work …
I will stay with this until technical advice on the correct procedure is available
FWIW the installation logs for nvidia G04 drivers reported more than 40 errors like this:
[snip] make: Leaving directory `/usr/src/kernel-modules/nvidia-340.96-desktop’
WARNING: /lib/modules/3.12.53-40-desktop/weak-updates/updates/nvidia-uvm.ko needs unknown symbol nvUvmInterfaceChannelDestroy [snip]
google search on this sort of error did not clarify the issue for me
Tried that (item 3 in list above, using yast2 software management), the re-installed drivers still failed to load. The installation log showed many similar warnings as reported above. I found some pertinent comments related to these warnings on CentOS forum here but I lack skill to relate that case to openSUSE 13.1.
Well, they are compatible with Leap 42.1’s much newer 4.1.x kernel, so yes they should be.
But: you need to build the kernel module for the 3.12 kernel, 3.12 is not compatible to 3.11, a module built for 3.11 will not work.
So again, remove all nvidia packages, then boot to kernel 3.12, and then install the driver again while running on 3.12. The module is being compiled for the running kernel when you install the kmp package.
Changing the symlinks in /boot will do absolutely nothing.
Again, you need to compile the nvidia kernel module for Kernel 3.12 to be able to use it with Kernel 3.12. Re-installing it while using Kernel 3.12 will do that.
In case you wanted to know how to boot a different kernel, you can select it in “Advanced Options” in the boot menu.
And you can uninstall specific kernels in YaST via the “Versions” tab e.g.
Ahem, if your grub config points to the symlinks, like mine, this will make you boot the old kernel, of course.
I just posted this to show the old and new version numbers we are talking about…
Sorry if I confused people.
Confirming that this works, removed all G02 packages plus xf86-video-nv (not sure which ones were really required…), rebooted, reinstalled, rebooted, all fine. (and re-linked my symlinks, ahem
Many thanks!
Just a question, in many years of using SuSE this has not been required so far (at least for me).
Is this just “bad luck”, a bug, or a limitation of the Evergreen project ? (no offense meant, really, just curious).
Just a question, in many years of using SuSE this has not been required so far (at least for me).
Is this just “bad luck”, a bug, or a limitation of the Evergreen project ? (no offense meant, really, just curious).
Well, it’s the latter. The Evergreen team updated to Kernel 3.12 (the kernel used by SLES12, to not having to maintain Kernel 3.11 themselves) and ignored this.
I can also confirm that uninstall/reinstall of nvidia packages after the kernel update resolved the issuse.
Can you confirm whether, or not, there may be other modules, similarly affected, which might be less obvious than a failed graphics driver?
Most kernel modules are included in the kernel package itself, and should not have problems.
You should know yourself whether you installed 3rd party modules. The most common ones are probably VirtualBox and broadcom-wl.
The openSUSE packages of those should have been updated as well, if you installed them manually (or used Oracle’s package in the case of VirtualBox) you have to rebuild or reinstall them manually but that applies for every kernel update.
Thanks for your technical advice for Evergreen users on this issue. The recommended procedure resolved the issue for me once I manually selected the correct drivers to install - yast2 kept auto selecting the -pae driver but -desktop kernel is installed. It is also good to know why this happened.