Hi Michael, Andrei
thanks for your swift responses!
One correction: I mentioned the wrong kernel version - its 5.11.15 for build
20210425.
Michael - I've tried your suggestion but it failed complaining about a - in my words - "mismatch" with nvidia-gfxG05-kmp-default-460.73.01_k5.11.11_1-37.1.x86_64.rpm
(The file I've tee'd the output to got overwritten so regrettably I can't provide more details, grmbl)
The kernel-source for 5.11.15 is present.
Your comment and also Andrei's point stating the nvidia modules are compiled on the machine made me try to update to the latest available build 20210429 which employs kernel 5.12.0.
(Not knowing much about the "nvidia issue" I assumed nvidia are trying to keep
some stuff from others looking into, thus forcing download of some pre-complied objects rather than to compile in situ)
After the change to 5.12.0 all is fine again - I'm writing this mail on the system.
One observation:
I was following the update closely (which I usually don't do ;-)) and was concerned when I saw:
------------------------------------------------------------------------------------------------------------
.......BTF [M] /usr/src/kernel-modules/nvidia-460.73.01-default/nvidia.ko
Skipping BTF generation for /usr/src/kernel-modules/nvidia-460.73.01-default/
nvidia.ko due to unavailability of vmlinux
make[2]: Verzeichnis „/usr/src/linux-5.12.0-1-obj/x86_64/default“ wird verlassen
make[1]: Leaving directory '/usr/src/linux-5.12.0-1'
ld -r -o nv-linux.o \
nvidia.mod.o nvidia/nv-interface.o
ld: cannot find nvidia/nv-interface.o: No such file or directory
make: *** [Makefile:113: nv-linux.o] Error 1
/
depmod: WARNING: could not open modules.order at /lib/modules/5.12.0-1-default:
No such file or directory
depmod: WARNING: could not open modules.builtin at /lib/modules/5.12.0-1-
default: No such file or directory
Modprobe blacklist files have been created at /etc/modprobe.d to prevent Nouveau
from loading. This can be reverted by deleting /etc/modprobe.d/nvidia-*.conf.
*** Reboot your computer and verify that the NVIDIA graphics driver can be loaded.
***
grep: /etc/sysconfig/kernel: No such file or directory
warning: %triggerin(nvidia-gfxG05-kmp-default-460.73.01_k5.11.11_1-37.1.x86_64)
scriptlet failed, exit status 1
........
---------------------------------------------------------------------------------------------------------------
Any idea whether this could turn into something serious or can it be ignored?
br
Juergen
Am Sonntag, 2. Mai 2021, 07:13:02 CEST schrieb Andrei Borzenkov:
> On 02.05.2021 04:32, Michael Hamilton wrote:
> > On Sunday 02 May 2021, Mailings wrote:
> >> Hi
> >>
> >> updated Tumbleweed a few days ago to build 20210425.
> >>
> >> Reboot ended in a command prompt rather than firing up KDE.
> >> Using Kernel 5.11.4 made it work again.
> >>
> >> Spent some time today in figuring out what the problem is and it seems
> >> the nVidia repository is out of sync - the kernel used there is still at
> >> 5.11.11 rather than 5.11.16.
> >>
> >> br
> >>
> >> Juergen
> >
> > I'm currently typing this from TW 20210427 running 5.11.16-1-default along
> > with the nvidia proprietary 460.73 driver (installed by the "easy"
> > method).
> >
> > If you are also on the 460 driver, my guess would be that your system's
> > nvidia kernel module has not been rebuilt for 5.11.16. The module is
> > normally automatically rebuilt as part of the TW zypper dup, but this
> > sometimes doesn't happen. This has happened to me a few times recently,
> > in these cases I found that a forced reinstall of the driver's kernel
> > module>
> > followed by a reboot usually fixes the issue:
> > % zypper in -f nvidia-gfxG05-kmp-default
> >
> > % reboot
> >
> > I've not tracked down exactly why sometimes fails, perhaps it is some
> > chicken and egg circumstance. I did notice on one occasion I seemed
> > to be missing a kernel-source install for my current kernel - but I'm not
> > clear on whether this was the cause of the issue.
>
> No, it was not (and if it was, it is a bug by itself).