Only some software, but not others, finding hardware Intel/AMD GPU Vulkan device?

English Applications
1

This is basically just a copy of the issue I had made on the koboldcpp github whereby other distros like Linux Mint don’t have this issue and always finds my Intel/AMD hardware GPU Vulkan device:

This happens on two completely different PCs - an older LGA1150 desktop with the elusive Broadwell integrated graphics with a Xeon E3-1285L v4, and a newer mini PC with a Radeon RX 6600M (integrated GPU seems to be disabled in firmware with no way to re-enable)

The jist is that nvtop and the Dolphin emulator (not KDE’s file manager) set to Vulkan can find my hardware Intel/AMD GPU(s) just fine, and it’s definitely running on the hardware GPU since I’m getting like 60+ fps even when set to “exclusive ubershaders” (which runs the entire emulated GPU as a pixel shader, and the RX 6600M does it at 60+fps even with 4k x 3k internal resolution!).

Yet vulkaninfo and koboldcpp cannot find my hardware Intel/AMD GPU(s) and instead only find llvmpipe.

And while the above github issue was only tested on a live ISO, I did confirm this to still be the case a few weeks even with a fresh install to a local physical SSD connected to the RX 6600M mini PC.

Interestingly, the only other distro I know of with this quirk of “Dolphin finds the RX 6600M but koboldcpp does not” is FoxClone (at least as of its current 55-noble version) which isn’t exactly a distro designed for gaming, but hey sometimes we need to pass the time when waiting for big hard drive images to be backed up and/or restored, and I’ll always prefer to pass the time using a PC than using a mobile phone. :stuck_out_tongue:

(oh and to be clear, this issue occurs on both the KDE and Xfce version of Tumbleweed)

This is a screenshot from the above-linked koboldcpp git issue taken exactly 1 month ago running in the live ISO on the RX 6600M:

screenshot
screenshot1920×1080 776 KB

2

What do you get with inxi -G?

3

I don’t think I’m competent enough to help solving your problem, but is that Xorg or Wayland sessions?

4

For reference I’m using the now-latest 2026-05-16 XFCE live ISO.

Xorg since it’s the XFCE live ISO (though I did state it happens with the KDE live ISO as well which is much more likely to be using Wayland than XFCE is)

Since all testing is being done on a live ISO for easy reproducibility (i.e. you too, forum user reading this post right now, should get the same result as me if you try this at home on whatever non-Nvidia PC hardware you own!), I had to first run sudo zypper install inxi before that command would work (though I suppose the same goes for vulkan-tools for running vulkaninfo --summary and nvtop):

linux@localhost:~> inxi -G Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] driver: amdgpu v: kernel Device-2: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel Display: x11 server: X.org v: 1.21.1.21 driver: X: loaded: modesetting unloaded: vesa dri: radeonsi gpu: amdgpu resolution: 1440x900~60Hz API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.0 renderer: AMD Radeon RX 6600M (radeonsi navi23 ACO DRM 3.64 7.0.7-1-default) API: Vulkan v: 1.4.350 drivers: llvmpipe surfaces: N/A Info: Tools: api: glxinfo,vulkaninfo de: xfce4-display-settings x11: xrandr linux@localhost:~>

(also I since figured out that “updating” aka downgrading the UEFI to the latest version on the vendor’s website, which was older than my installed version, actually re-enabled the integrated graphics; the discrete GPU is still set as the primary similar to how desktop PCs work which is for the best since, unless Zink and/or Vulkan is used, the iGPU is incredibly unusable via OpenGL for whatever reason)

5

You need to install libvulkan_radeon which should work with amdgpu?

1 Like
6

Sure enough, simply running sudo zypper install libvulkan_radeon did the trick!

(and while not required, running sudo zypper install vulkan-tools was still useful since it allows some software would otherwise list your Vulkan GPU hardware devices rather blindly as just “1” or “2” rather than “RX 6600M” or the like)

But obviously libvulkan_radeon isn’t going to be the correct package for Intel graphics, so I don’t suppose you know what the Intel equivalent would be as is used on my desktop? (the AMD was a mini PC)

