Assign Driver to Graphics Card

Hello,

I just installed Tumbleweed to new hardware. Info Center says my graphics processor is llvmpipe
The results of inxi -G are:
"
Graphics:
Device-1: ASPEED Graphics Family driver: N/A
Device-2: Advanced Micro Devices [AMD/ATI] Navi 48 [Radeon RX 9070/9070
XT/9070 GRE] driver: N/A
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
gpu: N/A resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: swrast platforms: wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 26.0.1 renderer: llvmpipe (LLVM 21.1.8
256 bits)
API: Vulkan v: 1.4.341 drivers: llvmpipe surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: amdgpu_top,radeontop
wl: wayland-info x11: xdpyinfo, xprop, xrandr
"
When I look online, I am told that the amdgpu driver should work for the Radeon 9070 XT. When I check my installed software, kernel-firmware-amdgpu 20260225-1.1 is installed. What file do I edit to tell the OS to use that driver for that card? Is the information in opensuse.org/SDB:Configuring_graphics_cards sufficiently current?

inxi -GSaz would be more useful. It may be the Aspeed is being defaulted to but without any KMS driver available. lsmod | grep video, dmesg | grep drm and journalctl -b -p3 may also be useful pasted here.

When you paste command output here, please begin your copy with the command line, end with the following prompt line, and enclose the paste within PRE tags (</> icon above input window)'.

~> inxi -GSaz
System:
  Kernel: 6.19.6-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/opensuse-tumbleweed/6.19.6-1-default/linux-b67afcf34244e78002db3aefc871d0dc6bd56e7f
    splash=silent nomodeset mitigations=auto quiet security=selinux selinux=1
    root=UUID=222df1a4-fa1b-44cb-b6d2-e5d748951c1c
    systemd.machine_id=cc1520b566154460a8ac97e981d0c3cf
  Desktop: KDE Plasma v: 6.6.2 tk: Qt v: N/A info: frameworks v: 6.23.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
    Tumbleweed 20260308
Graphics:
  Device-1: ASPEED Graphics Family vendor: ASRock driver: N/A alternate: ast
    bus-ID: d3:00.0 chip-ID: 1a03:2000 class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 48 [Radeon RX 9070/9070
    XT/9070 GRE] vendor: ASRock driver: N/A alternate: amdgpu arch: RDNA-4
    code: Navi-4x process: TSMC n4 (4nm) built: 2025+ pcie: gen: 5
    speed: 32 GT/s lanes: 16 bus-ID: f3:00.0 chip-ID: 1002:7550 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev gpu: N/A display-ID: 0
  Monitor-1: Unknown-1 model: Dell AW2725Q serial: <filter> built: 2025 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 165 gamma: 1.2
    size: 590x333mm (23.23x13.11") diag: 677mm (26.7") ratio: 16:9
    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: 26.0.1 glx-v: 1.4 direct-render: yes
    renderer: llvmpipe (LLVM 21.1.8 256 bits) device-ID: ffffffff:ffffffff
    memory: 29.95 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.341 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM
    21.1.8 256 bits) driver: mesa llvmpipe v: 26.0.1 (LLVM 21.1.8)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top,radeontop
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
~> lsmod | grep video 
video                  81920  1 amdgpu
wmi                    32768  2 video,wmi_bmof
~ # dmesg | grep drm
[    0.395349] [      T1] ACPI: bus type drm_connector registered
[    0.397997] [      T1] efi-framebuffer efi-framebuffer.0: [drm] Registered 1 planes with drm panic
[    0.398013] [      T1] [drm] Initialized efidrm 1.0.0 for efi-framebuffer.0 on minor 0
[    0.400403] [      T1] efi-framebuffer efi-framebuffer.0: [drm] fb0: efidrmdrmfb frame buffer device
[    5.542255] [      T1] systemd[1]: Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!drm
~ # journalctl -b -p3
Mar 10 13:20:40 localhost kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREA>
Mar 10 13:20:40 localhost kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobjec>
Mar 10 13:20:42 localhost kernel: amdgpu 0000:f3:00.0: probe with driver amdgpu failed with error -22
Mar 10 13:20:43 localhost kernel: usb 7-5.3: device descriptor read/64, error -32

Mod edit: Preformatted text for output.

~ # journalctl -b -p3
Mar 10 13:20:40 localhost kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20250807/dswload2-326)
Mar 10 13:20:40 localhost kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
Mar 10 13:20:42 localhost kernel: amdgpu 0000:f3:00.0: probe with driver amdgpu failed with error -22
Mar 10 13:20:43 localhost kernel: usb 7-5.3: device descriptor read/64, error -32

