Bugzilla – Bug 1220595
U-Boot: Raspberry Pi 4b 8GB does not boot from USB
Last modified: 2024-03-08 09:09:46 UTC
Because the original bug has been taken over with lots of stuff unrelated to U-Boot, let's split this off.. +++ This bug was initially created as a clone of Bug #1219908 +++ since a zypper dup on end of January, raspberry pi 4a 8GB do no longer boot from USB. U-Boot fails with (transcribed from photograph) starting USB... Bus xhci pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... abort_td: Expected a TRB_TRANSFER TRB first XHCI timeout on event type 33... unable to get device descriptor (error=-110) XHCI timeout on event type 33... Cannot allocate device context to get SLOT_ID 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 And that's it, no boot device => u-boot then goes on and tries to boot from TFTP. If I replace u-boot.bin with the one from Leap 15.5, everything boots fine again. The same USB device boots on my raspberry pi 4B 2GB RAM and on a raspberry pi 400 (4GB), it fails on both 4B 8GB RAM boxes. It is independent of the USB device (tried various USB3-connected SSDs but also cheap and not so cheap USB2 sticks I did check the firmware and settings of both 4b 8GB boards, both have latest eeprom firmware (2023-01-?, same as the 2GB board) and identical settings.
In my todo list. Meanwhile, have you tried to upgrade or downgrade EEPROM firmware?
There is no newer eeprom firmware. I can try downgrading it, did not yet think of that.
I have the same problem on RPi4b 8G that are currently have openSUSE Tumbleweed installed.
Stefan I'll stick to the topic, my other topic comments in the previous bug were the results of diagnosis that visibly changed the point of failure.
Stefan Seyfried, David Mair, I am closing this bug as duplicate of bsc#1219033 which was created firstly ;-). I am sure that the case bsc#1219908 is the same, but will keep it open if David Mair find something interesting to share. *** This bug has been marked as a duplicate of bug 1219033 ***