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

[BUG] SteamVR Error 109: Not initialization due to unknown reasons

Open LovelyParanoia opened this issue 1 year ago • 2 comments

Description VRmonitor show the status of every working device, but once you want to use it, is like there isn't any of them plugged. For the same reason is not possible to pass the initial room setup due to the configuration don't recognizes the devices itself. Every device has it's own green icon at screen. Steam proceed to show at least 3 error messages, 2 while launching VRmonitor and 1 while using VRmonitor.

To Reproduce

  1. Turn on the VR headset/Valve Index kit
  2. Open Steam launcher
  3. Click either the VR button or "Play" at SteamVR at library
  4. An error message will appear, telling you wasn't possible the process of initialization
  5. "OK" is pressed
  6. VRmonitor, VRsettings and a window called "unkown" will be opened, then another message like in step 4 appear, proceeding as step 5 anyway

Expected behavior Execution of SteamVR without warning alerts and working out-of.the-box like every Valve Index device with Steam installed. Being able to pass the room setup from beggining to end.

System Information

Manufacturer: LENOVO Model: LNVNB161216 Form Factor: Laptop CPU: AMD Ryzen 5 5600H with Radeon Graphics Operating System Version: Pop!_OS 22.04 LTS (64 bit) (Ubuntu based) Kernel Name: Linux Kernel Version: 6.8.0-76060800daily20240311-generic X Server Vendor: The X.Org Foundation X Server Release: 12101004 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20240507.87025 GPU: Nvidia RTX 3060 Video Card: AMD AMD Radeon Graphics (radeonsi, renoir, LLVM 15.0.7, DRM 3.57, 6.8.0-76060800daily20240311-generic) Driver Version: 4.6 (Compatibility Profile) Mesa 24.0.3-1pop1~1711635559~22.04~7a9f319 OpenGL Version: 4.6 Monitor Refresh Rate: 60 Hz Number of Monitors: 1 Number of Logical Video Cards: 2 Desktop Resolution: 1920 x 1080 Primary VRAM: 2048 MB Audio device: Nvidia GPU 9f HDMI/DP RAM: 13844 Mb VR Headset: Valve Index HMD (lighthouse) UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 928723 MB Proton version: Experimental branch (Jun 7, 2024) SteamVR version: Beta (Jun 7, 2024) Steam installer origin: Steam official website .deb file (flatpack was more error-proning) Headset video connection: USB-C using adaptor from thunderbolt 1.4 to DisplayPort

Auto-generated reports steam-logs.tar.gz steam-minidumps.tar.gz Steam Runtime Diagnostic.tar.gz SteamVR System Report.tar.gz

Screenshots Screenshot from 2024-06-06 22-07-04 Screenshot from 2024-06-06 23-01-33 Screenshot from 2024-06-06 17-25-41

Additional context

  • Launch commands was used to try different configurations with no improvement:
    • " __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only %command% "
    • " mesa_glthread=true %command% "
    • [setup enviroment options before launching SteamVR] (sorry, I already forget the command)
  • Tryied with nvidia-driver-470 and nvidia-driver-550 provided by the operative system itself
  • Launched with Wayland and X11 with no success in either case
  • Was working as intended at Windows before migration. There, the firmware was updated.

LovelyParanoia avatar Jun 06 '24 23:06 LovelyParanoia

Hello @LovelyParanoia, it's been a fairly long while since I tested SteamVR on an Optimus laptop and some missing logs of interest makes it a bit more difficult to ponder.

From memory, SteamVR has a hard time finding the physical display connection when X is running on a different GPU than the port is wired into. It's fairly common for an Optimus laptop to have the integrated display physically wired to the integrated GPU while the additional HDMI/Displayport connections are physically wired to the NVIDIA GPU. The Failed to connect to headset display suggests this is still true.

If this was my system, I'd try the following to align to my memory.

  1. Switch to an X based user session.
  2. Reconfigure X to run the user session on the NVIDIA GPU.
  3. Run Steam from a terminal to remove PrefersNonDefaultGPU=true as a possible factor.

After that it's still a question if the adapters you're using add another layer of complexity that hasn't been accounted for.

kisak-valve avatar Jun 10 '24 13:06 kisak-valve

I am hitting this error as well on my desktop. Nvidia 3090 with the latest 555 beta drivers on KDE 6.1 and kernel 6.9 on Fedora 40. I am using a Wayland session and X11 is not an option as I am running the Bazzite 'testing' image without X11 support.

dylanmtaylor avatar Jun 22 '24 20:06 dylanmtaylor