
How odd. With this combination I cannot get X to start, But with 5.12.3 for kernel and NVIDIA all is okay. This is the last working combo. modinfo nvidia filename: /lib/modules/5.12.3-1-default/updates/nvidia.ko uname -a Linux acme 5.12.3-1-default #1 SMP Wed May 12 09:01:49 UTC 2021 (25d4ec7) x86_64 x86_64 x86_64 GNU/Linux I'm using the gfxG05 driver for an NVIDIA GeForce GTX 1660 SUPER On Mon, Aug 9, 2021 at 12:30 PM Michael Hamilton <michael@actrix.gen.nz> wrote:
On Monday 09 August 2021, Roger Oberholtzer wrote:
I have been wanting to update my Tumbleweed system. However, when I last tried to do so a week or so ago the NVIDIA kernel driver was out of wack.
I see that the current Tumbleweed kernel is 5.13.4, while the current NVIDIA kernel module is 5.13.2. So I guess things are not quite working again yet. Right?
I have been trying to stay with the RPM NVIDIA stuff instead of installing the .run file. Generally that makes life easier...
The main reason I want to update now is that I went to install Virtual Box. And it is available for 5.13.4, which makes sense.
I've using the nvidia "easy way" driver, I normally have no problems with minor kernel updates, and everything is working at the moment:
nvidia-gfxG05-kmp-default-470.57.02_k5.13.2_1-43.1.x86_64 kernel-default-devel-5.13.6-1.2.x86_64
(I do see recent infrequent X11 hangs with chrome-beta with GPU acceleration enabled, but that also happened with previous kernels. I've emailed nvidia; I've disabled that chrome-beta option.)
Major kernel version bumps can sometimes cause an issue, but not always. I often rely on /etc/zypp/zypp.conf multiversion.kernels to dig me out of any surprises there (even going so far as keeping specific extra kernels around as a fallback).
Michael
-- Roger Oberholtzer