[Bug 2127780] Re: [SRU] [Ubuntu 25.10 Questing] Errors shown in every text session when piboot is not enabled

[Julian Andres Klode]

Hello fprietog, or anyone else affected,

Accepted flash-kernel into questing-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.109ubuntu6.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-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. 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.

** Changed in: flash-kernel (Ubuntu Questing)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-questing

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

Title:
  [SRU] [Ubuntu 25.10 Questing] Errors shown in every text session when
  piboot is not enabled

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Questing:
  Fix Committed

Bug description:
  [ Impact ]

  Users who have opted out of the A/B boot mechanism (by overriding
  flash-kernel's method to Pi) are presented with an incorrect warning
  on every login via the motd service.

  [ Test Plan ]

  For all supported models of Raspberry Pi:

  1. Flash questing (25.10) to a spare SD card

  2. Boot and run through first login

  3. Follow the instructions under
  https://waldorf.waveform.org.uk/2025/pull-yourself-up-by-your-
  bootstraps.html#tough-as-old-boots to switch back to the "pi" method
  in flash-kernel

  4. Reboot and login; observe the (erroneous) warning

  5. Enable the -proposed pocket

  6. sudo apt install -t questing-proposed flash-kernel{,-piboot}

  7. Logout and login

  8. Observe the warning no longer appears

  9. sudo flash-kernel

  10. sudo reboot

  11. Ensure reboot operates correctly

  12. Undo the "method:" override; sudo rm /etc/flash-kernel/db; sudo
  touch /etc/flash-kernel/db

  13. sudo flash-kernel

  14. sudo reboot

  [ Regression potential ]

  Messing with flash-kernel always brings the possibility of breaking
  the boot sequence. In this case the only changes to the code are in
  the piboot portion, so it is safe to restrict testing to those boards
  that use this (i.e. Raspberry Pis).

  However, testing should be done on at least three different
  generations of Pi (specifically 3, 4, and 5 which have differing
  portions of their boot in or out of EEPROM) to ensure that boot still
  operates successfully after.

  The test plan specifically includes a portion running flash-kernel and
  reboot with the proposed version in both configurations (pi and pi-
  try) to ensure things still operate correctly (not just the warning
  message).

  [ Original Description ]

  Ubuntu 25.10 Questing for Raspberry Pi. These errors are shown in
  every text session when piboot is not enabled:

  cat: /boot/firmware/current/state: No such file or directory (os error 2)
  piboot is in an invalid or unexpected state:
  Please file an issue: ubuntu-bug flash-kernel
  run-parts: /etc/update-motd.d/90-piboot-try exited with return code 2

  "/etc/update-motd.d/90-piboot-try" runs the command "/usr/sbin/piboot-
  try --status" that don't have in account the possibility of having
  piboot disabled so as file "/boot/firmware/current/state" just doesn't
  exists it's mistaken with a piboot invalid/unexpected state.

  I suggest a change in command piboot-try or in "/etc/update-
  motd.d/90-piboot-try" to first test if piboot is enabled to continue
  checking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2127780/+subscriptions