ALVR Driver not being loaded

[Equinoxx4978]

I've installed ALVR and got it all configured. When I clicked lauch SteamVR, it opened as expected, however the ALVR driver wasn't being loaded. The entry for ALVR was not located in the SteamVR settings add-ons page.

I looked in the ALVR app and it said the driver was located in /usr/lib/steamvr/alvr/ however when I opened SteamVR's files I saw that all my driver were stored in ~/.local/share/Steam/steamapps/common/SteamVR. When I moved the file from /usr/.... to /home/Josh/.local/share/Steam/steamapps/common/SteamVR/drivers the driver did appear within SteamVR, but the streamer still wouldn't connect within ALVR.

The reason (im guessing) that ALVR isnt able to connect to the streamer was because its driver was never being loaded because it's in the incorrect location and has things set out incorrectly.

For context (in needed) I'm running:

• Arch Linux
• AMD Radeon RX 6700XT
• Wayland
• Gnome 46

Any help is appreciated as I would really like to use my Quest 3 for PCVR without windows :)

[32bitx64bit]

Hey, if you're using the latest steamVR version the drivers just don't work. Trying using beta and use the previous version.

If that doesn't work try to go to Installation -> and click "register ALVR driver"

Edit. Just saw you're using Wayland on gnome. sucks to be you, SteamVR only supports wayland on KDE and wlroots, you can thank Gnome for that. ( See https://help.steampowered.com/en/faqs/view/18A4-1E10-8A94-3DDA ) You got 2 options, switch to X11 while playing VR. Or switch to KDE / a wlroots compositor if you must use wayland (for some reason)

[josbraden]

Ah a fellow Josh, is this a duplicate of #2130?

[sithlord48]

I have this same issue.
SteamVR just does not list the driver in the list of drivers. I doesn't matter if I use SteamVR 2.5.5 or the previous from the beta list.

I have removed my config files as well as reinstalled alvr and steam vr (a few times)

[Equinoxx4978]

@32bitx64bit ill try out a different DE and ill see how it goes. also will try x11 too just in case

[Equinoxx4978]

I've tried X11 and it's still not working.

I still get the issue of the streamer not connecting. Driver also does not appear in steamvr like before.

[sithlord48]

This is not a Gnome specific issue. I'm using KDE and tried both X11 and Wayland.

[32bitx64bit]

@32bitx64bit ill try out a different DE and ill see how it goes. also will try x11 too just in case

Hm. Odd. Can confirm it just randomly stopped working for me, even on the previous version, No idea what ALVR did, but they fucked something up.

[32bitx64bit]

Found a solution, trying right now.

[32bitx64bit]

Ok so, it seems for some reason at least for my system instead of using the AUR package for ALVR, just downloading the tar file, and extracting it, fixes the drvier not loading.

[Equinoxx4978]

Ok so, it seems for some reason at least for my system instead of using the AUR package for ALVR, just downloading the tar file, and extracting it, fixes the drvier not loading.

I'll give this a go

[Equinoxx4978]

Driver loads, but crashes because of 21:47:05.467632542 ERROR Handshake error for 9643.client: Cannot find audio device which name contains "pipewire" Then because of the crash the driver gets auto-disabled. Any help?

[sithlord48]

I can see it when i use the tarball deployment however I also get that handshake error.

I was able to get it to connect if I disabled both the game audio and microphone but then i only was able to see a black screen on my headset.

[32bitx64bit]

Driver loads, but crashes because of 21:47:05.467632542 ERROR Handshake error for 9643.client: Cannot find audio device which name contains "pipewire" Then because of the crash the driver gets auto-disabled. Any help?

If you're still on gnome wayland, gnome wayland does NOT support DRM (Direct Rendering Manager) on wayland.

If this isn't the case revert to the "Previous" version of steamVR, as the driver does not currently support latest steamVR version(s)

[sithlord48]

I am not on Gnome wayland issue, as i see the same issue with the pipewire device.

I can see it when i use the tarball deployment however I also get that handshake error. I was able to get it to connect if I disabled both the game audio and microphone but then i only was able to see a black screen on my headset.

[Equinoxx4978]

If you're still on gnome wayland, gnome wayland does NOT support DRM (Direct Rendering Manager) on wayland.

If this isn't the case revert to the "Previous" version of steamVR, as the driver does not currently support latest steamVR version(s)

I was on xorg at the time, i believe this may be due to something else...

[32bitx64bit]

If you're still on gnome wayland, gnome wayland does NOT support DRM (Direct Rendering Manager) on wayland. If this isn't the case revert to the "Previous" version of steamVR, as the driver does not currently support latest steamVR version(s)

I was on xorg at the time, i believe this may be due to something else...

Might just be a driver issue with ALVR then, and or a steamVR issue. As they have done a lot of fixes on the newest version, but thanks to ALVR not working on anything above 2.4.4 yeah.

