[BUG] Error 496 on first start of SteamVR after a boot

[anxest]

Describe the bug
The first time of the day I start steamVR, I got an error 496 : "Failed to connect to headset display
Your headset might not be connected, or your desktop environment might not support VR."
But I do have an image in the headset: I can see the loading zone, and the Home "waiting" picture infinitely loading (this is why I register a new bug: not totally sure it's the same as #703; I didn't activated the performance graph either). What I see in the headset is not reflected on the dock VR View though.
In this context, If I try to open the dashboard into my headset, the environment will darken, and I'll see the light bar that usually appear under the dashboard, but the dashboard won't display.
If I quit SteamVR from the dock on the screen, the "exiting VR" will display for a good 30 seconds before effectively turning off. If I restart SteamVR after this, it will now start "normally" (except the settings will display as I mentioned in #712), letting me play.
This issue will happen again after the next fresh start of my computer, or reboot.

To Reproduce
Steps to reproduce the behavior:

1. Turn on the computer or reboot the computer
2. Start SteamVR
3. See error

Expected behavior
Starting SteamVR normally, being able to start Home, display the dashboard and starting a game.

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): 1718521059
• SteamVR version: beta 2.6.2
• Distribution (e.g. Ubuntu): Arch (kernel 6.9.4-arch1-1) with Gnome shell 46, and X11
• Steam runtime diagnostics: Steam runtime diagnostics.txt
• Steam and SteamVR logs: steam-logs.tar.gz
• Minidumps: steam-minidumps.tar.gz

Screenshots

[disco-research2]

Which hardware are you on? Especially laptop or desktop?

[anxest]

It's a desktop

CPU Intel I7 13700k
MB Z690 DDR4
RAM 32GB DDR4 3600 MHz CL18
GPU AMD Radeon RX 7800 XT

[wallcarpet40]

Might be an AMD driver problem rather than SteamVR problem. I found some issues like this over at Gitlab:
https://gitlab.freedesktop.org/drm/amd/-/issues/1856
https://gitlab.freedesktop.org/drm/amd/-/issues/2342
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7041

This happens to me too with Valve Index and Radeon 6800XT. Sometimes even happens with Monado, where Monado will crash in the first start after a reboot. Then I have to start SteamVR, let it crash, choose "Restart Headset" in the SteamVR vrmonitor menu, which will recover the headset to a working state and then start Monado or SteamVR again.

[Flimsy-Fox]

I experience similar behavior on my system; SteamVR fails to connect to headset, and then resumes fine after I've either restarted or disconnected and reconnected headset. Though manifesting differently through the updates (the result was always the same: somehow or another restart headset), it has lasted for about a year (as long as I've owned this system).

Currently, the details are different than yours but I'm unsure if they mean that I have to make a separate issue. My process is as follows:

• Start system, then login.
• Start Steam, then SteamVR. In the Steam window, it says that SteamVR failed to launch; in the SteamVR window, it says that it cannot connect to headset. In the performance graph, there are no frametimes submitted.
• Restart the headset using SteamVR's menu. Restart SteamVR.
• Sometimes I may additionally need to logout, disconnect all cables from the headset, login, then reconnect all cables. I start SteamVR afterward.
• I observe that the SteamVR window opens, there are no errors submitted, and the frametime graph becomes populated with data. Everything works as expected.
• I logout, then log back in. Start SteamVR. Everything works as expected.
  Every time my system reboots, it reverts back to the previous behavior.

For completeness, here are my system details:
CPU: AMD Ryzen 7 7800X3D
GPUs: AMD Radeon RX 7800 XT (Primary), iGPU (Secondary, no display connection); with no PRIME setup
Memory: 32GB with 96GB Z-swap
Headset: Valve Index
Kernel: Linux 6.6.38-1-lts
GPU Driver: Mesa 24.1.3
Distro: Arch Linux 64-bit
DM: KDE Plasma 6.1.2 running Wayland

[pwaller]

Also experiencing this on amdgpu. I have had a good ~year of SteamVR working fairly flawlessly.

