Hi All,
TLDR don’t dup yet.
Not asking for help as such (I’ll take any you’ve got) but just offering a word of advice to people thinking about running zypper dup today.
There’s a new kernel point version 6.12 today and (as is typical) that means the system won’t boot. I got a shell on TTY2 and it’s responsive, but the journal is a mess of red. Rebooting and choosing the 6.11 kernel has worked fine.
I’ve no idea why, it happened to me just moments ago, I’m just here to give people a heads-up.
Darn, I hoped that the delay of release of 6.12 might mean that a new kernel worked first time
Well, that’d be why:
Dec 22 14:54:25 Pallas kwin_wayland[6655]: kwin_core: Failed to open /dev/dri/card0 device (Invalid argument)
Dec 22 14:54:25 Pallas kwin_wayland[6655]: kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
Dec 22 14:54:25 Pallas kwin_wayland[6655]: kwin_wayland_drm: No suitable DRM devices have been found
(stack dump follows)
This is an nvidia GPU, so I suspect there’s a problem with that driver.
@pallaswept need to rebuild the driver for the Nvidia card… maybe use a later one too? I use the run file and open driver, all good with Prime Render Offload…
pinxi -SaGxxz
System:
Kernel: 6.12.6-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.6-1-default
root=UUID=1ab675ed-aba2-4593-9ebc-1c893015b607 splash=silent quiet
security=apparmor intel_iommu=on iommu=pt fbdev=1 nosimplefb=1
mitigations=auto
Desktop: GNOME v: 47.2 tk: GTK v: 3.24.43 wm: gnome-shell
tools: gsd-screensaver-proxy avail: xscreensaver dm: GDM v: 47.0
Distro: openSUSE Tumbleweed 20241220
Graphics:
Device-1: NVIDIA GM107GL [Quadro K620] vendor: Hewlett-Packard
driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
non-free: 550.xx+ status: current (as of 2024-12; EOL~2026-12-xx)
arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-2019 pcie:
speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s bus-ID: 01:00.0
chip-ID: 10de:13bb class-ID: 0300
Device-2: NVIDIA TU117GLM [Quadro T400 Mobile] driver: nvidia v: 565.77
alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current (as of
2024-12; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s bus-ID: 02:00.0 chip-ID: 10de:1fb2 class-ID: 0300
Device-3: Intel DG2 [Arc A380] vendor: ASRock driver: i915 v: kernel
alternate: xe arch: Gen-12.7 code: Alchemist process: TSMC n6 (7nm)
built: 2022+ pcie: gen: 1 speed: 2.5 GT/s lanes: 1 ports:
active: HDMI-A-1,HDMI-A-3,HDMI-A-4 off: HDMI-A-2 empty: DP-1,DP-2,DP-3
bus-ID: 05:00.0 chip-ID: 8086:56a5 class-ID: 0300
Device-4: Realtek RTL2838 DVB-T driver: dvb_usb_rtl28xxu,rtl2832_sdr
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-4:2
chip-ID: 0bda:2838 class-ID: 0000 serial: <filter>
Display: x11 server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: gnome-shell driver: X: loaded: modesetting,nvidia unloaded: vesa
alternate: fbdev,intel,nouveau,nv dri: iris gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x2160 s-size: <missing: xdpyinfo>
Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,bottom-c
model: Sceptre E24 serial: <filter> built: 2020 res: mode: 1920x1080
scaling: 1 hz: 60 dpi: 187 gamma: 1.2 size: 521x293mm (20.51x11.54")
diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-2 mapped: HDMI-2 note: disabled model-id: AGO 0x0001
serial: <filter> built: 2013 res: 1920x1080 dpi: 87 gamma: 0.97
size: 256x192mm (10.08x7.56") diag: 378mm (14.9") ratio: 4:3, 5:4 modes:
max: 1024x768 min: 720x480
Monitor-3: HDMI-A-3 mapped: HDMI-3 pos: top-left model: Sceptre E24
serial: <filter> built: 2018 res: mode: 1920x1080 scaling: 1 hz: 60
gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 604mm (23.8") ratio: 16:9
modes: max: 1920x1080 min: 720x400
Monitor-4: HDMI-A-4 mapped: HDMI-4 pos: top-right model: Sceptre E24
serial: <filter> built: 2019 res: mode: 1920x1080 scaling: 1 hz: 60 dpi: 94
gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 604mm (23.8") ratio: 16:9
modes: max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.3.1 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Arc A380 Graphics (DG2)
device-ID: 8086:56a5 memory: 5.81 GiB unified: no
API: Vulkan v: 1.3.296 layers: 2 device: 0 type: discrete-gpu
name: NVIDIA T400 driver: N/A device-ID: 10de:1fb2 surfaces: xcb,xlib
device: 1 type: cpu name: llvmpipe (LLVM 19.1.5 256 bits) driver: N/A
device-ID: 10005:0000 surfaces: xcb,xlib
mburge
December 22, 2024, 4:59am
4
^^^ --- CONFTEST lines above --- ^^^
CC [M] /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv.o
CC [M] /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-pci.o
CC [M] /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-dmabuf.o
CC [M] /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-nano-timer.o
cc1: error: bad value ‘x86-64-v’ for ‘-march=’ switch
cc1: note: valid arguments to ‘-march=’ switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids emeraldrapids alderlake raptorlake meteorlake graniterapids graniterapids-d arrowlake arrowlake-s lunarlake pantherlake bonnell atom silvermont slm goldmont goldmont-plus tremont gracemont sierraforest grandridge clearwaterforest knl knm x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 lujiazui yongfeng k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 znver4 znver5 btver1 btver2 native; did you mean ‘x86-64-v2’?
cc1: error: bad value ‘x86-64-v’ for ‘-march=’ switch
cc1: note: valid arguments to ‘-march=’ switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids emeraldrapids alderlake raptorlake meteorlake graniterapids graniterapids-d arrowlake arrowlake-s lunarlake pantherlake bonnell atom silvermont slm goldmont goldmont-plus tremont gracemont sierraforest grandridge clearwaterforest knl knm x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 lujiazui yongfeng k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 znver4 znver5 btver1 btver2 native; did you mean ‘x86-64-v2’?
cc1: error: bad value ‘x86-64-v’ for ‘-march=’ switch
cc1: note: valid arguments to ‘-march=’ switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids emeraldrapids alderlake raptorlake meteorlake graniterapids graniterapids-d arrowlake arrowlake-s lunarlake pantherlake bonnell atom silvermont slm goldmont goldmont-plus tremont gracemont sierraforest grandridge clearwaterforest knl knm x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 lujiazui yongfeng k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 znver4 znver5 btver1 btver2 native; did you mean ‘x86-64-v2’?
CC [M] /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-acpi.o
make[5]: *** [/usr/src/linux-6.12.6-1/scripts/Makefile.build:230: /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv.o] Error 1
make[5]: *** Waiting for unfinished jobs....
make[5]: *** [/usr/src/linux-6.12.6-1/scripts/Makefile.build:230: /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-pci.o] Error 1
make[5]: *** [/usr/src/linux-6.12.6-1/scripts/Makefile.build:230: /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-dmabuf.o] Error 1
cc1: error: bad value ‘x86-64-v’ for ‘-march=’ switch
cc1: note: valid arguments to ‘-march=’ switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids emeraldrapids alderlake raptorlake meteorlake graniterapids graniterapids-d arrowlake arrowlake-s lunarlake pantherlake bonnell atom silvermont slm goldmont goldmont-plus tremont gracemont sierraforest grandridge clearwaterforest knl knm x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 lujiazui yongfeng k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 znver4 znver5 btver1 btver2 native; did you mean ‘x86-64-v2’?
make[5]: *** [/usr/src/linux-6.12.6-1/scripts/Makefile.build:230: /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-nano-timer.o] Error 1
cc1: error: bad value ‘x86-64-v’ for ‘-march=’ switch
cc1: note: valid arguments to ‘-march=’ switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids emeraldrapids alderlake raptorlake meteorlake graniterapids graniterapids-d arrowlake arrowlake-s lunarlake pantherlake bonnell atom silvermont slm goldmont goldmont-plus tremont gracemont sierraforest grandridge clearwaterforest knl knm x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 lujiazui yongfeng k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 znver4 znver5 btver1 btver2 native; did you mean ‘x86-64-v2’?
make[5]: *** [/usr/src/linux-6.12.6-1/scripts/Makefile.build:230: /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open/nvidia/nv-acpi.o] Error 1
make[4]: *** [/usr/src/linux-6.12.6-1/Makefile:1965: /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open] Error 2
make[3]: *** [/usr/src/linux-6.12.6-1/Makefile:224: __sub-make] Error 2
make[3]: Leaving directory '/usr/src/linux-6.12.6-1-obj/x86_64/default'
make[2]: *** [Makefile:224: __sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-6.12.6-1'
make[1]: *** [Makefile:89: modules] Error 2
make[1]: Leaving directory '/usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open'
make: *** [Makefile:59: modules] Error 2
make -C kernel-open modules_install
make[1]: Entering directory '/usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open'
make[2]: Entering directory '/usr/src/linux-6.12.6-1'
make[3]: Entering directory '/usr/src/linux-6.12.6-1-obj/x86_64/default'
DEPMOD /usr/lib/modules/6.12.6-1-default
Warning: modules_install: missing 'System.map' file. Skipping depmod.
make[3]: Leaving directory '/usr/src/linux-6.12.6-1-obj/x86_64/default'
make[2]: Leaving directory '/usr/src/linux-6.12.6-1'
make[1]: Leaving directory '/usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open'
/
depmod: WARNING: could not open modules.order at /usr/lib/modules/6.12.6-1-default: No such file or directory
depmod: WARNING: could not open modules.builtin at /usr/lib/modules/6.12.6-1-default: No such file or directory
depmod: WARNING: could not open modules.builtin.modinfo at /usr/lib/modules/6.12.6-1-default: No such file or directory
/usr/src/kernel-modules/nvidia-560.35.05-default /
make -C src/nvidia clean
make[1]: Entering directory '/usr/src/kernel-modules/nvidia-560.35.05-default/src/nvidia'
rm -f -rf _out/Linux_x86_64
make[1]: Leaving directory '/usr/src/kernel-modules/nvidia-560.35.05-default/src/nvidia'
make -C src/nvidia-modeset clean
make[1]: Entering directory '/usr/src/kernel-modules/nvidia-560.35.05-default/src/nvidia-modeset'
rm -f -rf _out/Linux_x86_64
make[1]: Leaving directory '/usr/src/kernel-modules/nvidia-560.35.05-default/src/nvidia-modeset'
make -C kernel-open clean
make[1]: Entering directory '/usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open'
rm -f -r conftest
make[2]: Entering directory '/usr/src/linux-6.12.6-1'
make[3]: Entering directory '/usr/src/linux-6.12.6-1-obj/x86_64/default'
CLEAN /usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open
make[3]: Leaving directory '/usr/src/linux-6.12.6-1-obj/x86_64/default'
make[2]: Leaving directory '/usr/src/linux-6.12.6-1'
make[1]: Leaving directory '/usr/src/kernel-modules/nvidia-560.35.05-default/kernel-open'
/
warning: %triggerin(nvidia-open-driver-G06-kmp-default-560.35.05-1.x86_64) scriptlet failed, exit status 1
( 4/103) Installing: kernel-default-devel-6.12.6-1.1.x86_64 ......................................................................................................................[done]
but I’ve been rocking the xanmod-v3 6.12 with the 550.135 (run file) for the last 20 days so
I’m using the open cuda drivers as per nvidia’s docs. Not interested in the runfile approach, if it ain’t packaged, it doesn’t get installed here. I find enough bugs already
I suspect I’m first to see this 6.12: drm_open_helper RIP · Issue #712 · NVIDIA/open-gpu-kernel-modules · GitHub here. According to that thread, the patches required to fix the driver haven’t been applied on their repo. I could have sworn I saw something about that for opensuse, but I guess not
The main reason I have an nvidia card, I endure all the broken graphics drivers, and now even cuda won’t work. Grrr nvidiaaaaa.
@pallaswept is that the rpm module rebuild?
@pallaswept I use the cuda run file, then update the driver from the run file.
I’m using officially packaged drivers.
The question here is ‘which combination of official packaged drivers from which official repo(s) will boot with official kernel 6.12 and work with official cuda packages installed from the cuda repo?’
It’s not clear if this needs me to force an older driver, just wait, find an updated package…etc. I might have to ask Stefan, but I would prefer not to bother him. I’ll try and figure it out. Any advice on that front would be great!
As I remember only 560.x Nvidia drivers has some patches/fixes for 6.12 kernel, 550.x - does not. May be it is time to switch to 560.x branch?
I was thinking along those lines… I thought that it might be because I am using 565 drivers… they installed automatically recently. That github thread suggests that only 550 series is working on nvidia’s repo, but I’m not sure that applies to opensuse?
I’m sure there’s some way that it’s intended to work, it’s just not clear what that is, and it’s not the official way or the automatic way. Fun!
hui
December 22, 2024, 6:24am
11
kernel-6.12.6-1-default works perfectly fine with the Nvidia 550.135 drivers. Non of my machines had any hiccups whilst updating to kernel-6.12.6-1-defaultIndex of /opensuse/tumbleweed installed according SDB:NVIDIA drivers - openSUSE Wiki
ich@rennsemmel:~> inxi -bG
System:
Host: rennsemmel Kernel: 6.12.6-1-default arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.2.4 Distro: openSUSE Tumbleweed 20241220
Machine:
Type: Desktop Mobo: Micro-Star model: Z590-A PRO (MS-7D09) v: 1.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 1.A0
date: 07/11/2024
CPU:
Info: 8-core 11th Gen Intel Core i9-11900KF [MT MCP] speed (MHz): avg: 2264
min/max: 800/5100:5300
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Ti] driver: nvidia v: 550.135
Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
loaded: nvidia unloaded: modesetting,vesa gpu: nvidia,nvidia-nvswitch
resolution: 2560x1440~60Hz
API: EGL v: 1.5 drivers: nvidia platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6.0 vendor: nvidia v: 550.135 renderer: NVIDIA GeForce
RTX 3080 Ti/PCIe/SSE2
API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib
Network:
Device-1: Intel Ethernet I225-V driver: igc
Drives:
Local Storage: total: 3.64 TiB used: 438.27 GiB (11.8%)
Info:
Memory: total: 32 GiB available: 31.22 GiB used: 4.52 GiB (14.5%)
Processes: 377 Uptime: 0h 56m Shell: Bash inxi: 3.3.36
ich@rennsemmel:~>
Trouble is, the cuda repo upgraded us from those some time ago.
Yeh it’s really not clear what works or what is intended to work, It’s not really sane to spend all day installing and rolling back until I get it right, so I’ve filed a bug:
https://bugzilla.opensuse.org/show_bug.cgi?id=1234780
Same here on Optimus laptop, Gnome+switcherooctl render offoad; both graphics and openCL working on 550.135 drivers, so problems are apparently limited to some higher versions or repos.
bruno@LT-B:~> inxi -SGz
System:
Kernel: 6.12.6-1-default arch: x86_64 bits: 64
Desktop: GNOME v: 47.2 Distro: openSUSE Tumbleweed 20241220
Graphics:
Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915
v: kernel
Device-2: NVIDIA GM107M [GeForce GTX 960M] driver: nvidia v: 550.135
Device-3: Chicony HD WebCam (Asus N-series) driver: uvcvideo type: USB
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: gnome-shell driver: X: loaded: modesetting,nvidia
unloaded: fbdev,nouveau,vesa dri: crocus gpu: i915
resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: crocus,nvidia
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 24.3.1
renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib,wayland
bruno@LT-B:~>
Ok, thanks @hui , updating then.
conram
December 22, 2024, 4:45pm
17
No problem on my old desktop.
~> inxi -bG
System:
Host: localhost.localdomain Kernel: 6.12.6-1-default arch: x86_64 bits: 64
Desktop: Xfce v: 4.19.3git-UNKNOWN Distro: openSUSE Tumbleweed 20241220
Machine:
Type: Desktop System: Hewlett-Packard product: h8-1213c v: 1.00
serial: <superuser required>
Mobo: PEGATRON model: 2AD5 v: 1.03 serial: <superuser required> UEFI: AMI
v: 8.21 date: 10/20/2014
CPU:
Info: quad core Intel Core i7-3770 [MT MCP] speed (MHz): avg: 1600
min/max: 1600/3900
Graphics:
Device-1: NVIDIA GA106 [Geforce RTX 3050] driver: nvidia v: 565.77
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: wayfire v: 0.9.0-unknown driver: X: loaded: nvidia
unloaded: modesetting,vesa gpu: nvidia resolution: 1920x1080
API: EGL v: 1.5 drivers: nvidia
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 renderer: NVIDIA GeForce
RTX 3050/PCIe/SSE2
API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib,wayland
Network:
Device-1: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k
Device-2: Broadcom BCM43225 802.11b/g/n driver: N/A
Device-3: Qualcomm Atheros AR8161 Gigabit Ethernet driver: alx
Drives:
Local Storage: total: 2.04 TiB used: 148.46 GiB (7.1%)
Info:
Memory: total: 20 GiB note: est. available: 17.5 GiB used: 1.9 GiB (10.8%)
Processes: 302 Uptime: 0h 5m Shell: Bash inxi: 3.3.36
Using the .run installer with DKMS on for rebuilding the driver.
Just to clarify this, the problem here is with the nvidia cuda toolkit and the associated repositories and drivers.
This isn’t relevant to anyone using the run file, or not using cuda.
Seems like so far there are only two people using cuda on tumbleweed
conram
December 22, 2024, 8:31pm
19
Better probably to ask the administrators to change the title to include cuda.
Probably better that people read threads before reacting to them.
You started with blaming kernel 6.12 for not supporting your external repository without a single word about what this repository is. Now you blame others that they do not read all 20+ posts just to find out you were referring to the software that does not even officially support Tumbleweed.
Reactions are just as good as your actions. You provided zero information when starting this topic. Do not blame others when they do not waste extra efforts to discover this information.
Hopefully I can get help to resolve this before more people update.