Tumbleweed Not Using Hardware Acceleration On Integrated AMD Graphics

[riptide1]

Hello,

Today I installed Tumbleweed on my new laptop that has an AMD Ryzen 5 7530U with Radeon Graphics. Even after installing the codecs, I can’t seem to get proper GPU acceleration working. Graphics processor is listed as llvmpipe in Plasma’s about this system section.

Initially Plasma didn’t even properly load in both X11 and Wayland sessions, I had to use IceWM to get the codecs, at which point that was fixed. Still the lock screen and SDDM show a black screen, instead of the current desktop wallpaper and scrolling anywhere, especially in Dolphin and Firefox has a noticeable lag to it.

Based on my search, it seemed like a regression with the 6.18 kernel series, however the same issue persists, even on the LTS 6.12 kernel series.

While booting, Plymouth also uses a very low resolution, which makes the password prompt take up pretty much the whole screen.

Any help is greatly appreciated.

[riptide1]

According to: lspci -k | grep -EA3 'VGA|3D|Display'

03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c5)
        Subsystem: Lenovo Device 50d5
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

It is in fact being detected and amdgpu is used.

vulkaninfo | grep deviceName still shows llvmpipe though:

deviceName = llvmpipe (LLVM 21.1.7, 256 bits)

This seems more like a driver issue to me, than a kernel issue.

[riptide1]

Running:

sudo zypper in kernel-firmware-amdgpu libdrm_amdgpu1 libdrm_amdgpu1-32bit libdrm_radeon1 libdrm_radeon1-32bit libvulkan_radeon libvulkan_radeon-32bit libvulkan1 libvulkan1-32bit

as per the wiki, results in Plasma properly reporting it.

vulkaninfo | grep deviceName shows llvmpipe with the proper GPU now for some reason:

        deviceName        = AMD Radeon Graphics (RADV RENOIR)
        deviceName        = llvmpipe (LLVM 21.1.7, 256 bits)

I still can’t apply the regular breeze SDDM theme, when I logout to try it out, the whole login page is just completely blinding white, the login page does still appear though.

OpenGL (EGL) info in Plasma’s info center still shows some errors:

_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)

amdgpu: amdgpu_device_initialize failed.

_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)

amdgpu: amdgpu_device_initialize failed.

Now I’m confused if hardware acceleration is actually working or not. Plymouth is still using the previous low resolution and SDDM is still having issues with the default breeze theme (which seems like a driver issue to me). The Open SUSE one works fine, however I can’t actually apply my display settings to it, resulting in everything being super tiny in the login screen.

Are there more OpenGL or Vulkan drivers that I am missing? As per the wiki, the Vulkan drivers should have been installed by default, but that wasn’t the case for me.

[riptide1]

Can anybody please confirm if the Plasma issues are related to my GPU drivers or not?

[deano_ferrari]

While waiting for assistance, check the installed Mesa* components with zypper se -si mesaand report back with the results. Missing Mesa components will cause llvmpipe fallback, broken SDDM themes, and Plasma rendering issues. Of course there could be other regressions at play.

[deano_ferrari]

Linking your other open topic as likely related…

General bugs with plasma after new install of tumbleweed

Hi, After installing tumbleweed on my new laptop, I am having a bunch of different graphical oddities with the plasma desktop. The first one being that I can’t apply my plasma settings to SDDM. It runs without any errors, but no actual changes happen after a logout. Trying the breeeze SDDM theme results in a completely white screen, with the login controls being barely visible. I don’t know if these are driver issues or not, never faced these on fedora plasma edition.

[riptide1]

Am I missing something here?

S  | Name                            | Type    | Version            | Arch   | Repository
---+---------------------------------+---------+--------------------+--------+------------------------
i  | Mesa                            | package | 25.3.1-1699.2.pm.1 | x86_64 | Packman
i  | Mesa-demo-egl                   | package | 9.0.0-7.1          | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-demo-x                     | package | 9.0.0-7.1          | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-dri                        | package | 25.3.1-1699.2.pm.8 | x86_64 | Packman
i  | Mesa-libEGL1                    | package | 25.3.1-1699.2.pm.1 | x86_64 | Packman
i  | Mesa-libGL1                     | package | 25.3.1-1699.2.pm.1 | x86_64 | Packman
i  | Mesa-libva                      | package | 25.3.1-1699.2.pm.8 | x86_64 | Packman
i  | Mesa-vulkan-device-select       | package | 25.3.1-1699.2.pm.8 | x86_64 | Packman
i  | Mesa-vulkan-device-select-32bit | package | 25.3.1-1699.2.pm.8 | x86_64 | Packman

[mrmazda]

@riptide1

Am I missing something here?

Have you tried not using Packman’s Mesa? Those are not always in sync with latest kernel.

[riptide1]

This was the same even before I switched to Packman’s Mesa. If anything, switching to that at least made the desktop session launch properly.

I will try reverting to an earlier snapshot and then install the vulkan packages again, to see if that changes anything.

[riptide1]

No change without the Packman Mesa either:

