Created attachment 178184 [details]
Fastfetch Screenshot

Any output when you start it from a terminal?

(In reply to Harald Sitter from comment #2)
> Any output when you start it from a terminal?

qt.qml.typeregistration: Invalid QML element name "Hint"; value type names should begin with a lowercase letter
Failed to load vulkan: Cannot load library vulkan: vulkan: cannot open shared object file: No such file or directory
initInstance: No Vulkan library available
Failed to create platform Vulkan instance
Failed to create vulkan instance
GPU count mismatch (from vulkan) 0 2
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Warning from helper: DMIDecodeHelper: Unable to get system information for  "system-version"


This is what i got

And you are sure your nvidia driver is actually working? Those warnings rather suggest your second device is indeed a CPU renderer based on llvmpipe.

What happens when you run the opengl helper like so (path may be different on fedora):

DRI_PRIME=0 /usr/lib/libexec/kinfocenter-opengl-helper
DRI_PRIME=1 /usr/lib/libexec/kinfocenter-opengl-helper
DRI_PRIME=2 /usr/lib/libexec/kinfocenter-opengl-helper

(In reply to Harald Sitter from comment #4)
> And you are sure your nvidia driver is actually working? Those warnings
> rather suggest your second device is indeed a CPU renderer based on llvmpipe.
> 
> What happens when you run the opengl helper like so (path may be different
> on fedora):
> 
> DRI_PRIME=0 /usr/lib/libexec/kinfocenter-opengl-helper
> DRI_PRIME=1 /usr/lib/libexec/kinfocenter-opengl-helper
> DRI_PRIME=2 /usr/lib/libexec/kinfocenter-opengl-helper


Sorry, I didn't really get what you said, but I ran this

   glxinfo | grep "OpenGL renderer"

OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)

Right.

Now run 

DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
DRI_PRIME=2 glxinfo | grep "OpenGL renderer"

(In reply to Harald Sitter from comment #6)
> Right.
> 
> Now run 
> 
> DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=2 glxinfo | grep "OpenGL renderer"



DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
                        DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
                        DRI_PRIME=2 glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)
glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))
glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))

these are output respectively

(In reply to Harald Sitter from comment #6)
> Right.
> 
> Now run 
> 
> DRI_PRIME=0 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=1 glxinfo | grep "OpenGL renderer"
> DRI_PRIME=2 glxinfo | grep "OpenGL renderer"

These are for better aligned outputs


DRI_PRIME=0 glxinfo | grep "OpenGL renderer"

OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)


DRI_PRIME=1 glxinfo | grep "OpenGL renderer"

glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))


DRI_PRIME=2 glxinfo | grep "OpenGL renderer"

glx: failed to create dri3 screen
failed to load driver: nouveau
OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))

> OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))

Why does glx manage to initialize vulkan but Qt not? I am at a loss for words

