A10-7870k GPU integrated graphics not working ANYMORE

[isaac0clarke (Isaac Clarke)]

Hello.
I have a A10-7870K PC.
Up to a month ago its integrated graphics (family Kaveri) still managed to accelerate Fedora KDE’s stuff, now no more.
(The CPU is software-rendering with “llvmpipe”.)
.
I have edited this opening post to explain the solution in the opening here:
The hardware was not the problem BOTH because changing BIOS settings for the Integrated Graphics does nothing AND because running the same Installer USB I’ve used to install Fedora KDE on that one same computer results in the iGPU being used correctly.
It seems that there is a “bug” in Mesa 25 where the Kaveri graphics (at least with iGPUs) are not supported, falling back to Software Rendering.
I downgraded back to Mesa 24.2.x (more later in the post) and now it works like before.
.
.
.
Here’s the copy-pasted hardware stuff

~$ inxi -Fzxx
System:
  Kernel: 6.13.5-200.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 41 (KDE Plasma)
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: 3891 min/max: 1700/3900 boost: enabled cores: 1: 3891
    2: 3891 3: 3891 4: 3891 bogomips: 31125
  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: gbm: drv: kms_swrast surfaceless: drv: swrast
    wayland: drv: swrast x11: drv: swrast
  API: OpenGL v: 4.5 vendor: mesa v: 25.0.0 glx-v: 1.4 direct-render: yes
    renderer: llvmpipe (LLVM 19.1.7 256 bits) device-ID: ffffffff:ffffffff
    display-ID: :0.0
  API: Vulkan v: 1.4.304 surfaces: xcb,xlib,wayland device: 0 type: cpu
    driver: N/A 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.13.5-200.fc41.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.2.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 RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 04:00.0 chip-ID: 10ec:8168
  IF: enp4s0 state: down mac: <filter>
  Device-2: TP-Link TL-WN823N v2/v3 [Realtek RTL8192EU] driver: rtl8xxxu
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 5-2:2 chip-ID: 2357:0109
  IF: wlp0s16f0u2 state: up mac: <filter>