S  | Name                            | Type    | Version    | Arch   | Repository
---+---------------------------------+---------+------------+--------+------------------------
i  | Mesa                            | package | 25.3.1-1.1 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-demo-egl                   | package | 9.0.0-7.1  | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-demo-x                     | package | 9.0.0-7.1  | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-dri                        | package | 25.3.1-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-libEGL1                    | package | 25.3.1-1.1 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-libGL1                     | package | 25.3.1-1.1 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-libva                      | package | 25.3.1-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-vulkan-anti-lag            | package | 25.3.1-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-vulkan-anti-lag-32bit      | package | 25.3.1-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-vulkan-device-select       | package | 25.3.1-1.2 | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-vulkan-device-select-32bit | package | 25.3.1-1.2 | x86_64 | openSUSE-Tumbleweed-Oss

OpenGl (EGL) info still shows:

_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)

amdgpu: amdgpu_device_initialize failed.

_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)

amdgpu: amdgpu_device_initialize failed.

the software renderer is again being used for OpenGL:

GBM platform:

EGL API version: 1.5

EGL vendor string: Mesa Project

EGL version string: 1.5

EGL client APIs: OpenGL OpenGL_ES

EGL driver name: kms_swrast

[karlmistelberger]

5700g:~ # zypper se -is Mesa
Loading repository data...
Reading installed packages...

S  | Name                      | Type    | Version            | Arch   | Repository
---+---------------------------+---------+--------------------+--------+------------------------
i  | Mesa                      | package | 25.3.1-1699.2.pm.1 | x86_64 | Packman
i+ | Mesa-demo-egl             | package | 9.0.0-7.1          | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-demo-x               | package | 9.0.0-7.1          | x86_64 | openSUSE-Tumbleweed-Oss
i  | Mesa-dri                  | package | 25.3.1-1699.2.pm.8 | x86_64 | Packman
i  | Mesa-libEGL1              | package | 25.3.1-1699.2.pm.1 | x86_64 | Packman
i  | Mesa-libGL1               | package | 25.3.1-1699.2.pm.1 | x86_64 | Packman
i  | Mesa-libva                | package | 25.3.1-1699.2.pm.8 | x86_64 | Packman
i  | Mesa-vulkan-device-select | package | 25.3.1-1699.2.pm.8 | x86_64 | Packman
5700g:~ # 

5700g:~ # vainfo 
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Mesa Gallium driver 25.3.1 for AMD Radeon Graphics (radeonsi, renoir, ACO, DRM 3.64, 6.18.2-1-default)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc
5700g:~ # 

[riptide1]

my vainfo:

Trying display: wayland
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Mesa Gallium driver 25.3.1 for AMD Radeon Graphics (radeonsi, renoir, ACO, DRM 3.64, 6.18.2-1-default)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

Isn’t the Supported profile and entry points dependent on the GPU?

Can you also please check your OpenGL (EGL) info in Plasma info center?

I just don’t know what to make about the errors there, along with the fact that kms_swrast is being used for OpenGL and the existence of the secondary llvmpipe based software rendering GPU (which shouldn’t be there?)

[karlmistelberger]

@riptide1

Isn’t the Supported profile and entry points dependent on the GPU?

Sure. However you are still using Mesa from oss instead of packman. You need to switch to packman.

[riptide1]

Hmm, that makes sense. Thank you very much!

Are the OpenGL warning present for you too?

[riptide1]

from what I can see, eglinfo should be run in a tty (it needs exclusive access to the gpu) to work properly. I ran it that way and don’t see any errors.

My actual GPU comes up as Device #0, with the kms_swrast being #1. Is this expected as some sort of software rendering fallback?

Can somebody please check and confirm this?

[panorain]

@riptide1

from what I can see, eglinfo should be run in a tty

eglinfo shows output when entered into Konsole here (as user non-root).

inxi -GSaz

API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1
    drv: swrast gbm: drv: kms_swrast surfaceless: drv: r600 wayland: drv: r600
    x11: drv: r600

Perhaps the machine is in software rendering mode?

Some information on that:
Fix software rendering fallback:

Remove entry:
   [QtQuickRendererSettings]
   SceneGraphBackend=software 
From: /home/user/.config/kdeglobals

Or

Pass as user > kcmshell6 qtquicksettings

[riptide1]

inxi -GSaz

  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
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.1 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM
    3.64 6.18.2-1-default) device-ID: 1002:15e7 memory: 1.95 GiB unified: no
    display-ID: :1.0
  API: Vulkan v: 1.4.335 layers: 1 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: mesa radv v: 25.3.1
    device-ID: 1002:15e7 surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 21.1.7 256 bits) driver: mesa

eglinfo indeed works in konsole without root for me too. I thought running it in a tty was needed for proper results.

SceneGraphBackend isn’t there in the file for me, however I did set the rendering backend as Vulkan in kcmshell6 qtquicksettings.

[panorain]

@riptide1

Are the OpenGL warning present for you too?

HP-Pavilion-g6:~> glxinfo | grep 'OpenGL renderer string'
OpenGL renderer string: AMD ARUBA (DRM 2.51.0 / 6.18.2-6.gda42972-default, LLVM 21.1.6)
HP-Pavilion-g6:~>

[riptide1]

glxinfo | grep 'OpenGL renderer string'

OpenGL renderer string: AMD Radeon Graphics (radeonsi, renoir, ACO, DRM 3.64, 6.18.2-1-default)

I guess having another software rendering device #1 is normal after all. Playing a high resolution video also shows GPU usage in amdgpu_top.

Looks like the SDDM problem is something else entirely then.