|
Bugzilla – Full Text Bug Listing |
| Summary: | u-boot-rpiarm64-2024.01-1.1 fails on RPI4b | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | David Walker <David> |
| Component: | Bootloader | Assignee: | Ivan Ivanov <ivan.ivanov> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dmair, guillaume.gardet, ivan.ivanov, seife |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | aarch64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Screenshot of failed boot
hwinfo for this Raspberry Pi 4b |
||
Re-assigning to the u-boot maintainer. From your screenshot, it seems RPi4 USB is broken in u-boot. What is EEPROM firmware version? > sudo rpi-eeprom-update BOOTLOADER: up to date CURRENT: Wed Jan 11 05:40:52 PM UTC 2023 (1673458852) LATEST: Wed Jan 11 05:40:52 PM UTC 2023 (1673458852) RELEASE: default (/lib/firmware/raspberrypi/bootloader-2711/default) Use raspi-config to change the release. VL805_FW: Using bootloader EEPROM VL805: up to date CURRENT: 000138c0 LATEST: 000138c0 Seems old. Is this the right way to check? Here are my installed raspberrypi-* packages: > sudo zypper se --details raspb i+ | raspberrypi-eeprom | package | 2023.10.30-1.1 | noarch | openSUSE-Tumbleweed-Oss i | raspberrypi-eeprom-firmware | package | 2023.10.30-1.1 | noarch | openSUSE-Tumbleweed-Oss i | raspberrypi-firmware | package | 2023.11.21-1.1 | noarch | openSUSE-Tumbleweed-Oss i | raspberrypi-firmware-config | package | 2023.11.21-1.1 | noarch | openSUSE-Tumbleweed-Oss i | raspberrypi-firmware-dt | package | 2023.11.21-3.1 | noarch | openSUSE-Tumbleweed-Oss Hi David, is this device 8GB version? Yes, it is. Created attachment 873313 [details]
hwinfo for this Raspberry Pi 4b
Probably more than you need, but here's the output of hwinfo.
*** Bug 1220595 has been marked as a duplicate of this bug. *** Adding myself as another who experienced this. Copying a u-boot.bin didn't work for me and I ended up re-building the Pi (used as a spam server) from a December 2021 Tumbleweed install media snapshot, I locked the u-boot and the raspberry* packages and did the on-line-update. Still works. David, if "copying the u-boot.bin didn't work" for you, then you are experiencing a different but. PLEASE do not also spoil this u-boot bugreport, just keep on pursuing this in the old bug#1219908 (In reply to Stefan Seyfried from comment #10) > David, if "copying the u-boot.bin didn't work" for you, then you are > experiencing a different but. > PLEASE do not also spoil this u-boot bugreport, just keep on pursuing this > in the old bug#1219908 Spoiling was never the intent, I'll keep quiet and monitor. This issue seems to be resolved by today's 20240409 Tumbleweed snapshot with u-boot-rpiarm64-2024.04-1.1. All three of my 8GB Rpi4b's are booting normally. Thanks! My two 8GB rpi4b's are also booting fine again with current Tumbleweed :-) \O/ Fixed in 2024.04 release (see previous comments) |
Created attachment 872044 [details] Screenshot of failed boot After upgrading from Tumbleweed ARM 20240109 to 20240118, my RPI4b failed to boot from USB, then attempted to boot via tftp. I've attached a photo of the screen. I fixed the problem by copying /boot/efi/u-boot.bin from a working RPI4b to the failing system's /boot/efi. Not being sure of the function of /boot/vc, I also copied the working u-boot.bin to the failing system's /boot/vc.