After upgrading to uboot-tools-2026.04-0.5.rc3.fc44, the rpi4 fails to boot from USB, no usb storage is detected. Reproducible: Always Steps to Reproduce: 1. Boot Fedora 44 Beta, which includes uboot-tools-2026.04-0.4.rc2.fc44 2. Upgrade to uboot-tools-2026.04-0.5.rc3.fc44 Actual Results: RC3: U-Boot 2026.04-rc3 (Feb 27 2026 - 00:00:00 +0000) DRAM: 3.9 GiB RPI 4 Model B (0xc03112) Core: 216 devices, 18 uclasses, devicetree: board MMC: mmcnr@7e300000: 1, mmc@7e340000: 0 Loading Environment from FAT... Card did not respond to voltage select! : -110 ** Bad device specification mmc 0 ** In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... USB DWC2 USB XHCI 1.00 XHCI timeout on event type 33... Cannot allocate device context to get SLOT_ID XHCI timeout on event type 33... Cannot allocate device context to get SLOT_ID Bus usb@7e980000: 1 USB Device(s) found Bus xhci_pci: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Expected Results: uboot-tools-2026.04-0.4.rc2.fc44: U-Boot 2026.04-rc2 (Feb 09 2026 - 00:00:00 +0000) DRAM: 3.9 GiB RPI 4 Model B (0xc03112) Core: 216 devices, 18 uclasses, devicetree: board MMC: mmcnr@7e300000: 1, mmc@7e340000: 0 Loading Environment from FAT... Card did not respond to voltage select! : -110 ** Bad device specification mmc 0 ** In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... USB DWC2 USB XHCI 1.00 Bus usb@7e980000: 1 USB Device(s) found Bus xhci_pci: 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Additional Information: No change with RC4.
Proposed as a Freeze Exception for 44-final by Fedora user jgroman using the blocker tracking app because: While majority of RPi4 users likely boot from SD card it would be useful to have this problem fixed for Final so that we do not break already existing use case.
It would be useful if you engaged with the maintainer TBH jgroman to get the full context of this bug
What context is missing? The report seems fairly clear?
Since we have release blocking aarch64 ISO images [1], proposing this as a blocker as well. Criterion [2]. [1] https://docs.fedoraproject.org/en-US/releases/f43/blocking/ [2] https://fedoraproject.org/wiki/Basic_Release_Criteria#Release-blocking_images_must_boot
Accepted as a freeze exception in: https://pagure.io/fedora-qa/blocker-review/issue/2079
AGREED AcceptedFinalBlocker Discussed at the 2026-03-23 (blocker / freeze exception) review meeting: This is a violation of "the installed system must boot" criterion (in "Expected installed system boot behavior"), when booting a RPi system installed to a USB device. https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-03-23/f44-blocker-review.2026-03-23-16.00.log.txt
Still digging into this
I've bisected the issue, just trying to work out a fix.
Heads up, go/no-go meeting is in ~one hour, we'll likely try and ping you for an update there.
I think I have a fix for this. I am just testing, and cross checking the patch isn't a cause of another (seemingly unrelated) issue.
FEDORA-2026-19394a88c8 (uboot-tools-2026.04-2.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-19394a88c8
FEDORA-2026-19394a88c8 (uboot-tools-2026.04-2.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-c4b1e19b5c (bcm283x-firmware-20260408-1.6bc3936.fc44, dt-schema-2026.04-1.fc44, and 1 more) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-c4b1e19b5c
FEDORA-2026-c4b1e19b5c has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c4b1e19b5c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c4b1e19b5c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Verified fixed in uboot-tools-2026.04-2.fc44: U-Boot 2026.04 (Apr 11 2026 - 00:00:00 +0000) DRAM: 3.9 GiB RPI 4 Model B (0xc03112) Core: 216 devices, 18 uclasses, devicetree: board MMC: mmcnr@7e300000: 1, mmc@7e340000: 0 Loading Environment from FAT... Card did not respond to voltage select! : -110 ** Bad device specification mmc 0 ** In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Net: eth0: ethernet@7d580000 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... USB DWC2 USB XHCI 1.00 Bus usb@7e980000: 1 USB Device(s) found Bus xhci_pci: 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found
AcceptedFE and AcceptedBlocker are redundant, dropping FE.
FEDORA-2026-c4b1e19b5c (bcm283x-firmware-20260408-1.6bc3936.fc44, dt-schema-2026.04-1.fc44, and 1 more) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.