linux icon indicating copy to clipboard operation
linux copied to clipboard

XBOX Wireless Receiver wont be enumerated on boot (device descriptor read/64, error -32)

Open Killom opened this issue 1 year ago • 1 comments

Describe the bug

XBOX 360 Wireless Receiver wont be enumerated on boot. If re-plugged on runtime, it will get enumerated correctly and is working. After soft reboot, Receiver is again not enumerated on boot and defunct until being re-plugged

Steps to reproduce the behaviour

  • Plug in Receiver
  • Turn on power

Device (s)

Raspberry Pi 4 Mod. B

System

raspinfo output:

https://pastebin.com/xGdvUmbF

Logs

dmesg | grep "usb 1-1.1"
[    1.849354] usb 1-1.1: new full-speed USB device number 3 using xhci_hcd
[    1.929550] usb 1-1.1: device descriptor read/64, error -32
[    2.121511] usb 1-1.1: device descriptor read/64, error -32
[    2.317350] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
[    2.397580] usb 1-1.1: device descriptor read/64, error -32
[    2.593553] usb 1-1.1: device descriptor read/64, error -32
[    3.313341] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd
[    3.313537] usb 1-1.1: Device not responding to setup address.
[    3.521639] usb 1-1.1: Device not responding to setup address.
[    3.733331] usb 1-1.1: device not accepting address 5, error -71
[    3.822056] usb 1-1.1: new full-speed USB device number 6 using xhci_hcd
[    3.822757] usb 1-1.1: Device not responding to setup address.
[    4.029584] usb 1-1.1: Device not responding to setup address.
[    4.237436] usb 1-1.1: device not accepting address 6, error -71

After re-plugging:

[11534.655100] usb 1-1.1: new full-speed USB device number 8 using xhci_hcd
[11534.781646] usb 1-1.1: New USB device found, idVendor=045e, idProduct=0719, bcdDevice= 1.00
[11534.781663] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11534.781668] usb 1-1.1: Product: Xbox 360 Wireless Receiver for Windows
[11534.781672] usb 1-1.1: Manufacturer: ©Microsoft
[11534.781675] usb 1-1.1: SerialNumber: FF7E7620

Additional context

No response

Killom avatar May 26 '24 21:05 Killom

Huh. I removed and reinstalled pipewire, wireplumber & deps. Doesn't make sense somehow, but the issue seems to be gone. (I was just poking around a bit with pipewire - completely unrelated - because sound output issues in Kodi..)

Edit: Forget what I wrote. Issue is back today.

Might be related with #5046 but if I understand it correctly, the active USB Hub used in #5046 didnt cut off the ports power when he should have done. In my case the controller is directly plugged into RPi -no intermediate Hub involved

I formerly had LibreELEC (11.x nightly) installed onto this RPi with the same setup for quite some years. I never encountered this issue with LibreELEC. So this issue is either exclusive to Raspbian, or the LibreELEC dev team found a mitigation for this issue.

Edit 2: Just found out, that my old LibreELEC boot environment was still plugged into SD slot. So I switched boot order. To my relief, the issue was gone the moment it booted LE from SD. I did several cold boots just to make sure the issue is gone. With success.

LibreELEC (community): nightly-20231229-4e24516 (RPi4.aarch64)
uname -a
Linux kodi 6.6.7 #1 SMP Fri Dec 29 05:46:30 UTC 2023 aarch64 GNU/Linux

So from now on I suspect Raspian Kernel

Killom avatar May 26 '24 22:05 Killom