[sithlord48]

It seams to be something on the steam side i was able to get this working when i told steam to run steamVR (only tested with 2.4.4) using the Steam-Play-None Compatibility layer. Using 20.8.1 on both the headset and computer. I used the alvr tarball

[sanpedrox2]

It works for me if i run vrmonitor.sh from ~/.local/share/Steam/steamapps/common/SteamVR/bin instead of letting alvr launch steamvr

[32bitx64bit]

Ok can't get it to launch like at all under wayland. My guess is its a steamVR wayland issue, as it launched mostly fine under x11. Beyond annoying as wayland is just superior in most ways Apart from global hotkeys...

[mrnamwen]

Can also confirm that running via vrmonitor.sh allows ALVR to be detected as others have mentioned, but also experiencing #2069 when trying to load the ALVR driver with a headset connected.

[xDShot]

Driver loads, but crashes because of 21:47:05.467632542 ERROR Handshake error for 9643.client: Cannot find audio device which name contains "pipewire" Then because of the crash the driver gets auto-disabled. Any help?

If you're still on gnome wayland, gnome wayland does NOT support DRM (Direct Rendering Manager) on wayland.

If this isn't the case revert to the "Previous" version of steamVR, as the driver does not currently support latest steamVR version(s)

It worked before, that's bullshit

[xDShot]

[zggzcgy]

I'm guessing this might be related to the SteamVR update, and it's recommended to follow #2115 to configure it to verify that it's available.

[32bitx64bit]

Driver loads, but crashes because of 21:47:05.467632542 ERROR Handshake error for 9643.client: Cannot find audio device which name contains "pipewire" Then because of the crash the driver gets auto-disabled. Any help?

If you're still on gnome wayland, gnome wayland does NOT support DRM (Direct Rendering Manager) on wayland. If this isn't the case revert to the "Previous" version of steamVR, as the driver does not currently support latest steamVR version(s)

It worked before, that's bullshit

I should probably clarify. DRM does not work on GNOME on Ubuntu.

[sithlord48]

I am not using Gnome and have the same issue . KDE plasma 6.1 seen the issue on both x11 and wayland

[LordJABA]

Same issue for me, im on KDE plasma 6.1 tried both x11 and wayland Arch (Garuda)

pacman -Si alvr

Repository      : chaotic-aur
Name            : alvr
Version         : 20.8.1-3
Description     : Experimental Linux version of ALVR. Stream VR games from your PC to your headset via Wi-Fi.
Architecture    : x86_64
URL             : https://github.com/alvr-org/ALVR
Licenses        : MIT
Groups          : None
Provides        : alvr
Depends On      : vulkan-icd-loader  libunwind  libdrm  x264  alsa-lib  libva.so=2-64  libva-drm.so=2-64
libva-x11.so  bash  hicolor-icon-theme
Optional Deps   : None
Conflicts With  : alvr
Replaces        : None
Download Size   : 13,99 MiB
Installed Size  : 34,75 MiB
Packager        : Eduard Tolosa <edu4rdshl@protonmail.com>
Build Date      : nie, 2 cze 2024, 16:00:45
Validated By    : SHA-256 Sum

[PugzAreCute]

Same here.

Arch linux 6.9.7-zen1-1-zen SteamVR 2.6.2 KDE Plasma 6.1.1 (wayland) ALVR streamer v20.9.1 (built from aur package)

EDIT: I have gotten ALVR to work

1. Open SteamVR installation path (via steam)
2. Copy the /usr/lib/steamvr/alvr to <steamvr installation path>/drivers/alvr
3. chmod +x <steamvr installation path>/drivers/alvr/driver.vrdrivermanifest [NOT SURE IF NEEDED]
4. Editing <steamvr installation path>/drivers/alvr/driver.vrdrivermanifest and making "hmd_presence" an empty array [NOT SURE IF NEEDED]
5. Running SteamVR via <steamvr installation path>/bin/vrmonitor.sh instead of launching through alvr

Now, I see the ALVR add-on in SteamVR and ALVR shows the streamer as connected.

NOTE: Even after doing this, when launching SteamVR through ALVR dashboard, it does not connect. The addon shows up but still does not connect. You HAVE to do two things:

1. Launch SteamVR throught the <steamvr installation path>/bin/vrmonitor.sh executable
2. Make sure that the driver is registered in the ALVR dashboard, otherwise the addon crashes and SteamVR disables it.

[LordJABA]

adding ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command% to steamvr custom command was enough for me to get it to work - wont detect driver without it

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[zatricky]

Still an issue ; workarounds required/etc

[The-personified-devil]

Originally reopened because it seemed like an unrelated issue. The sandboxing issue is tracked by #2242, closing in favor of that.