And heck we could even go for the trifecta of including whatever the equivalent package is for the open source nouveau Nvidia driver as well (maybe along with the half-speed Vulkan support it’ll also result in proper fan speed working like it does in the Xubuntu 26.04 live ISO?)

inxi -G for Intel Broadwell graphics:

linux@localhost:~> inxi -G Graphics: Device-1: Intel Broadwell-DT GT3 [Iris Pro Graphics P6300] driver: i915 v: kernel Display: x11 server: X.org v: 1.21.1.21 driver: X: loaded: modesetting unloaded: vesa dri: iris gpu: i915 resolution: 1440x900~60Hz API: OpenGL v: 4.6 vendor: intel mesa v: 26.1.0 renderer: Mesa Intel Iris Pro Graphics P6300 (BDW GT3) Info: Tools: api: glxinfo de: xfce4-display-settings x11: xrandr linux@localhost:~>

inxi -G for Nvidia RTX 3050:

linux@localhost:~> inxi -G Graphics: Device-1: NVIDIA GA106 [Geforce RTX 3050] driver: nouveau v: kernel Display: x11 server: X.org v: 1.21.1.21 driver: X: loaded: modesetting,nouveau unloaded: vesa gpu: nouveau resolution: 1440x900~60Hz API: OpenGL v: 4.6 vendor: mesa v: 26.1.0 renderer: llvmpipe (LLVM 22.1.5 256 bits) Info: Tools: api: glxinfo de: xfce4-display-settings x11: xrandr linux@localhost:~>

inxi -G for Broadwell + RTX 3050:

linux@localhost:~> inxi -G Graphics: Device-1: Intel Broadwell-DT GT3 [Iris Pro Graphics P6300] driver: i915 v: kernel Device-2: NVIDIA GA106 [Geforce RTX 3050] driver: nouveau v: kernel Display: x11 server: X.org v: 1.21.1.21 driver: X: loaded: modesetting,nouveau unloaded: vesa dri: iris gpu: nouveau resolution: 1440x900~60Hz API: OpenGL v: 4.6 vendor: mesa v: 26.1.0 renderer: llvmpipe (LLVM 22.1.5 256 bits) Info: Tools: api: glxinfo de: xfce4-display-settings x11: xrandr linux@localhost:~>

7

Quite simple:

S  | Name                    | Summary                                      | Type
---+-------------------------+----------------------------------------------+--------
   | libvulkan_asahi         | Mesa vulkan driver for Asahi (Apple Silicon) | package
   | libvulkan_dzn           | Mesa vulkan driver for dzn (D3D12)           | package
i+ | libvulkan_intel         | Mesa vulkan driver for Intel GPU             | package
   | libvulkan_intel-32bit   | Mesa vulkan driver for Intel GPU             | package
i+ | libvulkan_lvp           | Mesa vulkan driver for LVP                   | package
   | libvulkan_nouveau       | Mesa vulkan driver for NVK (Nouveau Vulkan)  | package
   | libvulkan_nouveau-32bit | Mesa vulkan driver for NVK (Nouveau Vulkan)  | package
   | libvulkan_powervr       | Mesa vulkan driver for PowerVR               | package
   | libvulkan_radeon        | Mesa vulkan driver for AMD GPU               | package
   | libvulkan_radeon-32bit  | Mesa vulkan driver for AMD GPU               | package
1 Like
8

That seemed to take care of everything, and libvulkan_intel was even the correct package for both Haswell and Broadwell (which from my understanding have separate driver paths or something).

Unfortunately it seems that Nouveau requires something much more major since, although the package installed, my RTX 3050 wasn’t being detected at all unlike in Xubuntu 26.04 LTS. However, since Nvidia+Linux aren’t exactly known to play nice a lot of times, I’d think that issue is kind of outside of the scope of this topic and would warrant a new thread if anything (not to mention, for all I know, someone else may have already asked about and resolved that very same nouveau issue!)

9

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