Drives:
  Local Storage: total: 1.24 TiB used: 97.28 GiB (7.6%)
  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: Kingston model: DataTraveler 3.0 size: 230.94 GiB
    type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 110.2 GiB used: 8.26 GiB (7.5%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 973.4 MiB used: 412.7 MiB (42.4%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 598.8 MiB used: 19.4 MiB (3.2%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 110.2 GiB used: 8.26 GiB (7.5%) fs: btrfs dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 5.71 GiB used: 512 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 38.9 C mobo: N/A gpu: radeon temp: 44.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 6 GiB available: 5.71 GiB used: 3.32 GiB (58.1%)
  Processes: 317 Power: uptime: 2m wakeups: 0 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 14
    Compilers: N/A Shell: Bash v: 5.2.32 running-in: konsole inxi: 3.3.37

.
.
I have looked up some other people with similar hardware and similar problems on this forum:

Case 1 was an honest stroke of luck for me. The post was made not even 2 days before I once more searched the web for help and so I found it.
The problem is similar to mine: “From the Install USB the graphic drivers work with the iGPU, after the update they don’t anymore.”
Here too the iGPU is Kavery, but the CPU is AMD A10-7800.
The fix didn’t INITIALLY work in my case, which brought me to google some more, bringing me to find →

Case 2 says that “a friend couldn’t downgrade”, so he had to use the “Solution” in its page here.
I don’t have the exact Konsole message here (didn’t copy it when the problem persisted) so I can’t exactly recall it, but the point is the computer said that “mesa is an unknown #something#”.
Now (yesterday, 20 march) that I used the sudo dnf downgrade mesa* command again, it downgraded from 25.x to 24.2.x, meaning that I don’t need to do anything from Case 2.
.
.
.
.
.
CLOSING WORDS

~$ sudo dnf downgrade mesa*
[sudo] password di ########:  
Aggiornamento e caricamento dei repository:
Repository caricati.
The lowest available version of the "mesa-demos.x86_64" package is already installed, cannot dow
ngrade it.
The lowest available version of the "mesa-libGLU.x86_64" package is already installed, cannot do
wngrade it.

Package                           Arch    Version                       Repository          Size
Downgrading:
mesa-dri-drivers                 i686    24.2.4-1.fc41                 fedora         149.9 MiB
  replacing mesa-dri-drivers     i686    25.0.1-2.fc41                 updates        168.6 MiB
mesa-dri-drivers                 x86_64  24.2.4-1.fc41                 fedora         142.2 MiB
  replacing mesa-dri-drivers     x86_64  25.0.1-2.fc41                 updates        160.6 MiB
mesa-filesystem                  i686    24.2.4-1.fc41                 fedora           3.6 KiB
  replacing mesa-filesystem      i686    25.0.1-2.fc41                 updates          3.6 KiB
mesa-filesystem                  x86_64  24.2.4-1.fc41                 fedora           3.6 KiB
  replacing mesa-filesystem      x86_64  25.0.1-2.fc41                 updates          3.6 KiB
mesa-libEGL                      i686    24.2.4-1.fc41                 fedora         366.8 KiB
  replacing mesa-libEGL          i686    25.0.1-2.fc41                 updates        354.6 KiB
mesa-libEGL                      x86_64  24.2.4-1.fc41                 fedora         340.2 KiB
  replacing mesa-libEGL          x86_64  25.0.1-2.fc41                 updates        335.9 KiB
mesa-libGL                       i686    24.2.4-1.fc41                 fedora         492.7 KiB
  replacing mesa-libGL           i686    25.0.1-2.fc41                 updates        452.1 KiB
mesa-libGL                       x86_64  24.2.4-1.fc41                 fedora         457.8 KiB
  replacing mesa-libGL           x86_64  25.0.1-2.fc41                 updates        424.9 KiB
mesa-libgbm                      i686    24.2.4-1.fc41                 fedora          68.3 KiB
  replacing mesa-libgbm          i686    25.0.1-2.fc41                 updates         23.2 KiB
mesa-libgbm                      x86_64  24.2.4-1.fc41                 fedora          69.3 KiB
  replacing mesa-libgbm          x86_64  25.0.1-2.fc41                 updates         24.0 KiB
mesa-va-drivers                  i686    24.2.4-1.fc41                 fedora          92.0   B
  replacing mesa-va-drivers      i686    25.0.1-2.fc41                 updates         92.0   B
mesa-va-drivers                  x86_64  24.2.4-1.fc41                 fedora          92.0   B
  replacing mesa-va-drivers      x86_64  25.0.1-2.fc41                 updates         92.0   B
mesa-vulkan-drivers              i686    24.2.4-1.fc41                 fedora         102.0 MiB
  replacing mesa-vulkan-drivers  i686    25.0.1-2.fc41                 updates        116.7 MiB
mesa-vulkan-drivers              x86_64  24.2.4-1.fc41                 fedora          98.3 MiB
  replacing mesa-vulkan-drivers  x86_64  25.0.1-2.fc41                 updates        112.7 MiB
Installing dependencies:
mesa-libglapi                    i686    24.2.4-1.fc41                 fedora         147.8 KiB
mesa-libglapi                    x86_64  24.2.4-1.fc41                 fedora         172.4 KiB

Transaction Summary:
Installing:         2 packages
Replacing:         14 packages
Downgrading:       14 packages

Total size of inbound packages is 95 MiB. Need to download 95 MiB.
After this operation, 66 MiB will be freed (install 494 MiB, remove 560 MiB).
Is this ok [y/N]: y
[ 1/16] mesa-libglapi-0:24.2.4-1.fc41.x86_64            100% | 109.5 KiB/s |  51.4 KiB |  00m00s
[ 2/16] mesa-libglapi-0:24.2.4-1.fc41.i686              100% | 104.2 KiB/s |  52.0 KiB |  00m00s
[ 3/16] mesa-filesystem-0:24.2.4-1.fc41.i686            100% | 216.2 KiB/s |  21.2 KiB |  00m00s
[ 4/16] mesa-filesystem-0:24.2.4-1.fc41.x86_64          100% |  58.5 KiB/s |  21.2 KiB |  00m00s
[ 5/16] mesa-libEGL-0:24.2.4-1.fc41.x86_64              100% | 293.4 KiB/s | 144.6 KiB |  00m00s
[ 6/16] mesa-libEGL-0:24.2.4-1.fc41.i686                100% | 472.1 KiB/s | 158.2 KiB |  00m00s
[ 7/16] mesa-libGL-0:24.2.4-1.fc41.x86_64               100% | 359.3 KiB/s | 176.8 KiB |  00m00s
[ 8/16] mesa-libGL-0:24.2.4-1.fc41.i686                 100% | 311.6 KiB/s | 190.4 KiB |  00m01s
[ 9/16] mesa-libgbm-0:24.2.4-1.fc41.x86_64              100% | 438.3 KiB/s |  48.2 KiB |  00m00s
[10/16] mesa-libgbm-0:24.2.4-1.fc41.i686                100% | 167.6 KiB/s |  50.3 KiB |  00m00s
[11/16] mesa-va-drivers-0:24.2.4-1.fc41.x86_64          100% |  60.1 KiB/s |  19.9 KiB |  00m00s
[12/16] mesa-va-drivers-0:24.2.4-1.fc41.i686            100% |  91.6 KiB/s |  19.9 KiB |  00m00s
[13/16] mesa-vulkan-drivers-0:24.2.4-1.fc41.x86_64      100% | 354.8 KiB/s |  17.1 MiB |  00m49s
[14/16] mesa-dri-drivers-0:24.2.4-1.fc41.x86_64         100% | 527.3 KiB/s |  28.5 MiB |  00m55s
[15/16] mesa-dri-drivers-0:24.2.4-1.fc41.i686           100% | 457.4 KiB/s |  30.4 MiB |  01m08s
[16/16] mesa-vulkan-drivers-0:24.2.4-1.fc41.i686        100% | 719.2 KiB/s |  18.1 MiB |  00m26s
------------------------------------------------------------------------------------------------
[16/16] Total                                           100% |   1.2 MiB/s |  95.0 MiB |  01m19s
Transazione in corso
[ 1/32] Verificare i file del pacchetto                 100% |  19.0   B/s |  16.0   B |  00m01s
[ 2/32] Preparare la transazione                        100% |  26.0   B/s |  30.0   B |  00m01s
[ 3/32] Downgrade di mesa-filesystem-0:24.2.4-1.fc41.x8 100% |  69.2 KiB/s |   4.3 KiB |  00m00s
[ 4/32] Downgrade di mesa-libgbm-0:24.2.4-1.fc41.x86_64 100% |   3.6 MiB/s |  70.1 KiB |  00m00s
[ 5/32] Downgrade di mesa-dri-drivers-0:24.2.4-1.fc41.x 100% |  97.4 MiB/s | 142.2 MiB |  00m01s
[ 6/32] Installazione di mesa-libglapi-0:24.2.4-1.fc41. 100% |  10.6 MiB/s | 173.2 KiB |  00m00s
[ 7/32] Downgrade di mesa-filesystem-0:24.2.4-1.fc41.i6 100% | 612.7 KiB/s |   4.3 KiB |  00m00s
[ 8/32] Downgrade di mesa-va-drivers-0:24.2.4-1.fc41.i6 100% |  98.6 KiB/s | 808.0   B |  00m00s
[ 9/32] Downgrade di mesa-libEGL-0:24.2.4-1.fc41.x86_64 100% |  11.1 MiB/s | 341.2 KiB |  00m00s
[10/32] Downgrade di mesa-libGL-0:24.2.4-1.fc41.x86_64  100% |   6.1 MiB/s | 458.7 KiB |  00m00s
[11/32] Downgrade di mesa-va-drivers-0:24.2.4-1.fc41.x8 100% |  72.1 KiB/s | 812.0   B |  00m00s
[12/32] Downgrade di mesa-vulkan-drivers-0:24.2.4-1.fc4 100% | 101.0 MiB/s |  98.3 MiB |  00m01s
[13/32] Downgrade di mesa-libgbm-0:24.2.4-1.fc41.i686   100% |   3.6 MiB/s |  69.1 KiB |  00m00s
[14/32] Downgrade di mesa-dri-drivers-0:24.2.4-1.fc41.i 100% | 108.8 MiB/s | 149.9 MiB |  00m01s
[15/32] Installazione di mesa-libglapi-0:24.2.4-1.fc41. 100% |   6.6 MiB/s | 148.6 KiB |  00m00s
[16/32] Downgrade di mesa-libEGL-0:24.2.4-1.fc41.i686   100% |   4.9 MiB/s | 367.8 KiB |  00m00s
[17/32] Downgrade di mesa-libGL-0:24.2.4-1.fc41.i686    100% |  23.0 MiB/s | 493.6 KiB |  00m00s
[18/32] Downgrade di mesa-vulkan-drivers-0:24.2.4-1.fc4 100% |  91.7 MiB/s | 102.0 MiB |  00m01s
[19/32] Rimozione di mesa-libEGL-0:25.0.1-2.fc41.i686   100% | 127.0   B/s |   6.0   B |  00m00s
[20/32] Rimozione di mesa-libEGL-0:25.0.1-2.fc41.x86_64 100% |  90.0   B/s |   6.0   B |  00m00s
[21/32] Rimozione di mesa-libGL-0:25.0.1-2.fc41.i686    100% | 352.0   B/s |   6.0   B |  00m00s
[22/32] Rimozione di mesa-libGL-0:25.0.1-2.fc41.x86_64  100% | 400.0   B/s |   6.0   B |  00m00s
[23/32] Rimozione di mesa-libgbm-0:25.0.1-2.fc41.i686   100% | 217.0   B/s |   5.0   B |  00m00s
[24/32] Rimozione di mesa-dri-drivers-0:25.0.1-2.fc41.i 100% |   4.5 KiB/s | 101.0   B |  00m00s
[25/32] Rimozione di mesa-vulkan-drivers-0:25.0.1-2.fc4 100% |   1.4 KiB/s |  47.0   B |  00m00s
[26/32] Rimozione di mesa-va-drivers-0:25.0.1-2.fc41.i6 100% | 500.0   B/s |   4.0   B |  00m00s
[27/32] Rimozione di mesa-va-drivers-0:25.0.1-2.fc41.x8 100% | 363.0   B/s |   4.0   B |  00m00s
[28/32] Rimozione di mesa-libgbm-0:25.0.1-2.fc41.x86_64 100% | 250.0   B/s |   4.0   B |  00m00s
[29/32] Rimozione di mesa-dri-drivers-0:25.0.1-2.fc41.x 100% |   2.7 KiB/s | 102.0   B |  00m00s
[30/32] Rimozione di mesa-vulkan-drivers-0:25.0.1-2.fc4 100% |   2.0 KiB/s |  48.0   B |  00m00s
[31/32] Rimozione di mesa-filesystem-0:25.0.1-2.fc41.x8 100% | 307.0   B/s |   4.0   B |  00m00s
[32/32] Rimozione di mesa-filesystem-0:25.0.1-2.fc41.i6 100% |   0.0   B/s |   4.0   B |  00m06s
Complete!

///
##
///

~$ sudo dnf update --refresh --exclude=mesa*
Aggiornamento e caricamento dei repository:
Fedora 41 openh264 (From Cisco) - x86_64               100% |   5.1 KiB/s | 989.0   B |  00m00s
Brave Browser                                          100% |  13.7 KiB/s |   2.0 KiB |  00m00s
Fedora 41 - x86_64 - Updates                           100% | 121.4 KiB/s |  23.7 KiB |  00m00s
Fedora 41 - x86_64                                     100% |  42.3 KiB/s |  26.8 KiB |  00m01s
RPM Fusion for Fedora 41 - Free                        100% |  17.2 KiB/s |   8.9 KiB |  00m01s
RPM Fusion for Fedora 41 - Free - Updates              100% |  18.9 KiB/s |   8.8 KiB |  00m00s
RPM Fusion for Fedora 41 - Nonfree - NVIDIA Driver     100% |  40.4 KiB/s |   9.7 KiB |  00m00s
RPM Fusion for Fedora 41 - Nonfree - Steam             100% |  18.9 KiB/s |   9.3 KiB |  00m00s
RPM Fusion for Fedora 41 - Nonfree - Updates           100% |  40.5 KiB/s |   9.4 KiB |  00m00s
RPM Fusion for Fedora 41 - Nonfree                     100% |  63.2 KiB/s |   9.5 KiB |  00m00s
Repository caricati.
Problem: installed package steam-1.0.0.82-1.fc41.i686 requires steam-devices = 1.0.0.82-1.fc41,
but none of the providers can be installed
 - cannot install both steam-devices-1.0.0.101^git20240522.e2971e4-2.fc41.noarch from updates a
nd steam-devices-1.0.0.82-1.fc41.i686 from @System
 - package steam-devices-1.0.0.101^git20240522.e2971e4-2.fc41.noarch from updates obsoletes ste
am-devices < 1.0.0.101^git20240522.e2971e4-2.fc41 provided by steam-devices-1.0.0.82-1.fc41.i686
from @System
 - cannot install both steam-devices-1.0.0.82-1.fc41.i686 from rpmfusion-nonfree-steam and stea
m-devices-1.0.0.101^git20240522.e2971e4-2.fc41.noarch from updates
 - package steam-devices-1.0.0.101^git20240522.e2971e4-2.fc41.noarch from updates obsoletes ste
am-devices < 1.0.0.101^git20240522.e2971e4-2.fc41 provided by steam-devices-1.0.0.82-1.fc41.i686
from rpmfusion-nonfree-steam
 - cannot install both steam-devices-1.0.0.82-1.fc41.i686 from rpmfusion-nonfree-updates and st
eam-devices-1.0.0.101^git20240522.e2971e4-2.fc41.noarch from updates
 - package steam-devices-1.0.0.101^git20240522.e2971e4-2.fc41.noarch from updates obsoletes ste
am-devices < 1.0.0.101^git20240522.e2971e4-2.fc41 provided by steam-devices-1.0.0.82-1.fc41.i686
from rpmfusion-nonfree-updates
 - cannot install the best update candidate for package steam-devices-1.0.0.82-1.fc41.i686
 - cannot install the best update candidate for package steam-1.0.0.82-1.fc41.i686

Package                     Arch    Version                               Repository        Size
Skipping packages with conflicts:
steam-devices              noarch  1.0.0.101^git20240522.e2971e4-2.fc41  updates       10.1 KiB

Nothing to do.

.

.
It happens that “the more complex problem” fixed itself on its own, and so to even attempt to reproduce it (I don’t want to because I lack the free time to) I’d have to rely on luck too.
.
I hope that this bug gets fixed in the future, I may try to update Mesa again in a couple of months, but for now I am done.
.
Thank you to all who helped, both directly and indirectly.
.
(P.S.: I have no idea what Steam is doing with its updates on Fedora and I don’t want to care until it becomes a problem. It says the same thing on all my PCs.)

[barryascott]

Please install inxi and post the output of inxi -Fzxx as pre-formatted text.
This will tell us key information about your hardware and software.

[isaac0clarke (Isaac Clarke)]

Here it is.

I am not expecting “a solution to come fast” because I am the first one which can’t do this stuff quickly.
(Btw I am changing the title of the problem because the CPU was not the “A10-7850K”, I made a typo.)

BEGINNING OF DATA

~$ inxi -Fzxx
System:
  Kernel: 6.13.5-200.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 41 (KDE Plasma)
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: 3891 min/max: 1700/3900 boost: enabled cores: 1: 3891
    2: 3891 3: 3891 4: 3891 bogomips: 31125
  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: gbm: drv: kms_swrast surfaceless: drv: swrast
    wayland: drv: swrast x11: drv: swrast
  API: OpenGL v: 4.5 vendor: mesa v: 25.0.0 glx-v: 1.4 direct-render: yes
    renderer: llvmpipe (LLVM 19.1.7 256 bits) device-ID: ffffffff:ffffffff
    display-ID: :0.0
  API: Vulkan v: 1.4.304 surfaces: xcb,xlib,wayland device: 0 type: cpu
    driver: N/A 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.13.5-200.fc41.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.2.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 RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 04:00.0 chip-ID: 10ec:8168
  IF: enp4s0 state: down mac: <filter>
  Device-2: TP-Link TL-WN823N v2/v3 [Realtek RTL8192EU] driver: rtl8xxxu
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 5-2:2 chip-ID: 2357:0109
  IF: wlp0s16f0u2 state: up mac: <filter>
Drives:
  Local Storage: total: 1.24 TiB used: 97.28 GiB (7.6%)
  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: Kingston model: DataTraveler 3.0 size: 230.94 GiB
    type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 110.2 GiB used: 8.26 GiB (7.5%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 973.4 MiB used: 412.7 MiB (42.4%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 598.8 MiB used: 19.4 MiB (3.2%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 110.2 GiB used: 8.26 GiB (7.5%) fs: btrfs dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 5.71 GiB used: 512 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 38.9 C mobo: N/A gpu: radeon temp: 44.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 6 GiB available: 5.71 GiB used: 3.32 GiB (58.1%)
  Processes: 317 Power: uptime: 2m wakeups: 0 Init: systemd v: 256
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 14
    Compilers: N/A Shell: Bash v: 5.2.32 running-in: konsole inxi: 3.3.37

ENDING OF DATA

It says “6gb” because it’s two sticks of 4gb DDR3 (it ain’t a gaming machine) and 2 is now “forced” as “VRAM”.
I do not believe this to be the issue at all.

I have another computer with an A-880k (Windows 10, forever offline, archival PC) which I was lucky to have found. I remember that PC having a semi-busted MOBO (SAME model) so it got the monostick + dedicated GPU.

The computer tells me that “it’s rendering with llvmpipe”, which as far as I know is just the CPU software-rendering the desktop.
I want a way to get hardware acceleration back on working as it was before.

[barryascott]

If you boot from the previous kernel is the problem fixed?

FYI to do pre-formatted text use the </> button. I fixed your post for you.

[isaac0clarke (Isaac Clarke)]

Ok, thanks (feels strange that someone can edit someone else’s message tho, would like to know how and why).
.
.
.
Anyways, no. Not even before a couple of updates now “using an older Kernel” ever fixed this.
.
As I told you, somehow Fedora KDE isn’t using the I.G. anymore.
When I will have the chance to, I’ll use the Install USB to see if it manages to use the integrated graphics.
.
Could it be that some MESA driver got installed wrong and therefore it fails to detect the I.G.?
Better question:
Where can the “supported Graphics devices” be checked, as an online page?

[barryascott]

@isaac0clarke

feels strange that someone can edit someone else’s message tho, would like to know how and why

I have been granted trust level 4 by the moderators.
This is not a privilege that is provided to all contributors.

I am not sure about integrated graphics issue.
Someone will need to comment.

[barryascott]

It would be worth checking that the integrated graphics is enabled in the BIOS.

[isaac0clarke (Isaac Clarke)]

As typed before, it’s “forced on with 2gb”.

Before it was in “auto, no [MOBO ports pass-through GPU image]” mode; I changed it after it stopped working.

I believe than in 12-24 hours I can test the PC with the USB.
If anyone gets any idea about what I might test, write it down please.

(Still, what page has all the supported GPUs, or how can I find it?)

[isaac0clarke (Isaac Clarke)]

UPDATE:
.
I have played around with the BIOS options, nothing changed.
.
I have tried out the Install USB, and Hardware Acceleration works.
.
.
.
Is there a way to check if the drivers work? Or to turn them on (H.A.)? Or to reinstall them from 0?

[isaac0clarke (Isaac Clarke)]

Barry, I tank you for your initial help with my issue.
,
,
Now that a couple of days have passed I managed to find out more info both directly from my hardware and indirectly through the barbed wire that is Google’s search engine.
.
I would like to ask you if you can help me again with my problem or at least if you could share what you think about the issue (seems that maybe, just maybe, it’s a Mesa bug with the Kaveri iGPU of my PC).

[barryascott]

You can try downgrading mesa to see if that fixes it.
Other people have reported issues caused by mesa recently.

I think this may do what you need.

sudo dnf downgrade mesa*

Then reboot.

[isaac0clarke (Isaac Clarke)]

Thanks Barry.
.
Altho the command is the one which didn’t work before, Yesterday I inserted it again to get the Error Message to paste it here.
It seems that, for some magical reason, this time it decided to work.
.
.
I updated the opening post to explain the problem properly and how one may go fixing it for themselves.
Thank you very much for your help.

[isaac0clarke (Isaac Clarke)]

The norwegian “Fedora versions” Wikipedia page says something about “cutting support for CPUs without AVX2”, and my Kaveri APU falls under such characteristic (Ctrl+F with either AVX2 or Kaveri will bring you there).

Wikipedia being Wikipedia I can’t take it as gospel, but I can’t find ANY good information about anything regarding “linux, mesa, fedora, kaveri” without being lost in a sea of useless pages thanks to how search engines work.

Even the “Mesa updates” pages are very dry and thus I can’t find anything of use to me.

I doubt that any answer will come in little time (1 week), I know it may even never come, but what I mainly want is at least a way to verify such data for myself. I am not too slow for this kind of stuff, it’s just that the manuals are not readily available…

.

I hope this “Kaveri” business is just a bug, because for a CPU (iGPU or not) which came out after 2010 to already have lost such support from even Linux overall would be very sad…

[barryascott]

@isaac0clarke

I hope this “Kaveri” business is just a bug, because for a CPU (iGPU or not) which came out after 2010 to already have lost such support from even Linux overall would be very sad…

Have you reported this as a bug against the amdgpu in the amdgpu bug tracker?

[isaac0clarke (Isaac Clarke)]

No, I have not (thank you for your help).

It’s not just that I don’t know where, and therefore how, but also that I don’t really want to make new atop new account for any and each website.

There was a dude with the OpenSUSE version of this site saying something similar to my problem, and there there were obviously other websites…

.

Could youlease tell me where I may report such problem?
Altho, if it’s not a problem, may I ask you if it were you to do it in my stead?

I am willing to “help” and/by doing things properly, but honestly as an end user there also is a “I don’t wanna do all of this to just use my PC” feeling.
There’s also the fact that I “have things” going on in my life (privacy), so if it must be me who reports so be it, but at least this once I’d rather dodge the “get to new website, make new account, understand how it works, make new post” sequence of events… I’d rather rest (reasons).

[barryascott]

Try reporting here https://gitlab.freedesktop.org/drm/amd/-/issues

Without a bug report the developers may not know there is something that needs work.

[isaac0clarke (Isaac Clarke)]

Then I’ll have to do it when I manage to find some time.

Thank you, have a good rest of your day.

[isaac0clarke (Isaac Clarke)]

I have made a post on the site.

Mesa 25 not working on Kaveri architecture, fallback to Software Rendering....

Any further discussion about this problem will happen there.
I do not believe I or anyone else would need to add anything else here (so for the people in the future reading this, just open this link please).