Ubuntu 18.04 64-bit RasPi 3 and 4 image fails to boot on RasPi 4B

[Chris Desnoyers]

[Impact]

The 64-bit 18.04 image linked from this page https://ubuntu.com/download/raspberry-pi for Raspberry Pi 3 and 4 fails to boot on my Raspberry Pi 4B (8G RAM). Boot fails with an error screen complaining that it needs newer software.

This is basically part of the big linux-firmware-raspi2 backport to bionic, but left this bug in the .changes for tracking purposes. See https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1888211 for more info.

[Test Case]

Build a new bionic-proposed raspi image, try booting it on a rev 1.4 board (e.g. Raspberry Pi 4 8GB).

[Regression Potential]

Same as in LP: #1888211.

[Original Description]

The 64-bit 18.04 image linked from this page https://ubuntu.com/download/raspberry-pi for Raspberry Pi 3 and 4 fails to boot on my Raspberry Pi 4B (8G RAM). Boot fails with an error screen complaining that it needs newer software.

The image in question can be found at https://ubuntu.com/download/raspberry-pi/thank-you?version=18.04&versionPatch=.4&architecture=arm64+raspi3 , so at first I figured maybe the wrong one had just been linked from the downloads page (image for raspi 3 instead of 4), but it has the same checksum as the image at https://ubuntu.com/download/raspberry-pi/thank-you?version=18.04&versionPatch=.4&architecture=arm64+raspi4 , so this seems unlikely.

The 64-bit 20.04 image linked from that same downloads page boots fine.

Most of the text from the error screen:
[note: I'm skipping some stuff here but could add it later if needed]

Raspberry Pi 4 - 8GB
board: d03114 a35e61b6 dc:a6:32:b1:a1:23
boot: mode 6 order 0x00000001 rsts 0x00001000
SD CID: [...]
part: 0 mbr [0x0c:00000800 0x83:00080800 0x00: 00000000 0x00: 00000000]
fw: start4.elf fixup4.dat
net: down ip: 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0
tftp: 0.0.0.0

Partition: 0
lba: 2048 oem: 'mkfs.fat' volume ' system-boot'
[...]
Read config.txt bytes [...]
recover4.elf not found
recovery.elf not found
Read start4.elf bytes [...]
Read fixup4.dat bytes [...]
[...]
start4.elf: is not compatible 0x0
This board requires newer software. Get the latest software from: [...]

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1886581/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Stéphane Graber (stgraber)]

This is a blocker to the release of the LXD appliance image as it's mainly targeted at newer rpi4 and especially the 8GB.

[Juerg Haefliger (juergh)]

What you get from the official download page is an old image that does not work with the Pi 4B rev 1.4.

[Juerg Haefliger (juergh)]

We don't have fully functional images yet.

[Brian Murray (brian-murray)]

Hello Chris, or anyone else affected,

Accepted linux-firmware-raspi2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware-raspi2/1.20200601+arm64-0ubuntu2~18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Chris Desnoyers (chris-desnoyers-renovo)]

Brian,

That's good to hear, thanks! Unfortunately I don't have an prior experience building bootable disk images for Ubuntu; is there a straightforward way for me to bake the updated firmware package into a bionic disk image for the raspi?

[Ajay Jadhav (ajoncloud)]

Count me in to test this as well, if you send me a bootable disk image that can boot off the SD Card. I am ready to go, I've a Pi4B/8GB

[Paul Larson (pwlars)]

I tested 1.20200601+arm64-0ubuntu2~18.04.1 by booting the image from http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-preinstalled/pending/ which already has proposed enabled, and it boots on rpi4-8G as well as my other rpi devices.

[Łukasz Zemczak (sil2100)]

Hello Chris, Ajay!

We are building daily proposed-based images for bionic which should have this fix in already. You can find those here:
http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-live/current/

Feel free to test those whenever you can! In the meantime, seeing that Paul was successful via comment #8, I'll consider this as verified.

[Chris Desnoyers (chris-desnoyers-renovo)]

Hi Lukasz! I just confirmed from today's image here http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-preinstalled/pending/ that the fix solved my problem. Thanks!

[Łukasz Zemczak (sil2100)]

Thanks for confirming! Let me release this update so that we can have it ready for the 18.04.5 release.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-firmware-raspi2 - 1.20200601+arm64-0ubuntu2~18.04.1

---------------
linux-firmware-raspi2 (1.20200601+arm64-0ubuntu2~18.04.1) bionic; urgency=medium

  * SRU to bionic to support booting RPi 4B rev 1.4 (LP: #1886581)
  * Update bluez firmware to latest upstream version (1.2-4+rpt3)
    (LP: #1888211)
  * Change packaging to use multi-upstream tarballs
  * Add diversion for BCM43430 binary blob
  * Bumped compat to 11 and fixed dh_strip issue

linux-firmware-raspi2 (1.20200601+arm64-0ubuntu1) groovy; urgency=medium

  * New upstream release, 1.20200601+arm64

 -- Dave Jones <email address hidden> Fri, 17 Jul 2020 18:55:11 +0100

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for linux-firmware-raspi2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.