[Bug 2085903] Re: [SRU] Please merge rpi-eeprom 26
Launchpad Bug Tracker
2085903 at bugs.launchpad.net
Tue Nov 12 19:28:22 UTC 2024
This bug was fixed in the package rpi-eeprom - 26.3-0ubuntu1
---------------
rpi-eeprom (26.3-0ubuntu1) plucky; urgency=medium
* New upstream release (LP: #2085903)
* rpi-eeprom-firmware: Split firmware binaries into new package to permit it
to be installed on all archs as dependency of newer rpiboot
-- Dave Jones <dave.jones at canonical.com> Tue, 12 Nov 2024 13:35:23
+0000
** Changed in: rpi-eeprom (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rpi-eeprom in Ubuntu.
https://bugs.launchpad.net/bugs/2085903
Title:
[SRU] Please merge rpi-eeprom 26
Status in rpi-eeprom package in Ubuntu:
Fix Released
Status in rpi-eeprom source package in Noble:
Triaged
Status in rpi-eeprom source package in Oracular:
Triaged
Bug description:
[ Impact ]
The newer boot firmware is required to successfully boot newer
hardware, including the CM5, and to support recently released addon
hardware (e.g. the new DSI touch-panel).
There are also packaging changes here to split the firmware blobs into
their own architecture independent package, which is to enable the
next version bump of the rpiboot package (which has now grown a
dependency on rpi-eeprom upstream). Without this packaging change, we
cannot bump rpiboot, which in turn means Ubuntu users will be unable
to flash the CM5 (or possibly future variants of the CM4).
[ Test Plan ]
The majority of the changes are to the closed-source boot firmware.
This is only used on Pi models from the 4 onwards, but does include
the compute module variants. Due to the packaging changes (split of
rpi-eeprom-firmware) we must also test the upgrade route works for
existing users.
Hence, to cover the upgrade path and boot operation on all relevant
models, the following test plan is proposed for all proposed $series:
* Flash the Ubuntu Server for Raspberry Pi pre-installed image for the relevant series to $media
* Boot the card and wait for cloud-init to complete
* Login
* sudo apt update
* sudo apt install -t $series-proposed rpi-eeprom
* Ensure rpi-eeprom-firmware is automatically pulled in during update
* sudo rpi-eeprom-update
* This will report the current bootloader version installed on the board's EEPROM and the latest available
* If EEPROM is out of date: sudo rpi-eeprom-update -a
* If EEPROM is not out of date, force the update:
- For Pi/CM 5: sudo rpi-eeprom-update /lib/firmware/raspberrypi/bootloader-2712/default/pieeprom-2024-09-23.bin
- For Pi/CM 4: sudo rpi-eeprom-update /lib/firmware/raspberrypi/bootloader-2711/default/pieeprom-2024-04-15.bin
* sudo reboot
* Ensure subsequent boot completes successfully
Repeat this procedure (including freshly flashed image) for the
following models:
* Pi 4B 2GB/4GB/8GB
* CM4 (as many variants as we have available)
* Pi 5 2GB/4GB/8GB (2GB specifically to cover the D0 stepping case)
* CM5
Repeat this procedure for the following boot $media:
* SD card (where applicable)
* USB-attached SSD (all models)
* NVMe (Pi 5 only)
This may require adjustment of the BOOT_ORDER value stored in the
EEPROM configuration, via rpi-eeprom-config. Testers are strongly
advised to leave 0x1 somewhere in the modified boot order while
testing.
[ Risk Analysis ]
Bumping rpi-eeprom is always potentially risky, given it's flashed to
the board's EEPROM with all the attendant risks running the gamut all
the way up to "bricked boards". In mitigation, the version being
proposed has been used in RaspiOS for some months, and the test plan
attempts to cover all affected boards, all relevant boot media, and
includes coverage of the package upgrade.
[ Original Description ]
This is required to support LP: #2032178 (merge current rpiboot)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2085903/+subscriptions
More information about the foundations-bugs
mailing list