I’m on a(n almost) clean-installed openSUSE Tumbleweed. I’m on an ASUS Zenbook and I’m sure my GPU is loaded:
~> lspci -k
...
00:02.0 VGA compatible controller: Intel Corporation Lunar Lake [Intel Arc Graphics 130V / 140V] (rev 04)
DeviceName: VGA
Subsystem: ASUSTeK Computer Inc. Device 1e13
Kernel driver in use: xe
Kernel modules: xe
...
Even my Firefox is claiming it uses WebRender. However in System Settings:
Operating System: openSUSE Tumbleweed 20250428
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ Ultra 7 258V
Memory: 30.8 GiB of RAM
Graphics Processor: llvmpipe
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ASUS Zenbook S 14 UX5406SA_UX5406SA
System Version: 1.0
It is still using llvmpipe. How do I configure my system?
First post the results of
inxi -GSaz
So that the people who know what they’re doing (I’m not an Intel guy) know what hardware etc … you have
~> inxi -GSaz
System:
Kernel: 6.14.4-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.14.4-1-default
root=UUID=9a5cc792-555f-4e07-a2f3-c05de2808c89 splash=silent
mitigations=auto quiet security=selinux selinux=1
Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.13.0
wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
Tumbleweed 20250428
Graphics:
Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V] vendor: ASUSTeK
driver: xe v: kernel arch: Xe2 process: TSMC n3 (3nm) built: 2024+ ports:
active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:64a0
class-ID: 0300
Device-2: Shinetech ASUS FHD webcam driver: hid-sensor-hub,usbhid,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:2
chip-ID: 3277:0059 class-ID: fe01 serial: <filter>
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,intel dri: iris gpu: xe display-ID: 0
Monitor-1: eDP-1 model: Samsung 0x419d built: 2022 res: mode: 2880x1800
hz: 120 scale: 200% (2) to: 1440x900 dpi: 242 gamma: 1.2
size: 302x189mm (11.89x7.44") diag: 356mm (14") ratio: 16:10
modes: 2880x1800
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.4 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Graphics (LNL) device-ID: 8086:64a0
memory: 15.05 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM
20.1.3 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: gputop, intel_gpu_top, lsgpu
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Well “xe” seems to be the right driver … my nvidia needs a modeset=1 in wayland …
lsmod | grep xe
and
cat /proc/cmdline
~> lsmod | grep xe
xe 3407872 90
drm_ttm_helper 16384 1 xe
ttm 114688 2 drm_ttm_helper,xe
i2c_algo_bit 20480 1 xe
gpu_sched 69632 1 xe
drm_buddy 24576 1 xe
drm_suballoc_helper 12288 1 xe
drm_gpuvm 49152 1 xe
drm_exec 12288 2 drm_gpuvm,xe
drm_display_helper 282624 1 xe
cec 94208 2 drm_display_helper,xe
video 81920 3 asus_wmi,asus_nb_wmi,xe
intel_vsec 20480 2 intel_pmc_core,xe
boot cmdline: BOOT_IMAGE=/boot/vmlinuz-6.14.4-1-default root=UUID=9a5cc792-555f-4e07-a2f3-c05de2808c89 splash=silent mitigations=auto quiet security=selinux selinux=1
Also glxinfo:
~> glxinfo | grep OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (LNL)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.0.4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
The only place I notice llvmpipe is for Vulkan. Please show installed Mesa packages:
# zypper --no-refresh se -s -i Mesa | egrep -v 'debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f
i | Mesa | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i | Mesa-dri | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i | Mesa-gallium | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i | Mesa-libEGL1 | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i | Mesa-libGL1 | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i | Mesa-libglapi0 | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i | Mesa-vulkan-device-select | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i+ | libOSMesa8 | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i+ | Mesa-demo-es | package | 9.0.0-lp156.87.4 | x86_64 | (System Packages)
i+ | Mesa-demo-x | package | 9.0.0-lp156.87.4 | x86_64 | (System Packages)
i+ | Mesa-libd3d | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i+ | Mesa-libOpenCL | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
i+ | Mesa-libva | package | 23.3.4-150600.83.3.1 | x86_64 | UpdateSLE
il | Mesa-demo-egl | package | 9.0.0-lp160.1.4 | x86_64 | (System Packages)
$ inxi -Ga
Graphics:
Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel
arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-2
empty: DP-1, DP-2, HDMI-A-1, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:5912
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.11 compositor: kwin driver: X:
loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris
gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 120 s-size: 406x254mm (15.98x10.00")
s-diag: 479mm (18.85")
Monitor-1: HDMI-A-2 mapped: HDMI-2 model: Samsung SMS24A850
serial: HCJC400052 built: 2012 res: mode: 1920x1200 hz: 60 scale: 100% (1)
dpi: 94 gamma: 1.2 size: 518x324mm (20.39x12.76") diag: 611mm (24.1")
ratio: 16:10 modes: max: 1920x1200 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.4 glx-v: 1.4
direct-render: yes renderer: Mesa Intel HD Graphics 630 (KBL GT2)
device-ID: 8086:5912 memory: 30.09 GiB unified: yes
API: Vulkan v: 1.3.275 layers: 1 device: 0 type: integrated-gpu name: Intel
HD Graphics 630 (KBL GT2) driver: mesa intel v: 23.3.4
device-ID: 8086:5912 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo gpu: gputop,
intel_gpu_top, lsgpu x11: xdriinfo, xdpyinfo, xprop, xrandr
$
~> zypper --no-refresh se -s -i Mesa | egrep -v 'debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f
i | libOSMesa8 | package | 25.0.4-413.2 | x86_64 | mirror-oss
i | Mesa | package | 25.0.4-413.2 | x86_64 | mirror-oss
i | Mesa-demo-egl | package | 9.0.0-4.1 | x86_64 | mirror-oss
i | Mesa-demo-x | package | 9.0.0-4.1 | x86_64 | mirror-oss
i | Mesa-dri | package | 25.0.4-413.2 | x86_64 | mirror-oss
i | Mesa-gallium | package | 25.0.4-413.2 | x86_64 | mirror-oss
i | Mesa-libEGL1 | package | 25.0.4-413.2 | x86_64 | mirror-oss
i | Mesa-libGL1 | package | 25.0.4-413.2 | x86_64 | mirror-oss
i | Mesa-libva | package | 25.0.4-413.2 | x86_64 | mirror-oss
i | Mesa-vulkan-device-select | package | 25.0.4-413.2 | x86_64 | mirror-oss
I think KDE is just using the wrong information. The same happened on my system after libvulkan_lvp was made a dependency of Mesa. I don’t even have a graphics card that can use the vulkan drivers, I think therefore it shows llvmpipe, still I have hardware acceleration through the kernel drivers. When I remove libvulkan_lvp (ignoring that it might break Mesa/Mesa-dri), KDE will show the correct information.
I suspect so, since I am not encountering any software rendering sluggish. Furmark also acts weird (it’s based on mesa-egl I believe) where there are llvmpipe and Intel Graphics backends which provide same performance and both use only one CPU core. I can’t be sure because intel_gpu_top complains not finding i915 devices.
Where can I report this issue? The info was fine on Fedora 42 KDE (except the intel-gpu-tools) before I distrio-hopped to TW.
@swannema that would explain why my card started showing as a “discrete” gpu 2 updates ago even though this isn’t a laptop and I don’t have onboard or hybrid graphics … I see llvmpipe but it only gets used if I disable modeset=1 on my Nvidia card
The System Settings > Graphics information might be more useful from a desktop POV?
To get Intel OpenCL working you need to install:
intel-opencl
You can install clinfo to check OpenCL from a terminal. I had to install it manually because it wasn’t pulled by any other packages as a dependency. That was a year ago, so maybe it installs now.
Number of platforms 1
Platform Name Intel(R) OpenCL Graphics
Platform Vendor Intel(R) Corporation
Platform Version OpenCL 3.0
Platform Profile FULL_PROFILE
Then you’ll probably need these for other features if they’re not installed.
intel-vaapi-driver
To get my Intel ARC A750 Xe device to do Raytracing in Blender I had to install intel-level-zero-gpu-raytracing-1.0.0-1.x86_64.rpm from their github. Raytracing doesn’t work in the Blender from the TW repo because it’s not compiled with Level Zero support. You need to download Blender from their website.
intel-level-zero-gpu-raytracing has been deleted from the level-zero-raytracing-support github.
I’m going to have to compile Level Zero because Raytracing stopped working in the newer 4.x versions of Blender.
My Windows Manager report as follows: openSUSE Paste
Also I’ve checked nvtop and it successfully reports GPU usage from plasmashell, etc.
@jsmith64 Raytracing support was enabled in Mesa. I noticed that 4.4.0 Blender benchmark showed it needed support… I only have A380 and A310 hardware. I do have the raytracing rpm installed…https://build.opensuse.org/package/show/home:malcolmlewis:TESTING/intel-level-zero-gpu-raytracing
@yikerman Xe support is still work in progress, there are still packages that look for i915 and not Xe…
You could try telling Mesa to use the ARC gpu with a /etc/environment file containing MESA_VK_DEVICE_SELECT="8086:64a0" I’m assuming that Mesa-vulkan-device-select is installed?
2 Likes
The incorrect information is resolved after installing intel-va-driver and/or intel-opecl. Thanks!
1 Like
Thanks Malcom…I had to change the device ID to my A750 (56a1) in environment but it made to difference. I’ll start a new thread and see if anyone has it working.
And to the OP, you’re very welcome!
1 Like
system
May 8, 2025, 12:22pm
17
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
