Page MenuHomeSolus

SteamVR
Open, NormalPublic

Description

When pushing the play button for SteamVR:

An error occurred while updating SteamVR (missing executable)

Got error messages from the following executables in ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64

./gpuvis: error while loading shared libraries: libsndio.so.6.1: cannot open shared object file: No such file or directory
./vrcmd VR_IsHmdPresent returned false to indicate that there are no attached HMDs
./vrcompositor: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory
./vrdashboard: error while loading shared libraries: libopenvr_api.so: cannot open shared object file: No such file or directory
./vrmonitor: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory
./vrserver: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory

Hopefully this makes some sense

vrcmd VR_IsHmdPresent returned false even after following this particular instruction

Event Timeline

Timalex created this task.May 22 2017, 9:53 PM
JoshStrobl triaged this task as Normal priority.May 23 2017, 8:37 AM
JoshStrobl edited projects, added Software; removed Lacks Project.
JoshStrobl moved this task from Backlog to Package Fixes on the Software board.

A small update

Errors after starting SteamVR from Steam

Currently both Non-native and Native

Shared IPC Compositor Connect Failed (306)

Had the following error repeatedly before launching the standalone SteamVR from Budgie's menu in between (?)
Solus native

vrclient Shared Lib Not Found (102)

The headset and controllers are recognized though.

Other changes
./vrcmd alternately spams the following

ioctl (GFEATURE): Broken pipe
ioctl (SFEATURE): Broken pipe

With gavandor's fix, https://dev.solus-project.com/T3752, error 306 is gone and VR is now live and running on Solus.

Status update
./gpuvis is launching fine ✓

./vrcmd: error while loading shared libraries: libopenvr_api.so: cannot open shared object file: No such file or directory
yaomtc added a subscriber: yaomtc.Feb 25 2018, 9:38 PM

I noticed that the udev rule wasn't present in /usr/lib64/udev/rules.d, nor in /usr/lib/udev/rules.d, though the Steam Controller rule is in both. I tried adding the rule and rebooting, but my Vive still isn't recognized by Steam, only by the system as a second display. What do I need to do?

After power cycling the SteamVR link box, I was able to get Steam to detect my Vive. However, then I run into this error:

SteamVR failed to initialize for unknown reasons. (Error: Shared IPC Compositor Connect Failed (306))

So I re-read Valve's readme again, and found this part that I'd missed.

AMD graphics require the radv driver from Mesa 17.3 or above or mainline mesa after this commit. For proper VK_KHR_external_semaphore_fd and EXT_memory_object_fd support Linux 4.13-rc1 or newer is required. It doesn't support direct mode currently, so the HMD display will have to be positioned on your desktop in extended mode, and your system compositor disabled while using VR.

However you can't disable the compositor in Budgie. So, SteamVR doesn't seem possible for AMD users at the moment? Unless Gnome/MATE supports it, but I haven't looked in to that yet.

Found at least one thing is needed in mesa for direct mode: VK_EXT_direct_mode_display, which a patch has recently been made for: https://patchwork.freedesktop.org/patch/203827/