 |
I can confirm this bug. The same thing happened to me. Relevant forum topic: https://forums.rockylinux.org/t/rocky-9-6-raspberry-cannot-boot-after-dnf-update/18773/10 |
- Anonymous
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009703 | Alternative Architectures | General | public | 2025-06-25 00:50 | 2025-06-27 13:53 |
| Reporter | Ryan Kitty | Assigned To | |||
| Priority | high | Severity | block | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0009703: Upgrading to RockyLinux 9.6 on Raspberry Pi 3B breaks /boot | ||||
| Description | (This is my first report here, so hopefully I did this right) Upon doing a dnf update on my Raspberry Pi 3B, the system does not initialize after a reboot. I've come to find out that the files for the bootcode.bin and start.elf are placed within the /boot/efi directory instead of the /boot directory. The Pi's hardware doesn't search that directory to boot (on this older model I think), and as such, "bricks" the system until you take the card to a computer and move the files out of that directory and back into /boot. I think the affected package(s) is either raspberrypi2-kernel4-6.1.31-v8.1.el9.altarch.aarch64, kernel-rpi-firmware, or raspberrypi2-kernel4. I'm not 100% sure. | ||||
| Steps To Reproduce | 1. Boot Raspberry Pi 3B 2. dnf update 3. Reboot Raspberry Pi 3B after update | ||||
| Tags | No tags attached. | ||||
|
|
I can confirm this bug. The same thing happened to me. Relevant forum topic: https://forums.rockylinux.org/t/rocky-9-6-raspberry-cannot-boot-after-dnf-update/18773/10 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-25 00:50 | Ryan Kitty | New Issue | |
| 2025-06-27 13:53 | urandom zero | Note Added: 0010495 |