[Bug 1961871] Re: 20.04.4 candidate image doesn't work with some usb/eth on pi-zero-2

[Juerg Haefliger]

Even after adding both lines dtoverlay=dwc2 and
dtoverlay=dwc2,dr_mode=host the device boots fine with an r8152 USB NIC
attached (and the network comes up).

Can you enable 2nd stage debugging (uart_2ndstage=1 in config.txt)?

You should see on the serial console if the overlay is loaded twice:

MESS:00:00:02.775986:0: brfs: File read: 2129 bytes
MESS:00:00:02.783554:0: brfs: File read: /mfs/sd/overlays/dwc2.dtbo
MESS:00:00:02.795064:0: Loaded overlay 'dwc2'
MESS:00:00:02.808943:0: brfs: File read: 801 bytes
MESS:00:00:02.812798:0: brfs: File read: /mfs/sd/overlays/dwc2.dtbo
MESS:00:00:02.824888:0: Loaded overlay 'dwc2'
MESS:00:00:02.827544:0: dtparam: dr_mode=host

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/1961871

Title:
  20.04.4 candidate image doesn't work with some usb/eth on pi-zero-2

Status in u-boot package in Ubuntu:
  New

Bug description:
  The devices I have at home all seem to work fine, but I noticed on the pi-zero-2 we have in the lab that it was working fine with the armhf candidate image from 20220221 but not with arm64. I was eventually able to get serial console on it and discovered that the device had booted, but failed to detect the network adapter, which in this case is using the r8152 driver and is part of a usb hub.
  It's weird that it worked fine on the armhf image but not arm64, so I looked a bit more and found that the arm64 image contained both of these lines in config.txt:
    dtoverlay=dwc2
    dtoverlay=dwc2,dr_mode=host
  On armhf, only the second line existed. I commented out the first line with 'dtoverlay=dwc2' and rebooted, then it was able to detect the ethernet-usb dongle and load the drivers for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1961871/+subscriptions