2022-07-22 firmware broke booting Ubuntu 22.04

[KcrPL]

Describe the bug

This morning I used the rpi-eeprom-update tool to update the RPi's EEPROM to 2022-07-22. While the upgrade worked, booting to the OS on the SD Card no longer did. All I had was the ACTivity light (green LED) blinking the error code. The blinking repeats.

4 long and 4 short ones. I couldn't really find a lot of info about it but after 3 hours I gave up and reverted to 2022-04-26 (that I was using before) and it's working now.

Steps to reproduce the behaviour

• Upgrade to 2022-07-22 firmware using the rpi-eeprom-update tool (Recovery also works)
• You see the Activity LED giving you the error code: 4 long blinks and 4 short ones. It repeats.

Device (s)

Raspberry Pi 4 Mod. B

Bootloader configuration.

# version initially shipped with bionic) don't understand the conditional
# [sections] below and simply ignore them. The Pi4 doesn't boot at all with
# firmwares this old so it's safe to place at the top. Of the Pi2 and Pi3, the
# Pi3 uboot happens to work happily on the Pi2, so it needs to go at the bottom
# to support old firmwares.

[pi4]
# commented by do-release-upgrade (LP: #1936401)
#kernel=uboot_rpi_4.bin
max_framebuffers=2

[pi2]
# commented by do-release-upgrade (LP: #1936401)
#kernel=uboot_rpi_2.bin

[pi3]
# commented by do-release-upgrade (LP: #1936401)
#kernel=uboot_rpi_3.bin

[all]
# added by do-release-upgrade (LP: #1936401)
kernel=vmlinuz
initramfs initrd.img followkernel
arm_64bit=1
# commented by do-release-upgrade (LP: #1936401)
#device_tree_address=0x03000000

# The following settings are "defaults" expected to be overridden by the
# included configuration. The only reason they are included is, again, to
# support old firmwares which don't understand the "include" command.

enable_uart=1
cmdline=cmdline.txt

# merged from syscfg.txt by do-release-upgrade (LP: #1936401)

enable_uart=1
dtparam=audio=on
dtparam=i2c_arm=on
dtparam=spi=on
cmdline=cmdline.txt
# merged from usercfg.txt by do-release-upgrade (LP: #1936401)

System

No response

Bootloader logs

No response

USB boot

No response

NVMe boot

No response

Network (TFTP boot)

No response

[timg236]

Good news :) I’ll try to get this merged and released tomorrow

[KcrPL]

Alright, thank you! Thanks to all of you for fixing this issue.

Please close the issue once you release it to beta/stable :)

[timg236]

I've merged this to beta/stable. Thanks all for helping debug this.

I'll leave it a few more days before bumping the APT release

[KcrPL]

I can once again confirm that it's working :-)

[KcrPL]

Closing, thanks again guys!

[Flamethr0wer]

Hello. I'm having a very similar issue, with the same blinking pattern, but in 20.04 and the screen shows a "this board requires newer software" error. It says start4x.elf and fixup4x.dat are incompatible. @timg236 I flashed those eeprom recovery files into my Raspberry Pi but got the same error. You said you were able t reproduce it for 20.04. Do you know how to solve it in this version?