(In reply to Harald Sitter from comment #9)
> > OpenGL renderer string: zink Vulkan 1.3(NVIDIA GeForce MX350 (NVIDIA_PROPRIETARY))
> 
> Why does glx manage to initialize vulkan but Qt not? I am at a loss for words

😅

Paging Neal. Maybe he has an idea what's up with your vulkan stack.

Ultimately the problem is that the vulkan code fails to work at all and so device enumeration runs through opengl and that has problems for some reason too (though arguably we don't need to care because the vulkan code should provide superior enumeration - if it was working).

Oh, btw another thing I have noticed with my laptop is that if only nouveau drivers are installed then other that fastfetch my GPU doesn't show up anywhere like nvtop or even some applications don't even recognise the mx350 only after installing the proprietary drivers it starts to show up. I guess this is unrelated to the issue, but I thought of letting you know anyway.

Created attachment 178284 [details]
KInfoCenter screenshot from my Framework 16

This seems to work as expected on my system.

Additionally, the helper seems to do the right thing too?

ngompa@fedora ~> /usr/libexec/kinfocenter-opengl-helper
[{"name":"AMD Radeon 780M (radeonsi, gfx1103_r1, LLVM 19.1.0, DRM 3.59, 6.12.11-200.fc41.x86_64)","vkDeviceType":0}]
ngompa@fedora ~> DRI_PRIME=1 /usr/libexec/kinfocenter-opengl-helper
[{"name":"AMD Radeon RX 7700S (radeonsi, navi33, LLVM 19.1.0, DRM 3.59, 6.12.11-200.fc41.x86_64)","vkDeviceType":0}]

I'm inclined to say this might be something specifically broken with the NVIDIA driver. In the Fedora KDE Matrix room, I was pointed to this issue: https://github.com/NVIDIA/egl-wayland/issues/162

Yes this https://github.com/NVIDIA/egl-wayland/issues/162 might be the issue, I can get those same errors on my system too.

mesa tries to load the nouveau userspace gl driver, even though the nouveau kernel driver is not loaded. 
i asked on the egl-wayland issue for the mesa issue, but i think i found it https://gitlab.freedesktop.org/mesa/mesa/-/issues/12462

(In reply to Luan Vitor Simião Oliveira from comment #16)
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/12462

Thanks I will be following that👍🏻

@angad could you try installing vulkan-loader-devel, and checking if the issue is resolved?

(In reply to Luan Vitor Simião Oliveira from comment #18)
> @angad could you try installing vulkan-loader-devel, and checking if the
> issue is resolved?

Well it does get resolved, but how to do know that are you a genius or something??

Created attachment 178307 [details]
infocentre

See yourself looks good

usr/lib64/libvulkan.so is only included with that package and qt is trying to load Vulcan through it instead of /usr/lib64/libvulkan.so.1

Created attachment 178310 [details]
OpenGL (EGL)

(In reply to Luan Vitor Simião Oliveira from comment #21)
> usr/lib64/libvulkan.so is only included with that package and qt is trying
> to load Vulcan through it instead of /usr/lib64/libvulkan.so.1
 
oh ok btw is this normal?

no idea, probably not, since that`s an devel package, either qt needs to load libvulkan.so.1, or libvulkan.so should be moved to the regular vulkan-loader package

I think ultimately the bug is in qtwayland. I mean, there's something wrong with nvidia too, but the main problem is that the vulkan code doesn't enumerate devices and that seems to be simply because qtwayland doesn't try to load libvulkan.so.1 as first choice.

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/232

I'm also experiencing this bug in the newly released Plasma Desktop 6.3.2, I'll post the 2 versions of kinfo with and without sudo

➜  ~ kinfo
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor 1: Mesa Intel® HD Graphics 4400
Graphics Processor 2: llvmpipe
➜  ~ 


➜  ~ sudo kinfo
[sudo] senha para joserafael: 
MESA-INTEL: warning: Haswell Vulkan support is incomplete
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-200.fc41.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor 1: Intel® HD Graphics 4400
Graphics Processor 2: NVIDIA GeForce GT 740M

sudo seems to make it work because it forces kinfocenter to use x11, if you force x11 through some other way it will also "fix" the text

*** Bug 500949 has been marked as a duplicate of this bug. ***

Git commit a18a54d9a513cf633787eb8e7a566c91759109a7 by Harald Sitter.
Committed on 06/03/2025 at 11:36.
Pushed by sitter into branch 'master'.

about: when loading opengl gpus, handle nvidia the nvidia way

- use nvidia's glx library
- set the renderer offload variable

this should produce more reasonable strings on systems where vulkan is
not working for whatever reason

M  +39   -5    kcms/about-distro/src/GPUEntryFactory.cpp

https://invent.kde.org/plasma/kinfocenter/-/commit/a18a54d9a513cf633787eb8e7a566c91759109a7

Git commit 4d789b59c4b9e22602e8e03f86fcc7896a6b1f39 by Harald Sitter.
Committed on 06/03/2025 at 11:40.
Pushed by sitter into branch 'Plasma/6.3'.

about: when loading opengl gpus, handle nvidia the nvidia way

- use nvidia's glx library
- set the renderer offload variable

this should produce more reasonable strings on systems where vulkan is
not working for whatever reason
(cherry picked from commit a18a54d9a513cf633787eb8e7a566c91759109a7)

M  +39   -5    kcms/about-distro/src/GPUEntryFactory.cpp

https://invent.kde.org/plasma/kinfocenter/-/commit/4d789b59c4b9e22602e8e03f86fcc7896a6b1f39

Created attachment 179177 [details]
packages for only computing installation

If you use nvidia glx library, I fear  you can't detect the nvidia adapter in this following case : only computing installation.

see the capture

I wonder if a a bug that I reported has the same cause or if the fix for this one will affect it in any way:
https://bugs.kde.org/show_bug.cgi?id=500403
Or if there, the fix still need to happen on distros' side.

I apologize, but the problem still applies to me in 6.3.3

Please open a new bug report and post the output of running kinfocenter from a terminal.

So this didn't get fixed after the update 6.3.3 update, although one thing has happened on the nouveau driver it does show GPU:2 now previously it was not even showing the NVIDIA GPU but with proprietary drivers it still shows llvmpipe

Created attachment 179658 [details]
Screenshot after the 6.3.3 update

(In reply to Angad from comment #36)
> Created attachment 179658 [details]
> Screenshot after the 6.3.3 update

I confirm.

Operating System: openSUSE Tumbleweed 20250321
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-12100
Memory: 15.3 Gio of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics 730
Graphics Processor 2: llvmpipe
Manufacturer: ASRock
Product Name: B760M-HDV/M.2 D4

Setting back to confirmed since more than one person can reproduce the issue

Is that with comment 18 noted and applied?

(In reply to Harald Sitter from comment #39)
> Is that with comment 18 noted and applied?

no installing vulkan-loader-devel fixes the whole issue, it's without the package installed

It also happens to me:

```
$ kinfo
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-arch1-1-surface (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 15.5 GiB of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics 620
Graphics Processor 2: llvmpipe

```

But this is the output of `vkcube`:

```
$ vkcube
Selected WSI platform: xcb
Selected GPU 0: NVIDIA GeForce GTX 1060, type: DiscreteGpu
```

In my case using the nvidia adapter only for computing.

:~> kinfo
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Operating System: openSUSE Tumbleweed 20250321
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-12100
Memory: 15.3 Gio of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics 730
Graphics Processor 2: llvmpipe

:~> vkcube
Selected WSI platform: xcb
Selected GPU 0: Intel(R) UHD Graphics 730 (ADL-S GT1), type: IntegratedGpu

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.13.10-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz
Memory: 7.6 GiB of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics
Graphics Processor 2: zink Vulkan 1.4
Manufacturer: TIMI
Product Name: Mi NoteBook Horizon Edition 14

now it shows zink Vulkan 1.4 instead of llvmpipe i think this is after the recent mesa update or kde frameworks update that i got on fedora

This got fixed now

I still have this problem on two of my PCs. (https://discussion.fedoraproject.org/t/llvmpipe-is-used-instead-of-gpu/156052)

The first one has an Intel I7 2960XM and Intel HD 3000
The second one has a Pentium E5200 with an ATI Radeon HD 4650 (RV730 PRO)

Here's the changelog between the last version with the right GPU and the first version showing llvmpipe : 

  ImageMagick 1:7.1.1.46-1.fc42 -> 1:7.1.1.47-1.fc42
  ImageMagick-libs 1:7.1.1.46-1.fc42 -> 1:7.1.1.47-1.fc42
  akonadi-server 24.12.3-1.fc42 -> 25.04.0-2.fc42
  akonadi-server-mysql 24.12.3-1.fc42 -> 25.04.0-2.fc42
  ark 24.12.3-1.fc42 -> 25.04.0-1.fc42
  ark-libs 24.12.3-1.fc42 -> 25.04.0-1.fc42
  audiocd-kio 24.12.3-1.fc42 -> 25.04.0-1.fc42
  audiocd-kio-doc 24.12.3-1.fc42 -> 25.04.0-1.fc42
  baloo-widgets 24.12.3-1.fc42 -> 25.04.0-1.fc42
  colord-kde 24.12.3-1.fc42 -> 25.04.0-1.fc42
  dnsmasq 2.90-4.fc42 -> 2.90-6.fc42
  dolphin 24.12.3-1.fc42 -> 25.04.0-3.fc42
  dolphin-libs 24.12.3-1.fc42 -> 25.04.0-3.fc42
  dolphin-plugins 24.12.3-1.fc42 -> 25.04.0-1.fc42
  ffmpegthumbs 24.12.3-1.fc42 -> 25.04.0-1.fc42
  filelight 1:24.12.3-1.fc42 -> 1:25.04.0-1.fc42
  gstreamer1-plugins-good 1.26.0-1.fc42 -> 1.26.0-2.fc42
  gstreamer1-plugins-good-qt 1.26.0-1.fc42 -> 1.26.0-2.fc42
  gstreamer1-plugins-good-qt6 1.26.0-1.fc42 -> 1.26.0-2.fc42
  hplip 3.25.2-1.fc42 -> 3.25.2-2.fc42
  hplip-common 3.25.2-1.fc42 -> 3.25.2-2.fc42
  hplip-libs 3.25.2-1.fc42 -> 3.25.2-2.fc42
  intel-vpl-gpu-rt 24.4.4-2.fc42 -> 25.1.3-1.fc42
  kaccounts-integration-qt6 24.12.3-1.fc42 -> 25.04.0-2.fc42
  kaccounts-providers 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kamera 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kate-libs 24.12.3-1.fc42 -> 25.04.0-2.fc42
  kcharselect 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kde-cli-tools 6.3.4-1.fc42 -> 6.3.4-2.fc42
  kde-connect 24.12.3-1.fc42 -> 25.04.0-2.fc42
  kde-connect-libs 24.12.3-1.fc42 -> 25.04.0-2.fc42
  kde-inotify-survey 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kde-partitionmanager 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kdebugsettings 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kdeconnectd 24.12.3-1.fc42 -> 25.04.0-2.fc42
  kdegraphics-mobipocket 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kdegraphics-thumbnailers 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kdenetwork-filesharing 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kdesu 1:6.3.4-1.fc42 -> 1:6.3.4-2.fc42
  kdialog 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kdnssd 24.12.3-1.fc42 -> 25.04.0-1.fc42
  keditbookmarks 24.12.3-1.fc42 -> 25.04.0-1.fc42
  keditbookmarks-libs 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kf6-kcolorscheme 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kconfigwidgets 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kdbusaddons 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kglobalaccel 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kguiaddons 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kiconthemes 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kio-core 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kio-core-libs 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kio-doc 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kio-file-widgets 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kio-gui 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kio-widgets 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kio-widgets-libs 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kirigami 6.13.0-2.fc42 -> 6.13.0-3.fc42
  kf6-kirigami-addons 1.7.0-1.fc42 -> 1.7.0-2.fc42
  kf6-kjobwidgets 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kstatusnotifieritem 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kuserfeedback 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kwindowsystem 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-kxmlgui 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kf6-qqc2-desktop-style 6.13.0-1.fc42 -> 6.13.0-2.fc42
  kfind 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kglobalacceld 6.3.4-1.fc42 -> 6.3.4-2.fc42
  khelpcenter 1:24.12.3-1.fc42 -> 1:25.04.0-1.fc42
  kinfocenter 6.3.4-1.fc42 -> 6.3.4-2.fc42
  kio-admin 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kio-extras 24.12.3-1.fc42 -> 25.04.0-2.fc42
  kio-gdrive 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kjournald 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kjournald-libs 24.12.3-1.fc42 -> 25.04.0-1.fc42
  konsole 24.12.3-1.fc42 -> 25.04.0-1.fc42
  konsole-part 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kpipewire 6.3.4-1.fc42 -> 6.3.4-2.fc42
  kpmcore 24.12.3-1.fc42 -> 25.04.0-1.fc42
  krdp 6.3.4-1.fc42 -> 6.3.4-2.fc42
  krdp-libs 6.3.4-1.fc42 -> 6.3.4-2.fc42
  krfb 24.12.3-1.fc42 -> 25.04.0-2.fc42
  krfb-libs 24.12.3-1.fc42 -> 25.04.0-2.fc42
  kscreen 1:6.3.4-1.fc42 -> 1:6.3.4-2.fc42
  kscreenlocker 6.3.4-1.fc42 -> 6.3.4-2.fc42
  kwalletmanager5 24.12.3-1.fc42 -> 25.04.0-1.fc42
  kwayland 6.3.4-1.fc42 -> 6.3.4-2.fc42
  kwin 6.3.4-2.fc42 -> 6.3.4-3.fc42
  kwin-common 6.3.4-2.fc42 -> 6.3.4-3.fc42
  kwin-libs 6.3.4-2.fc42 -> 6.3.4-3.fc42
  kwin-wayland 6.3.4-2.fc42 -> 6.3.4-3.fc42
  kwrite 24.12.3-1.fc42 -> 25.04.0-2.fc42
  layer-shell-qt 6.3.4-1.fc42 -> 6.3.4-2.fc42
  libkcddb 24.12.3-1.fc42 -> 25.04.0-1.fc42
  libkcddb-doc 24.12.3-1.fc42 -> 25.04.0-1.fc42
  libkcompactdisc 24.12.3-1.fc42 -> 25.04.0-1.fc42
  libkdcraw 24.12.3-1.fc42 -> 25.04.0-1.fc42
  libkexiv2-qt5 24.12.3-1.fc42 -> 25.04.0-1.fc42
  libkexiv2-qt6 24.12.3-1.fc42 -> 25.04.0-1.fc42
  libkgapi 24.12.3-1.fc42 -> 25.04.0-1.fc42
  libkscreen 6.3.4-1.fc42 -> 6.3.4-2.fc42
  libksysguard 6.3.4-1.fc42 -> 6.3.4-2.fc42
  libksysguard-common 6.3.4-1.fc42 -> 6.3.4-2.fc42
  libkworkspace6 6.3.4-2.fc42 -> 6.3.4-3.fc42
  libplasma 6.3.4-1.fc42 -> 6.3.4-2.fc42
  libsane-hpaio 3.25.2-1.fc42 -> 3.25.2-2.fc42
  plasma-desktop 6.3.4-1.fc42 -> 6.3.4-2.fc42
  plasma-desktop-doc 6.3.4-1.fc42 -> 6.3.4-2.fc42
  plasma-integration 6.3.4-1.fc42 -> 6.3.4-2.fc42
  plasma-integration-qt5 6.3.4-1.fc42 -> 6.3.4-2.fc42
  plasma-lookandfeel-fedora 6.3.4-2.fc42 -> 6.3.4-3.fc42
  plasma-workspace 6.3.4-2.fc42 -> 6.3.4-3.fc42
  plasma-workspace-common 6.3.4-2.fc42 -> 6.3.4-3.fc42
  plasma-workspace-libs 6.3.4-2.fc42 -> 6.3.4-3.fc42
  plasma-workspace-wayland 6.3.4-2.fc42 -> 6.3.4-3.fc42
  plasma5support 6.3.4-1.fc42 -> 6.3.4-2.fc42
  powerdevil 6.3.4-1.fc42 -> 6.3.4-3.fc42
  python3-boto3 1.37.33-1.fc42 -> 1.37.35-1.fc42
  python3-botocore 1.37.33-1.fc42 -> 1.37.35-1.fc42
  qcoro-qt6 0.11.0-1.fc42 -> 0.11.0-2.fc42
  qt6-filesystem 6.8.2-2.fc42 -> 6.9.0-2.fc42
  qt6-qt5compat 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtbase 6.8.2-3.fc42 -> 6.9.0-1.fc42
  qt6-qtbase-common 6.8.2-3.fc42 -> 6.9.0-1.fc42
  qt6-qtbase-gui 6.8.2-3.fc42 -> 6.9.0-1.fc42
  qt6-qtbase-mysql 6.8.2-3.fc42 -> 6.9.0-1.fc42
  qt6-qtconnectivity 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtdeclarative 6.8.2-1.fc42 -> 6.9.0-2.fc42
  qt6-qtimageformats 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtmultimedia 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtpdf 6.8.2-4.fc42 -> 6.9.0-1.fc42
  qt6-qtpositioning 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtquick3d 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtquicktimeline 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtsensors 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtserialport 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtshadertools 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtspeech 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtspeech-flite 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtspeech-speechd 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtsvg 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qttools 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qttools-common 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qttranslations 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtvirtualkeyboard 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtwayland 6.8.2-1.fc42 -> 6.9.0-2.fc42
  qt6-qtwebchannel 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtwebengine 6.8.2-4.fc42 -> 6.9.0-1.fc42
  qt6-qtwebsockets 6.8.2-1.fc42 -> 6.9.0-1.fc42
  qt6-qtwebview 6.8.2-2.fc42 -> 6.9.0-1.fc42
  sddm-breeze 6.3.4-1.fc42 -> 6.3.4-2.fc42
  sddm-wayland-plasma 6.3.4-2.fc42 -> 6.3.4-3.fc42
  signon-kwallet-extension 24.12.3-1.fc42 -> 25.04.0-1.fc42
  spectacle 1:6.3.4-1.fc42 -> 1:6.3.4-2.fc42
  virtualbox-guest-additions 7.1.6-1.fc42 -> 7.1.8-1.fc42
  xdg-desktop-portal-kde 6.3.4-1.fc42 -> 6.3.4-2.fc42
  xwaylandvideobridge 0.4.0-8.fc42 -> 0.4.0-9.fc42

(In reply to Villemur Clément from comment #45)
> I still have this problem on two of my PCs.
> (https://discussion.fedoraproject.org/t/llvmpipe-is-used-instead-of-gpu/
> 156052)
> 
> The first one has an Intel I7 2960XM and Intel HD 3000
> The second one has a Pentium E5200 with an ATI Radeon HD 4650 (RV730 PRO)
> 
> Here's the changelog between the last version with the right GPU and the
> first version showing llvmpipe : 

Thanks for the detail. I'm sorry to hear this is still happening on these systems.
Can you copy and paste the output of the following two commands from one of the systems into this report? Thanks.

kinfo
glxinfo | grep "OpenGL renderer"

(In reply to TraceyC from comment #46)
> (In reply to Villemur Clément from comment #45)
> > I still have this problem on two of my PCs.
> > (https://discussion.fedoraproject.org/t/llvmpipe-is-used-instead-of-gpu/
> > 156052)
> > 
> > The first one has an Intel I7 2960XM and Intel HD 3000
> > The second one has a Pentium E5200 with an ATI Radeon HD 4650 (RV730 PRO)
> > 
> > Here's the changelog between the last version with the right GPU and the
> > first version showing llvmpipe : 
> 
> Thanks for the detail. I'm sorry to hear this is still happening on these
> systems.
> Can you copy and paste the output of the following two commands from one of
> the systems into this report? Thanks.
> 
> kinfo
> glxinfo | grep "OpenGL renderer"

kinfo : 
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.3-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-2960XM CPU @ 2.70GHz
Memory: 8 Gio of RAM (7.7 Gio usable)
Graphics Processor: llvmpipe

glxinfo | grep "OpenGL renderer" : 
OpenGL renderer string: Mesa Intel(R) HD Graphics 3000 (SNB GT2)

I'm not sure if it's related or not, but both of these systems do not support Vulkan using the GPU.

Thanks for the additional information. I'll let the developers take a closer look.

*** Bug 506527 has been marked as a duplicate of this bug. ***

I have the same issue with Intel/Nvidia hybrid graphics configured in PRIME mode. Please see below the output of kinfo and glxinfo.

$ kinfo
libEGL warning: egl: failed to create dri2 screen
Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.12.28-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 31.0 GiB of RAM
Graphics Processor 1: Mesa Intel® Iris® Xe Graphics
Graphics Processor 2: zink Vulkan 1.4

$ glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa Intel(R) Iris(R) Xe Graphics (ADL GT2)

$ prime-run glxinfo | grep "OpenGL renderer"
OpenGL renderer string: NVIDIA T600 Laptop GPU/PCIe/SSE2

(In reply to Oleg Gorobets from comment #50)
> I have the same issue with Intel/Nvidia hybrid graphics configured in PRIME
> mode. Please see below the output of kinfo and glxinfo.
> 
> $ kinfo
> libEGL warning: egl: failed to create dri2 screen
> Operating System: Arch Linux 
> KDE Plasma Version: 6.3.5
> KDE Frameworks Version: 6.14.0
> Qt Version: 6.9.0
> Kernel Version: 6.12.28-1-lts (64-bit)
> Graphics Platform: Wayland
> Processors: 20 × 12th Gen Intel® Core™ i7-12700H
> Memory: 31.0 GiB of RAM
> Graphics Processor 1: Mesa Intel® Iris® Xe Graphics
> Graphics Processor 2: zink Vulkan 1.4
> 
> $ glxinfo | grep "OpenGL renderer"
> OpenGL renderer string: Mesa Intel(R) Iris(R) Xe Graphics (ADL GT2)
> 
> $ prime-run glxinfo | grep "OpenGL renderer"
> OpenGL renderer string: NVIDIA T600 Laptop GPU/PCIe/SSE2

I had a similar problem, and it didn't involve anything with the dedicated GPU.
First, run `kinfocenter` from the terminal.
If the output includes something like:
"GPU count mismatch (from vulkan). Are you maybe missing vulkan drivers? 1 2"
Then (seeing you have an Intel integrated GPU), install `vulkan-intel` and check if the problem persists

Created attachment 183078 [details]
kinfocenter without vulkan-intel driver

Created attachment 183079 [details]
kinfocenter with vulkan-intel driver

(In reply to Robi from comment #51)

> I had a similar problem, and it didn't involve anything with the dedicated
> GPU.
> First, run `kinfocenter` from the terminal.
> If the output includes something like:
> "GPU count mismatch (from vulkan). Are you maybe missing vulkan drivers? 1 2"
> Then (seeing you have an Intel integrated GPU), install `vulkan-intel` and
> check if the problem persists

Thanks Robi. Indeed, there is "GPU count mismatch" error in kinfocenter. Installing vulkan-intel solved the problem for me (see screen shots attached above). However this still feels a bit odd if I think about it. Even without Vulkan for Intel, Vulkan for NVidia is present. Kinfocenter can detect correct GPU name and shows it in console logs but not in the GUI.

Output of kinfocenter without vulkan-intel:

Physical device 0: 'NVIDIA T600 Laptop GPU' 570.576.0 (api 1.4.303 vendor 0x10DE device 0x1FB6 type 2)
GPU count mismatch (from vulkan). Are you maybe missing vulkan drivers? 1 2

This issue is still present, my nvidia gpu does not show up under gpu 2 but i does show it is correctly installed in the terminal.

I am running Endeavour OS 

https://drive.google.com/file/d/1ou5WTuAQygdqJ3BTC1IPOpGYz4bkKMIr/view?usp=drive_link

I can confirm vulkan-intel fixed it. Thanks!

The nvidia gpu should be listed as second gpu. To fix this you need to install lib32-vulkan-mesa-layers and lib32-vulkan-intel as well

Before: https://forum.endeavouros.com/uploads/default/original/3X/0/3/03545b0c1439bfed2fa6594f651853ba348d5041.jpeg
After: https://forum.endeavouros.com/uploads/default/original/3X/1/b/1b40761375c3e8aab61c5e712bf3962e7020e308.jpeg

It looks like the problem is here: https://invent.kde.org/plasma/kinfocenter/-/blob/master/kcms/about-distro/src/GPUEntryFactory.cpp#L53

See https://doc.qt.io/qt-6/qfile.html#platform-specific-issues

On Unix, there are some special system files (e.g. in /proc) for which size() will always return 0, yet you may still be able to read more data from such a file; the data is generated in direct response to you calling read(). In this case, however, you cannot use atEnd() to determine if there is more data to read (since atEnd() will return true for a file that claims to have size 0). Instead, you should either call readAll(), or call read() or readLine() repeatedly until no more data can be read.

So if we rewrite the 'while' loop into something like this, it should work:

QTextStream in(&file);
QString line = in.readLine();
while (!line.isNull()) {
    if (line.startsWith("nvidia"_L1)) {
        return true;
    }
    line = in.readLine();
}

*** Bug 507998 has been marked as a duplicate of this bug. ***

Oleg, would you like to submit a merge request with that change?

(In reply to Nate Graham from comment #61)
> Oleg, would you like to submit a merge request with that change?

Sure. Can you guide me how to do this for the first time? I have registered an account on invent.kde.org but I don't have permissions to push branches or create merge requests. Shall I just send a patch?

Great!

In a nutshell, you:
1. Check out the git repo with the code
2. Create a local branch with your patch
3. Create fork of the remote repo
4. Push your branch to your remote fork
5. Create a merge request from that branch

More specific instructions can be found at https://community.kde.org/Infrastructure/GitLab#Submitting_a_merge_request

(In reply to Nate Graham from comment #63)

Thank you, Nate. Here it is: https://invent.kde.org/plasma/kinfocenter/-/merge_requests/265

Git commit d0c9d774b092ed939932b4612b181f376adbfbda by Nate Graham, on behalf of Oleg Gorobets.
Committed on 14/08/2025 at 13:10.
Pushed by ngraham into branch 'master'.

Fix isNvidiaLoaded() method which currently always returns false

We cannot use atEnd() to determine if there is more data to read since
atEnd() will return true for /proc files. Instead, we call readLine()
repeatedly until no more data can be read.
FIXED-IN: 6.4.5

M  +4    -2    kcms/about-distro/src/GPUEntryFactory.cpp

https://invent.kde.org/plasma/kinfocenter/-/commit/d0c9d774b092ed939932b4612b181f376adbfbda

Git commit 7c7075acb4b5bdcb6e931d701cbee6057a420ed4 by Nate Graham.
Committed on 14/08/2025 at 13:10.
Pushed by ngraham into branch 'Plasma/6.4'.

Fix isNvidiaLoaded() method which currently always returns false

We cannot use atEnd() to determine if there is more data to read since
atEnd() will return true for /proc files. Instead, we call readLine()
repeatedly until no more data can be read.
FIXED-IN: 6.4.5


(cherry picked from commit d0c9d774b092ed939932b4612b181f376adbfbda)

b1cb44c3 Fix isNvidiaLoaded() method which currently always returns false.

Co-authored-by: Oleg Gorobets <oleg.goro@gmail.com>

M  +4    -2    kcms/about-distro/src/GPUEntryFactory.cpp

https://invent.kde.org/plasma/kinfocenter/-/commit/7c7075acb4b5bdcb6e931d701cbee6057a420ed4

I still have this problem with my ATI Radeon HD 4650 (RV730 PRO). It's still showing llvmpipe after the plasma 6.4.5 update. 

It's still showing llvmpipe in the About this system page. 

```
maledict@device-260:/var/home/maledict$ glxinfo | grep "OpenGL renderer"
OpenGL renderer string: AMD RV730 (DRM 2.50.0 / 6.16.7-200.fc42.x86_64, LLVM 20.1.8)
maledict@device-260:/var/home/maledict$ kinfo
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 2 × Pentium® Dual-Core  CPU      E5200  @ 2.50GHz
Memory: 4 Gio of RAM (3.8 Gio usable)
Graphics Processor: llvmpipe
```

(In reply to Villemur Clément from comment #67)
> I still have this problem with my ATI Radeon HD 4650 (RV730 PRO). It's still
> showing llvmpipe after the plasma 6.4.5 update. 

I wonder what you get from running /usr/lib/kinfocenter-opengl-helper ?

(In reply to Oleg Gorobets from comment #68)
> (In reply to Villemur Clément from comment #67)
> > I still have this problem with my ATI Radeon HD 4650 (RV730 PRO). It's still
> > showing llvmpipe after the plasma 6.4.5 update. 
> 
> I wonder what you get from running /usr/lib/kinfocenter-opengl-helper ?

The file /usr/lib/kinfocenter-opengl-helper doesn't exist. I'm running Fedora Kinoite so maybe that's why. 

Idk if this is useful but here's the difference between the last version it was working and the next update. 
https://bugs.kde.org/show_bug.cgi?id=499882#c45

I've found the program elsewhere 
/usr/libexec/kinfocenter-opengl-helper 
[{"name":"AMD RV730 (DRM 2.50.0 / 6.16.7-200.fc42.x86_64, LLVM 20.1.8)","vkDeviceType":0}]

(In reply to Villemur Clément from comment #70)
> I've found the program elsewhere 
> /usr/libexec/kinfocenter-opengl-helper 
> [{"name":"AMD RV730 (DRM 2.50.0 / 6.16.7-200.fc42.x86_64, LLVM
> 20.1.8)","vkDeviceType":0}]

So OpenGL looks good, it correctly detects the GPU. Then llvmpipe must be coming from Vulkan. But your GPU is from 2008, it doesn't even have Vulkan support. I wonder if you have any Vulkan drivers installed (vulkan-radeon, amdvlk or something similar)? Also, can you run vulkaninfo? What is the output from vulkaninfo | grep "GPU id :" ?

(In reply to Oleg Gorobets from comment #71)

> So OpenGL looks good, it correctly detects the GPU. Then llvmpipe must be
> coming from Vulkan. But your GPU is from 2008, it doesn't even have Vulkan
> support. I wonder if you have any Vulkan drivers installed (vulkan-radeon,
> amdvlk or something similar)? Also, can you run vulkaninfo? What is the
> output from vulkaninfo | grep "GPU id :" ?

I think you're right about llvmpipe coming from Vulkan. I had (and maybe still have) the same problem with an Intel HD 3000 (doesn't support Vulkan either). 

rpm -qa |grep vulkan
vulkan-loader-1.4.313.0-1.fc42.x86_64
vulkan-tools-1.4.313.0-1.fc42.x86_64
mesa-vulkan-drivers-25.1.9-1.fc42.x86_64

 rpm -qa |grep amd
amd-gpu-firmware-20250808-1.fc42.noarch
amd-ucode-firmware-20250808-1.fc42.noarch

vulkaninfo | grep "GPU id :"
WARNING: [../src/amd/vulkan/radv_physical_device.c:2041] Code 0 : Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
GPU id : 0 (llvmpipe (LLVM 20.1.8, 128 bits)) [VK_KHR_xcb_surface, VK_KHR_xlib_surface]:
GPU id : 0 (llvmpipe (LLVM 20.1.8, 128 bits)) [VK_KHR_wayland_surface]:

(In reply to Villemur Clément from comment #72)

> rpm -qa |grep vulkan
> vulkan-loader-1.4.313.0-1.fc42.x86_64
> vulkan-tools-1.4.313.0-1.fc42.x86_64
> mesa-vulkan-drivers-25.1.9-1.fc42.x86_64
 
> vulkaninfo | grep "GPU id :"
> GPU id : 0 (llvmpipe (LLVM 20.1.8, 128 bits)) [VK_KHR_xcb_surface,

Ok, so you have mesa-vulkan-drivers installed without actual hardware support for Vulkan. Therefore mesa reports llvmpipe instead. As a workaround you can remove mesa-vulkan-drivers package, restart and see if it solves the problem. 

The interesting part is that people were thinking of ignoring "llvmpipe" output already. See stripLlvmpipe() method:

https://invent.kde.org/plasma/kinfocenter/-/blob/master/kcms/about-distro/src/GPUEntryFactory.cpp#L177

But I believe this method is skipped in your case because of this 'if':

https://invent.kde.org/plasma/kinfocenter/-/blob/master/kcms/about-distro/src/GPUEntryFactory.cpp#L200

It was designed for a different case, where there are Vulkan-capable GPUs without drivers installed. Your case is the opposite. 

Are you comfortable compiling from source and testing? I believe if you simply remove this 'if' (and keep everything what's inside) it will handle both cases correctly.

I can confirm that removing mesa-vulkan-drivers fixed the issue. I will try to compile kinfocenter without the if to see if it fixed the issue.

I've tried but I can't compile kinfocenter because of some weird permission issues. I think it is related to the fact that I'm using an immutable system :/

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/270

Just dropping by to say that in Fedora 43 + KDE Plasma 6.5.1, the bug of showing llvmpipe on older hardware still persists.

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.5-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-2410M CPU @ 2.30GHz
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: llvmpipe

(In reply to Villemur Clément from comment #74)
> I can confirm that removing mesa-vulkan-drivers fixed the issue. I will try
> to compile kinfocenter without the if to see if it fixed the issue.

I've had this 'llvmpipe' issue for a while too, possibly since Plasma 6 - currently using 6.5.2 - on an older machine with a Radeon HD 6870 (Barts GPU). The last generation to have no hardware Vulkan support, I believe. I removed mesa-vulkan-drivers and the 'Graphics Processor' listed in KDE Info changed from 'llvmpipe' to 'AMD BARTS', the same string listed as the OpenGL renderer in glxinfo.

However, removing this package means that Vulkan Info fails when looking at the Vulkan section in KDE Info.

Anyone who has older GPU without Vulkan support can you please post the output of the following command (with mesa-vulkan-drivers installed):

vulkaninfo | grep -A1 deviceType

Git commit cee5ec9a8f7238f9c94d8cac9bf11a3b6f118ce5 by Harald Sitter, on behalf of Oleg Gorobets.
Committed on 27/11/2025 at 11:34.
Pushed by sitter into branch 'master'.

Do not show 'llvmpipe' reported by Vulkan, instead pass GPU detection to OpenGL.

This covers the case where Vulkan drivers are installed but there is no hardware support for Vulkan.
In this case mesa driver will report 'llvmpipe' as GPU name. Strip it from the list of devices and pass GPU detection to OpenGL.

M  +3    -9    kcms/about-distro/src/GPUEntryFactory.cpp

https://invent.kde.org/plasma/kinfocenter/-/commit/cee5ec9a8f7238f9c94d8cac9bf11a3b6f118ce5

(In reply to Oleg Gorobets from comment #79)
> Anyone who has older GPU without Vulkan support can you please post the
> output of the following command (with mesa-vulkan-drivers installed):
> 
> vulkaninfo | grep -A1 deviceType

Probably too late, since I seee a commit has already done for some changes, but, on my laptop, which is a:
Inspiron 5770, which has 2 GPUs (Intel UHD 620 iGPU and AMD Radeon R5 dGPU).
AFAIK, the AMD Radeon R5 dGPU might not have Vulkan support or it doesn't work well, as I tried to use if for games (with DXVK) and didn't work or maybe the performance was way too bad, I don't remember exactly.
The command 'vulkaninfo | grep -A1 deviceType' has this output:
WARNING: [Loader Message] Code 0 : Layer VK_LAYER_MANGOHUD_overlay_x86_64 uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.
[2025-11-29 15:45:48.763] [MANGOHUD] [warning] [gpu_fdinfo.cpp:419] Intel i915 gt dir: failed to open /sys/bus/pci/devices/0000:00:02.0/drm/card0/gt/gt0/throttle_reason_status
        deviceType        = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
        deviceName        = Intel(R) UHD Graphics 620 (KBL GT2)
--
        deviceType        = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName        = AMD Radeon R5 M465 Series (RADV ICELAND)
--
        deviceType        = PHYSICAL_DEVICE_TYPE_CPU
        deviceName        = llvmpipe (LLVM 19.1.7, 256 bits)

I also have MangoHUD v0.8.1 installed and enabled, so there is also some output for that.
I don't have any other GPU that for sure has doesn't have Vulkan support.
I ran the command on Debian 14 (testing repository) with Plasma 6.5.3 (on Wayland)

(In reply to John from comment #81)
>         deviceType        = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
>         deviceName        = Intel(R) UHD Graphics 620 (KBL GT2)
> --
>         deviceType        = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
>         deviceName        = AMD Radeon R5 M465 Series (RADV ICELAND)
> --
>         deviceType        = PHYSICAL_DEVICE_TYPE_CPU
>         deviceName        = llvmpipe (LLVM 19.1.7, 256 bits)

Both of your GPUs have Vulkan support and are correctly detected by vulkaninfo. I was interested in GPUs without Vulkan support and the latest MR was targeting exactly such cases. But why do you have "llvmpipe" reported as your 3rd GPU? Any idea?

(In reply to Oleg Gorobets from comment #79)
> Anyone who has older GPU without Vulkan support can you please post the
> output of the following command (with mesa-vulkan-drivers installed):
> 
> vulkaninfo | grep -A1 deviceType

Here's the output on my system with AMD RV 730 (radeon hd 4650)
WARNING: [../src/amd/vulkan/radv_physical_device.c:2041] Code 0 : Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
        deviceType        = PHYSICAL_DEVICE_TYPE_CPU
        deviceName        = llvmpipe (LLVM 20.1.8, 128 bits)

(In reply to Oleg Gorobets from comment #82)
> (In reply to John from comment #81)
> Both of your GPUs have Vulkan support and are correctly detected by
> vulkaninfo. I was interested in GPUs without Vulkan support and the latest
> MR was targeting exactly such cases. But why do you have "llvmpipe" reported
> as your 3rd GPU? Any idea?
Sorry I could not help with a GPU without Vulkan support!
As for the 3rd GPU, I don't know!
It may be something that Debian 14 does for the moment or Mesa 25.2.6-1 from it does.
Or one of these environment variables that I have set for trying out things does:
# Number of threads MESA will run with. Should be between 1 and 2 * number of logical cores.
OMP_NUM_THREADS=4
# Print debug info about device selection decision-making
MESA_VK_DEVICE_SELECT_DEBUG
# Forgot what was this for
VK_LOADER_LAYERS_ENABLE=
# Force use of the threaded renderer. It's unclear if this is the default on Linux too.
QSG_RENDER_LOOP=threaded
# Enable overlay plane usage, which provide better power efficiency for windowed programs, like video players with this status.
KWIN_USE_OVERLAYS=1

GPU-Viewer program also shows it as the 3rd option in its Available Device(s) droptdown and it shows it like this:
llvmpipe (LLVM 21.1.6, 256 bits)
If I choose (select) it in the drop-down, then all the information below changes to be about it, but it doesn't let me to copy anything from it.
In any case it says the same name as in the dropdown, that is a physical device type CPU, it's part of Mesa 25.2.6, driver name: llvmpipe.
Maybe it just wants to say that software rendering on the CPU is available too.

Other commands that I found out while trying to configure MangoHUD and find a way to force Steam use the integrated GPU, instead of the dedicated (discrete GPU) and their output (after the dotted lines):

MESA_VK_DEVICE_SELECT=list vulkaninfo
-------------------------------------------------------------
WARNING: [Loader Message] Code 0 : Layer VK_LAYER_MANGOHUD_overlay_x86_64 uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.
[2025-11-30 00:06:23.702] [MANGOHUD] [warning] [gpu_fdinfo.cpp:419] Intel i915 gt dir: failed to open /sys/bus/pci/devices/0000:00:02.0/drm/card0/gt/gt0/throttle_reason_status
selectable devices:
  GPU 0: 1002:6900 "AMD Radeon R5 M465 Series (RADV ICELAND)" discrete GPU 0000:01:00.0
  GPU 1: 8086:5917 "Intel(R) UHD Graphics 620 (KBL GT2)" integrated GPU 0000:00:02.0
  GPU 2: 10005:0 "llvmpipe (LLVM 19.1.7, 256 bits)" CPU 0000:00:00.0

switcherooctl list
-------------------------------------------------------------
Device: 0
  Name:        Intel® UHD Graphics 620
  Default:     yes
  Discrete:    no
  Environment: DRI_PRIME=pci-0000_00_02_0 VK_LOADER_DRIVERS_SELECT=*intel*

Device: 1
  Name:        Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon™ R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]
  Default:     no
  Discrete:    yes
  Environment: DRI_PRIME=pci-0000_01_00_0 VK_LOADER_DRIVERS_SELECT=*radeon*

(In reply to Villemur Clément from comment #83)
> (In reply to Oleg Gorobets from comment #79)
> > Anyone who has older GPU without Vulkan support can you please post the
> > output of the following command (with mesa-vulkan-drivers installed):
> > 
> > vulkaninfo | grep -A1 deviceType
> 
> Here's the output on my system with AMD RV 730 (radeon hd 4650)
> WARNING: [../src/amd/vulkan/radv_physical_device.c:2041] Code 0 : Device
> '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid
> argument (VK_ERROR_INCOMPATIBLE_DRIVER)
>         deviceType        = PHYSICAL_DEVICE_TYPE_CPU
>         deviceName        = llvmpipe (LLVM 20.1.8, 128 bits)

Maybe too late as well, but I also have something very similar with Radeon HD 6870:

WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_dzn.so. Skipping this driver.
WARNING: [../src/amd/vulkan/radv_physical_device.c:2182] Code 0 : Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
        deviceType        = PHYSICAL_DEVICE_TYPE_CPU
        deviceName        = llvmpipe (LLVM 20.1.8, 256 bits)