Unable to boot Raspberry Pi with Ubuntu 20.04

[flamethrow3r]

But I've used the Raspberry Pi imager to flash the card, so that should also flash the firmware, right?

[flamethrow3r]

(Sorry, I didn't see my previous reply and thought it had been deleted; I didn't know there were different pages. This is a duplicate)

[him610]

It's a book. You mean the sixth to last chapter?

No, look at the screenshot posted in #1, here is what those lines read...

start4x.elf: is not compatible
This board requires newer software
Get the latest software from https://www.raspberrypi.com/software/

It says your board is incompatible with the software you are trying to load, your board needs newer software, and to get it you need to download one of the recommended Raspberry Pi OS releases.

I have used the OS on my Pi-1, my Pi-3B, and a netbook (x86) for years. It is a good OS; it's made for the Raspberry PI family of SBCs.

[flamethrow3r]

But I need Ubuntu 20.04 to be able to use ROS Humble for my project, Raspberry Pi OS is no good in this case. What confuses me is how it worked before and not anymore...

[him610]

I need Ubuntu 20.04 to be able to use ROS Humble

maybe this will help, Install ROS2 Humble on Raspberry Pi 4
https://roboticsbackend.com/install-...-raspberry-pi/

[flamethrow3r]

But that page uses 22.04. That version isn't giving me boot problems, but due to compatibility issues with some programs, I must use 20.04.

[ActionParsnip]

Use Raspberry Pi OS on the SDCard. Use the EEPROM updater to update the board, then re-transfer Ubuntu to the SDCard and boot up. You will now be on the latest firmware in the Pi

[flamethrow3r]

I already tried that along with other older versions of the eeprom, but no luck.

[flamethrow3r]

I'm just guessing here, but given that replacing the .elf and .dat files got Ubuntu 20.04 to at least boot, maybe the subsequent installer crash is due to another reason. Does anyone know why this could be happening?

[flamethrow3r]

I just bought a new Raspberry Pi 4B and tried Ubuntu 20.04 in it. It gave me the exact same error, so it seems it's easily reproducible. I've also found new information and updated the original post with it.