This message might be premature, but my impression from reading a couple of messages in the opensuse-factory mailing list is that I may have to patch the 5.9 kernel to use it with the nvidia driver:
I installed nvidia ‘the hard way’ on a desktop and laptop. When a new kernel arrives, I reboot to terminal after zypper dup, run sh nvidia.run* to install the driver, mkinitrd and reboot. Quick and easy.
It wouldn’t be hard to add the extra step of applying a patch before running *sh nvidia.run … but I don’t know if I can patch a kernel that way to fix this problem, or even which of the installed kernel files would take the patch. Excluding kernel-firmware files, zypper se -si 'kernel’ says that I have installed:
Any thoughts will be appreciated. If I’d have to patch the source and compile, I’d likely look unhappily at a change to Leap.
I also see from http://rglinuxtech.com/?p=2841 that I could run the installer on an unpatched kernel with the -no-unified-memory option, but this would eliminate CUDA, and I don’t know how this would affect my system otherwise.
Hi
I would just wait it out until 5.9.1 arrives, by then I’m sure there will be plenty of options…
I install the hard way (nvidia, cuda and cudnn). If push comes to shove, just lock the relevant files and kernel. AFAIK uvm has been disabled anyway on the rpm builds?
Just a warning to casual readers: this might be a useful hack for a local install, but distributing the resulting code might not be legal.
I’m not a lawyer, so I cannot elaborate further.
It would seem that adding “Portions copyright by NVIDIA disassembly of NVIDIA code not allowed” to the boot up would solve that problem.
I know that NCR’s MP-RAS had multiple copyright notices in boot up as do HP’s HPUX and IBM’s AIX.
Read an article recently (forgot where published)
ETA on nVidia resolving their patch and licenses based on their information from nVidia was sometime second half November.
Of course, there’s no way to know how accurate that might be, but the impression was that was some kind of info directly from nVidia developers tasked with the problem.