USB devices are not working on Raspberry pi zero 2 with arm64 image

Bug #1975669 reported by Gavin Lin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-raspi (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

[Summary]
USB devices are not working on Raspberry pi zero 2 with arm64 image.

I have tried following devices with adapters:
rpiz2 micro usb -> usb type-c -> usb type-c storage
rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a storage
rpiz2 micro usb -> usb type-c -> usb type-c ethernet dongle
rpiz2 micro usb -> usb type-c -> usb type-a -> usb type-a ethernet dongle

I have checked both 20.04 and 22.04, all these devices work fine with armhf images but not work with arm64 images.
And all these devices work fine on Raspberry pi 3a+ with armhf and arm64 images

[Steps to reproduce]
1. Flash image to SD card
2. Boot into system
3. Check usb device with lsusb

[Expected result]
All usb devices are working fine.

[Actual result]
USB devices are not working on Raspberry pi zero 2 with arm64 image.

[Additional information]
SKU: Raspberry pi zero 2
Kernel: 5.15.0-1008-raspi

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-raspi 5.15.0.1008.8
ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
Uname: Linux 5.15.0-1008-raspi aarch64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 25 04:00 seq
 crw-rw---- 1 root audio 116, 33 May 25 04:00 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1008-raspi.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Wed May 25 06:36:24 2022
ImageMediaBuild: 20220419
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:

Lspci-vt: -[0000:00]-
Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
PciMultimedia:

ProcEnviron:
 TERM=vt220
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 BCM2708 FB
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:6A:C0:29 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-1008-raspi N/A
 linux-backports-modules-5.15.0-1008-raspi N/A
 linux-firmware 20220329.git681281e4-0ubuntu3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-raspi
StagingDrivers: bcm2835_codec bcm2835_isp bcm2835_v4l2 vc_sm_cma bcm2835_mmal_vchiq snd_bcm2835
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:

Revision history for this message
Gavin Lin (gavin.lin) wrote :
Revision history for this message
Juerg Haefliger (juergh) wrote (last edit ):

Works fine for me:

$ cat /proc/device-tree/model
Raspberry Pi Zero 2 Rev 1.0
$ uname -a
Linux rpi-zero2-rev1d0-2c3c 5.15.0-1008-raspi #8-Ubuntu SMP PREEMPT Thu May 19 11:58:51 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
$ lsusb
Bus 001 Device 002: ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Juerg Haefliger (juergh)
tags: added: kern-3404
Revision history for this message
Gavin Lin (gavin.lin) wrote :

I got some more accessories to try yesterday, turns out the problem is related to micro usb to usb type-A/tupe-C adapter, only one of the five I tried worked both in armhf and arm64 images.
With that one, everything looks fine now.

Juerg Haefliger (juergh)
Changed in linux-raspi (Ubuntu):
status: New → Invalid
Revision history for this message
Per Ljung (pbljung) wrote :

Gavin - Which micro usb to usb type-A/tupe-C adapter worked for you? I am having a similar issue where a dongle works on Rpi0 and Rpi3 but not Rpi02

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.