# USB problem with RPi4 (balenaOS 2.82.10+rev1) **URL:** \ **Category:** balenaOS\ **Tags:** raspberrypi4\ **Created:** [August 8, 2021, 3:31am UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721 "2021-08-08T03:31:48Z")\ **Posts on this page:** 19\ **Page:** 1
**Author:** ![dajm01](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dajm01](https://forums.balena.io/u/dajm01)\ **Post date:** [August 8, 2021, 3:31am UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/1 "2021-08-08T03:31:48Z")
Hi I’m a new user of [balena.io](http://balena.io). Very impressed with the experience so far, and keen to get a real project underway. Unfortunately, I seem to have hit an early hardware issue. I’m using a Raspberry Pi 4 B 8GB, and trying to get a USB GPS device (GlobalSat BU-353S4) to work. I have confirmed that the hardware works: if I load the Pi with a copy of Ubuntu server (21.04) then `lsusb` shows: `Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P` However, if I set the Pi up as a balena device (balenaOS 2.82.10+rev1, development edition), and connect to the HostOS then `lsusb` just shows: `Bus 002 Device 001: ID 1d6b:0003 ` `Bus 001 Device 001: ID 1d6b:0002 ` If I connect a USB memory stick, this _does_ show up: `Bus 002 Device 002: ID 0781:5583 USB SanDisk 3.2Gen1` but there is no sign of the GPS. It seems that the required modules are present: `# find /lib | grep pl2303` `/lib/modules/5.10.31-v8/kernel/drivers/usb/serial/pl2303.ko` There are indications that not all is well with the USB ports. `dmesg | grep usb` shows output that includes: `[3.366928] usb 1-1: device descriptor read/64, error -71` … `[6.026753] usb 1-1: device not accepting address 4, error -22` I don’t see anything like this with Ubuntu loaded, and - after trying a bunch of different things - an wondering if there is a general problem with the USB support, rather than something specific with the GPS device. I did note that the config.txt for the Ubuntu system includes `dtoverlay=dwc2` I’ve tried including this a balena configuration variable (and checked that it gets into the config.txt) but `dmesg` output suggests that `dwc_otg` is still loaded… I’m assuming that until I can get the device to show up in the HostOS, I can’t expect to be able to use it from a container. **Update** : I’ve discovered if I use balenaOS 2.75.0+rev1 instead, then the device is detected, the pl2303 driver is loaded, and /dev/ttyUSB0 is created. So looks like it is a 2.82.10 issue. For completeness, I’ve also tried 2.80.5+rev1 - that also seems to be working. So the problem appears to be specific to balenaOS 2.82.10+rev1 and nothing to do with dwc2 vs dwc\_otg. ---
**Author:** ![fod\_unit](https://avatars.discourse-cdn.com/v4/letter/f/4da419/32.png) [@fod\_unit](https://forums.balena.io/u/fod_unit)\ **Post date:** [August 8, 2021, 11:26pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/2 "2021-08-08T23:26:02Z")
I’ve spent a few hours troubleshooting the same on a raspberry pi 4-2G. Error messages match the above. It was a small sea of error -22 and -71 in the log files. The exception to your results is that I couldn’t even see a flash drive plugged in – no usb devices worked (at least that I tried). The devices were available and showed in lsusb if I switched to a generic linux image. Downgrading to 2.80.5 resolves the USB bus issues and I can see the devices that are connected. Thank you for the suggestion to downgrade releases. ---
**Author:** ![bstein2379](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@bstein2379](https://forums.balena.io/u/bstein2379)\ **Post date:** [August 9, 2021, 1:06pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/3 "2021-08-09T13:06:28Z")
Thanks for reporting what you found. I too was having issues with USB on the Raspberry Pi 4 B 8GB. As soon as I downgraded to 2.80.5+rev1 it now works. Consequently, I was not having issues with USB on the Raspberry Pi 4 B 4GB. That was detecting my USB device just fine using 2.82.10+rev1. ---
**Author:** ![danthegoodman1](https://avatars.discourse-cdn.com/v4/letter/d/7bcc69/32.png) [@danthegoodman1](https://forums.balena.io/u/danthegoodman1)\ **Post date:** [August 9, 2021, 6:37pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/4 "2021-08-09T18:37:45Z")
Thanks for reporting this issue. I will create a Github issue for this! ---
**Author:** ![danthegoodman1](https://avatars.discourse-cdn.com/v4/letter/d/7bcc69/32.png) [@danthegoodman1](https://forums.balena.io/u/danthegoodman1)\ **Post date:** [August 9, 2021, 6:42pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/6 "2021-08-09T18:42:21Z")
You can track the github issue here: [USB GPS modules not appearing in \>= 2.82.10+rev1 · Issue #695 · balena-os/balena-raspberrypi · GitHub](https://github.com/balena-os/balena-raspberrypi/issues/695) ---
**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\ **Post date:** [September 3, 2021, 11:51pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/9 "2021-09-03T23:51:37Z")
@dajm01 @fod_unit – We just released a new version of the OS (version 2.83.10+rev1) that should include a fix for this issue. Go ahead and give it another try if you have a moment, thanks! ---
**Author:** ![fod\_unit](https://avatars.discourse-cdn.com/v4/letter/f/4da419/32.png) [@fod\_unit](https://forums.balena.io/u/fod_unit)\ **Post date:** [September 4, 2021, 1:53am UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/11 "2021-09-04T01:53:57Z")
Hi @dtischler I ran this through one of my 2G raspberry Pi 4 units. Behavior changed but the problem remains. [30.504301] usb 1-1: device descriptor read/64, error -71 [30.748109] usb 1-1: new high-speed USB device number 7 using xhci\_hcd [34.664367] usb 1-1: device descriptor read/64, error -71 [37.360355] usb 1-1: device descriptor read/64, error -71 [37.468552] usb usb1-port1: attempt power cycle [38.120177] usb 1-1: new high-speed USB device number 8 using xhci\_hcd [38.120372] xhci\_hcd 0000:01:00.0: Setup ERROR: setup address command for slot 1. [38.328298] xhci\_hcd 0000:01:00.0: Setup ERROR: setup address command for slot 1. [38.536186] usb 1-1: device not accepting address 8, error -22 [38.664165] usb 1-1: new high-speed USB device number 9 using xhci\_hcd [38.664311] xhci\_hcd 0000:01:00.0: Setup ERROR: setup address command for slot 1. [38.872298] xhci\_hcd 0000:01:00.0: Setup ERROR: setup address command for slot 1. [39.080147] usb 1-1: device not accepting address 9, error -22 [39.080484] usb usb1-port1: unable to enumerate USB device [39.224222] usb 1-1: new high-speed USB device number 10 using xhci\_hcd [42.328425] usb 1-1: device descriptor read/64, error -71 [44.736845] usb 1-1: device descriptor read/64, error -71 [44.972267] usb 1-1: new high-speed USB device number 11 using xhci\_hcd [47.008473] audit: type=1334 audit(1630719462.944:86): prog-id=18 op=UNLOAD [47.008505] audit: type=1334 audit(1630719462.944:87): prog-id=17 op=UNLOAD [48.480533] usb 1-1: device descriptor read/64, error -71 [51.944612] usb 1-1: device descriptor read/64, error -71 lsusb output is basically missing all the devices. Applies to the host and the containers (running privileged - same image): Bus 002 Device 001: ID 1d6b:0003 Bus 001 Device 001: ID 1d6b:0002 ---
**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\ **Post date:** [September 4, 2021, 2:01am UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/12 "2021-09-04T02:01:10Z")
Brilliant, thanks for testing it @fod_unit ! That is a fresh install of v2.83? In the host OS, can you grab the output from `ls /dev` please? ---
**Author:** ![fod\_unit](https://avatars.discourse-cdn.com/v4/letter/f/4da419/32.png) [@fod\_unit](https://forums.balena.io/u/fod_unit)\ **Post date:** [September 4, 2021, 2:23am UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/14 "2021-09-04T02:23:46Z")
hi @dtishler - it is not a fresh install - this was an upgrade. I can do a fresh install if it helps. Here’s the output of /dev ```auto ashmem cuse gpiomem loop0 mem net ram11 ram6 rpivid-intcmem stderr tty13 tty21 tty3 tty38 tty46 tty54 tty62 uhid vcs3 vcsa5 vga_arbiter autofs disk hwrng loop1 mmcblk0 null ram12 ram7 rpivid-vp9mem stdin tty14 tty22 tty30 tty39 tty47 tty55 tty63 uinput vcs4 vcsa6 vhci binder dma_heap i2c-1 loop2 mmcblk0p1 port ram13 ram8 serial0 stdout tty15 tty23 tty31 tty4 tty48 tty56 tty7 urandom vcs5 vcsu vhost-net block dri initctl loop3 mmcblk0p2 ppp ram14 ram9 serial1 tty tty16 tty24 tty32 tty40 tty49 tty57 tty8 vc-mem vcs6 vcsu1 watchdog bus fd input loop4 mmcblk0p3 ptmx ram15 random shm tty0 tty17 tty25 tty33 tty41 tty5 tty58 tty9 vchiq vcsa vcsu2 watchdog0 cachefiles full kmsg loop5 mmcblk0p4 pts ram2 raw snapshot tty1 tty18 tty26 tty34 tty42 tty50 tty59 ttyAMA0 vcio vcsa1 vcsu3 zero char fuse kvm loop6 mmcblk0p5 ram0 ram3 rfkill snd tty10 tty19 tty27 tty35 tty43 tty51 tty6 ttyS0 vcs vcsa2 vcsu4 zram0 console gpiochip0 log loop7 mmcblk0p6 ram1 ram4 rpivid-h264mem spidev0.0 tty11 tty2 tty28 tty36 tty44 tty52 tty60 ttyprintk vcs1 vcsa3 vcsu5 cpu_dma_latency gpiochip1 loop-control mapper mqueue ram10 ram5 rpivid-hevcmem spidev0.1 tty12 tty20 tty29 tty37 tty45 tty53 tty61 ubi_ctrl vcs2 vcsa4 vcsu6 ` Happy to give you the verbose output on any devices if you need it. ``` ---
**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\ **Post date:** [September 7, 2021, 7:29pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/15 "2021-09-07T19:29:40Z")
@fod_unit Well, I would have hoped that an Upgrade of the OS would resolve the issue, it _should_ have… But for the sake of testing, could you do a fresh install of v2.83 and again give us the output of `lsusb` and `ls /dev` please? Thanks! ---
**Author:** ![fod\_unit](https://avatars.discourse-cdn.com/v4/letter/f/4da419/32.png) [@fod\_unit](https://forums.balena.io/u/fod_unit)\ **Post date:** [September 9, 2021, 12:53am UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/16 "2021-09-09T00:53:18Z")
@dtischler - scratch install didn’t change the behavior. Here’s the outputs: ```auto Bus 002 Device 001: ID 1d6b:0003 Bus 001 Device 001: ID 1d6b:0002 ``` and ```auto ashmem full loop1 mmcblk0p5 ram13 rpivid-h264mem tty tty20 tty33 tty46 tty59 uinput vcsa2 vhost-net autofs fuse loop2 mmcblk0p6 ram14 rpivid-hevcmem tty0 tty21 tty34 tty47 tty6 urandom vcsa3 watchdog binder gpiochip0 loop3 mqueue ram15 rpivid-intcmem tty1 tty22 tty35 tty48 tty60 vc-mem vcsa4 watchdog0 block gpiochip1 loop4 net ram2 rpivid-vp9mem tty10 tty23 tty36 tty49 tty61 vchiq vcsa5 zero bus gpiomem loop5 null ram3 serial0 tty11 tty24 tty37 tty5 tty62 vcio vcsa6 zram0 cachefiles hwrng loop6 port ram4 serial1 tty12 tty25 tty38 tty50 tty63 vcs vcsu char i2c-1 loop7 ppp ram5 shm tty13 tty26 tty39 tty51 tty7 vcs1 vcsu1 console initctl mapper ptmx ram6 snapshot tty14 tty27 tty4 tty52 tty8 vcs2 vcsu2 cpu_dma_latency input mem pts ram7 snd tty15 tty28 tty40 tty53 tty9 vcs3 vcsu3 cuse kmsg mmcblk0 ram0 ram8 spidev0.0 tty16 tty29 tty41 tty54 ttyAMA0 vcs4 vcsu4 disk kvm mmcblk0p1 ram1 ram9 spidev0.1 tty17 tty3 tty42 tty55 ttyS0 vcs5 vcsu5 dma_heap log mmcblk0p2 ram10 random stderr tty18 tty30 tty43 tty56 ttyprintk vcs6 vcsu6 dri loop-control mmcblk0p3 ram11 raw stdin tty19 tty31 tty44 tty57 ubi_ctrl vcsa vga_arbiter fd loop0 mmcblk0p4 ram12 rfkill stdout tty2 tty32 tty45 tty58 uhid vcsa1 vhci ``` Hope this helps! ---
**Author:** ![jswanson](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@jswanson](https://forums.balena.io/u/jswanson)\ **Post date:** [September 15, 2021, 10:11pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/17 "2021-09-15T22:11:06Z")
@dtischler Hi! I have a similar problem- I have a few Raspberry Pi 4 B in the field that have lost all USB functionality after upgrading to balenaOS 2.83.10+rev1. Notably the VLI hub interface does not appear with `lsusb`. A few observations: - This issue seems specific to Rev 1.4 versions of the Raspberry Pi 4 B, identical balenaOS 2.83.10+rev1 images on Rev 1.1 boards work fine. - Stock Raspberry Pi OS images on Rev 1.4 boards work as well - balenaOS 2.75.0+rev1 on Rev 1.4 boards works Any ideas would be very appreciated! ---
**Author:** ![nmaas87](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/nmaas87/32/5570_2.png) [@nmaas87](https://forums.balena.io/u/nmaas87)\ **Post date:** [September 16, 2021, 5:29am UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/18 "2021-09-16T05:29:04Z")
Excellent point: " Rev 1.4 removes the EEPROM from the Via VL805, so the kernel and firmware gained a mechanism to load the firmware. " > > > The VL805 FW may either be loaded from an SPI EEPROM or alternatively > loaded dir…ectly by the VideoCore firmware. A PCI reset will reset > the VL805 XHCI controller on the Raspberry Pi4 requiring the firmware > to be reloaded if an SPI EEPROM is not present. > > Use a VideoCore mailbox to trigger the loading of the VL805 > firmware (if necessary) after a PCI reset. > > Signed-off-by: Tim Gover \ [https://www.raspberrypi.org/forums/viewtopic.php?t=275782](https://www.raspberrypi.org/forums/viewtopic.php?t=275782) The VL805 is the USB 3 controller, so maybe something which should be fixed at some point in downstream Yocto? @dtischler ---
**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\ **Post date:** [September 28, 2021, 8:45pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/21 "2021-09-28T20:45:47Z")
@dajm01 @fod_unit @bstein2379 @jswanson @nmaas87 According to [linux-raspberrypi\_5.10.bbappend: Remove obsolete VL805 patch by floion · Pull Request #712 · balena-os/balena-raspberrypi · GitHub](https://github.com/balena-os/balena-raspberrypi/pull/712) this should now be resolved, would one of you be willing to try out balenaOS v2.85.2+rev3 on a device to see if your issue is cleared up? Thanks! ---
**Author:** ![dajm01](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dajm01](https://forums.balena.io/u/dajm01)\ **Post date:** [September 28, 2021, 9:42pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/22 "2021-09-28T21:42:46Z")
Hi @dtischler We have tried balenaOS v2.85.2+rev3 and confirm that the USB GPS device is now accessible, which is great. Apologies for not testing the previous version 2.83.10+rev1. I have also confirmed that the device is a rev1.4 pi 4B. One quirk is that `lsusb` in the hostOS doesn’t identify the device. I see the ID: `Bus 001 Device 009: ID 067b:2303` but not the further details `Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P` I see when connected to ubuntu 21.04. I do see details for other devices, e.g. `ID 0781:5583 USB SanDisk 3.2Gen1`. But this is a minor inconvenience, given that the device is now working! Thanks for the efforts on this. ---
**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\ **Post date:** [September 28, 2021, 9:57pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/23 "2021-09-28T21:57:55Z")
Hmmm, and what about if you try a more verbose output with `lsusb -v` ? Either way, glad to hear that it’s functional for you @dajm01! ---
**Author:** ![dajm01](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dajm01](https://forums.balena.io/u/dajm01)\ **Post date:** [September 28, 2021, 10:17pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/24 "2021-09-28T22:17:08Z")
`lsusb -v` finds the correct manufacturer: `iManufacturer 1 Prolific Technology Inc.` but not the more detailed device descriptor (`PL2303 Serial Port` etc) that ubuntu reported. Rather, I’m seeing: `iProduct 2 USB-Serial Controller D` ---
**Author:** ![jswanson](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@jswanson](https://forums.balena.io/u/jswanson)\ **Post date:** [September 29, 2021, 2:42pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/25 "2021-09-29T14:42:52Z")
Hi @dtischler, balenaOS v2.85.2+rev3 is working on my end as well! Similarly with RPi 4B Rev 1.4. Thanks Balena team for getting this out so quickly! ---
**Author:** ![fod\_unit](https://avatars.discourse-cdn.com/v4/letter/f/4da419/32.png) [@fod\_unit](https://forums.balena.io/u/fod_unit)\ **Post date:** [October 2, 2021, 2:47pm UTC](https://forums.balena.io/t/usb-problem-with-rpi4-balenaos-2-82-10-rev1/343721/26 "2021-10-02T14:47:17Z")
Hi @dtischler After update to balenaOS v2.85.2+rev3, things look much improved. I am getting good data without errors so far. I’ll advise if I see any change after I get a bit more operational time in. Thanks for taking care of this.