Bug 1686508
Summary: | Raspberry Pi 3 fails to boot recent F29 IoT images | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> |
Component: | uboot-tools | Assignee: | Peter Robinson <pbrobinson> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | dan, dennis, jdisnard, labbott, mattdm, pbrobinson, pwhalen |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | bcm283x-firmware-20190212-2.83977fe.fc29 uboot-tools-2018.09-3.fc29 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-03-29 19:17:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1269538 |
Description
Paul Whalen
2019-03-07 15:29:09 UTC
Attempting to boot Fedora-IoT-30-20190301.0.aarch64.raw.xz MMC: mmc@7e202000: 0, mmc@7e300000: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... USB0: scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found EFI removable media binary efi/fedora/grubaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk mmc... Card did not respond to voltage select! Scanning disk mmc... Disk mmc not ready Found 4 disks FDT memrsv map 0: Failed to add to map 1886968 bytes read in 89 ms (20.2 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC FDT memrsv map 0: Failed to add to map ## Starting EFI application at 00080000 ... Waiting for Ethernet connection... EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... Using the dtb's from release 1 and removing the updated dtb's (bcm27*.dtb), the Raspberry Pi 3 boots as expected. bcm283x-firmware-20190212-2.83977fe.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cb85393cad bcm283x-firmware-20190212-2.83977fe.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-486c6579ea bcm283x-firmware-20190212-2.83977fe.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-486c6579ea bcm283x-firmware-20190212-2.83977fe.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-cb85393cad bcm283x-firmware-20190212-3.83977fe.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c2a7014f37 bcm283x-firmware-20190212-2.83977fe.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-486c6579ea bcm283x-firmware-20190212-2.83977fe.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-486c6579ea bcm283x-firmware-20190212-2.83977fe.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. bcm283x-firmware-20190212-4.83977fe.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-8528d07711 This isn't a firmware/DT problem at all, it's a problematic U-Boot UEFI patch Note this is completely reproducible on standard Fedora with uboot-tools-2018.09-2.fc29 on aarch64, I suspect it also causes issues on other platforms, it was probably missed for so long because we don't respin arm disk images post GA and people tend not to update U-Boot if it's not broken. uboot-tools-2018.09-3.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ebfd1fe19b bcm283x-firmware-20190212-4.83977fe.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8528d07711 uboot-tools-2018.09-3.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ebfd1fe19b bcm283x-firmware-20190212-4.83977fe.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. uboot-tools-2018.09-3.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. |