cancel
Showing results for 
Search instead for 
Did you mean: 

Can no longer connect adb to my Quest via Chromebook Crostini

walthecat
Honored Guest
Is anyone else having issues with connecting adb to the quest from a Chromebook Crostini VM (or I guess any other linux distro?)

This was working for me previously, but now doesn't work. I don't know if the update to 15.0 has broken it, or an update on the ChromeOS.

When I first plug in the quest it briefly shows up in lsusb then disappears after about 5 seconds, and then adb devices is just empty.

Logs show an XHCI issue: 

xHCI host not responding to stop endpoint command.
Host halt failed, -110
xHCI host controller not responding, assume dead
HC died; cleaning up

From that point on I get whenever I try to reconnect the logs show:

fail to recv command from usb control socket: failed to receive request or response: Resource temporarily unavailable (os error 11)

Failed crosvm call returned code 1
2020-04-14T11:29:00.465819+01:00
Failed to attach USB device: unexpected response: error: Input/output error (os error 5)

Don't think it's an issue with the cable as I've tried a couple that normally work, and if I toggle out of developer mode it can still mount as a drive in the ChromeOS.
0 REPLIES 0