protonscr

Error 307 on Ubuntu 18.04.3 with Radeon Vega 64

steamvropen bug
ValveSoftware/SteamVR-for-Linux#274 · opened 2019-11-30 by DKesserich · updated 2020-10-02 · 3 comments · github
DDKesserich 2019-11-30 github

SteamVR always gives an 'Unable to get compositor interface (307) error when running on Ubuntu 18.04.3 with a Radeon Vega 64. Using an original Vive.

System Information (please complete the following information):

Additional Info:

Full specs:
CPU: Ryzen 1700X
RAM: 16 GB
Motherboard: Gigabyte GA-AX370-Gaming K7

xrandr --output HDMI-A-2 --set non-desktop 0 does make the Vive available as a normal display.

About a year ago I tried SteamVR with Ubuntu with this exact same PC and it pretty much just worked. I had a lot of system stability issues that may have been because the USB stick I installed from had some bad sectors and that made for a bad install so I went back to Windows. This time around I just can't get SteamVR to work at all. vrmonitor log shows 'Unable to get compositor interface (307).' I've tried with both the AMD drivers and the drivers from the kisak ppa and have the same results. I'm able to run non-VR stuff fine. I've tried booting back into WIndows and setting the Vive to Extended mode in case there was some setting in the Vive itself that was tripping it up, but that didn't make any difference. Tried just about everything from this issue, as it seemed to be the closest to what I am seeing, but still get the same results. I don't have any onboard video, so it can't be SteamVR trying to use the wrong GPU.

At a bit of a loss here.

DDKesserich 2019-11-30 github

Okay, changing the order of operations I've been able to get the compositor to start up, but I can't get output to the HMD.

New OoO:

  1. Install Ubuntu.
  2. Run the Ubuntu updater and Reboot.
  3. Add the Kisak ppa and update. Move /usr/share/vulkan/icd.d/intel_icd.x86_64.json. Reboot again.
  4. Install Steam.
  5. Plug in the Vive HDMI and USB. Install SteamVR when prompted. Launch SteamVR.

Now SteamVR starts up but it either gives me:

  1. 'Your headset is not in fullscreen' warning. If it gives me this warning, within ~30 seconds my primary monitor goes completely corrupt.
  2. 'Your headset is being treated as a monitor, switch to Direct Mode.' If I have this warning my primary monitor stays normal, and I can see a mirror window on the desktop and everything is updating correctly, but nothing is outputing to the HMD. If I click the 'enable direct mode' button, after SteamVR restarts it gives me the first warning followed by desktop corruption.
Ddsalt 2019-12-05 github

Warning 2 (re. direct mode) is indicating that vrcompositor could not get a lease on the headset display. Check what versions of xserver-xorg-core and xserver-xorg-video-amdgpu – if older than 1.20 and 18.1 respectively, upgrade.

Note, however, that there's a problem with ending the lease, which may cause that warning to happen on the second and subsequent launches of SteamVR in any given X session. If you see this, log out of your desktop session and log back in.

JJulianGro 2020-10-02 github

I think I might be suffering form the same issue.
After installing a Vega 56 into my system, I always get error 307 from SteamVR. Changing from Ubuntu 18.04 to Debian 10 made my Valve Index not appear as a second display anymore but the error still persists.

I never had a problem with my GTX 1080.

Nothing extracted yet.