@malcolmlewis It’s getting late. I’ll try again tomorrow. Maybe I missed installing some repositories or packages required by NVIDIA’s .run file. This is a fresh install after all, so it’s basically blank.
Thanks for your continued support, there is hope.
I’m not using secure boot. I decided that would be another can of worms. Or do I need to to make this work?
@nickelarse I’m not using secure boot here with the run file. Again, I would suggest you clean up any installed rpm parts… Download the cuda run file, chmod 0755 the run file as your user. Log out of the desktop, then switch to a tty (ctrl+alt+F1) and then login as root.
Switch to run level 3 systemctl isolate multi-user.target the cd to the directory where the cuda file is and then ./cuda_13.1.0_590.44.01_linux.run it should install and ask to accept etc. I don’t install the documentation…
If it errors out, look at the log it produces. Make sure your user is in the video and render groups.
@nickelarse see here as well https://forums.opensuse.org/t/brand-new-build-only-1024/190146/166 (Leap 16, but same issue…)
@malcolmlewis I’ve cleared out all NVIDIA rpms. I’ve run NVIDIA-Linux-x86_64-580.105.08.run (the CUDA one you suggested seems for CUDA, not graphics drivers, or have I missed the point?). The MIT/GPL option fails to build, but NVIDIA Proprietary appears to build, but after reboot, console only.
I think I’ve ended up in a bit of a mess. Precisely what do I download from NVIDIA? I went to their website and downloaded a .run file for my 5070, but this is possibly the wrong thing. I got it from here: Driver Details | NVIDIA.
@nickelarse the driver is included with the cuda file, default is the open driver. You are downloading the wrong driver… it’s 590.44.01.
@malcolmlewis Thanks for pointing out the obvious mistake (and clarifying the CUDA thing)! The NVIDIA site gave me that wrong version when I searched. But I’ve now searched it through a different menu and get the 590 version like suggested. However, first I’ll try the open driver on a fresh install, as doing it through zypper is definitely preferable to having to install from their website every time the kernel updates.
I’ve started again. Fresh Tumbleweed install with nomodeset, with secure boot disabled (in BIOS and in YaST setup), and Update NVRAM enabled (in YaST setup). Steps after installation (based on that other thread you mention):
inxi -GSaz
System:
Kernel: 6.18.0-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 clocksource: tsc
avail: hpet,acpi_pm
parameters: BOOT_IMAGE=(hd0,gpt1)/opensuse-tumbleweed/6.18.0-1-default/linux-920be6329be2211fef6d2bda38b8289a290ea832
splash=silent resume=/dev/system/swap mitigations=auto quiet security=selinux selinux=1
rd.driver.blacklist=nouveau root=UUID=4f92a9d0-499a-44e6-aa64-ef7d6a58592b
rootflags=subvol=@/.snapshots/1/snapshot
Console: pty pts/1 DM: SDDM Distro: openSUSE Tumbleweed 20251205
Graphics:
Device-1: NVIDIA GB203 [GeForce RTX 5070 Ti] vendor: Palit Microsystems driver: N/A
alternate: nouveau non-free: 550-580.xx+ status: current (as of 2025-11) arch: Lovelace
code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
link-max: gen: 5 speed: 32 GT/s bus-ID: 01:00.0 chip-ID: 10de:2c05 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics] vendor: Gigabyte
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1, DP-2, DP-3, HDMI-A-1,
Writeback-1 bus-ID: 13:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 36.0 C
Display: unspecified server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.8 compositor: kwin_x11
driver: X: loaded: modesetting unloaded: vesa failed: nvidia alternate: fbdev,nouveau,nv
dri: radeonsi gpu: amdgpu tty: 208x98
Monitor-1: Unknown-1 size-res: N/A in console modes: 1024x768
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
gbm: drv: kms_swrast surfaceless: drv: radeonsi inactive: wayland,x11
API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.3.1 note: console (EGL sourced)
renderer: llvmpipe (LLVM 21.1.6 256 bits), AMD Ryzen 9 9950X 16-Core Processor (radeonsi
raphael_mendocino LLVM 21.1.6 DRM 3.64 6.18.0-1-default)
API: Vulkan v: 1.4.328 layers: 4 device: 0 type: integrated-gpu name: AMD Ryzen 9 9950X
16-Core Processor (RADV RAPHAEL_MENDOCINO) driver: mesa radv v: 25.3.1 device-ID: 1002:13c0
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.6 256 bits) driver: mesa llvmpipe
v: 25.3.1 (LLVM 21.1.6) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
gpu: nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
@nickelarse did you run zypper inr (install new recommends)?
Only use zypper dup on Tumbleweed.
And if you use the AMD gpu, also what is the Monitor in use?
@malcolmlewis The AMD GPU is just built into the processor. I don’t use it. Or at least, I don’t intend to use it. Monitor is a Dell 4K. Yes, I ran zypper inr. Was this the issue? Should I replace zypper inr with zypper dup?
I’ve just re-run the whole process on Leap, and the graphics driver works! So works on Leap, but not Tumbleweed.
@nickelarse What model number is the Dell Monitor? Can you show the inxi -GSaz output from Leap 16.0?
I would suggest plugging into the AMD gpu to test. You could look at using Prime Render Offload? That’s what I use here but Intel/Nvidia.
Sorry for slow reply, been at work. Leap 16.0 output from inxi:
System:
Kernel: 6.12.0-160000.7-default arch: x86_64 bits: 64 compiler: gcc
v: 13.4.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.7-default
root=UUID=53fa3885-d69f-4882-9f73-686fd1b8f796 mitigations=auto quiet
security=selinux selinux=1 rd.driver.blacklist=nouveau
Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.16.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: openSUSE Leap 16.0
Graphics:
Device-1: NVIDIA GB203 [GeForce RTX 5070 Ti] vendor: Palit Microsystems
driver: nvidia v: 580.95.05 alternate: nouveau,nvidia_drm non-free: N/A
status: unknown device ID pcie: gen: 4 speed: 16 GT/s lanes: 16 link-max:
gen: 5 speed: 32 GT/s ports: active: none off: DP-4
empty: DP-5,DP-6,HDMI-A-2 bus-ID: 01:00.0 chip-ID: 10de:2c05
class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: Gigabyte driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none empty: DP-1, DP-2, DP-3, HDMI-A-1,
Writeback-1 bus-ID: 13:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 32.0 C
Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1.1.4:5
chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: vesa
alternate: fbdev,nouveau,nv dri: radeonsi
gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 162 s-size: 602x341mm (23.70x13.43")
s-diag: 692mm (27.24")
Monitor-1: DP-4 mapped: DP-0 note: disabled model: Dell U2725QE
serial: <filter> built: 2025 res: 3840x2160 dpi: 163 gamma: 1.2
size: 600x340mm (23.62x13.39") diag: 685mm (27") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 1 drv: radeonsi gbm: drv: kms_swrast surfaceless:
drv: nvidia x11: drv: nvidia inactive: wayland
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.95.05
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 5070 Ti/PCIe/SSE2
memory: 15.55 GiB
API: Vulkan v: 1.4.309 layers: 3 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 5070 Ti driver: N/A device-ID: 10de:2c05 surfaces: xcb,xlib
device: 1 type: integrated-gpu name: AMD Radeon Graphics (RADV
RAPHAEL_MENDOCINO) driver: N/A device-ID: 1002:13c0 surfaces: xcb,xlib
@nickelarse and your plugged into the onboard AMD GPU?
So it’s a Dell U2725QE Monitor.
@deano_ferrari any thought on this?
@malcolmlewis no, not plugged into the onboard, I’m plugged directly into the NVIDIA card. I had no intention to use the onboard card at all, it just happens to be in the processor.
@nickelarse Can you disable the iGPU in the BIOS?
I have a similar problem with NVidia on kernel 6.18; see 1254882 – Kernel crashing with NVidia binary drivers after update to 6.18.0-1.0.2.
I checked again just half an hour ago, and AFAICS there is now a newer nvidia-open-driver-G06-signed-kmp-meta-580; I had kernel 6.17.9 with nvidia-open-driver-G06-signed-kmp-default-580.105.08_k6.17.9_1.0.2.sr20251106-2.1.6.4.sr20251106.x86_64 (notice the k6.17.9 in the name which probably means “for kernel 6.17.9”), and now, since 2025-12-11 (Thursday), there is a newer nvidia-driver-G06-kmp-default-580.119.02_k6.18.0_1-43.1.x86_64.rpm (notice k6.18.0) at the NVidia repo.
I tried a dup with myrlyn, but it wanted to downgrade a number of nvidia packages to V570 (from my installed 580), so I aborted the whole thing.
Maybe we simply need to wait for the NVidia packages to be updated; right now something seems to be in an inconsistent state.
You could try to downgrade your kernel to the latest 6.17; that might fix your current problem. If it works, lock kernel-default for now and let’s wait for a few days; NVidia together with the kernel maintainers will probably sort that whole thing out.
HTH
@malcolmlewis Only had a quick glance at this. Not a MOK enrollment issue with the nvidia driver?
Other than that, it seems to be an issue as sdundhammer has since reported.
Edit: I now read that secure boot was disabled by the OP.
@malcolmlewis I can’t find a way. Would this be the problem? Are the two interfering? I’d have hoped, in the presence of an external graphics card, the internal one would be ignore, but I can see it certainly knows it’s there. Does this mean I could actually plug a display into that and use it as well (not that I can see much point)?
@shundhammer Thanks for the info. Sounds like there are some issues. However, I’ve now got somewhat confused about what bugs I even need to report. In summary, I think they are these (please moderators tell me if I’m wrong before I file bug reports):
Don’t worry: I am sure the maintainer of the NVidia repo will sort this out quickly. The timing for this just before the weekend was very unfortunate. We’ll just have to be patient for a day or two to give him a fighting chance.
I don’t know about LUKS and nomodeset. Google AI says:
if you use
nomodesetfor graphics, you might need to ensureluks=1is also present in your bootloader for encrypted drives, or removenomodesetpermanently after installing correct drivers via YaST/Zypper, as noted in openSUSE’s SDB and SUSE documentation.
Not sure if you re-checked this in the meantime: It’s now in a consistent state with kernel 6.18, a matching NVidia kmp and the matching userspace NVidia packages.