protonscr

Valve Index Not Recognized ("Headset not detected")

steamvrclosed
ValveSoftware/SteamVR-for-Linux#313 · opened 2020-03-18 by blue42u · updated 2022-12-17 · 9 comments · github
Bblue42u 2020-03-18 github

I'm not sure if this issue belongs here, if it has a better home somewhere else please direct me.

Describe the bug
SteamVR reports "headset not detected (108)," no matter which USB 3.x port I plug the Valve Index into. The Valve HMD entries also do not appear in lsusb, but I can access the cameras using a webcam program (Cheese).

Screenshot from 2020-03-18 18-24-23
2020-03-18-183114

To Reproduce
Steps to reproduce the behavior:

  1. Plug in the Index headset.
  2. Start up SteamVR.
  3. See error.

Expected behavior
A green headset icon in SteamVR.

System Information (please complete the following information):

  • Distribution: Debian Unstable
  • SteamVR version: 1.10.30
  • Steam client version: Mar 18, 2020
  • Opted into Steam client beta?: Yes
  • Graphics driver version: 440.64 (NVIDIA)
  • Gist for SteamVR System Information: here. Also Steam's system report.

Additional context
I've been able to run The Lab by borrowing a friend's laptop and sharing the USB connection (via usbip) over a Wifi connection, so the Index hardware isn't faulty. It just doesn't work plugged into my gaming rig directly.

Hardware:

$ lspci | grep USB
05:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01)
07:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0a:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1)
0a:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1)
0b:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03)
0d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

The three AMD controllers are from my motherboard, the Renesas controller from the Vantec card, and the VIA controller from the SIIG card. None of them work with the Index, all of them work with other devices.

Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.

Kkisak-valve maintainer 2020-03-19 github

Hello @blue42u, can you check if you have the steam-devices package installed with something like apt policy steam-devices and install it if it isn't already?

Bblue42u 2020-03-19 github

Can confirm that steam-devices is installed, and the installed udev rules match the most recent:

$ apt policy steam-devices
steam-devices:
  Installed: 1.0.0.61-2
  Candidate: 1.0.0.61-2
  Version table:
 *** 1.0.0.61-2 500
        500 http://ftp.us.debian.org/debian sid/non-free amd64 Packages
        500 http://ftp.us.debian.org/debian sid/non-free i386 Packages
        100 /var/lib/dpkg/status
$ diff -s 60-steam-vr.rules /lib/udev/rules.d/60-steam-vr.rules 
Files 60-steam-vr.rules and /lib/udev/rules.d/60-steam-vr.rules are identical
ZZarathustraDK 2020-03-19 github

I had this issue before. From what I gather it has something to do with your GPU's port-priority. My guess is your card has 3 displayports and you've put the Index in the "wrong" one. For me (2080TI) I had one port for my monitor, one port for my AV-hub (which is normally off), and one port for the Index. Monitor worked fine, but the index refused to get detected. Then I turned on the AV-hub, lo and behold, the index got detected.

TLDR: Try change up your displayport-inputs. There's a port 1, port 2 and a port 3 (not labelled but it's in the manual I think). Port 1 needs to be your monitor, port 2 the index OR port 3 the index as long as port 2 is also active (like a second monitor for instance).

There's probably a smart, tuxy way to fix this with a terminal, but I wouldn't know how.

Bblue42u 2020-03-19 github

I've been testing without the DisplayPort, just tried with plugged in. No difference for any of the 3 DP ports. (Using HDMI for my monitor for now.)

Mind you, the displays (and everything else) work after sharing the USB from my friend's laptop. I'm starting to wonder if there's a subtle break in my tether, if that's even possible.

Kkb173 2020-03-20 github

I have this issue as well. I have a dual-boot with Windows and Ubuntu set up. At first, the Index worked on Ubuntu. Later, I did a firmware update for the Index on Windows. Since then, it is not detected on Ubuntu. (It is still working fine on Windows.)

My udev rules match the most recent and I tried all DisplayPort connections. I tried Beta and default Steam. xrandr reports no connections other than the monitor. The logs say Returning HmdNotFound because the client-side presence check failed.. I can also view the Index's camera view in Cheese.

I have a GTX 980 with the nvidia-driver-440 package and I'm using Linux Kernel 5.0.0-38-generic.

Edit: After much plugging out and in, I got this output with dmesg:

[ 8371.973728] usb 8-3.3: new SuperSpeed Gen 1 USB device number 19 using xhci_hcd
[ 8371.994047] usb 8-3.3: New USB device found, idVendor=0424, idProduct=5744, bcdDevice= 2.21
[ 8371.994051] usb 8-3.3: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[ 8371.994053] usb 8-3.3: Product: USB5744
[ 8371.994055] usb 8-3.3: Manufacturer: Microchip Tech
[ 8371.995125] hub 8-3.3:1.0: USB hub found
[ 8371.995156] hub 8-3.3:1.0: 4 ports detected
[ 8372.281927] usb 8-3.3.1: new SuperSpeed Gen 1 USB device number 20 using xhci_hcd
[ 8372.527485] usb 8-3.3.1: New USB device found, idVendor=28de, idProduct=2400, bcdDevice= 0.04
[ 8372.527487] usb 8-3.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8372.527488] usb 8-3.3.1: Product: 3D Camera
[ 8372.527488] usb 8-3.3.1: Manufacturer: Etron Technology, Inc.
[ 8372.527489] usb 8-3.3.1: SerialNumber: 00000001
[ 8372.537859] uvcvideo: Found UVC 1.00 device 3D Camera (28de:2400)295
[ 8372.610100] uvcvideo 8-3.3.1:1.0: Entity type for entity Extension 4 was not initialized!
[ 8372.610102] uvcvideo 8-3.3.1:1.0: Entity type for entity Processing 3 was not initialized!
[ 8372.610103] uvcvideo 8-3.3.1:1.0: Entity type for entity Camera 1 was not initialized!
[ 8372.610155] input: 3D Camera: eTronVideo as /devices/pci0000:00/0000:00:1c.7/0000:0a:00.0/usb8/8-3/8-3.3/8-3.3.1/8-3.3.1:1.0/input/input48

Unfortunately I can't try the workaround from #295 because I don't get any new entry in /dev/hidraw* when this happens.

JJulianGro 2020-03-26 github

For me the Index has only worked in the past if I had it plugged in before boot. Just restarting after getting the "Headset not detected" always fixed it for me.
Just adding this as it is somewhat weird on linux to actually need a restart for something to work =|

KKindDragon 2020-04-15 github

Same issue for me with Valve Index and SteamVR 1.10.32 - "Please plug in your VR headset"
System Information https://gist.github.com/KindDragon/62cd5941c69ea77104b9ddcaed67adb9
SteamVR Log https://gist.github.com/KindDragon/b2c5b29d16b5361fe3f7cd62cd51ca7f

Also, Ubuntu reboot when I exit from SteamVR

Bblue42u 2020-05-14 github

After replacing my tether (Steam Support was kind enough to send me a new one), it seems to work consistently now. There are still a few software bugs (like the system buttons not always opening the dashboard), but I can play VR games now so I'm happy.

For anyone else running into this issue, try plugging into a laptop or another machine and checking if that works (with lsusb or equivalent), or requesting a replacement tether. It might be a hardware issue.

Closing for now, as my particular issue is resolved.

AAll-The-Foxes 2022-12-17 github

I used it fine last night. Today I open Steam and the Steam client has an update, and now I can't get my headset to work no matter what I do.

Nothing extracted yet.