Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xow stops at "Waiting for device" #176

Open
cademullen-1219 opened this issue Jul 1, 2021 · 8 comments
Open

xow stops at "Waiting for device" #176

cademullen-1219 opened this issue Jul 1, 2021 · 8 comments

Comments

@cademullen-1219
Copy link

cademullen-1219 commented Jul 1, 2021

So xow was working for me for a little while, but just recently it has stopped detecting my adapter. I tried a bunch of different USB ports on my PC, countless reboots and resets of the xow service with the adapter unplugged/plugged in; no luck. I've heard that dual booting with Windows can cause issues, and I have to use Windows for my work, so I fear that may be what's causing this. What's even worse is that Windows doesn't even recognize the device anymore, it says "Device Descriptor Request Failed". My best guess is that it's some kind of firmware issue with the adapter, but I have no idea how to go about fixing it. My apologies if this is a known issue, I've done my best to search for help and I haven't found anything. I hope somebody can help me out here, I'm at a loss.

Here's a recent log:

Jun 30 22:31:44 cade-h110ma systemd[1]: Started Xbox One Wireless Dongle Driver.
Jun 30 22:31:50 cade-h110ma xow[733]: 2021-06-30 22:31:50 INFO  - xow v0.5-27-g700529b ©Severin v. W.
Jun 30 22:31:50 cade-h110ma xow[733]: 2021-06-30 22:31:50 INFO  - Waiting for device...
Jun 30 22:34:37 cade-h110ma systemd[1]: Stopping Xbox One Wireless Dongle Driver...
Jun 30 22:34:37 cade-h110ma systemd[1]: xow.service: Deactivated successfully.
Jun 30 22:34:37 cade-h110ma systemd[1]: Stopped Xbox One Wireless Dongle Driver.

Here's an older log from when it was working (expected output):

Jun 18 10:53:09 cade-h110ma systemd[1]: Started Xbox One Wireless Dongle Driver.
Jun 18 10:53:14 cade-h110ma xow[721]: 2021-06-18 10:53:14 INFO  - xow v0.5-27-g700529b ©Severin v. W.
Jun 18 10:53:14 cade-h110ma xow[721]: 2021-06-18 10:53:14 INFO  - Waiting for device...
Jun 18 10:53:14 cade-h110ma xow[721]: 2021-06-18 10:53:14 INFO  - Wireless address: 62:45:b4:fd:e1:18
Jun 18 10:53:14 cade-h110ma xow[721]: 2021-06-18 10:53:14 INFO  - Dongle initialized
Jun 18 11:02:44 cade-h110ma xow[721]: 2021-06-18 11:02:44 INFO  - Controller '1' connected
Jun 18 11:02:45 cade-h110ma xow[721]: 2021-06-18 11:02:45 INFO  - Device announced, product id: 02ea
Jun 18 11:02:45 cade-h110ma xow[721]: 2021-06-18 11:02:45 INFO  - Serial number: 02600564056637
Jun 18 11:02:48 cade-h110ma xow[721]: 2021-06-18 11:02:48 INFO  - Battery level: medium

Screenshots from Windows:

device_not_recognized

descriptor_request_failed

Wireless adapter model: 6HN-00002
Xbox controller model: 1708
Linux distro: Manjaro GNOME

@kakra
Copy link
Contributor

kakra commented Jul 1, 2021

Try to use a different USB port (you probably already did that). If that doesn't help, find an active USB hub (with external power source), connect that to your computer, and try connecting the dongle to that hub.

From my experience, USB ports may degrade electrically over time. Devices that worked before just stop working after some time. This happens especially for ports that are plugged and unplugged often. An active USB hub can usually work around it - as long as it doesn't have other strange USB quirks with some devices.

I have a USB hub for that matter: Some devices only reliably work with that hub, others only work when connected directly to the PC.

Before buying a hub, you could try a completely different PC.

It's probably not a firmware issue with the dongle itself because that firmware will be uploaded to the dongle on each connect, it's not stored permanently on the stick.

@cademullen-1219
Copy link
Author

I tried lots of different ports on my PC and none of them worked. I also tried on a fairly new Macbook running Windows through bootcamp, and that didn't work either. I got the same "Device Descriptor Request Failed" error.

Something that I should mention is that I got this adapter on eBay, which may explain why it's faulty. The strange thing is that it was working earlier; perhaps the device was extremely degraded from previous use and only had a short lifespan as a result. I think I might want to try getting a new adapter from the Microsoft store.

@kakra
Copy link
Contributor

kakra commented Jul 1, 2021

Yeah, maybe it was on eBay because it was not working reliably in all devices already for the previous owner...

@cademullen-1219
Copy link
Author

It was from a vendor that resells used adapters and claims that they are tested and working. Hopefully the last time I make that mistake... At any rate I've ordered a new one from Microsoft and it should get here in about a week, with any luck this will fix my issues.

@TheVanMan2345
Copy link

I had this same issue after dual booting windows 11 with Manjaro KDE. I think it creates some kind of a firmware conflict.

To get it working again, I unplugged the dongle, stopped the xow service, restarted the xow service, and then plugged the dongle back in when it read "waiting for device"

Worked like a charm for me, I hope you find the same.

@mpaccione
Copy link

Hi I am having a similar issue however just upgraded Linux.
Did you figure out a fix?

@TheVanMan2345
Copy link

TheVanMan2345 commented Apr 8, 2022 via email

@mpaccione
Copy link

mpaccione commented Apr 8, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants