Is anybody able to shed any light on this problem?
I was using an old PS3 Eye as a USB microphone for a voice recognition project running on a Pi 5. It was running fine, until it didn't. I had needed to reboot the Pi for some reason, and the USB device never reconnected. I assumed it was the device dying, perhaps killed by the power reset, as it did not connect on the original or another Pi 5, so bought a new one. That does not appear to connect either, but after further testing does work on older Pis, and so does the original after trying that as well.
On a Pi 2 running Bullseye (Debian 11), the following gets recorded in /var/log/syslog when connecting the device:And on disconnecting:On a Pi 3B running Bookworn (Debian 12), /var/log/syslog records:Almost the same except for which device number it was up to, and the same disconnect message also appears.
On two separate Pi 5 devices, /var/log/syslog records:And nothing on disconnect.
Both Pi 5 devices have recently had apt upgrade run on them and been rebooted on the 24th. The history of the device that the PS3 Eye was originally connected to has the following recent changes:The PS3 Eye did not stop working until Mar 24th, and /var/log/syslog then recorded:The same problem exists for both the USB2 and USB3 ports.
The 70-alsa-permanent.rules udev file is for the PS3 Eye, but the same problem exists whether the file is there or not, and it does not appear to be needed on the Pi3 ot Pi2 for the device to be recognised.
Any suggestions as to what might be wrong, and how to fix it, would be welcome.
I was using an old PS3 Eye as a USB microphone for a voice recognition project running on a Pi 5. It was running fine, until it didn't. I had needed to reboot the Pi for some reason, and the USB device never reconnected. I assumed it was the device dying, perhaps killed by the power reset, as it did not connect on the original or another Pi 5, so bought a new one. That does not appear to connect either, but after further testing does work on older Pis, and so does the original after trying that as well.
On a Pi 2 running Bullseye (Debian 11), the following gets recorded in /var/log/syslog when connecting the device:
Code:
Mar 28 17:39:34 PiHole kernel: [8986464.095589] usb 1-1.4: new high-speed USB device number 5 using dwc_otgMar 28 17:39:34 PiHole kernel: [8986464.228302] usb 1-1.4: New USB device found, idVendor=1415, idProduct=2000, bcdDevice= 2.00Mar 28 17:39:34 PiHole kernel: [8986464.228352] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0Mar 28 17:39:34 PiHole kernel: [8986464.228376] usb 1-1.4: Product: USB Camera-B4.09.24.1Mar 28 17:39:34 PiHole kernel: [8986464.228394] usb 1-1.4: Manufacturer: OmniVision Technologies, Inc.Mar 28 17:39:34 PiHole kernel: [8986464.229520] gspca_main: ov534-2.14.0 probing 1415:2000Mar 28 17:39:36 PiHole kernel: [8986466.156381] usb 1-1.4: current rate 17027 is different from the runtime rate 16000Mar 28 17:39:36 PiHole kernel: [8986466.158855] usb 1-1.4: 3:1: cannot get min/max values for control 2 (id 3)Mar 28 17:39:36 PiHole mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"Mar 28 17:39:36 PiHole mtp-probe: bus: 1, device: 5 was not an MTP deviceMar 28 17:39:36 PiHole systemd-udevd[10764]: controlC2: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 2' failed with exit code 99.Mar 28 17:39:36 PiHole mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"Mar 28 17:39:36 PiHole mtp-probe: bus: 1, device: 5 was not an MTP deviceCode:
Mar 28 17:39:46 PiHole kernel: [8986476.350381] usb 1-1.4: USB disconnect, device number 5Code:
Mar 28 17:34:20 PiDev kernel: usb 1-1.4: USB disconnect, device number 8Mar 28 17:34:27 PiDev kernel: usb 1-1.4: new high-speed USB device number 9 using dwc_otgMar 28 17:34:27 PiDev kernel: usb 1-1.4: New USB device found, idVendor=1415, idProduct=2000, bcdDevice= 2.00Mar 28 17:34:27 PiDev kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0Mar 28 17:34:27 PiDev kernel: usb 1-1.4: Product: USB Camera-B4.09.24.1Mar 28 17:34:27 PiDev kernel: usb 1-1.4: Manufacturer: OmniVision Technologies, Inc.Mar 28 17:34:27 PiDev kernel: gspca_main: ov534-2.14.0 probing 1415:2000Mar 28 17:34:29 PiDev kernel: usb 1-1.4: current rate 16792 is different from the runtime rate 16000Mar 28 17:34:29 PiDev kernel: usb 1-1.4: 3:1: cannot get min/max values for control 2 (id 3)Mar 28 17:34:29 PiDev mtp-probe[17813]: checking bus 1, device 9: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"Mar 28 17:34:29 PiDev mtp-probe[17813]: bus: 1, device: 9 was not an MTP deviceMar 28 17:34:29 PiDev (udev-worker)[17815]: controlC2: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 2' failed with exit code 99.Mar 28 17:34:29 PiDev mtp-probe[17819]: checking bus 1, device 9: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"Mar 28 17:34:29 PiDev mtp-probe[17819]: bus: 1, device: 9 was not an MTP deviceOn two separate Pi 5 devices, /var/log/syslog records:
Code:
Mar 28 18:13:37 PiDev5 kernel: usb 1-2: new high-speed USB device number 18 using xhci-hcdMar 28 18:13:37 PiDev5 kernel: usb 1-2: unable to read config index 0 descriptor/allMar 28 18:13:37 PiDev5 kernel: usb 1-2: can't read configurations, error -71Mar 28 18:13:37 PiDev5 kernel: usb 1-2: new high-speed USB device number 19 using xhci-hcdMar 28 18:13:37 PiDev5 kernel: usb 1-2: unable to read config index 0 descriptor/allMar 28 18:13:37 PiDev5 kernel: usb 1-2: can't read configurations, error -71Mar 28 18:13:37 PiDev5 kernel: usb usb1-port2: attempt power cycleMar 28 18:13:37 PiDev5 kernel: usb 1-2: new high-speed USB device number 20 using xhci-hcdMar 28 18:13:37 PiDev5 kernel: usb 1-2: device descriptor read/all, error -71Mar 28 18:13:38 PiDev5 kernel: usb 1-2: new high-speed USB device number 21 using xhci-hcdMar 28 18:13:38 PiDev5 kernel: usb 1-2: device descriptor read/all, error -71Mar 28 18:13:38 PiDev5 kernel: usb usb1-port2: unable to enumerate USB deviceBoth Pi 5 devices have recently had apt upgrade run on them and been rebooted on the 24th. The history of the device that the PS3 Eye was originally connected to has the following recent changes:
Code:
Start-Date: 2024-03-20 15:29:07Commandline: apt-get install -y -qq apt-transport-https ca-certificates curlRequested-By: pi (1000)Install: apt-transport-https:arm64 (2.6.1)End-Date: 2024-03-20 15:29:07Start-Date: 2024-03-20 15:30:55Commandline: apt-get install -y -qq docker-ce docker-ce-cli containerd.io docker-compose-plugin docker-ce-rootless-extras docker-buildx-pluginRequested-By: pi (1000)Install: containerd.io:arm64 (1.6.28-2), docker-compose-plugin:arm64 (2.25.0-1~debian.12~bookworm), docker-ce-cli:arm64 (5:25.0.5-1~debian.12~bookworm), iptables:arm64 (1.8.9-2, automatic), pigz:arm64 (2.6-1, automatic), libslirp0:arm64 (4.7.0-1, automatic), docker-buildx-plugin:arm64 (0.13.1-1~debian.12~bookworm), docker-ce:arm64 (5:25.0.5-1~debian.12~bookworm), docker-ce-rootless-extras:arm64 (5:25.0.5-1~debian.12~bookworm), libip6tc2:arm64 (1.8.9-2, automatic), slirp4netns:arm64 (1.2.0-1, automatic)End-Date: 2024-03-20 15:31:03Start-Date: 2024-03-20 16:09:41Commandline: apt-get install -y python3 python3-dev python3-venv python3-pip bluez libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff6 libturbojpeg0-dev tzdata ffmpeg liblapack3 liblapack-dev libatlas-base-devRequested-By: pi (1000)Install: libjpeg-dev:arm64 (1:2.1.5-2), libjpeg62-turbo-dev:arm64 (1:2.1.5-2, automatic), automake:arm64 (1:1.16.5-1.3, automatic), libturbojpeg0-dev:arm64 (1:2.1.5-2), autoconf:arm64 (2.71-3), autotools-dev:arm64 (20220109.1, automatic), m4:arm64 (1.4.19-3, automatic), liblapack-dev:arm64 (3.11.0-2)End-Date: 2024-03-20 16:09:43Code:
Mar 24 21:38:13 PiNVMe systemd[1219]: Startup finished in 154ms.Mar 24 21:38:13 PiNVMe systemd[1219]: Starting dbus.service - D-Bus User Message Bus...Mar 24 21:38:13 PiNVMe systemd[1219]: Started dbus.service - D-Bus User Message Bus.Mar 24 21:38:13 PiNVMe wireplumber[1236]: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?Mar 24 21:38:13 PiNVMe pipewire-pulse[1237]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?Mar 24 21:38:13 PiNVMe dbus-daemon[708]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29' (uid=1000 pid=1237 comm="/usr/bin/pipewire-pulse")Mar 24 21:38:13 PiNVMe pipewire[1235]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?Mar 24 21:38:13 PiNVMe systemd[1]: Starting rtkit-daemon.service - RealtimeKit Scheduling Policy Service...Mar 24 21:38:13 PiNVMe dbus-daemon[708]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'Mar 24 21:38:13 PiNVMe systemd[1]: Started rtkit-daemon.service - RealtimeKit Scheduling Policy Service.Mar 24 21:38:13 PiNVMe systemd-udevd[342]: /etc/udev/rules.d/70-alsa-permanent.rules:1: GOTO="my_usb_audio_end" has no matching label, ignoringMar 24 21:38:13 PiNVMe systemd-udevd[342]: /etc/udev/rules.d/70-alsa-permanent.rules:1: The line takes no effect any more, droppingMar 24 21:38:13 PiNVMe systemd-udevd[342]: /etc/udev/rules.d/70-alsa-permanent.rules:2: GOTO="my_usb_audio_end" has no matching label, ignoringMar 24 21:38:13 PiNVMe systemd-udevd[342]: /etc/udev/rules.d/70-alsa-permanent.rules:2: The line takes no effect any more, droppingMar 24 21:38:13 PiNVMe wireplumber[1236]: RTKit error: org.freedesktop.DBus.Error.AccessDeniedMar 24 21:38:13 PiNVMe wireplumber[1236]: could not set nice-level to -11: Permission deniedMar 24 21:38:13 PiNVMe pipewire-pulse[1237]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDeniedMar 24 21:38:13 PiNVMe pipewire-pulse[1237]: mod.rt: could not set nice-level to -11: Permission deniedMar 24 21:38:13 PiNVMe pipewire[1235]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDeniedMar 24 21:38:13 PiNVMe pipewire[1235]: mod.rt: could not set nice-level to -11: Permission deniedMar 24 21:38:13 PiNVMe wireplumber[1236]: RTKit error: org.freedesktop.DBus.Error.AccessDeniedMar 24 21:38:13 PiNVMe wireplumber[1236]: could not make thread 1248 realtime using RTKit: Permission deniedMar 24 21:38:13 PiNVMe pipewire-pulse[1237]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDeniedMar 24 21:38:13 PiNVMe pipewire-pulse[1237]: mod.rt: could not make thread 1252 realtime using RTKit: Permission deniedMar 24 21:38:13 PiNVMe wireplumber[1236]: [0:00:40.050974845] [1236] INFO Camera camera_manager.cpp:284 libcamera v0.2.0+46-075b54d5Mar 24 21:38:13 PiNVMe pipewire[1235]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDeniedMar 24 21:38:13 PiNVMe pipewire[1235]: mod.rt: could not make thread 1253 realtime using RTKit: Permission deniedMar 24 21:38:13 PiNVMe kernel: Bluetooth: RFCOMM TTY layer initializedMar 24 21:38:13 PiNVMe kernel: Bluetooth: RFCOMM socket layer initializedMar 24 21:38:13 PiNVMe kernel: Bluetooth: RFCOMM ver 1.11Mar 24 21:38:13 PiNVMe wireplumber[1236]: The decibel volume range for element 'Speaker' (-2837 dB - -6 dB) has negative maximum. Disabling the decibel range.Mar 24 21:38:13 PiNVMe wireplumber[1236]: The decibel volume range for element 'Speaker' (-2837 dB - -6 dB) has negative maximum. Disabling the decibel range.Mar 24 21:38:13 PiNVMe wireplumber[1236]: The decibel volume range for element 'Speaker' (-2837 dB - -6 dB) has negative maximum. Disabling the decibel range.Mar 24 21:38:13 PiNVMe wireplumber[1236]: The decibel volume range for element 'Speaker' (-2837 dB - -6 dB) has negative maximum. Disabling the decibel range.Mar 24 21:38:13 PiNVMe wireplumber[1236]: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.Mar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/ldacMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx_hdMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_hdMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptxMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptxMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbcMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbcMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc_xqMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc_xqMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_1Mar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_0Mar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1Mar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0Mar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststreamMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplexMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05Mar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05Mar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05_duplexMar 24 21:38:13 PiNVMe bluetoothd[927]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_duplexMar 24 21:38:13 PiNVMe wireplumber[1236]: <WpSiAudioAdapter:0x55564733d070> Object activation aborted: proxy destroyedMar 24 21:38:13 PiNVMe wireplumber[1236]: <WpSiAudioAdapter:0x55564733d070> failed to activate item: Object activation aborted: proxy destroyedMar 24 21:38:39 PiNVMe kernel: usb 1-2: new high-speed USB device number 2 using xhci-hcdMar 24 21:38:40 PiNVMe kernel: usb 1-2: unable to read config index 0 descriptor/allMar 24 21:38:40 PiNVMe kernel: usb 1-2: can't read configurations, error -71Mar 24 21:38:40 PiNVMe kernel: usb 1-2: new high-speed USB device number 3 using xhci-hcdMar 24 21:38:40 PiNVMe kernel: usb 1-2: unable to read config index 0 descriptor/allMar 24 21:38:40 PiNVMe kernel: usb 1-2: can't read configurations, error -71Mar 24 21:38:40 PiNVMe kernel: usb usb1-port2: attempt power cycleMar 24 21:38:40 PiNVMe kernel: usb 1-2: new high-speed USB device number 4 using xhci-hcdMar 24 21:38:40 PiNVMe kernel: usb 1-2: device descriptor read/all, error -71Mar 24 21:38:40 PiNVMe kernel: usb 1-2: new high-speed USB device number 5 using xhci-hcdMar 24 21:38:40 PiNVMe kernel: usb 1-2: device descriptor read/all, error -71Mar 24 21:38:40 PiNVMe kernel: usb usb1-port2: unable to enumerate USB deviceMar 24 21:52:49 PiNVMe systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...Mar 24 21:52:49 PiNVMe systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.Mar 24 21:52:49 PiNVMe systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.Mar 24 21:52:49 PiNVMe systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.Mar 24 21:55:25 PiNVMe systemd-timesyncd[673]: Timed out waiting for reply from 85.199.214.101:123 (2.debian.pool.ntp.org).Mar 24 21:55:26 PiNVMe systemd-timesyncd[673]: Contacted time server 131.111.8.61:123 (2.debian.pool.ntp.org).Mar 24 21:56:14 PiNVMe kernel: usb 3-1: new high-speed USB device number 3 using xhci-hcdMar 24 21:56:14 PiNVMe kernel: usb 3-1: unable to read config index 0 descriptor/allMar 24 21:56:14 PiNVMe kernel: usb 3-1: can't read configurations, error -71Mar 24 21:56:14 PiNVMe kernel: usb 3-1: new high-speed USB device number 4 using xhci-hcdMar 24 21:56:14 PiNVMe kernel: usb 3-1: unable to read config index 0 descriptor/allMar 24 21:56:14 PiNVMe kernel: usb 3-1: can't read configurations, error -71Mar 24 21:56:14 PiNVMe kernel: usb usb3-port1: attempt power cycleMar 24 21:56:15 PiNVMe kernel: usb 3-1: new high-speed USB device number 5 using xhci-hcdMar 24 21:56:15 PiNVMe kernel: usb 3-1: device descriptor read/all, error -71Mar 24 21:56:15 PiNVMe kernel: usb 3-1: new high-speed USB device number 6 using xhci-hcdMar 24 21:56:15 PiNVMe kernel: usb 3-1: device descriptor read/all, error -71Mar 24 21:56:15 PiNVMe kernel: usb usb3-port1: unable to enumerate USB deviceThe 70-alsa-permanent.rules udev file is for the PS3 Eye, but the same problem exists whether the file is there or not, and it does not appear to be needed on the Pi3 ot Pi2 for the device to be recognised.
Any suggestions as to what might be wrong, and how to fix it, would be welcome.
Statistics: Posted by IanS — Thu Mar 28, 2024 6:24 pm