[Bug 2085903] Re: [SRU] Please merge rpi-eeprom 26

Wed May 7 18:10:49 UTC 2025

This bug was fixed in the package rpi-eeprom - 26.3-0ubuntu0.24.10.2

---------------
rpi-eeprom (26.3-0ubuntu0.24.10.2) oracular; urgency=medium

  * Include Breaks/Replaces on rpi-eeprom-firwmare to ensure partial upgrades
    from earlier version can succeed (LP: #2095175)

rpi-eeprom (26.3-0ubuntu0.24.10.1) oracular; 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

rpi-eeprom (26.3-1) bookworm; urgency=medium

  [ Tim Gover ]
  * 2024-11-07: recovery.bin - Update default release to latest version (default)

rpi-eeprom (26.2-1) bookworm; urgency=medium

  [ Tim Gover ]
  * firmware: 2712: Archive old releases
  * firmware: 2711: Archive firmware older than the last automatic update (2023-01-11)
  * pieeprom-2024-11-05: 2712: NUMA - Add system_heap.max_order=0 when needed (latest)

  [ Andrew Scheller ]
  * Fix release-notes typo

rpi-eeprom (26.1-1) bookworm; urgency=medium

  [ Harry Horsperg ]
  * Update release-notes.md

  [ Andrew Scheller ]
  * Add missing 'sudo' to rpi-eeprom-config's help-text

  [ Tim Gover ]
  * 2024-10-10: 2712: Add support to override the boot-mode at power on (latest)
  * 2024-10-10: 2711: Use soft-reset to preseve SDRAM contents after ramoops (latest)
  * release-notes: Additional updates for the 2024-10-10 release
  * image: Add release-fw helper script
  * pieeprom- 2024-10-21: 2712: 2711: Fix PCIe BAR issue for some switches  (latest)

rpi-eeprom (26.0-1) bookworm; urgency=medium

  [ Tim Gover ]
  * imager: 2712: Move to the 2024-09-10 release
  * pieeprom-2024-09-23: 2712: SDRAM performance tuning (latest)
  * 2024-09-24: 2712: Promote 2024-09-23 release (default) (automatic update)

rpi-eeprom (25.2-1) bookworm; urgency=medium

  [ Tim Gover ]
  * rpi-eeprom-config: Increase the timeout for flashrom shell-cmd

rpi-eeprom (25.1-1) bookworm; urgency=medium

  [ andrum993 ]
  * 2712 release-notes.md: fix typo

  [ Tim Gover ]
  * pieeprom-2024-09-10: 2712: Fix filename

rpi-eeprom (25.0-1) bookworm; urgency=medium

  [ Tim Gover ]
  * image: Update 2712 release to 2024-07-30
  * pieeprom-2024-09-05: 2712: 2711: Fix self-update if EEPROM is write-protected (latest)
  * 2024-09-10: 2712: Fix lockup on 7" DSI panel clones (latest)
  * pieeprom-2024-10-09: 2712: Promote to default release (automatic update)

  [ andrum993 ]
  * Update release-notes.md

  [ Nicolai Buchwitz ]
  * Fix docs link to CM4 bootloader

  [ Serge Schneider ]
  * Update package description to include Pi 5
  * d/c: Remove libraspberrypi-bin from Depends

 -- Dave Jones <dave.jones at canonical.com>  Fri, 17 Jan 2025 14:36:32
+0000

** Changed in: rpi-eeprom (Ubuntu Oracular)
       Status: Fix Committed => 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:
  Fix Released
Status in rpi-eeprom source package in Oracular:
  Fix Released

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.

  WARNING:
  This test plan should only be carried out by those comfortable recovering from flashing a bad rom. The purpose of this test plan is to uncover boot issues. If you are uncomfortable following the bootloader recovery process [1], please do not attempt the test plan.

  [1]: https://www.raspberrypi.com/documentation/computers/raspberry-
  pi.html#eeprom-boot-flow

  NOTE:
  The test plan may require adjustment of the BOOT_ORDER value stored in the EEPROM configuration, via rpi-eeprom-config. Testers are strongly advised to leave 0x1 (SD card) somewhere in the modified boot order while testing, to allow for easier recovery in the event of issues.

  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)

  [ 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