Technical Specs: (As best as I can remember at this time)

  • AMD Ryzen Processor
  • Radeon Graphics card
  • PopOS (Currently attempting with KDE Plasma Wayland)
  • I do have Proton Installed.

A while back I decided to give Linux gaming a go, and have overall been really satisfied with the result, with only occasional frustrations. I have mostly been able to figure things out on my own, but I think I’ve reached my technical limit / ability to use search engines in this area.

I am getting very odd behavior when trying to set up/use the Valve Index. I don’t know much about Steam VR, but I will describe what is going on to the best of my ability.

When I click the VR Goggle icon in Steam, it seems to open up Steam VR in a mini-window, and another window for first-time set up.

Here’s where it gets strange/confusing: In the Steam VR, it shows the green icon for the headset, the controllers, and the lighthouses. But in the first time set up (When I select either standing or play area), it says the controllers and headset are off. Steam VR is also giving me an odd error code: 307; and then it tells me it needs to be restarted. When I click the error code to get more information, it tells me a bunch of stuff I need to do in Windows, (Which does not help my situation, of course). Also, when I tried to update the firmware in the lighthouses, I get a Bluetooth error code (I think it was: BT-232).

Has anyone encountered any of these issues?

I have done a few things upon reading the help pages in the Steam VR documentation. For example: I switched to using KDE Plasma with Wayland, as I understand Gnome on Ubuntu is lacking features that KDE Plasna has. Beyond that, however, I am not sure what more I need to do, or if I can do much more. I’m also not sure where I can get more information about these odd status codes, as most answers I find end up being Windows-centric.

  • ZarathustraDKBEnglish
    1·
    10 months ago
    • Gnome + Wayland is a bust currently. Recommend KDE + Wayland.
    • If you experience problems during first run, check that you’re using the radeon icd-loader and not the amdvlk or intel one. SteamVR on linux have a strange habit of just randomly assigning one if all are available, and I’ve experienced a couple of installs/distros where the amdvlk one was simply there by default for some reason.
    • Steam beta + SteamVR beta straight up doesn’t work right now. For a “stable” experience I recommend current Steam + the temp_SteamVR 1.27.5-branch. From there your proton-version may vary depending on which game you’re running, but latest stable is a pretty safe bet.
    • For me, I always have to run and kill SteamVR once per session before it behaves properly. Afterwards, start SteamVR first, then launch your game either from desktop steam, or within VR.
    • oliveoliverYTBEnglish
      1·
      10 months ago

      how do i check i changed yesterday from nvidia gpu to amd and not working steam vr

      • ZarathustraDKBEnglish
        1·
        10 months ago

        Run:

        ls /usr/share/vulkan/icd.d/

        ​

        Then what you want to see is:

        radeon_icd.i686.json radeon_icd.x86_64.json

        ​

        If there’s anything else you need to uninstall the package responsible for it. Usually that’d be amdvlk or some kind of intel-related driver.