No USB detected on Raspberry Pi 4 with aarch64

[blacktemplar]

I am currently trying to install the 64bit version on my Raspberry Pi 4 and I followed this guide: https://archlinuxarm.org/platforms/armv ... berry-pi-4 including the comments at the bottom about AArch64 installation.

Unfortunately none of my USB ports get detected and I found the following error messages in dmesg:

$this->bbcode_second_pass_code('', '
Aug 28 13:16:09 alarm kernel: pci 0000:01:00.0: VL805 firmware version 00000000
Aug 28 13:16:09 alarm kernel: pci 0000:01:00.0: xHCI HW not ready after 5 sec (HC bug?) status = 0x805
Aug 28 13:16:09 alarm kernel: pci 0000:01:00.0: quirk_usb_early_handoff+0x0/0x1a0 took 5299536 usecs
Aug 28 13:16:09 alarm kernel: xhci_hcd 0000:01:00.0: xHCI Host Controller
Aug 28 13:16:09 alarm kernel: xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
Aug 28 13:16:09 alarm kernel: xhci_hcd 0000:01:00.0: can't setup: -110
Aug 28 13:16:09 alarm kernel: xhci_hcd 0000:01:00.0: USB bus 1 deregistered
Aug 28 13:16:09 alarm kernel: xhci_hcd 0000:01:00.0: init 0000:01:00.0 fail, -110
Aug 28 13:16:09 alarm kernel: xhci_hcd: probe of 0000:01:00.0 failed with error -110
')

I tried to google those to find some answers but couldn't find anything that could solve it.

If I install the 32bit version the USB ports work fine (I was even able to boot directly from USB with the 32bit version).

[cosinekitty]

I'm encountering the same thing. I have done hours of research, and tried all kinds of things. When running Raspbian Lite armv7l on my Pi 4, the USB works fine. But with aarch64, this happens:

$this->bbcode_second_pass_code('', '
[ 16.281304] pci 0000:01:00.0: xHCI HW not ready after 5 sec (HC bug?) status = 0x815
[ 16.298866] pci 0000:01:00.0: quirk_usb_early_handoff+0x0/0x1a0 took 5332535 usecs
[ 16.316296] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 16.329372] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[ 26.347073] xhci_hcd 0000:01:00.0: can't setup: -110
[ 26.359015] xhci_hcd 0000:01:00.0: USB bus 1 deregistered
[ 26.372967] xhci_hcd 0000:01:00.0: init 0000:01:00.0 fail, -110
[ 26.386906] xhci_hcd: probe of 0000:01:00.0 failed with error -110
')

When I boot up, there is absolutely no USB available. I have to log in via ssh. Then lsusb -v prints no output at all. It simply doesn't see anything.

Also, about 1 in 4 times I boot up, Ethernet also doesn't work, so there is no way I can do anything to access the computer. I have to unplug it and plug it back in.

I'm using the recommended power supply (3.5 amp). This system has 8GB. Raspbian's rpi-eeprom-update utility says my bootloader EEPROM is up to date (April 16 2020 18:11:26), for what it's worth. I tried editing /boot/boot.txt, first trying over_voltage=1, then over_voltage=2, and finally over_voltage=8. Yes, I remembered to run ./mkscr each time before rebooting.

What should we try? Is there something we can do to provide better diagnostic information? Thanks in advance to anyone who can give us some clues.

[Czar]

viewtopic.php?p=64313#p64313

Adding said module fixed my issue.

[blacktemplar]

I already added the module pcie_brcmstb and it didn't change anything. Since the problem does not only consist during boot but also afterwards I am not sure if this can fix it.

[cosinekitty]

Just a follow-up. I'm giving up on aarch64 on Raspberry Pi 4 for now. I can get aarch64 working on Raspberry Pi 3B, and I can get armv7l working on Raspberry Pi 4, but try to put the two together and USB never works at all, and Ethernet fails about 1 in 4 boots.

The whole reason I thought I needed aarch64 is because this Pi 4 has 8GB of RAM and I didn't think a 32-bit Linux could address more than 4GB. It turns out that is wrong: in https://www.raspberrypi.org/blog/8gb-ra ... -now-at-75 it says that the 32-bit OS "... allows multiple processes to share all 8GB of memory, subject to the restriction that no single process can use more than 3GB." OK, I can live with that! I confirmed that my system sees all the RAM:

$this->bbcode_second_pass_code('', '
[don@mango ~]$ uname -a
Linux mango 5.4.61-2-ARCH #1 SMP PREEMPT Fri Sep 4 12:46:16 UTC 2020 armv7l GNU/Linux
[don@mango ~]$ free -h
total used free shared buff/cache available
Mem: 7.7Gi 52Mi 7.6Gi 0.0Ki 76Mi 7.6Gi
Swap: 0B 0B 0B
')

I hope this post saves other people some hassle and frustration... just follow the default instructions on the Installation tab at https://archlinuxarm.org/platforms/armv ... berry-pi-4 and ignore the aarch64 stuff at the bottom.

[blacktemplar]

I too gave up on aarch64 (I also have a 8GB version, so maybe this is somehow the root of the problem). I could now successfully install Manjaro, even with direct USB booting.

[rbollons]

I'm also experiencing this with an RPi 8gb when running the aarch64 install steps.
I've tried these things to no avail:

- Add pcie_brcmstb into MODULES in /etc/mkinitcpio.conf and rebuild (mkinitcpio -P)
- Manually install Uboot with 2020.10rc2 (as mentioned in this post https://archlinuxarm.org/forum/viewtopic.php?p=64313#p64313)
- Increase over voltage

I found that limiting the RAM to <3GB caused the USB to work (I tried in 1GB increments), anything >4GB does not and results in the same xhci_hcd error in dmesg

[moonman]

Looks like a patch (or rather reverse of a patch) may be required to get this fixed for 8GB boards, which probably hasn't made it into mainline yet.: https://github.com/raspberrypi/linux/issues/3747

[lihs]

Same problem.

I found some information of ubuntu.

https://bugs.launchpad.net/bugs/1848790

Hope it can help fix this.

[slashdolt]

Bump for the same problem, I wasted a lot of time screwing around with this. I wish they'd note somewhere on the RPI4 page that USB doesn't work with 8gb RPI 4. It'd save someone a lot of frustration.