Wired Connection does not work whatsoever after updating to 20.12.0

[RobbieNeko]

Description

After updating to v20.12.0, both the native wired support as well as the old method of wired support refuse to work whatsoever. They do not even attempt to connect to the headset. This is after trying both UDP and TCP, both Store and Github in the Wired Connection protocol, restarting steamvr, closing and re-opening ALVR on both the headset and on the computer.

General Troubleshooting

• I carefully followed the instructions in the README and successfully completed the setup wizard
• I read the ALVR GitHub Wiki

Environment

Hardware

https://linux-hardware.org/?probe=2ae8742158

Installation

ALVR Version: v20.12.0

ALVR Settings File:

SteamVR Version: 2.9.5

Install Type:

• Packaged (exe, deb, rpm, etc)
• Portable (zip) At least I imagine that's what the launcher uses?
• Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
Fedora 41 KDE

[zmerp]

Have you updated both server and client?

[RobbieNeko]

Yes, both are freshly updated to v20.12.0 (I had to update the PC side due to the headset side having updated. Meta does not claim any newer updates are available)

[zmerp]

You could try the nightly releases, make sure to install the same version on both headset and pc. Try to see if you can find the first release that has the bug

[truefakts]

I'm running into a similar issue as you, also running Fedora 41 with KDE. I'm using a 6600XT with the video encoding codecs from rpmfusion, and a Quest 3 with a USB 3.2 connection. For reference, everything was working fine for me yesterday before the upgrade.

I finally got a wired connection working with 20.12. I suspect the problem that we both are having is related to the upgrade instead of ALVR itself. I was extremely frustrated this morning, and after about an hour of troubleshooting, I uninstalled everything, except for ADBforwarder and that seems to have fixed it! I don't know why, but things are working for me on v20.12.0 now.

Here's what I did:

• Uninstalled ALVR from the headset (using the meta store version)
• Restarted the headset and reinstalled from the store
• Using the ALVR launcher, deleted all versions of ALVR that are installed on my PC
• Deleted the ALVR directory from my machine, and redownloaded the .zip from the releases page
• Unzipped the ALVR directory into my home directory
• From the ALVR Launcher, went to Installation > Run setup wizard and reset all my settings
• From the ALVR Launcher, went to Devices > and set Wired Connection to off
• Under trusted devices, I added my headset as a wired device (127.0.0.1) and as a wireless device (192.168.0.220) which correspond to the IP address reservations I have for the headset on my network. The localhost IP is obviously for the ethernet redirect
• From the ALVR Launcher, went to Connection > Stream Protocol = TCP (for wireless, I toggle this to UDP)
• Now, with all that setup I went to my ~/Adbforwarder directory and launched ADBForwarder via terminal
• Then I launched SteamVR from ALVR and everything works again!

Now, for all future launches of games that required a USB tether I just run ADBForwarder and ALVR launcher. Everything works once again, I tested this a couple of times today. I then wrote a quick script to launch ADBForwarder and ALVR launcher with the single click of a button in my applications menu. This is totally optional, but kind of nice to have. Feel free to copy this, and set this as an executable program on your machine and add an entry into your applications menu:

To use this script:

• Rename ~/alvr_launcher_linux/ALVR Launcher to ~/alvr_launcher_linux/ALVR_Launcher to use this script as-is
• unzip Adbforwarder into ~/Adbforwarder

#!/bin/bash


# Start ALVR in the background and supress the screen saver
kde-inhibit --power --screenSaver /home/drew/alvr_launcher_linux/ALVR_Launcher &
echo "Started program2"
sleep 2

# Start ADBForwarder the background
/home/drew/Adbforwarder/ADBForwarder

[zmerp]

@truefakts Could you please try again the integrated wired mode? I assume one of the issues were multiple conflicting ADB processes. The launcher and ALVR server itself use two separate ADB copies

[shmink]

I'm on fedora 41 as well and just tried 20.12.1 and it worked in wired mode straight away. Only issue I ran into was the black screen but this fix sorted it.

❯ neofetch
             .',;::::;,'.                tom@fedora 
         .';:cccccccccccc:;,.            ---------- 
      .;cccccccccccccccccccccc;.         OS: Fedora Linux 41 (Workstation Editi 
    .:cccccccccccccccccccccccccc:.       Kernel: 6.12.9-200.fc41.x86_64 
  .;ccccccccccccc;.:dddl:.;ccccccc;.     Uptime: 40 mins 
 .:ccccccccccccc;OWMKOOXMWd;ccccccc:.    Packages: 2886 (rpm), 50 (flatpak) 
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:.   Shell: zsh 5.9 
,cccccccccccccc;MMM.;cc;;WW::cccccccc,   Resolution: 2560x1440 
:cccccccccccccc;MMM.;cccccccccccccccc:   DE: GNOME 47.3 
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc:   WM: Mutter 
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc;   WM Theme: Dracula 
ccccc:XM0';cccc;MMM.;cccccccccccccccc'   Theme: Dracula [GTK2/3] 
ccccc;MMo;ccccc;MMW.;ccccccccccccccc;    Icons: Adwaita [GTK2/3] 
ccccc;0MNc.ccc.xMMd:ccccccccccccccc;     Terminal: gnome-terminal 
cccccc;dNMWXXXWM0::cccccccccccccc:,      CPU: AMD Ryzen 7 5800X3D (16) @ 4.816G 
cccccccc;.:odl:.;cccccccccccccc:,.       GPU: AMD ATI Radeon RX 6800/6800 XT /  
:cccccccccccccccccccccccccccc:'.         Memory: 5649MiB / 31991MiB 

My quest 2 is on the latest OS version and ALVR app is up to date. I freshly installed ALVR streamer as I'm new here so not sure if that played a part as well. I also always have to approve USB debugging on the quest itself whenever I plug it in.

Let me know if there's any more information about my system that could help.

[JunzheJosephZhu]

I ran into a similar issue and wound up resolving it by making a Udev rule,
sudo nano /etc/udev/rules.d/00-all-usb.rules

SUBSYSTEM=="usb", MODE="0666"

or running ADBForwarder in sudo