You are not logged in.
Hey,
I'm trying to play star wars battlefront 2 through steam, but if I press the "play" button on steam, an EA window pops up, then closes after some seconds. Then after about 5 minutes, the play button reappears. Currently i've tried Proton Experimental, GE-Proton-10, Proton-9.0-7, GE-Proton-9
The main thing that stands out to me is the LIBGL_ALWAYS_SOFTWARE hack being called (shows up in the log when running with PROTON_LOG=1 %command%, but the log file is too big and i can't upload it to a gist)
I'm currently running an AMD 9070XT, and i believe i have all the proper drivers installed
~ took 5s
❯ vulkaninfo --summary
WARNING: radv is not a conformant Vulkan implementation, testing use only.
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.313
Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_headless_surface : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
Instance Layers: count = 10
---------------------------
VK_LAYER_FROG_gamescope_wsi_x86_64 Gamescope WSI (XWayland Bypass) Layer (x86_64) 1.3.221 version 1
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1
VK_LAYER_MESA_screenshot Mesa Screenshot layer 1.4.303 version 1
VK_LAYER_MESA_vram_report_limit Limit reported VRAM 1.4.303 version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
Devices:
========
GPU0:
apiVersion = 1.4.311
driverVersion = 25.1.4
vendorID = 0x1002
deviceID = 0x7550
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Radeon RX 9070 XT (RADV GFX1201)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 25.1.4-arch1.1
conformanceVersion = 1.4.0.0
deviceUUID = 00000000-0300-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000~
❯ pacman -Qs amd
local/amdgpu_top 0.10.5-1
Tool that shows AMD GPU utilization
local/lib32-vulkan-radeon 1:25.1.4-1
Open-source Vulkan driver for AMD GPUs - 32-bit
local/libteam 1.32-2
Library for controlling team network device
local/vulkan-radeon 1:25.1.4-1
Open-source Vulkan driver for AMD GPUs
~
❯ pacman -Qs vulkan
local/lib32-vulkan-icd-loader 1.4.313.0-1
Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/lib32-vulkan-mesa-layers 1:25.1.4-1
Mesa's Vulkan layers - 32-bit
local/lib32-vulkan-radeon 1:25.1.4-1
Open-source Vulkan driver for AMD GPUs - 32-bit
local/qt6-shadertools 6.9.1-1 (qt6)
Provides functionality for the shader pipeline that allows Qt Quick to operate on Vulkan, Metal, and Direct3D, in addition to
OpenGL
local/spirv-tools 1:1.4.313.0-1 (vulkan-devel)
API and commands for processing SPIR-V modules
local/vulkan-icd-loader 1.4.313.0-1 (vulkan-devel)
Vulkan Installable Client Driver (ICD) Loader
local/vulkan-mesa-layers 1:25.1.4-1
Mesa's Vulkan layers
local/vulkan-radeon 1:25.1.4-1
Open-source Vulkan driver for AMD GPUs
local/vulkan-tools 1.4.313.0-1 (vulkan-devel)
Vulkan tools and utilitiesOffline
Could you share the outputs of
dmesg | grep amd
lspci -k | grep -A 3 -E "(VGA|3D)"It seems with vulkan there are contradictory issues regarding which drivers are to be used:
This article points to vulkan-radeon being the problem (or lack of amdvlk), but directly beneath it amdvlk appears to be the problem (and from what other pages and discussions I've read, is definitely the more problematic one)
It might be worth having a look at switching or using both (even though amdvlk may not be desirable), since there appear to be issues
WARNING: radv is not a conformant Vulkan implementation, testing use only.Last edited by airbus777neo (2025-06-22 08:02:36)
Just a computer fanatic finally beginning to etch out of his shell in experience
"The man who chases two rabbits catches none." — Confucius
Offline
It might be worth having a look at switching or using both (even though amdvlk may not be desirable), since there appear to be issues
WARNING: radv is not a conformant Vulkan implementation, testing use only.
https://www.khronos.org/conformance/ado … t-products
Getting cards added to that list takes time, effort and money .
Sofar no one has taken those steps for the amd RX 9000 family with the mesa radv driver .
Judging by forum posts and being involved with several aur mesa git packages, there are very few usecases for archlinux where amdvlk is better then radv.
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
Online
❯ sudo dmesg | grep amd
[ 2.572278] [drm] amdgpu kernel modesetting enabled.
[ 2.572392] amdgpu: Virtual CRAT table created for CPU
[ 2.572397] amdgpu: Topology: Add CPU node
[ 2.572422] amdgpu: Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.
[ 2.572482] amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
[ 2.575283] amdgpu 0000:03:00.0: amdgpu: detected ip block number 0 <soc24_common>
[ 2.575284] amdgpu 0000:03:00.0: amdgpu: detected ip block number 1 <gmc_v12_0>
[ 2.575284] amdgpu 0000:03:00.0: amdgpu: detected ip block number 2 <ih_v7_0>
[ 2.575285] amdgpu 0000:03:00.0: amdgpu: detected ip block number 3 <psp>
[ 2.575286] amdgpu 0000:03:00.0: amdgpu: detected ip block number 4 <smu>
[ 2.575286] amdgpu 0000:03:00.0: amdgpu: detected ip block number 5 <dm>
[ 2.575287] amdgpu 0000:03:00.0: amdgpu: detected ip block number 6 <gfx_v12_0>
[ 2.575288] amdgpu 0000:03:00.0: amdgpu: detected ip block number 7 <sdma_v7_0>
[ 2.575288] amdgpu 0000:03:00.0: amdgpu: detected ip block number 8 <vcn_v5_0_0>
[ 2.575289] amdgpu 0000:03:00.0: amdgpu: detected ip block number 9 <jpeg_v5_0_0>
[ 2.575290] amdgpu 0000:03:00.0: amdgpu: detected ip block number 10 <mes_v12_0>
[ 2.575302] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
[ 2.575303] amdgpu: ATOM BIOS: 113-3E490TX-UP3
[ 2.610842] amdgpu 0000:03:00.0: vgaarb: deactivate vga console
[ 2.610847] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[ 2.610876] amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
[ 2.610877] amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
[ 2.610943] amdgpu 0000:03:00.0: BAR 2 [mem 0x4060000000-0x40601fffff 64bit pref]: releasing
[ 2.610946] amdgpu 0000:03:00.0: BAR 0 [mem 0x4050000000-0x405fffffff 64bit pref]: releasing
[ 2.610974] amdgpu 0000:03:00.0: BAR 0 [mem 0x4400000000-0x47ffffffff 64bit pref]: assigned
[ 2.610982] amdgpu 0000:03:00.0: BAR 2 [mem 0x4200000000-0x42001fffff 64bit pref]: assigned
[ 2.611035] amdgpu 0000:03:00.0: amdgpu: VRAM: 16304M 0x0000008000000000 - 0x00000083FAFFFFFF (16304M used)
[ 2.611038] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[ 2.611357] [drm] amdgpu: 16304M of VRAM memory ready
[ 2.611358] [drm] amdgpu: 15882M of GTT memory ready.
[ 2.611435] amdgpu 0000:03:00.0: amdgpu: PCIE GART of 512M enabled (table at 0x00000083DAB00000).
[ 2.612430] amdgpu 0000:03:00.0: amdgpu: Found VCN firmware Version ENC: 1.7 DEC: 9 VEP: 0 Revision: 49
[ 2.843700] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 2.843703] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[ 2.843747] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000002e, smu fw if version = 0x00000032, smu fw program = 0, smu fw version = 0x00684600 (104.70.0)
[ 2.843754] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[ 2.882129] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
[ 3.216712] amdgpu 0000:03:00.0: amdgpu: program CP_MES_CNTL : 0x4000000
[ 3.216715] amdgpu 0000:03:00.0: amdgpu: program CP_MES_CNTL : 0xc000000
[ 3.277411] amdgpu: HMM registered 16304MB device memory
[ 3.278902] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[ 3.278910] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[ 3.278953] amdgpu: Virtual CRAT table created for GPU
[ 3.279021] amdgpu: Topology: Add dGPU node [0x7550:0x1002]
[ 3.279022] kfd kfd: amdgpu: added device 1002:7550
[ 3.279028] amdgpu 0000:03:00.0: amdgpu: SE 4, SH per SE 2, CU per SH 8, active_cu_number 64
[ 3.279031] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 3.279031] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 3.279032] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 3.279032] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 6 on hub 0
[ 3.279032] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 7 on hub 0
[ 3.279033] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 8 on hub 0
[ 3.279033] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 9 on hub 0
[ 3.279033] amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[ 3.279034] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
[ 3.284194] amdgpu 0000:03:00.0: amdgpu: Using BACO for runtime pm
[ 3.284434] amdgpu 0000:03:00.0: [drm] Registered 4 planes with drm panic
[ 3.284435] [drm] Initialized amdgpu 3.63.0 for 0000:03:00.0 on minor 1
[ 3.304500] fbcon: amdgpudrmfb (fb0) is primary device
[ 3.304503] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[ 6.510664] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])❯ lspci -k | grep -A 3 -E "(VGA|3D)"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 [RX 9070/9070 XT] (rev c0)
Subsystem: Sapphire Technology Limited Device 3490
Kernel driver in use: amdgpu
Kernel modules: amdgpuOffline
airbus777neo wrote:It might be worth having a look at switching or using both (even though amdvlk may not be desirable), since there appear to be issues
WARNING: radv is not a conformant Vulkan implementation, testing use only.https://www.khronos.org/conformance/ado … t-products
Getting cards added to that list takes time, effort and money .Sofar no one has taken those steps for the amd RX 9000 family with the mesa radv driver .
Judging by forum posts and being involved with several aur mesa git packages, there are very few usecases for archlinux where amdvlk is better then radv.
Sorry, trying to understand your reply. Are you saying
a) radv doesn't have support yet for the RX9000 family
b) you agree amdvlk might solve the issue?
Just want to make sure i understand
Offline
Looking at the link he provided it seems the RX 9070XT does not have any driver for arch that conforms with vulkan (only for Windows 10 and Ubuntu)
And yeah essentially amdvlk is often worse off compared to vulkan-radeon
You could still try it if you want to, but...
Even the wiki says so https://wiki.archlinux.org/title/AMDGPU#Installation:
Test with only vulkan-radeon first: although not appearing as the first provider of vulkan-driver (due to its alphabetical order), it avoids some issues that have repeatedly been reported about amdvlk.
(Not sure if I should put that in a quote, lol)
The only next best thing I can suggest would probably be to look deep into this page: https://wiki.archlinux.org/title/Steam
Last edited by airbus777neo (2025-06-22 18:26:35)
Just a computer fanatic finally beginning to etch out of his shell in experience
"The man who chases two rabbits catches none." — Confucius
Offline