USB devices not detected on CM4

Bug #1969689 reported by William Wilson
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-raspi (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned
Kinetic
Invalid
Undecided
Unassigned

Bug Description

USB devices are not working on the CM4. When running `lsusb` the hub is detected, but devices are not.

```
ubuntu@ubuntu:~$ sudo dmesg | egrep -i "dwc2|usb"
[ 0.151915] usbcore: registered new interface driver usbfs
[ 0.151976] usbcore: registered new interface driver hub
[ 0.152047] usbcore: registered new device driver usb
[ 1.125855] usbcore: registered new interface driver lan78xx
[ 1.125926] usbcore: registered new interface driver smsc95xx
[ 1.125965] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.126070] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.126318] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.765785] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 1.864470] dwc2 fe980000.usb: supply vusb_d not found, using dummy regulator
[ 1.864674] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator
[ 1.916752] dwc2 fe980000.usb: DWC OTG Controller
[ 1.916788] dwc2 fe980000.usb: new USB bus registered, assigned bus number 1
[ 1.916822] dwc2 fe980000.usb: irq 36, io mem 0xfe980000
[ 1.917028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 1.917040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.917048] usb usb1: Product: DWC OTG Controller
[ 1.917055] usb usb1: Manufacturer: Linux 5.15.0-1005-raspi dwc2_hsotg
[ 1.917062] usb usb1: SerialNumber: fe980000.usb
[ 1.917627] hub 1-0:1.0: USB hub found
[ 7.831293] usbcore: registered new interface driver brcmfmac
```

@waveform was able to confirm the issue. The line `dtoverlay=dwc2,dr_mode=host` is present in config.txt. We suspect this to be a dtb/kernel issue. This is happening on both armhf and arm64.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1969689

tags: added: iso-testing
Dave Jones (waveform)
Changed in linux-raspi (Ubuntu):
status: New → Confirmed
milestone: none → ubuntu-22.04.1
Juerg Haefliger (juergh)
tags: added: kern-3070
Revision history for this message
Juerg Haefliger (juergh) wrote :

Works for me:

ubuntu@rpi-cm4-rev1d0-0643:~$ sudo dmesg | egrep -i "dwc2|usb"
[ 0.158689] usbcore: registered new interface driver usbfs
[ 0.158752] usbcore: registered new interface driver hub
[ 0.158821] usbcore: registered new device driver usb
[ 0.991698] usbcore: registered new interface driver lan78xx
[ 0.991775] usbcore: registered new interface driver smsc95xx
[ 0.991820] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.991920] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.992017] uhci_hcd: USB Universal Host Controller Interface driver
[ 3.240675] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 3.337533] dwc2 fe980000.usb: supply vusb_d not found, using dummy regulator
[ 3.346914] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator
[ 3.406469] dwc2 fe980000.usb: DWC OTG Controller
[ 3.411464] dwc2 fe980000.usb: new USB bus registered, assigned bus number 1
[ 3.418734] dwc2 fe980000.usb: irq 21, io mem 0xfe980000
[ 3.424358] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 3.432800] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.440191] usb usb1: Product: DWC OTG Controller
[ 3.444994] usb usb1: Manufacturer: Linux 5.15.0-1005-raspi dwc2_hsotg
[ 3.451638] usb usb1: SerialNumber: fe980000.usb
[ 3.456787] hub 1-0:1.0: USB hub found
[ 3.858285] usb 1-1: new high-speed USB device number 2 using dwc2
[ 4.070527] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 4.078886] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.088386] hub 1-1:1.0: USB hub found
[ 11.138369] usbcore: registered new interface driver brcmfmac
[ 158.995621] usb 1-1.2: new low-speed USB device number 3 using dwc2
[ 159.107792] usb 1-1.2: New USB device found, idVendor=093a, idProduct=2510, bcdDevice= 1.00
[ 159.116349] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 159.123850] usb 1-1.2: Product: USB Optical Mouse
[ 159.128698] usb 1-1.2: Manufacturer: PixArt
[ 159.171337] usbcore: registered new interface driver usbhid
[ 159.177047] usbhid: USB HID core driver
[ 159.196745] input: PixArt USB Optical Mouse as /devices/platform/soc/fe980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:093A:2510.0001/input/input0
[ 159.209904] hid-generic 0003:093A:2510.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-fe980000.usb-1.2/input0
ubuntu@rpi-cm4-rev1d0-0643:~$ lsusb
Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Revision history for this message
Dave Jones (waveform) wrote :

@juergh Hmmm, what's the revision code on your CM4? I'm wondering if you've got either a different revision board, or if you've got a different RAM amount (both jawn-smith and I are testing on 4GB RAM variants and I wonder, given the history of issues with USB on the Pi4 on the higher-RAM models, whether something similar could be occurring?)

Revision history for this message
Dave Jones (waveform) wrote :

Argh, I'm an idiot -- had the flashing cable plugged into the micro-USB while the keyboard was *also* plugged into the USB-A sockets (which I knew doesn't work and apparently missed when originally debugging this). Closing as invalid.

Changed in linux-raspi (Ubuntu Jammy):
status: New → Invalid
Changed in linux-raspi (Ubuntu Kinetic):
status: Confirmed → Invalid
Changed in linux-raspi (Ubuntu Kinetic):
milestone: ubuntu-22.04.1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.