[BUG] Error 496 no matter what i try
Describe the bug When starting steamVR, i always get error 496 ("Failed to connect to headset display. Your headset might not be connected, or your desktop environment might not support VR."). I also had that issue previously, but up until recently, i could "fix" it by just restarting steamVR. Now the error persists, no matter what i do. I restart steamVR, restart the headset, try different display ports and usb ports, try a different nvidia driver for my RTX 2070, restart the pc, try different versions of steamVR, etc. but no luck.
To Reproduce Steps to reproduce the behavior:
- start steamVR.
Expected behavior steamVR working without errors
System Information (please complete the following information): Please use the latest Steam beta client and SteamVR beta for your bug reports!
- Steam client version (build number or date): 1737514353
- SteamVR version: beta
- Distribution (e.g. Ubuntu): Mint 21.3 Cinnamon
- Steam runtime diagnostics: [generate via Help -> Steam Runtime Diagnostics in the Steam client]
- Steam and SteamVR logs: [generate by running this command in a terminal
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
- Minidumps:
Screenshots
From everything I've read it's is related to Mesa https://github.com/ValveSoftware/SteamVR-for-Linux/issues/715#issuecomment-2646385755
I will add that removing my HTC Link Box from the HDMI and USB equations allows SteamVR to see my HMD, but no game dose
It´s unable to access your HMD display connection but fails to do so!
try checking wether your GPU sees your headset on a port via:
cat /sys/class/drm/card1-DP-3/edid | parse-edid
try different names it might be card0-DP-1 or so on your system. should look like this:
Checksum Correct
Section "Monitor"
Identifier "Index HMD"
ModelName "Index HMD"
VendorName "VLV"
# Monitor Model Year: 2018
# EDID version 1.3
# Digital Display
# Display Physical Size not given. Normal for projectors.
Gamma 2.20
Option "DPMS" "false"
#Extension block found. Parsing...
I only know about extension blocks of type 02h. PLEASE email me!
even if the Index is "off" (screen not active but blue leds on the front) If you don´t see it, it might be an issue with your GPU driver or the physical connection!
From your vrcompositor.txt:
Fri Jan 24 2025 23:57:19.267714 [Info] - HMD deviceUUID is e5729c8c26695603
Fri Jan 24 2025 23:57:19.267742 [Info] - Looking for direct display through RandR
Fri Jan 24 2025 23:57:19.267754 [Info] - - Root 0x1db
Fri Jan 24 2025 23:57:19.336562 [Info] - - Output 0x1bc - 0 modes, 0 preferred
Fri Jan 24 2025 23:57:19.336668 [Info] - - Output 0x1bd - 0 modes, 0 preferred
Fri Jan 24 2025 23:57:19.336767 [Info] - - Output 0x1be - 0 modes, 0 preferred
Fri Jan 24 2025 23:57:19.336804 [Info] - - Output 0x1bf - 0 modes, 0 preferred
Fri Jan 24 2025 23:57:19.336834 [Info] - - Output 0x1c0 - 20 modes, 1 preferred
Fri Jan 24 2025 23:57:19.336846 [Info] - - Mode 0 0x1c1 1920x1080 (looking for 2880x1600)
Fri Jan 24 2025 23:57:19.336865 [Info] - - Output 0x1d5 - 0 modes, 0 preferred
Fri Jan 24 2025 23:57:19.336884 [Info] - - Output 0x1d6 - 0 modes, 0 preferred
Fri Jan 24 2025 23:57:19.336895 [Info] - Tried to find direct display through RandR: (nil)
Fri Jan 24 2025 23:57:19.336903 [Info] - Looking for direct display through Vulkan WSI
Fri Jan 24 2025 23:57:19.474968 [Info] - - Vulkan output 0: 1920x1080 resolution, 530x300 dimensions - BenQ GL2460 (HDMI-0)
Fri Jan 24 2025 23:57:19.475086 [Info] - Tried to find direct display through Vulkan WSI: (nil)
Fri Jan 24 2025 23:57:19.475114 [Error] - CHmdWindowSDL: Failed to create direct mode surface
Fri Jan 24 2025 23:57:19.475389 [Error] - CHmdWindowSDL: VR requires direct mode.
If you're still having issues it could very well be related to mesa. It seems to be the source in my case at least, was getting the same error prior. Updating it to 25.0.2 would refuse to connect to the display, however reverting to 25.0.1 worked fine.
I talk a little more about it here https://github.com/ValveSoftware/SteamVR-for-Linux/issues/715#issuecomment-2764229062
I too have this issue with an nvidia GPU. My headset is detected at DP-3 and shows up as Index HMD but it just doesn't connect. dmesg shows these issues with nvidia:
[ 6.296705] nvidia 0000:01:00.0: [drm] No compatible format found
[ 6.296707] nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
Since my laptop doesn't have an actual display port it could just be that none of my TB4 connections are wired to the GPU...
Wondering, what is the output of xrandr for you?
I'm facing a somewhat similar issue over at #778 but with AMD and I'm not sure if our issue relates much but try power cycling your Index (just unplug the barrel jack connector and back) before starting SteamVR, the output of xrandr should look different with tons of other resolution and refresh rates available listed.
Just a shot in the dark.
@WaviestBalloon you are actually the goat, saved me from an issue i have been trying to solve for like 4 days.