At some point recently (in the last couple of months), this has become a frequent problem. I'm using NixOS so I'm able to revert my kernel/software stack to a known good state (aside from SteamVR, which steam updates whenever it likes). I observe that with Linux 6.13.1 and Mesa 24.3.4, I can't get steamvr to work at all. With Linux 6.12.5 and Mesa 24.2.6, things can be made to work, though frequently the first attempt of a startup of steamvr crashes with, e.g.

[   47.727353] [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
[   47.727544] [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
[   47.727690] [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!

The crash is not reliably reproducible though, so it is difficult to tell for sure if it is present or fixed in a given configuration.

The Index headset may give red LEDs, but unplugging/reseating the cable break and trying again often works.

SteamVR beta doesn't appear to work at at all at the moment, crashing in all the configurations I tried.

[meir]

having the same issue aswell, NixOS with an AMD 7900 XT, for some reason it also sometimes freezes up Hyprland completely for a few seconds when first launching before giving an error

[pwaller]

cc @kisak-valve

https://gitlab.freedesktop.org/drm/amd/-/issues/1856#note_2828989 (Timo's comment)

It sounds like there has is progress in understanding the potential causes of the issue on the AMD side, but that it potentially about how the headset interacts with the GPU, and help may be needed from people with an understanding of what's going on headset side to get to the bottom of it.

[fondfinnel]

Hey all - wanted to weigh in on this because it's been driving me nuts after getting a 9070XT. I was losing my mind thinking it was amdvlk being updated causing issues, however I very much believe it's directly related to mesa.

Just for clarification - I have a Valve Index running off of a NixOS host. I tried reinstalling Arch to test that out but I gave up after an hour of headaches getting other problems to deal with.

After reverting my flake to the last nixpkgs commit with mesa 25.0.1 it was up and running again with no issues.

I highly suggest everyone else try reverting mesa to make sure I'm not crazy.

If you're like @meir and I the specific nixpkgs commit is 027c44209b4675c74b5bf95f9c93ef966dda2b88. I just changed where my flake pointed to for system builds to this commit entirely.

[Spacefish]

The root cause for the *ERROR* dc_stream_state is NULL for crtc issue has been found by AMD and they patched it in the amdgpu driver / the display controller part of it, but the patch is not upstream yet, see: https://gitlab.freedesktop.org/drm/amd/-/issues/1856#note_2836580

[fondfinnel]

I have yet to try it myself on mesa 25.0.3 but supposedly it fixes the issue. I'll have to get back to you on that.

…

On April 16, 2025 10:49:01 AM EDT, meir ***@***.***> wrote: meir left a comment (ValveSoftware/SteamVR-for-Linux#715) @natervader it did fix the 496 issue indeed, however it still has issues with consistent rendering after the first boot using the nixpkgs unstable, hyprland and a 7900XT booting up the pc launch SteamVR, it launches then after a second or 2 it freezes up all screens for a couple seconds then it renders fine, but sometimes stops rendering on the HMD with the -203 error as if it loses the connection for a second However its fixed when restarting, it only reoccurs after a boot -- Reply to this email directly or view it on GitHub: #715 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[meir]

i deleted my response because i realized i misread your comment entirely, im currently trying to figure out how to specify the mesa package to use in the unstable channel, it seems like hardware.opengl.package has been deprecated for hardware.graphics but it has no .package field anymore

[fondfinnel]

Couldn't tell you right now, but I just rolled back the nixpkgs flake back to a specific commit. In the case of switching to mesa 25.0.1, I just found the commit prior to 25.0.2 and specified it.

…

On April 16, 2025 12:50:14 PM EDT, meir ***@***.***> wrote: meir left a comment (ValveSoftware/SteamVR-for-Linux#715) i deleted my response because i realized i misread your comment entirely, im currently trying to figure out how to specify the mesa package to use in the unstable channel, it seems like `hardware.opengl.package` has been deprecated for `hardware.graphics` but it has no `.package` field anymore -- Reply to this email directly or view it on GitHub: #715 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[meir]

i actually did end up testing out the latest flakes on unstable after giving up on trying to use that specific mesa driver, steamvr gives a crash at the start but then continues and works actually fine now.

only issue is that the steamvr ui crashes so youre stuck with the old ui in vr