MESA using LLVMPIPE instead of the Graphics Hardware

Just to update:

I have been busy with a lot of things, and still now I can’t work on it.

I didn’t forget tho.

Gonna follow those instructions as soon as I can.

@leorize , I’ve managed to run the commands yesterday, but for personal reasons I am making this message just now.


So, here’s the before values:

~$ inxi -Fzxx
System:
 Kernel: 6.16.3-200.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
 Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
   Distro: Fedora Linux 42 (KDE Plasma Desktop Edition)
Machine:
 Type: Desktop Mobo: ASUSTeK model: A88XM-A/USB 3.1 v: Rev X.0x
   serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 0309
   date: 03/04/2016
CPU:
 Info: quad core model: AMD A10-7870K Radeon R7 12 Compute Cores 4C+8G
   bits: 64 type: MCP arch: Steamroller rev: 1 cache: L1: 256 KiB L2: 4 MiB
 Speed (MHz): avg: 2992 min/max: 1700/3900 boost: enabled cores: 1: 2992
   2: 2992 3: 2992 4: 2992 bogomips: 31121
 Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
 Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
   vendor: ASUSTeK driver: radeon v: kernel arch: GCN-2 ports: active: HDMI-A-1
   empty: DVI-D-1,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:130f
 Display: wayland server: Xwayland v: 24.1.8 compositor: kwin_wayland
   driver: gpu: radeon display-ID: 0
 Monitor-1: HDMI-A-1 model: LG (GoldStar) TV res: 1360x768 hz: 60 dpi: 22
   diag: 1836mm (72.3")
 API: EGL v: 1.5 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.5 vendor: amd mesa v: 25.1.7 glx-v: 1.4
   direct-render: yes renderer: KAVERI (radeonsi ACO DRM 2.50
   6.16.3-200.fc42.x86_64) device-ID: 1002:130f display-ID: :0.0
 API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: cpu
   driver: mesa llvmpipe device-ID: 10005:0000
 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
   de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
   xdpyinfo, xprop, xrandr
Audio:
 Device-1: Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio
   vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:01.1
   chip-ID: 1002:1308
 Device-2: Advanced Micro Devices [AMD] FCH Azalia vendor: ASUSTeK
   driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1022:780d
 API: ALSA v: k6.16.3-200.fc42.x86_64 status: kernel-api
 Server-1: PipeWire v: 1.4.7 status: active with: 1: pipewire-pulse
   status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
   4: pw-jack type: plugin
Network:
 Device-1: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee
   v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
   chip-ID: 10ec:818b
 IF: wlp3s0 state: up mac: <filter>
 Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
   vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: speed: 2.5 GT/s
   lanes: 1 port: d000 bus-ID: 04:00.0 chip-ID: 10ec:8168
 IF: enp4s0 state: down mac: <filter>
Drives:
 Local Storage: total: 1.02 TiB used: 254.8 GiB (24.4%)
 ID-1: /dev/sda vendor: Kingston model: SA400S37120G size: 111.79 GiB
   speed: 6.0 Gb/s serial: <filter> temp: 36 C
 ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
   speed: 6.0 Gb/s serial: <filter>
Partition:
 ID-1: / size: 110.2 GiB used: 50.86 GiB (46.1%) fs: btrfs dev: /dev/sda3
 ID-2: /boot size: 973.4 MiB used: 477.6 MiB (49.1%) fs: ext4
   dev: /dev/sda2
 ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
   dev: /dev/sda1
 ID-4: /home size: 110.2 GiB used: 50.86 GiB (46.1%) fs: btrfs
   dev: /dev/sda3
Swap:
 ID-1: swap-1 type: zram size: 6.7 GiB used: 1.81 GiB (27.0%) priority: 100
   dev: /dev/zram0
Sensors:
 System Temperatures: cpu: 35.8 C mobo: N/A gpu: radeon temp: 28.0 C
 Fan Speeds (rpm): N/A
Info:
 Memory: total: 8 GiB note: est. available: 6.7 GiB used: 3.22 GiB (48.1%)
 Processes: 307 Power: uptime: 24m wakeups: 0 Init: systemd v: 257
   target: graphical (5) default: graphical
 Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 15
   Compilers: N/A Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.38

And here’s the after values:

~$ inxi -Fzxx
System:
 Kernel: 6.16.3-200.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
 Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
   Distro: Fedora Linux 42 (KDE Plasma Desktop Edition)
Machine:
 Type: Desktop Mobo: ASUSTeK model: A88XM-A/USB 3.1 v: Rev X.0x
   serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 0309
   date: 03/04/2016
CPU:
 Info: quad core model: AMD A10-7870K Radeon R7 12 Compute Cores 4C+8G
   bits: 64 type: MCP arch: Steamroller rev: 1 cache: L1: 256 KiB L2: 4 MiB
 Speed (MHz): avg: 1694 min/max: 1700/3900 boost: enabled cores: 1: 1694
   2: 1694 3: 1694 4: 1694 bogomips: 31122
 ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
   speed: 6.0 Gb/s serial: <filter>
Partition:
 ID-1: / size: 110.2 GiB used: 50.85 GiB (46.1%) fs: btrfs dev: /dev/sda3
 ID-2: /boot size: 973.4 MiB used: 477.6 MiB (49.1%) fs: ext4
   dev: /dev/sda2
 ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
   dev: /dev/sda1
 ID-4: /home size: 110.2 GiB used: 50.85 GiB (46.1%) fs: btrfs
   dev: /dev/sda3
Swap:
 ID-1: swap-1 type: zram size: 6.7 GiB used: 1.04 GiB (15.5%) priority: 100
   dev: /dev/zram0
Sensors:
 System Temperatures: cpu: 47.2 C mobo: N/A gpu: radeon temp: 50.0 C
 Fan Speeds (rpm): N/A
Info:
 Memory: total: 8 GiB note: est. available: 6.7 GiB used: 2.91 GiB (43.4%)
 Processes: 322 Power: uptime: 3m wakeups: 0 Init: systemd v: 257
   target: graphical (5) default: graphical
 Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 15
   Compilers: N/A Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.38

Here’s a screenshot of the “after alone” of VKcube.
Nothing changed, so uploading the different one is a waste of internet.

Still, for Vulkan it says “LLVMPIPE” and also renders it in Software for games (Quake Remaster goes max 15fps in the menu’s demo and 5 to 7 when in the HUB).
For OpenGL games like Portal_1 it says “KAVERI” and runs at decent, even if poor, performance.

At least, instead of sudo grubby --args=radeon.cik_support=0 --args=amdgpu.cik_support=1 --update-kernel=ALL

please give a try to sudo grubby --args="radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1" --update-kernel=ALL,

it works for me.

After reboot, verify with sudo grubby --info=ALL

The grubby man page confirms that --args accepts a space-separated list of kernel parameters, and using quotes ensures the shell passes them as a single argument.

Quotes: The command uses quotes around the --args value, which is critical to prevent shell misparsing. Without quotes, the shell would interpret the space-separated parameters as separate arguments, causing grubby to fail or apply only the first parameter.

Multiple --args options are not guaranteed to merge correctly in all grubby versions. The man page suggests parameters are combined, but in practice, later --args may overwrite earlier ones or cause parsing issues, depending on the grubby implementation or user error (e.g., running as separate commands).

Looks like I was late to the party and the paste expired already :frowning:

If you have a GitHub account, can you post the content as a GitHub Gist instead? That would last forever instead.

Re: inxi -Fzxx values after applying the command, it is interesting that the “Graphics” section disappeared. There might be an issue with your installation, but I can’t diagnose further without the (now expired) logs.

Really funny busyness here.
Does the website even warn that the link expires the third day?

Whatever.

I will try running a Fedora 42 install USB to see if it can run VKcube with Vulkan, but then again, it shouldn’t.
This guy says that “he can just run the R9 390 without issue”.

@leorize , I am gonna open this comment with a recap of the issue from the beginning:

It was Fedora 39; Mesa was 24. Vulkan worked.
Mesa 25 came and Vulkan didn’t work, Software Rendering was so bad that even the desktop would render at 20fps if above 800x600.
A small update came out, stuff seemed fixed, then it either broke again or was never truly fixed.

We come to now. For almost 40 days I was “busy” so just lately I managed to answer back.

Here are the datapoints needed.


I also ran a Live USB of Fedora 42.

Altho MangoHUD’s way to show data seems to be inconsistent on this PC alone (here[1] it literally just says “FPS” instead of “VULKAN” or “VK”, never have I seen that anywhere else) I believe it just means “Vulkan rendered through LLVMPIPE”, which means “Software rendered Vulkan”.


Since I want to avoid doing THIS and I want to understand why and how this stuff isn’t working, I wanna try fix this before doing ^that^.



I love character limits.


The “after” results:

https://paste.centos.org/view/c01afb3b

Here’s the txt version:


Here’s the Live:
https://paste.centos.org/view/df7d30fe

Here’s the txt version:

liveuser@localhost-live:~$ inxi -Fzxx
System:
  Kernel: 6.14.0-63.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.0.1
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 42 (KDE Plasma Desktop Edition)
Machine:
  Type: Desktop Mobo: ASUSTeK model: A88XM-A/USB 3.1 v: Rev X.0x
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 0309
    date: 03/04/2016
CPU:
  Info: quad core model: AMD A10-7870K Radeon R7 12 Compute Cores 4C+8G
    bits: 64 type: MCP arch: Steamroller rev: 1 cache: L1: 256 KiB L2: 4 MiB
  Speed (MHz): avg: 1694 min/max: 1700/3900 boost: enabled cores: 1: 1694
    2: 1694 3: 1694 4: 1694 bogomips: 31119
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
    vendor: ASUSTeK driver: radeon v: kernel arch: GCN-2 ports: active: HDMI-A-1
    empty: DVI-D-1,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:130f
  Display: wayland server: Xwayland v: 24.1.6 compositor: kwin_wayland
    driver: gpu: radeon display-ID: 0
  Monitor-1: HDMI-A-1 model: LG (GoldStar) TV res: 1360x768 hz: 60 dpi: 22
    diag: 1836mm (72.3")
  API: EGL v: 1.5 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.5 vendor: amd mesa v: 25.0.2 glx-v: 1.4
    direct-render: yes renderer: KAVERI (radeonsi ACO DRM 2.50
    6.14.0-63.fc42.x86_64) device-ID: 1002:130f display-ID: :0.0
  API: Vulkan v: 1.4.304 surfaces: xcb,xlib,wayland device: 0 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:01.1
    chip-ID: 1002:1308
  Device-2: Advanced Micro Devices [AMD] FCH Azalia vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1022:780d
  API: ALSA v: k6.14.0-63.fc42.x86_64 status: kernel-api
  Server-1: 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
Network:
  Device-1: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
    chip-ID: 10ec:818b
  IF: wlp3s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 04:00.0 chip-ID: 10ec:8168
  IF: enp4s0 state: down mac: <filter>
Drives:
  Local Storage: total: 1.03 TiB used: 203.46 GiB (19.2%)
  ID-1: /dev/sda vendor: Kingston model: SA400S37120G size: 111.79 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
    speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdc vendor: Generic model: Flash Disk size: 15.23 GiB type: USB
    rev: 2.0 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 1.34 GiB used: 594.5 MiB (43.3%) fs: overlay source: ERR-102
Swap:
  ID-1: swap-1 type: zram size: 6.7 GiB used: 1.43 GiB (21.4%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 40.5 C mobo: N/A gpu: radeon temp: 28.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 6.7 GiB used: 2.81 GiB (41.9%)
  Processes: 278 Power: uptime: 9m wakeups: 0 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: N/A Shell: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.38

Here you can see “Vulkan” is the name given to “what is rendering it”.
[It was just VULKAN with the default MangoHUD settings, but by selecting more stuff I can see it still using LLVMPIPE here, even if everything else seems to at least recognize KAVERI…]


  1. ↩︎

Thanks for the logs.

So from this line:

[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.16.3-200.fc42.x86_64 root=UUID=7f057b81-3dff-433a-8a84-acceb76fd6b3 ro rootflags=subvol=root rhgb quiet amdgpu.cik_support=1

It appears that radeon.cik_support=0 is missing from the kernel command line, which meant the legacy radeon driver is still controlling your GPU instead of amdgpu.

I’d say to give @josevillani instructions a try and see if the required kernel arguments show up:

Please send logs again after you tried this, thanks!

I’ll try tomorrow.

Still, I don’t like to run things I don’t understand like this for the reasons I gave above.

Regardless, might as well at least try, since nothing important is on that PC.

I’ve had a bad and busy week. Here’s the stuff:

~$ sudo grubby --info=ALL
[sudo] password di X:
index=0
kernel="/boot/vmlinuz-6.16.5-200.fc42.x86_64"
args="ro rootflags=subvol=root rhgb quiet $tuned_params radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1"
root="UUID=7f057b81-3dff-433a-8a84-acceb76fd6b3"
initrd="/boot/initramfs-6.16.5-200.fc42.x86_64.img $tuned_initrd"
title="Fedora Linux (6.16.5-200.fc42.x86_64) 42 (KDE Plasma Desktop Edition)"
id="50c8efd42c5f4ed6a9de26633f1988e7-6.16.5-200.fc42.x86_64"
index=1
kernel="/boot/vmlinuz-6.16.3-200.fc42.x86_64"
args="ro rootflags=subvol=root rhgb quiet $tuned_params radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1"
root="UUID=7f057b81-3dff-433a-8a84-acceb76fd6b3"
initrd="/boot/initramfs-6.16.3-200.fc42.x86_64.img $tuned_initrd"
title="Fedora Linux (6.16.3-200.fc42.x86_64) 42 (KDE Plasma Desktop Edition)"
id="50c8efd42c5f4ed6a9de26633f1988e7-6.16.3-200.fc42.x86_64"
index=2
kernel="/boot/vmlinuz-6.15.6-200.fc42.x86_64"
args="ro rootflags=subvol=root rhgb quiet $tuned_params radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1"
root="UUID=7f057b81-3dff-433a-8a84-acceb76fd6b3"
initrd="/boot/initramfs-6.15.6-200.fc42.x86_64.img $tuned_initrd"
title="Fedora Linux (6.15.6-200.fc42.x86_64) 42 (KDE Plasma Desktop Edition)"
id="50c8efd42c5f4ed6a9de26633f1988e7-6.15.6-200.fc42.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-50c8efd42c5f4ed6a9de26633f1988e7"
args="ro rootflags=subvol=root rhgb quiet radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1"
root="UUID=7f057b81-3dff-433a-8a84-acceb76fd6b3"
initrd="/boot/initramfs-0-rescue-50c8efd42c5f4ed6a9de26633f1988e7.img"
title="Fedora Linux (0-rescue-50c8efd42c5f4ed6a9de26633f1988e7) 40 (KDE Plasma)"

I’ve been busy today, and right now I am TIRED.

I can’t articulate very well what I want to say, so I’m just gonna drop this here:

Thank you people for the hands given, even if I’d’ve liked a little more info about what these magic spells do.
Now my Kaveri/Godavari iGPU seems to work somewhat better AND to use Vulkan without LLVMPIPE (meaning that it’s not Software Mode).
After using a lot of > " < and wording the sentence appropiately I got Wikipedia’d into a very barebone page which would have been useless without what I barely learn’t here because these things are just not spelled out anywhere.

tl;dr it seems that my hardware is “partially supported” by a software which has been in development for the last 11 years.

I have no reason to close the thread right now. If anything I have a very good reason I should not:
I am very TIRED and should stop think about things right now. It’s 19 hours since I got out of bed.

Glad you finally did it. That’s what I’ve been telling you 4 months ago there and again there. I was not going to let you down on this when the solution was known. Best!

I have been trying to benchmark some games these last two weeks, but due to poor health and “issues with the computer” it’s not going as smooth as it should.

I just don’t want to not post any update at all on this page, evenmore because W10 support died yesterday, literally.

tl;dr

Both W10 and Fedora KDE are not good-to-perfect experiences because of bugs and strange lacks of support for the monitors’ resolutions.
On W10 it’s WAY easier to set up a custom resolution compared to Wayland[1] but, I am going to be honest, this APU is almost 10 years old and will die soon if anyone were to seriously use this as a daily driver.
When I will be done, I’ll upload the results of the benchmark and the updated data, but for now I can not set this issue as “solved” because I can’t actually test everything right now.

The “fix” up there “works”, but other than “working” I can’t say anything else for certain…


  1. X11 is and will remain dead. It can obviously still be used, evenmore for the non-modern, non-gaming distros, it may even be a better option, but mainstream Distros are and will be on Wayland now. ↩︎

I have to close this as “fixed” even if “the fix can’t be perfect”…

Long story short:
The “ATI (radeon)” driver doesn’t support Vulkan.
The “amdgpu” driver doesn’t work well with GCN 1, 2 and 3 cards, and therefore is off by default.
In this issue my PC had problems turning ATI off.

I can’t say stuff for GCN 4 and 5 because I have no personal experience with them, and heard nobody really having any issues.


This comment down here

shows that stuff “works” thanks to this

action.


I made a new page on this Forum (about this problem) which is somewhat of a basic guide, which contains the problems I have been having throughout these last years with this iGPU.

If I will need to open a new issue about this CPU+iGPU in particular then I will, but if I wont then this issue and that “guide” will be everything that’s needed to know and/or necessary to solve your problems.