Same procedure as every year. Was updating to 20240321-0 today with kernel-default-6.8.1-1.1 ( 6.7.9-1-default before that had a working NVIDIA-Linux-x86_64-390.157 ) Compilation of nVidia modules fails. /usr/src/kernel-modules/nvidia-390.157-default/nvidia-drm/nvidia-drm-drv.c:661:23: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 661 | DRM_UNLOCKED), | ^~~~~~~~~~~~ /usr/src/linux-6.8.1-1/include/drm/drm_ioctl.h:155:26: note: in definition of macro ‘DRM_IOCTL_DEF_DRV’ No graphics after reboot. :-( Was able to reboot to 6.7.9-1-default with nVidia driver working. nvidia-drm-drv.c : line 661: static const struct drm_ioctl_desc nv_drm_ioctls[] = { #if defined(NV_DRM_ATOMIC_MODESET_AVAILABLE) DRM_IOCTL_DEF_DRV(NVIDIA_GEM_IMPORT_NVKMS_MEMORY, nv_drm_gem_import_nvkms_memory_ioctl, DRM_UNLOCKED), <------------------------------! #endif /* NV_DRM_ATOMIC_MODESET_AVAILABLE */ Someone has dropped DRM_UNLOCKED from drm_ioctl.h : diff /usr/src/linux-6.8.1-1/include/drm/drm_ioctl.h /usr/src/linux-6.7.9-1/include/drm/drm_ioctl.h 112a113,123
* @DRM_UNLOCKED: * * Whether &drm_ioctl_desc.func should be called with the DRM BKL held * or not. Enforced as the default for all modern drivers, hence there * should never be a need to set this flag. * * Do not use anywhere else than for the VBLANK_WAIT IOCTL, which is the * only legacy IOCTL which needs this. */ DRM_UNLOCKED = BIT(4), /**
So obviously nobody tested this before releasing 20240321-0 . Why was DRM_UNLOCKED dropped? Is it possible to ad DRM_UNLOCKED to /usr/src/linux-6.8.1-1/include/drm/drm_ioctl.h ? Any known side effects? How can I compile the nVidia driver (I did compile other software but never the nVidia kernel drivers)? Thanks in advance BR Pete Am 05/03/2023 um 23:32 schrieb Peter Maffter:
System was working till todays zypper dup.
Now again: no graphic system with kernel-default-6.2.1-1.1 .
zypper update nvidia-gfxG04-kmp of course does not help.
This time at least the old system with 6.1.12-1-default is working so that I can write this email and on the 20230304-0 system I could try to compile the NVIDIA-Linux-x86_64-390.157.run But I do remember that this does not help.
I read: "create /etc/ld.so.conf.d/nvidia and include /usr/lib/tls" Was this the solution to this problem?
I am quite a nope here: does "include" mean write something to /etc/ld.so.conf.d/nvidia ?
Currently on 20230227-0 there is: find /usr -name "libnvidia-tls.so.390.157" -ls [...]14480 Feb 14 12:29 /usr/lib64/libnvidia-tls.so.390.157 [...]13752 Feb 14 12:29 /usr/lib/libnvidia-tls.so.390.157 which seems to be the old one from here: https://download.nvidia.com/opensuse/tumbleweed/x86_64/
Thx in advance Pete
Am 13/02/2023 um 21:49 schrieb Peter Maffter:
Hello,
after the update the screen only shows a '-'. All the usual other tty screens that you get with e.g. STRG-ALT-F1 are also gone.
I can connect to the PC via ssh from my Ubuntu Laptop and check what is going on.
I am using an old GTX 570 on that PC.
Previously when the G06 stuff was installed instead of updating the needed G04 stuff, I was able to install NVIDIA-Linux-x86_64-390.157.run manually and the login and XFCE worked.
But now even that fails. :-(
Any pointers? Is that the beginning of the things that are named in Subject "Nvidia 390x driver users - glibc 2.37 will bring bad news" ?
I do have strange output about signature and verification: 2023-02-13T00:08:13.628957+01:00 machine4 kernel: [ 3.411047][ T527] nvidia: loading out-of-tree module taints kernel. 2023-02-13T00:08:13.628957+01:00 machine4 kernel: [ 3.411690][ T527] nvidia: module license 'NVIDIA' taints kernel. 2023-02-13T00:08:13.628958+01:00 machine4 kernel: [ 3.412304][ T527] Disabling lock debugging due to kernel taint 2023-02-13T00:08:13.628958+01:00 machine4 kernel: [ 3.418769][ T527] nvidia: module verification failed: signature and/or required key missing - tainting kernel 2023-02-13T00:08:13.628963+01:00 machine4 kernel: [ 3.426827][ T538] tg3 0000:0d:00.0 eth0: Tigon3 [partno(BCM57781) rev 57785100] (PCI Express) MAC address 00:25:22:e6:5d:d3 2023-02-13T00:08:13.628964+01:00 machine4 kernel: [ 3.427483][ T538] tg3 0000:0d:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) 2023-02-13T00:08:13.628964+01:00 machine4 kernel: [ 3.428122][ T538] tg3 0000:0d:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] 2023-02-13T00:08:13.628965+01:00 machine4 kernel: [ 3.428740][ T538] tg3 0000:0d:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] 2023-02-13T00:08:13.628965+01:00 machine4 kernel: [ 3.482616][ T527] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 2023-02-13T00:08:13.628966+01:00 machine4 kernel: [ 3.488784][ T527] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem 2023-02-13T00:08:13.628971+01:00 machine4 kernel: [ 3.489637][ T527] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 (using threaded interrupts) 2023-02-13T00:08:13.628972+01:00 machine4 kernel: [ 3.499362][ T527] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.157 Wed Oct 12 09:15:25 UTC 2022 2023-02-13T00:08:13.628972+01:00 machine4 kernel: [ 3.505733][ T527] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver 2023-02-13T00:08:13.628973+01:00 machine4 kernel: [ 3.506428][ T527] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1
Update openSUSE Tumbleweed 20230211-0 -> 20230212-0 did not help either. Boot to the recover modes of 6.1.10-1 or 6.1.8-1 does not help .
6.1.8-1 recovery at least says that "Failed to start X Display Manager" and gives the F1,F2,...ttys. but when I install NVIDIA-Linux-x86_64-390.157.run the F1,F2, ttys are also gone.
Please help.
Thanks in advance BR Pete