
As I wrote elsewhere in this thread, after further investigation, I think my problem is actually this: https://forums.opensuse.org/showthread.php/543847-nvidia-gpu-i2c-timeout-err... So now I need to see when the patch that is mentioned gets in the Tumbleweed kernel. On Mon, Aug 9, 2021 at 10:25 PM Michael Hamilton <michael@actrix.gen.nz> wrote:
I'm using GeForce GTX 1650 SUPER (on AMD FX-6300 ASUS M5A97 EVO).
When I've had problems in the past, sometimes a forced reinstall of the module or the entire set of nvidia installables sorted things out. From my admin notes:
- Nvidia - in the event the kernel module needs a manual rebuild: - run zypper in -f nvidia-gfxG05-kmp-default - if that's not enough force a reinstall of all nvidia repo packages zypper --no-refresh se --installed-only -r NVIDIA | awk '$1 == "i+" { print $3 }' | xargs zypper in --force where NVIDIA is the name of the nvidia repo, should result in something like: zypper in --force nvidia-computeG05 nvidia-gfxG05-kmp-default nvidia-glG05 x11-video-nvidiaG05
(There's probably a simpler way to do this.)
The last time I had any issues it was due to the usr merge. See
https://en.opensuse.org/openSUSE:Usr_merge
I still have the workaround link noted at the above page in place:
cd /usr; ln -s . /usr/usr
But I don't think the workaround should be necessary anymore.
Michael
On Tuesday 10 August 2021, Roger Oberholtzer wrote:
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