You are not logged in.
It *is* vulkan related, see the causing thread as well as the suggested workaround (boiling down to "don't use vulkan for proton") - some call in https://archlinux.org/packages/extra/x8 … an-radeon/ (MESA) seems to induce a timeout in the amdgpu kernel module (likely presentation related since vulkan/clients seem to struggle with that a lot)
Offline
It *is* vulkan related, see the causing thread as well as the suggested workaround (boiling down to "don't use vulkan for proton") - some call in https://archlinux.org/packages/extra/x8 … an-radeon/ (MESA) seems to induce a timeout in the amdgpu kernel module (likely presentation related since vulkan/clients seem to struggle with that a lot)
Yeah tried the commands in steam and all it did was throw directx errors at me. Good thing is I don't have to do the unthinkable
... Thanks for your help seth.
Offline
What dx errors?
What's the output of
glxinfo -b(I assume xf86-video-amdgpu is still removed?)
If this works better w/ the AMD ddx driver you can test xorg-server 21.1.25-2 which iirc (gitlab is unresponsive) fixed the ABI incompatibility
Offline
What dx errors?
What's the output ofglxinfo -b(I assume xf86-video-amdgpu is still removed?)
If this works better w/ the AMD ddx driver you can test xorg-server 21.1.25-2 which iirc (gitlab is unresponsive) fixed the ABI incompatibility
This when using the emulation line "PROTON_USE_WINED3D=1 %command%":
Directx 12 is not supported on your system. Try running without the -dx12 or d3d12 command line argument.No I put the package back on for testing yesterday.
err the output is 33
Last edited by slayerking (2026-10-17 09:43:05)
Offline
glxinfo -BDropped the shift too fast ![]()
No I put the package back on for testing yesterday.
And you get the same errors w/ or w/o?
Offline
glxinfo -BDropped the shift too fast
No I put the package back on for testing yesterday.
And you get the same errors w/ or w/o?
Ahh ok, Yes same error. I removed it again last night and installed mesa-git now vulkan-radeon is gone as well.
glxinfo -B
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon RX 7900 XTX (radeonsi, navi31, ACO, DRM 3.64, 7.2.9-zen1-1-zen) (0x744c)
Version: 27.0.0
Accelerated: yes
Video memory: 24576MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 23834 MB, largest block: 23834 MB
VBO free aux. memory - total: 31841 MB, largest block: 31841 MB
Texture free memory - total: 23834 MB, largest block: 23834 MB
Texture free aux. memory - total: 31841 MB, largest block: 31841 MB
Renderbuffer free memory - total: 23834 MB, largest block: 23834 MB
Renderbuffer free aux. memory - total: 31841 MB, largest block: 31841 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 24576 MB
Total available memory: 56543 MB
Currently available dedicated video memory: 23834 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 7900 XTX (radeonsi, navi31, ACO, DRM 3.64, 7.2.9-zen1-1-zen)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 27.0.0-devel (git-335d5698dc)
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 27.0.0-devel (git-335d5698dc)
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 27.0.0-devel (git-335d5698dc)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20Offline
Ah, there's something called "Diablo II: Resurrected" - I assume you're talking about that and not the game from 2000?
So the DX12 requirement is probably legit (and that depends on vulkan) - your GL looks ok.
Let's see how mesa-git performs then…
You could also test https://aur.archlinux.org/packages/linux-drm-tip-git
Offline
Ah, there's something called "Diablo II: Resurrected" - I assume you're talking about that and not the game from 2000?
So the DX12 requirement is probably legit (and that depends on vulkan) - your GL looks ok.Let's see how mesa-git performs then…
You could also test https://aur.archlinux.org/packages/linux-drm-tip-git
Yeah the new D2r and the new Hellraiser game. I assume it won't do it again with mesa-git as it got rid of vulkan-radeon. I don't think proton was in it as much as vulkan as my browser did the same thing just going to use a bookmark so no proton involved.
If it does start doing it again I will try that linux-drm-tip and report back. Thanks again
Offline
I assume it won't do it again with mesa-git as it got rid of vulkan-radeon
I guess you haven't looked at the sticky comment ?
repo mesa uses tricks to split upstream sourcecode into multiple packages for reasons unknown (to me) , aur mesa-git tries its best to avoid doing that.
Mesa-git includes vulkan, opencl-mesa and almost anything repo mesa splits off to separate packages.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
slayerking wrote:I assume it won't do it again with mesa-git as it got rid of vulkan-radeon
I guess you haven't looked at the sticky comment ?
repo mesa uses tricks to split upstream sourcecode into multiple packages for reasons unknown (to me) , aur mesa-git tries its best to avoid doing that.
Mesa-git includes vulkan, opencl-mesa and almost anything repo mesa splits off to separate packages.
No, No I didn't thanks for that, Usually just read the pkgbuild to check what it's doing, Obviously not enough it seems. It seems to be ok now haven't had one crash yet (don't want to jinx myself) hopefully stays that way.
Offline
Think I found the problem #5711 and it looks like a fix maybe on the way soon
Offline