Debian Team,
I have a number of Raspberry Pi4 HW revision 1.4
cat /proc/device-tree/model
Raspberry Pi 4 Model B Rev 1.4
Using the pre-built images they only boot when using old EEPROM versions.
For example I have a Pi that does boot with the following output
running RasberryPi OS
sudo rpi-eeprom-update
*** UPDATE AVAILABLE ***
Run "sudo rpi-eeprom-update -a" to install this update without a prompt.
To configure the bootloader update policy run "sudo raspi-config"
BOOTLOADER: update available
CURRENT: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)
LATEST: Wed 23 Sep 12:02:14 UTC 2026 (1790164934)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138a1
LATEST: 000138a1
The update will be installed at the next reboot.
Install the update now? [y/N] n
However if I update so the output looks like this...
sudo rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Fri 30 Oct 23:20:35 UTC 2026 (1793402435)
LATEST: Wed 23 Sep 12:02:14 UTC 2026 (1790164934)
RELEASE: default (/usr/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
Then with this eeprom the raspberry Pi latest pre-built images no longer boot.
I believe this should be filed as a bug; however, I do not know which
package or pseudo package to file it under.
Any help appreciated.
Regards,
Phil
