Headset Disconnected - Error 208 - Since the latest SteamVR

[ZaphireZA]

Hi,

I've been having this issue since the latest SteamVR and tried all the solutions to get it working, even with the live support and they confirmed that its most likely not the cables.

Anyone else experiencing this all of a sudden?

https://drive.google.com/file/d/1o2z67DjmkaJpgqAuPzy8i8SsACU3YSL9/view?usp=sharing

[Cargo Cult]

It looks like you're hitting a device configuration read issue:

Sun Mar 31 2019 11:48:53.299 - lighthouse: LHR-F5F67550: Expected 3494 bytes of config but only found 2170. Rejecting config
Sun Mar 31 2019 11:48:53.299 - lighthouse: Unable to read device config for vid 0x28DE pid 0x2000 serial LHR-F5F67550. Rejecting it

A fix for this should be out quite soon - in the meantime, unplugging and replugging the Vive's USB cable before starting SteamVR should get things going again.

(Also, huge thanks for posting a system report. It makes diagnosing and fixing rare issues like this possible!)

[ZaphireZA]

Thanks Cargo, is this something like firmware that upgraded incorrectly on the headset itself? Reason I ask is because I tried it on another PC as well and it had the same problem

[Dan]

Everything worked great a couple days ago, today it just jumps instantly to 208 error. I've restarted, unplugged and replugged everything to different ports, and no matter what I do, it just goes right to 208 error. It shouldn't be this hard to use something I paid so much money for.

[lokiss88]

Getting it too Dan. For me restarting it over a few times gets me in. Once it wouldn't budge, restarted the pc and it worked.

It's obviously a temporary issue, first time in 3 years having any problems with it at all.

Fix incoming.

[Cargo Cult]

@Zaphire: We're still figuring out the precise cause of the issue, but the fact that it appears specific to the headset itself is really interesting. We may get back to you for testing!

@Dan, lokiss88: Can you post system reports? It would be good to check whether you're encountering the same issue or a different one. Thanks!

[Dan]

Getting similar errors in my logs.

Sun Mar 31 2019 16:51:06.860 - lighthouse: LHR-3110974B: Expected 3503 bytes of config but only found 2790. Rejecting config
Sun Mar 31 2019 16:51:06.860 - lighthouse: Unable to read device config for vid 0x28DE pid 0x2000 serial LHR-3110974B. Rejecting it
Sun Mar 31 2019 16:51:06.861 - Driver 'lighthouse' started activation of tracked device with serial number 'LHR-3110974B'

[Dan]

Still trying, different usb ports, resetting usb ports, restarting computer. Nothing works, as soon as I hit the VR button in steam it just goes right to a 208 error. I hope they release a fix soon, this is annoying.

[Dan]

Was able to fix mine. Still had the 208 error on the screen, I unplugged the hdmi and usb cables from the computer, unplugged the power to the linkbox. Unplugged all 3 cables from the linkbox to my HDM. Left it about 30 seconds, plugged in the power, then the hdmi and usb into the computer, plugged the HDM power, hdmi then usb. And the damn thing started working.

I have plugged and replugged every cable, just not all of them at the same time before. I guess that was all it needed. After fighting with this for the last couple days, that's all it took. I feel stupid but happy.

[Cargo Cult]

Quick update - there's a fix for some instances of the 'read device config' issue in the latest beta:

https://steamcommunity.com/games/250820/announcements/detail/1732104945964552108

Let us know how you all get on. Thanks!

[ZaphireZA]

Hi Cargo, thanks for the share. I logged in remotely to my PC to test if it is working but I still have the same issue. Will try and unplug everything and remove drivers tonight when I get home to do a better test but here is the quick test's log file so long.

https://drive.google.com/file/d/1EkKT3k22XMQiIis2eBF-xwDCDXwLfJUH/view?usp=sharing

[Cargo Cult]

Originally posted by Zaphire:

Hi Cargo, thanks for the share. I logged in remotely to my PC to test if it is working but I still have the same issue. Will try and unplug everything and remove drivers tonight when I get home to do a better test but here is the quick test's log file so long.

https://drive.google.com/file/d/1EkKT3k22XMQiIis2eBF-xwDCDXwLfJUH/view?usp=sharing

Looks like it's hitting a separate issue - the device config read is now working:

Mon Apr 01 2019 23:32:01.631 - lighthouse: LHR-F5F67550: Read config of 3494 bytes from [vid:28de, pid:2000] (LHR-F5F67550) and inflated to 16657 bytes
Mon Apr 01 2019 23:32:01.632 - lighthouse: HMD Model: HTC Vive

Instead, it's failing to find the headset display:

Mon Apr 01 2019 23:32:01.945 - Could not activate pending device LHR-F5F67550: VRInitError_Driver_HmdDisplayNotFound

This could be caused by the remote login - if you can test locally, that would be fantastic.

Thanks so much!

[ZaphireZA]

Unfortunately still can't get it to work.

Here is the latest log files
https://drive.google.com/file/d/1gkr-4zL8hJDeFfGYb8ZwRzJHqZ6fKqvi/view?usp=sharing

[Cargo Cult]

Originally posted by Zaphire:

Unfortunately still can't get it to work.

Here is the latest log files
https://drive.google.com/file/d/1gkr-4zL8hJDeFfGYb8ZwRzJHqZ6fKqvi/view?usp=sharing

Looks like it's still failing to detect the headset display - it's not listed amongst the available displays.

Can you try completely powering everything down then back up again? GPUs can occasionally cache incorrect display device details, and I'm wondering if something like that is going on here.

(The good news - the device config read thing still looks fixed!)

[ZaphireZA]

Hey Cargo,

Nothing seems to work. Left the PC off for a few hours and tried again but still had the same issue.

I tried it now on a brand new PC, loaded SteamVR and even plugged the VR directly into the laptop with the other cables (not using the 3 in 1) and no luck.

Here is the log file of the one on the other PC I tried.

https://drive.google.com/file/d/1rOcTDyJR09DIghV-LHxhN4zyInwoRJPi/view?usp=sharing

[Cargo Cult]

@Zaphire: The HMD's display still isn't appearing in the list of available displays - this is at a layer outside of SteamVR, so I'm not sure what to do next.

Sounds like you've already tried everything I would suggest with swapping cables around. I'd double check the HMDI plug is fully seated in the headset - I recall it being really tricky to fit properly - and if that still doesn't work, it sounds like the headset itself is faulty in some way.

Next stop: contacting HTC? I think you really have tried everything possible. Sorry it had to be a hardware issue!