Nvidia 5090 not working with Garuda Broadwing Dr460nized

LokiX11 · 25 March 2025 23:28

I have been trying to get my system to run with the nvidia drivers for a discrete Nvidia 5090 adapter (founders edition if it matters). And cant seem to get it to work.

I installed the system, and when I startup I try to run

nvidia-smi

No devices were found

Is it too new and do I simply need to wait a bit? or is there some other way to get my system to run the nvidia drivers?

Here is the output of my garuda-inxi:


System:
Kernel: 6.13.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=8bb8d754-1157-4d6f-bb9c-be884eda8bae rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: OriginPC product: Genesis v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: ASUSTeK model: ROG MAXIMUS XII HERO (WI-FI) v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 2701 date: 12/26/2022
CPU:
Info: model: Intel Core i9-10900K bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 5 microcode: 0xFC
Topology: cpus: 1x dies: 1 clusters: 10 cores: 10 threads: 20 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-10x32 KiB; i-10x32 KiB L2: 2.5 MiB
desc: 10x256 KiB L3: 20 MiB desc: 1x20 MiB
Speed (MHz): avg: 800 min/max: 800/5300 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
17: 800 18: 800 19: 800 20: 800 bogomips: 147994
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GB202 [GeForce RTX 5090] driver: nvidia v: 570.133.07
alternate: nouveau,nvidia_drm non-free: N/A status: unknown device ID pcie:
gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 5 speed: 32 GT/s
bus-ID: 01:00.0 chip-ID: 10de:2b85 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: 0
Monitor-1: Unknown-1 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 96
size: 508x285mm (20x11.22") diag: 582mm (22.93") modes: 1920x1080
API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
wayland: drv: swrast x11: drv: swrast inactive: gbm
API: OpenGL v: 4.5 vendor: mesa v: 25.0.2-arch1.2 glx-v: 1.4
direct-render: yes renderer: llvmpipe (LLVM 19.1.7 256 bits)
device-ID: ffffffff:ffffffff memory: 61.2 GiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 11 device: 0 type: cpu name: llvmpipe
(LLVM 19.1.7 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 link-max: gen: 5 speed: 32 GT/s bus-ID: 01:00.1
chip-ID: 10de:22e8 class-ID: 0403
Device-3: Texas Instruments PCM2903B Audio CODEC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-9.1.2.4:18 chip-ID: 08bb:29b3 class-ID: 0300
Device-4: Elgato Systems GmbH Wave XLR driver: snd-usb-audio type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9.1.3.4:22
chip-ID: 0fd9:007d class-ID: fe01 serial: <filter>
API: ALSA v: k6.13.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d4d class-ID: 0200
IF: eno2 state: down mac: <filter>
Device-3: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion]
vendor: ASUSTeK driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 1 port: N/A bus-ID: 04:00.0 chip-ID: 1d6a:11b1 class-ID: 0200
temp: 74.8 C
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:12 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 20.1 TiB used: 30.15 GiB (0.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Seagate model: FireCuda 520 SSD
ZP2000GM30002 size: 1.82 TiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: STNSC014
temp: 40.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 PRO 2TB
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 QVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 870 QVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 850 PRO 1TB
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-7: /dev/sdf maj-min: 8:80 vendor: Samsung model: SSD 850 PRO 1TB
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: MBR
ID-8: /dev/sdg maj-min: 8:96 vendor: Crucial model: CT4000X10PROSSD9
size: 3.64 TiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.1
spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: N/A fw-rev: 1000
scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 30.15 GiB (3.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/sde1 maj-min: 8:65
ID-3: /home raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 30.15 GiB (3.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-4: /var/log raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 30.15 GiB (3.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-5: /var/tmp raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 30.15 GiB (3.2%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.67 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 20
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 45.2 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 62.67 GiB used: 6.35 GiB (10.1%)
Processes: 416 Power: uptime: 21m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2497 libs: 618 tools: octopi,paru Compilers:
clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.1
running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2025-03-25
Last full system update: 2025-03-25 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Duke187 · 25 March 2025 23:49

Hello LokiX11 and welcome in the Forum,

Did you checked for a bios update also the inxi say you need to reboot the computer.

Also read somewhere the nvidia 570.86.16 beta or 560.86.10 working but dont nail me with the 570 134.07 driver. ALSO I DONT KNOW (NEWER KERNEL)

Im not a nvidia user beside my older Laptop so wait please for more experienced user or Leader

Other Forum Topic

LokiX11 · 26 March 2025 00:25

Thanks Duke187. The reboot was likely because bottles updated and I had not rebooted, that said it shouldn’t have effected it. I did not think about the BIOS update, silly me. Doing that now and will try again and report back. If that does not work, will wait a bit before trying the older drivers to see if there is another fix. But who knows maybe the bios will help Thanks again!

LokiX11 · 26 March 2025 15:41

Updated firmware to latest firmware from earlier this year, and still cant get the card to show up in nvidia-smi or work in general. I did try disabling Resize-Bar as I had read on some general posts for Linux, as well as enabling IOMMU, both of which did not fix the issue either. Posting my latest garuda-inxi in hopes that there may be some additional detail someone can see that I may not be thinking of. Can try the versions that Duke187 mentioned but may wait before doing that in case there are any other insights.

System:
Kernel: 6.13.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=8bb8d754-1157-4d6f-bb9c-be884eda8bae rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: OriginPC product: Genesis v: N/A
serial: <superuser required> Chassis: type: 3 serial: <superuser required>
Mobo: ASUSTeK model: ROG MAXIMUS XII HERO (WI-FI) v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3201 date: 11/20/2024
CPU:
Info: model: Intel Core i9-10900K bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 5 microcode: 0xFC
Topology: cpus: 1x dies: 1 clusters: 10 cores: 10 threads: 20 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-10x32 KiB; i-10x32 KiB L2: 2.5 MiB
desc: 10x256 KiB L3: 20 MiB desc: 1x20 MiB
Speed (MHz): avg: 4900 min/max: 800/5300 scaling: driver: intel_pstate
governor: powersave cores: 1: 4900 2: 4900 3: 4900 4: 4900 5: 4900 6: 4900
7: 4900 8: 4900 9: 4900 10: 4900 11: 4900 12: 4900 13: 4900 14: 4900
15: 4900 16: 4900 17: 4900 18: 4900 19: 4900 20: 4900 bogomips: 147994
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GB202 [GeForce RTX 5090] driver: nvidia v: 570.133.07
alternate: nouveau,nvidia_drm non-free: N/A status: unknown device ID pcie:
gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 5 speed: 32 GT/s
bus-ID: 01:00.0 chip-ID: 10de:2b85 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nvidia display-ID: 0
Monitor-1: Unknown-1 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 96
size: 508x285mm (20x11.22") diag: 582mm (22.93") modes: 1920x1080
API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
wayland: drv: swrast x11: drv: swrast inactive: gbm
API: OpenGL v: 4.5 vendor: mesa v: 25.0.2-arch1.2 glx-v: 1.4
direct-render: yes renderer: llvmpipe (LLVM 19.1.7 256 bits)
device-ID: ffffffff:ffffffff memory: 61.2 GiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 11 device: 0 type: cpu name: llvmpipe
(LLVM 19.1.7 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Comet Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:06c8 class-ID: 0403
Device-2: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 link-max: gen: 5 speed: 32 GT/s bus-ID: 01:00.1
chip-ID: 10de:22e8 class-ID: 0403
Device-3: Texas Instruments PCM2903B Audio CODEC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-9.1.2.4:17 chip-ID: 08bb:29b3 class-ID: 0300
Device-4: Elgato Systems GmbH Wave XLR driver: snd-usb-audio type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9.1.3.4:27
chip-ID: 0fd9:007d class-ID: fe01 serial: <filter>
API: ALSA v: k6.13.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:0d4d class-ID: 0200
IF: eno2 state: down mac: <filter>
Device-3: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion]
vendor: ASUSTeK driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 1 port: N/A bus-ID: 04:00.0 chip-ID: 1d6a:11b1 class-ID: 0200
temp: 63.3 C
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:11 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 16.46 TiB used: 31.36 GiB (0.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Seagate model: FireCuda 520 SSD
ZP2000GM30002 size: 1.82 TiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: STNSC014
temp: 38.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 PRO 2TB
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 QVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 870 QVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 850 PRO 1TB
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-7: /dev/sdf maj-min: 8:80 vendor: Samsung model: SSD 850 PRO 1TB
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: MBR
Partition:
ID-1: / raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 31.36 GiB (3.3%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 612 KiB (0.2%) fs: vfat dev: /dev/sde1 maj-min: 8:65
ID-3: /home raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 31.36 GiB (3.3%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-4: /var/log raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 31.36 GiB (3.3%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
ID-5: /var/tmp raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 31.36 GiB (3.3%) fs: btrfs dev: /dev/sde2 maj-min: 8:66
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.67 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 20
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 38.8 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB note: est. available: 62.67 GiB used: 4.5 GiB (7.2%)
Processes: 447 Power: uptime: 0m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2497 libs: 618 tools: octopi,paru Compilers:
clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.1
running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2025-03-25
Last full system update: 2025-03-26
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

nepti · 26 March 2025 16:51

The GPU is not recognized correctly.

And it looks like the wrong drivers are installed. The 5090 is not supported by the proprietary nvidia drivers, post the output from:

pacman -Qs nvidia

Only the nvidia-open drivers support the Blackwell GPUs, in your case for the linux-zen kernel you need nvidia-open-dkms.

MagDux · 26 March 2025 17:15

Mmh… according to the Nvidia website the 570.133.07 Linux-aarch64 explicitly supports the RTX 5090: Driver Details | NVIDIA

I would try uninstalling nvidia-dkms with all dependencies, rebooting, and then re-installing it. That did help in the past when I had an issue after an update. Be prepared for a blank screen; make sure you have a snapshot you can access from the bootloader, just in case.
You could also try the BETA driver from the Nvidia website. Although the obvious downside is that this manual install will not update in the future, so even if it works you might want to switch back later.
If the issue is the combination with the zen Kernel, you could just get another one. Garuda Rani has a list to choose from, including default linux, lts, and cachyos.

nepti · 26 March 2025 17:45

Please learn the difference between arm64 and amd64 platform.

No, the proprietary nvidia-dkms driver is not recommended for Turing and newer GPUs and does not support Blackwell GPUs.

On Arch/archbased Linux, never install drivers from the nvidia website, but only from the official repositories.

Please do not recommend installing other kernels without installing the appropriate nvidia driver.

LokiX11 · 26 March 2025 18:14

Thank for the help here. I saw that just before that it needs to be the Open drivers, will switch to that now: As requested, here is the pacman -Qs mvidia output, will report back shortly on the Open Drivers. Thanks again for the help.

[🔴] × pacman -Qs nvidia
local/egl-gbm 1.1.2-1
The GBM EGL external platform library
local/egl-wayland 4:1.1.18-1
EGLStream-based Wayland external platform
local/egl-x11 1.0.0-1
NVIDIA XLib and XCB EGL Platform Library
local/garuda-nvidia-config 2:1.1.6-1.1
Meta configuration package for nvidia systems on Garuda Linux
local/gwe 0.15.9-1.1
A system utility for controlling NVIDIA GPUs
local/lib32-libvdpau 1.5-3
Nvidia VDPAU library
local/lib32-nvidia-utils 570.133.07-1
NVIDIA drivers utilities (32-bit)
local/lib32-opencl-nvidia 570.133.07-1
OpenCL implemention for NVIDIA (32-bit)
local/libvdpau 1.5-3
Nvidia VDPAU library
local/libxnvctrl 570.133.07-1
NVIDIA NV-CONTROL X extension
local/mhwd-nvidia 570.133.07.1-1
NVIDIA pci id list for MHWD
local/mhwd-nvidia-390xx 390.143-1
mhwd-nvidia-390xx PCI ID database
local/mhwd-nvidia-470xx 470.94-1
mhwd-nvidia-470xx PCI ID database
local/nvidia-dkms 570.133.07-1
NVIDIA kernel modules - module sources
local/nvidia-settings 570.133.07-1
Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 570.133.07-1
NVIDIA drivers utilities
local/opencl-nvidia 570.133.07-1
OpenCL implemention for NVIDIA

LokiX11 · 26 March 2025 18:25

Should I remove garuda-nvidia-config to update to the nvidia-open modules? Here is the output when I attempt to install

2 extra/nvidia-open-dkms 570.133.07-1 [9.97 MiB 100.25 MiB]
NVIDIA open kernel modules - module sources

Dependency error here:

resolving dependencies...
looking for conflicting packages...
:: nvidia-open-570.133.07-2 and nvidia-dkms-570.133.07-1 are in conflict (nvidia). Remove nvidia-dkms? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-dkms breaks dependency 'nvidia-dkms' required by garuda-nvidia-config

Edited as I did try with nvidia-open, instead of nvidia-open-dkms, problem the same however in that it cant replace nvidia-dkms, with nvidia-open-dkms due to the garuda-nvidia-config, dependency issue.

nepti · 26 March 2025 18:41

Yep, remove this first.

This is the wrong package (nvidia-open is for the linux kernel), you need the nvidia-open-dkms driver for the linux-zen kernel:

LokiX11 · 26 March 2025 18:57

Thanks, I did notice that and updated the earlier thread as I did it and went through it.

I did remove with pacman -R garuda-nvidia-config and then installed the nvidia-open-dkms modules with yay. That appears to have fixed my issue, and I will now mark this one as solved. Thanks Nepti! Also thanks Duke187 and Magdux

nepti · 26 March 2025 19:05

We always mark here the solution and not the implementation.
I have changed the marked solution.

system · 28 March 2025 19:05

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.