Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 7503

Troubleshooting • USB-Device not detected on re/boot, but hot-plugging works

$
0
0
hi there,
I'm trying to figure out an USB related problem on a Pi 4 Model B Rev 1.4, Raspbian GNU/Linux 12 (bookworm)

A USB-microphone works fine when plugged into a running system:

Code:

[  527.782050] usb 1-1.1: new full-speed USB device number 7 using xhci_hcd[  527.876540] usb 1-1.1: New USB device found, idVendor=287d, idProduct=0250, bcdDevice= 0.01[  527.876573] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0[  527.876585] usb 1-1.1: Product: Pettersson M500-384kHz USB Ultrasound Microphone[  527.876596] usb 1-1.1: Manufacturer: Pettersson[  528.001182] usbcore: registered new interface driver snd-usb-audio
but fails to be recognized when the systems boots or reboots:

Code:

[    3.621800] usb 1-1.1: new full-speed USB device number 3 using xhci_hcd[    7.163689] usbcore: registered new interface driver brcmfmac[   18.990006] usb 1-1.1: device descriptor read/64, error -110[   34.601979] usb 1-1.1: device descriptor read/64, error -110[   34.777772] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd[   50.217991] usb 1-1.1: device descriptor read/64, error -110[   65.834025] usb 1-1.1: device descriptor read/64, error -110[   65.938259] usb 1-1-port1: attempt power cycle[   66.521797] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd[   68.177789] usb 1-1.1: device not accepting address 5, error -22[   68.178137] usb 1-1.1: WARN: invalid context state for evaluate context command.[   68.249793] usb 1-1.1: new full-speed USB device number 6 using xhci_hcd[   69.905795] usb 1-1.1: device not accepting address 6, error -22[   69.906198] usb 1-1.1: WARN: invalid context state for evaluate context command.[   69.906365] usb 1-1-port1: unable to enumerate USB device
Tested on 2 different Pi4. If I use a hub between microphone and Pi, eg. a passive 4-port logilink, it works as expected. The system is intended to run at a remote location, so has to be reboot-safe. A hub would be a sort of work around, but not ideal though..
edit: it also works without problems on a Pi2.

Does that problem sound familiar to anyone?
Any hints, boot flags etc. appreciated!
thanks, u.

Statistics: Posted by unosonic — Sat Feb 07, 2026 1:45 pm — Replies 1 — Views 72



Viewing all articles
Browse latest Browse all 7503

Trending Articles