SteamVR-for-Linux icon indicating copy to clipboard operation
SteamVR-for-Linux copied to clipboard

[BUG] Cannot initiate Valve Index in Plasma Wayland, error 310

Open nixRidge opened this issue 1 year ago • 6 comments

Describe the bug In the Plasma Wayland session, I cannot use SteamVR as the Valve Index doesn't turn on. SteamVR opens and displays the following:

SteamVR Fail A Key component of SteamVR isn't working properly. Please restart SteamVR.

Error code 310

To Reproduce

  1. Launch Plasma Wayland
  2. Launch SteamVR and allow it to use setcap if prompted.
  3. Wait for SteamVR to launch.
  4. Observe it launching with error code 310 and aforementioned message.

Expected behavior Expected to play a little Boneworks in the Wayland session.

System Information

  • Distribution: Arch Linux, Linux 6.2.7
  • SteamVR versions: Tested with 1.25.6 and Beta 1.25.7
  • Steam client version: Mar 20 2023, 22:21:44
  • Opted into Steam client beta?: Yes (tried stable first, then beta. version above is beta)
  • Graphics driver version: Mesa 23.0.0
  • Gist for SteamVR System Information: Wayland | X11
  • Possibly relevant system info:

AMD Radeon RX 6700 XT xwayland 23.1.0 Plasma 5.27.3 Wayland 1.21.0 wayland-protocols 1.31

Additional context It was working fine in the Wayland session at the start of February this year. Tested and working in the X11 session. The udev rules are OK. xrandr sees the HMD in both X11 and Wayland. kscreen-console does NOT see the HMD in Wayland. Tried setting "enableLinuxVulkanAsync" to both true and false, as well as completely removing the string from steamvr.vrsettings. I have also tried completely removing Steam and anything related to it, then setting Steam and SteamVR up again from scratch. Lighthouses are not detected in Wayland, working in X11.

Thank you for your time.

Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.

nixRidge avatar Mar 24 '23 01:03 nixRidge

Same here, had to switch to Plasma X11 to get it working. Also on Arch but with a 5700 XT

yaomtc avatar Apr 27 '23 18:04 yaomtc

Hi @FridgeRacer , @yaomtc

have you found a solution for error 310?

Some time ago (several months ago) I could play Alyx, however I can't play it anymore i get this code error 310.

I have tried everything from reinstalling steamvr, and using another port for the hdmi.

Thanks so much!

Hicks79 avatar Sep 14 '23 14:09 Hicks79

Not in a position to test right now, @Hicks79, however I can share that I have gotten the HMD working with Plasma Wayland back in July, albeit with colour issues in the overlay, no async reprojection (of course) and no sound. Bluetooth power management still does not work. It is not worth playing on my setup at least, in such a state. A tip though, make sure you have atomic modesetting in enabled (it is on by default, but can be turned off with an environment variable. If you haven't turned this off manually it's most likely on.)

I'll keep the issue open since it still seems to be, well, an issue.

@Hicks79 Do attach relevant system information and logs, maybe it'll help.

nixRidge avatar Sep 14 '23 15:09 nixRidge

Thanks for the Info @FridgeRacer !

System Information

Distribution: Ubuntu 18.04 (Pro), Kernel 4.15.0
SteamVR versions: Tested with Beta 1.27
Opted into Steam client beta?: Yes
Graphics driver version: Nvidia 525.125.06
Desktop: x11

Hicks79 avatar Sep 14 '23 16:09 Hicks79

@Hicks79 Your kernel is very old, can you try with an up to date one? Nothing stating that it shouldn't work on 4.15, but who knows.

nixRidge avatar Sep 14 '23 16:09 nixRidge

hmm I have never had problems before with HL:Alyx for example : S

Hicks79 avatar Sep 14 '23 18:09 Hicks79