Mod edit: Preformatted text

I don’t see anything that looks like Aspeed in the kernel’s drm directory to support it, which explains driver: N/A for it, and so little in lsmod output. With the AMD as primary or only, all drivers it needs ought to automatically load.

Have you looked in firmware setup for something that prefers use of the AMD GPU over the Aspeed?

ASRock’s BIOS setup for the WRX90 WS EVO seems fairly sparse compared to many I’ve seen. I don’t see anything related to PCI cards. There’s a displayport connector directly off the motherboard that I believe is for managerial use. I think ASPEED graphics is for use with that. I’m going to try a little resarch on the “amdgpu 0000:f3:00.0: probe with driver amdgpu failed with error -22” Since f3:00.0 is the bus id of the graphics card, maybe this failure is why it’s not in use.

Some of the stuff I have seen relating to error --22 also seems to be related to switching to different graphics hardware. I looked again in the BIOS settings and found “Turn Off Onboard VGA” and below it, priority was already given to PCI card graphics. I turned it off, and not too much changed. Here’s the new results.
BanisterJH@localhost:~> inxi -GSaz

System:
  Kernel: 6.19.6-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/opensuse-tumbleweed/6.19.6-1-default/linux-b67afcf34244e78002db3aefc871d0dc6bd56e7f
    splash=silent nomodeset mitigations=auto quiet security=selinux selinux=1
    root=UUID=222df1a4-fa1b-44cb-b6d2-e5d748951c1c
    systemd.machine_id=cc1520b566154460a8ac97e981d0c3cf
  Desktop: KDE Plasma v: 6.6.2 tk: Qt v: N/A info: frameworks v: 6.23.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
    Tumbleweed 20260308
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [Radeon RX 9070/9070
    XT/9070 GRE] vendor: ASRock driver: N/A alternate: amdgpu arch: RDNA-4
    code: Navi-4x process: TSMC n4 (4nm) built: 2025+ pcie: gen: 5
    speed: 32 GT/s lanes: 16 bus-ID: f3:00.0 chip-ID: 1002:7550 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev gpu: N/A display-ID: 0
  Monitor-1: Unknown-1 model: Dell AW2725Q serial: <filter> built: 2025 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 165 gamma: 1.2
    size: 590x333mm (23.23x13.11") diag: 677mm (26.7") ratio: 16:9
    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: 26.0.1 glx-v: 1.4 direct-render: yes
    renderer: llvmpipe (LLVM 21.1.8 256 bits) device-ID: ffffffff:ffffffff
    memory: 29.95 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.341 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM
    21.1.8 256 bits) driver: mesa llvmpipe v: 26.0.1 (LLVM 21.1.8)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top,radeontop
    wl: wayland-info x11: xdpyinfo, xprop, xrandr 

BanisterJH@localhost:~>

BanisterJH@localhost:~> lsmod | grep video

video                  81920  1 amdgpu
wmi                    32768  2 video,wmi_bmof 

BanisterJH@localhost:~>

localhost:~ # dmesg | grep drm

[    0.393678] [      T1] ACPI: bus type drm_connector registered
[    0.397438] [      T1] efi-framebuffer efi-framebuffer.0: [drm] Registered 1 planes with drm panic
[    0.397451] [      T1] [drm] Initialized efidrm 1.0.0 for efi-framebuffer.0 on minor 0
[    0.399496] [      T1] efi-framebuffer efi-framebuffer.0: [drm] fb0: efidrmdrmfb frame buffer device
[    5.623172] [      T1] systemd[1]: Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!drm 

localhost:~ #

localhost:~ # journalctl -b -p3

Mar 10 22:08:53 localhost kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20250807/dswload2-326)
Mar 10 22:08:53 localhost kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220)
Mar 10 22:08:55 localhost kernel: amdgpu 0000:f3:00.0: probe with driver amdgpu failed with error -22
Mar 10 22:08:56 localhost kernel: usb 7-5.3: device descriptor read/64, error -32 

localhost:~ #

Yes, that output was cutoff in your original posting due to the formatting. The use of <pre> and </pre> produces

command output here can be cut off if too long to display in the forum 

whereas using backtiks ``` above and below output produces

command output here will not get cut off when viewing in the forum unlike with <pre> .....</pre>

Are kernel-firmware-amdgpu and libdrm_amdgpu1 both installed? If yes, a bug report may be needed so Tiwai will take a look at Navi 48 support.

My job has called me away from home for a few days. As soon as I’m able, I’ll check.

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