![](https://seccdn.libravatar.org/avatar/abdee805d4df05af9a496107100c582c.jpg?s=120&d=mm&r=g)
* Peter Maffter via openSUSE Users <users@lists.opensuse.org> [11-20-23 18:20]:
If there would be a step by step guidance how to compile the kernel module(s?) of nVidia for 390.xx for Tumbleweed, that would be enough for me.
I have the sources on my machine ( /usr/src/kernel-modules/nvidia-390.157-default ), I understand, what the patch does ( https://paste.opensuse.org/pastes/d0b21ec8d3d4 in /usr/src/kernel-modules/nvidia-390.157-default/nvidia-drm/nvidia-drm-drv.c ), it is just that my last kernel compilation was somewhere around 1999 afair and I do guess, that this process changed a lot since then for Tumbleweed.
With a little guidance I can help myself (at least I think so ;-) ).
BR
Am 20/11/2023 um 20:34 schrieb David C. Rankin via openSUSE Users:
On 11/20/23 04:55, Peter Maffter via openSUSE Users wrote:
Does this mean, I have to patch every time I do an update of Tumbleweed x.y to x.(y+1) or (x+1).0 ? :-(
Is there a step by step guidance for Tumbleweed, I never did this for nVidia (I had to patch other sources a long time ago so I understand the principle, but kicking of a complete build of /usr/src/kernel-modules/nvidia-390.157-default is new to me).
Generally with openSUSE, there will be an updated Nvidia driver released. But you have run into one of the drawbacks of a rolling-release when the kernel version changes. The Nvidia-390xx driver will break on just about every kernel version update (e.g. 6.3->6.4, 6.4->6.5, and 6.5->6.6, etc...) It takes time to test and put out an updated version of the driver package.
The downside to the 390xx driver is it is no longer actively developed (only maintained). So it is up to the distribution to patch the kernel module files to accommodate whatever changes affect it when a new kernel is released.
If you can get ahold of the source file for the nvidia-390xx-utils package that does the dkms setup for build of the nvidia kernel modules, then it is simple to edit the .spec file and include the patch I linked to.
With Arch, the 390xx driver is user-maintained, so I know to get a patch ready when a new kernel is imminent. A little effort up-front makes for a seamless kernel update and successful build of new drivers when the new kernel appears.
I don't use tumbleweed yet (one rolling-release at a time has been enough...), but you are in the same boat with the 390xx driver. The nvidia-utils package will need to be patched to build the new driver (or there was a manual build of the driver you can use, others will have to chime in there, I don't use it, I think Patrick has the link .. if I recall correctly..., should be a simple search to find it)
Whether you want to try patching yourself, or wait for openSUSE to provide an update, this is where rolling-releases have a chicken-or-the-egg issue. Ideally, there would be someone to looks into this and have an updated package for Tumbleweed ready when then new kernel update hits the tumbleweed repos -- but there is limited manpower to put toward non-distro proprietary driver support (even though we all know there will be many people caught by surprise if that work isn't done)
At least with openSUSE, there will be an update coming -- it's just a matter of when.
just patch the NV*.run files and install it. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc