Hi guys,
I have an issue with a game that relies on mesa (The Book of Unwritten Tales).
It worked properly on bookworm, but now with trixie I have issues.
It's always falling back to software rendering.
I'm using X11 because with Wayland there is only a black screen.
I already tried all the following switches:
Code:
DRI_PRIME=1DRI_PRIME=pci-0000_00_1c_0MESA_VK_DEVICE_SELECT="1002:6900!"MESA_LOADER_DRIVER_OVERRIDE=radeonsiGLX_VENDOR_LIBRARY_NAME=amdgpuAttached you can find the strace.
The interesting part is:
Code:
[pid 13806] 18:15:07 statx(AT_FDCWD, "/sys/dev/char/136:1/device/drm", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_BASIC_STATS, 0xffefec3c) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)DRI_PRIME: error. Using the default GPUpid 13806] 18:15:07 openat(AT_FDCWD, "/sys/dev/char/136:1/device/vendor", O_RDONLY|O_LARGEFILE) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)[pid 13806] 18:15:07 openat(AT_FDCWD, "/sys/dev/char/136:1/device/device", O_RDONLY|O_LARGEFILE) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)[pid 13806] 18:15:07 statx(6, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_BASIC_STATS, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFCHR|0600, stx_size=0, ...}) = 0[pid 13806] 18:15:07 statx(AT_FDCWD, "/sys/dev/char/136:1/device/drm", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_BASIC_STATS, 0xffefe30c) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)MESA-LOADER: failed to retrieve device informationglx: failed to create dri3 screenfailed to load driver: radeonsiWithout driver override it's:
Code:
MESA-LOADER: failed to retrieve device informationfailed to get driver name for fd 0No driver foundfailed to load driver: (null)DRI_PRIME doesn't seem to matter at all.
Interestingly, mesa *always* tries to open /sys/dev/char/136:1
This device doesn't exist:
Code:
$ ls -l /sys/dev/char/136:1ls: Zugriff auf '/sys/dev/char/136:1' nicht möglich: Datei oder Verzeichnis nicht gefunden136:1 is /dev/pts/1 !
Code:
$ ls -l /dev/pts/1crw------- 1 judy tty 136, 1 5. Feb 18:15 /dev/pts/1Whats going on here? Why is mesa always trying to open pts/1?
Of course it won't find the graphics device there.
Graphics is 226,0 or 226,1:
Code:
$ ls -l /dev/dri/card*crw-rw----+ 1 root video 226, 0 5. Feb 16:54 /dev/dri/card0crw-rw----+ 1 root video 226, 1 5. Feb 16:54 /dev/dri/card1Is there maybe a way to override the device which mesa tries to open?
With "DRI_PRIME=pci-0000_00_1c_0" it didn't work.
Some more info about the system:
Code:
$ DRI_PRIME=1 xdriinfoScreen 0: radeonsiCode:
$ lspci | grep -E "^.*(VGA|Display)"00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 0701:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] (rev 83)Code:
$ MESA_VK_DEVICE_SELECT=list vulkaninfoselectable devices:GPU 0: 1002:6900 "AMD Radeon R7 M340 (RADV ICELAND)" discrete GPU 0000:01:00.0GPU 1: 8086:1916 "Intel(R) HD Graphics 520 (SKL GT2)" integrated GPU 0000:00:02.0GPU 2: 10005:0 "llvmpipe (LLVM 19.1.7, 256 bits)" CPU 0000:00:00.0Code:
$ ls -l /sys/dev/char | grep 226lrwxrwxrwx 1 root root 0 5. Feb 17:40 226:0 -> ../../devices/pci0000:00/0000:00:02.0/drm/card0lrwxrwxrwx 1 root root 0 5. Feb 17:40 226:1 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/drm/card1lrwxrwxrwx 1 root root 0 5. Feb 17:40 226:128 -> ../../devices/pci0000:00/0000:00:02.0/drm/renderD128lrwxrwxrwx 1 root root 0 5. Feb 17:40 226:129 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/drm/renderD129Maybe somebody has an advice?
Thank you very much in advance!
Statistics: Posted by Freeze — 2026-02-05 17:50