[Bug 2121612] [NEW] A/B boot fails with out-of-order partition table

[Dave Jones]

Public bug reported:

While looking at updated firmwares for LP: #2121560 I noticed one fix in
the boot firmware and wondered if it affected our A/B boot setup, which
relies on tryboot_a_b. Turns out it does: if the partition table is
"out-of-order" (i.e. partition 1 is not listed first in the partition
table), we fail to boot. This isn't the standard layout on our images,
but it is conceivable that custom setups may encounter it. While we're
bumping the firmware package for the wifi fix, we should include this
fix too.

However, bumping boot firmware is always risky: we should test the new
firmware on all currently supported boards to ensure things still work.

** Affects: linux-firmware-raspi (Ubuntu)
     Importance: Medium
     Assignee: Dave Jones (waveform)
         Status: Confirmed

** Changed in: linux-firmware-raspi (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux-firmware-raspi (Ubuntu)
       Status: New => Confirmed

** Changed in: linux-firmware-raspi (Ubuntu)
     Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: linux-firmware-raspi (Ubuntu)
    Milestone: None => ubuntu-25.10

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to linux-firmware-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2121612

Title:
  A/B boot fails with out-of-order partition table

Status in linux-firmware-raspi package in Ubuntu:
  Confirmed

Bug description:
  While looking at updated firmwares for LP: #2121560 I noticed one fix
  in the boot firmware and wondered if it affected our A/B boot setup,
  which relies on tryboot_a_b. Turns out it does: if the partition table
  is "out-of-order" (i.e. partition 1 is not listed first in the
  partition table), we fail to boot. This isn't the standard layout on
  our images, but it is conceivable that custom setups may encounter it.
  While we're bumping the firmware package for the wifi fix, we should
  include this fix too.

  However, bumping boot firmware is always risky: we should test the new
  firmware on all currently supported boards to ensure things still
  work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/2121612/+subscriptions