Hello @jkirk, info: llvmpipe (LLVM 15.0.6, 256 bits): from your Proton log tells us that your integrated GPU isn't being used and was forced to use the CPU to render the game. Your extended diagnostics information tells us that Vulkan in general doesn't have a usable GPU, and it's not immediately clear why.
Oh wow, thx @kisak-valve for looking into this and for your comment!
Can you give me some pointer on where to to start debugging the problem?
The following are mostly learnings + notes-to-self. Please do not hesitate to point me to incorrect information and/or wrong assumptions. Thx!
I am new to the whole Proton / Vulkan stuff and trying to get my head around everything and this is what I tried so far.
I didn't know what to look at, but now I found this section in the Steam Runtime System Information:
"architectures" : {
"i386-linux-gnu" : {
"can-run" : true,
"libdl-LIB" : "lib/i386-linux-gnu",
"libdl-PLATFORM" : "i686",
"runtime-linker" : {
"path" : "/lib/ld-linux.so.2",
"resolved" : "/usr/lib/i386-linux-gnu/ld-linux.so.2"
},
"library-issues-summary" : [
],
"graphics-details" : {
"x11/vulkan" : {
"renderer" : "llvmpipe (LLVM 15.0.6, 256 bits)",
"version" : "Mesa 22.3.6 (LLVM 15.0.6)",
"issues" : [
"software-rendering"
],
[...]
Also the x11/vdpau + x11/vaapi sections show problems. I need to figure out why but I assume they are unrelated to the "software-rendering" problem, or?
The docs state that for DXVK 2.7 "a compatible driver must support Vulkan 1.3" and Intel (ANV) 25.0 is required.
xserver-xorg-video-intel 2:2.99.917+git20210115-1 installed. I just read the description which states:The use of this driver is discouraged if your GPU is new enough (ca.
2007 and newer). You can try uninstalling this driver and let the
server use its built-in modesetting driver instead.
Is this the problem? Why is it installed anyway? Is it used? How to find that out?
It seems not (modesetting_drv.so is used and not intel_drv.so):
❯ grep 'LoadModule: "modesetting"' -A 5 /var/log/Xorg.0.log
[ 17.313] (II) LoadModule: "modesetting"
[ 17.313] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 17.313] (II) Module modesetting: vendor="X.Org Foundation"
[ 17.313] compiled for 1.21.1.7, module version = 1.21.1
[ 17.313] Module class: X.Org Video Driver
[ 17.313] ABI class: X.Org Video Driver, version 25.2
and what about this old README?
❯ cat /usr/share/doc/xserver-xorg-video-intel/README.Debian
xserver-xorg-video-intel (2:2.13.0-2) unstable; urgency=low
* Starting from 2.10, the Intel X driver depends on a kernel driver for
mode setting (that's called KMS). The corresponding kernel option is
CONFIG_DRM_I915, and is enabled in Debian kernels.
* To enable KMS, either of those should be sufficient:
+ /etc/modprobe.d/i915-kms.conf should contain:
options i915 modeset=1
+ CONFIG_DRM_I915_KMS=y should be set in the kernel config.
* If you have issues with this driver, the "vesa" or "fbdev" drivers
may be useful fallbacks.
-- Cyril Brulebois <[email protected]> Sun, 07 Nov 2010 19:51:56 +0100
❯ dpkg -l | grep mesa-vulkan
ii mesa-vulkan-drivers:amd64 22.3.6-1+deb12u1 amd64 Mesa Vulkan graphics drivers
ii mesa-vulkan-drivers:i386 22.3.6-1+deb12u1 i386 Mesa Vulkan graphics drivers
❯ vulkaninfo | grep -E "driverName|driverInfo" -A2
driverName = Intel open-source Mesa driver
driverInfo = Mesa 22.3.6
conformanceVersion:
major = 1
--
driverName = Intel open-source Mesa driver
driverInfo = Mesa 22.3.6
conformanceVersion:
major = 1
--
driverName = llvmpipe
driverInfo = Mesa 22.3.6 (LLVM 15.0.6)
conformanceVersion:
major = 1
--
driverName = llvmpipe
driverInfo = Mesa 22.3.6 (LLVM 15.0.6)
conformanceVersion:
major = 1
❯ glxinfo | grep "OpenGL version string"
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.6
So yes, as Intel (ANV) is part of the Mesa project, I think I have version 22.3.6 installed.
Open questions:
software-rendering used/shown in Steam?Primary VRAM Not Detected is shown in the Steam System Information. Is that a problem?I will purge the xserver-xorg-video-intel driver, reboot and check if anything changed.
After some further research, I found this:
❯ vkcube
Selected GPU 0: Intel(R) Graphics (RPL-P), type: IntegratedGpu
❯ vulkaninfo | grep deviceName
deviceName = Intel(R) Graphics (RPL-P)
deviceName = llvmpipe (LLVM 15.0.6, 256 bits)
But my dedicated steam user showed this (called via sudo):
steam@tranquility:~$ vkcube
Selected GPU 0: llvmpipe (LLVM 15.0.6, 256 bits), type: Cpu
steam@tranquility:~$ vulkaninfo | grep deviceName
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
ERROR: [../src/intel/vulkan/anv_device.c:842] Code 0 : Unable to open device /dev/dri/renderD128: Permission denied (VK_ERROR_INCOMPATIBLE_DRIVER)
ERROR: [../src/intel/vulkan_hasvk/anv_device.c:685] Code 0 : Unable to open device /dev/dri/renderD128: Permission denied (VK_ERROR_INCOMPATIBLE_DRIVER)
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
deviceName = llvmpipe (LLVM 15.0.6, 256 bits)
I checked the permission of /dev/dri/renderD128
❯ l /dev/dri/renderD128
crw-rw----+ 1 root render 226, 128 Feb 6 08:33 /dev/dri/renderD128
After I added the user steam to the group render I got about 60 FPS:
❯ groups steam
steam : steam audio users render
❯ sudo adduser steam render
[sudo] password for jkirk:
Adding user `steam' to group `render' ...
Done.
The game runs fine now. Thank you for your support.
Closing the issue.
proton 9.0-4x1 2025-08PROTON_USE_WINED3D=1x1 2025-08PROTON_USE_WINED3D=1 %command%x1 2025-08
Compatibility Report
System Information
I confirm:
Symptoms
Game starts, but after "Loading" is shown FPS drops to 1.
Workaround: Properties > General > Launch Options:
PROTON_USE_WINED3D=1 %command%Reproduction
steam-1291010.log