[Bug 2130734] Re: Get this error after upgrade to 25:10: piboot-try: New boot assets in /boot/firmware/new failed

Petter Sjölander 2130734 at bugs.launchpad.net
Fri Nov 7 11:53:00 UTC 2025


Found the problem. I was an old EEPROM from 2022 that could not load
6.17

ubuntu at rpi43:~$ sudo apt-get install -y rpi-eeprom
sudo rpi-eeprom-update        # shows current vs latest
sudo rpi-eeprom-update -a     # apply if newer
sudo reboot
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
rpi-eeprom is already the newest version (27.5-0ubuntu2).
Solving dependencies... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
*** UPDATE AVAILABLE ***

Run "sudo rpi-eeprom-update -a" to install this update now.

To configure the bootloader update policy run "sudo raspi-config"

BOOTLOADER: update available
   CURRENT: Tue Jan 25 14:30:41 UTC 2022 (1643121041)
    LATEST: Tue Feb 11 17:00:13 UTC 2025 (1739293213)
   RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)
            Use raspi-config to change the release.

  VL805_FW: Dedicated VL805 EEPROM
     VL805: up to date
   CURRENT: 000138c0
    LATEST: 000138c0
*** PREPARING EEPROM UPDATES ***

BOOTLOADER: update available
   CURRENT: Tue Jan 25 14:30:41 UTC 2022 (1643121041)
    LATEST: Tue Feb 11 17:00:13 UTC 2025 (1739293213)
   RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)
            Use raspi-config to change the release.

  VL805_FW: Dedicated VL805 EEPROM
     VL805: up to date
   CURRENT: 000138c0
    LATEST: 000138c0
   CURRENT: Tue Jan 25 14:30:41 UTC 2022 (1643121041)
    UPDATE: Tue Feb 11 17:00:13 UTC 2025 (1739293213)
    BOOTFS: /boot/firmware
'/tmp/tmp.eOujmV0Wwe' -> '/boot/firmware/pieeprom.upd'
Copying recovery.bin to /boot/firmware for EEPROM update

EEPROM updates pending. Please reboot to apply the update.
To cancel a pending update run "sudo rpi-eeprom-update -r".


Welcome to Ubuntu 25.10 (GNU/Linux 6.14.0-1017-raspi aarch64)

 * Documentation:  https://docs.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/pro

 System information as of Fri Nov  7 12:46:29 CET 2025

  System load:           1.27
  Usage of /:            10.0% of 56.76GB
  Memory usage:          23%
  Swap usage:            0%
  Temperature:           65.7 C
  Processes:             195
  Users logged in:       0
  IPv4 address for eth0: 192.168.1.108
  IPv6 address for eth0: fd60:b734:2d2a:711:dea6:32ff:fe0a:b2b

 * Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
   just raised the bar for easy, resilient and secure K8s cluster deployment.

   https://ubuntu.com/engage/secure-kubernetes-at-the-edge

piboot-try:
New boot assets in /boot/firmware/new failed. Fallen back to known good
state. Use piboot-try --reset-new to re-test boot assets. If you are able
to determine the boot failure is due to a bug, please file an issue:
ubuntu-bug flash-kernel

0 updates can be applied immediately.


Last login: Fri Nov  7 12:37:58 2025 from 192.168.1.1

ubuntu at rpi43:~$ sudo piboot-try --reset-new
sudo reboot
Marked new boot assets unknown
Please be aware next reboot will boot twice
ubuntu at rpi43:~$ client_loop: send disconnect: Connection reset

PS C:\Users\vlc845> ssh ubuntu at sjolander.one -p 2223
Welcome to Ubuntu 25.10 (GNU/Linux 6.17.0-1004-raspi aarch64)

 * Documentation:  https://docs.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/pro

 System information as of Fri Nov  7 12:47:36 CET 2025

  System load:           2.19
  Usage of /:            10.0% of 56.76GB
  Memory usage:          21%
  Swap usage:            0%
  Temperature:           69.1 C
  Processes:             193
  Users logged in:       0
  IPv4 address for eth0: 192.168.1.108
  IPv6 address for eth0: fd60:b734:2d2a:711:dea6:32ff:fe0a:b2b

 * Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
   just raised the bar for easy, resilient and secure K8s cluster deployment.

   https://ubuntu.com/engage/secure-kubernetes-at-the-edge

0 updates can be applied immediately.


Last login: Fri Nov  7 12:46:31 2025 from 192.168.1.1

-- 
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/2130734

Title:
  Get this error after upgrade to 25:10: piboot-try: New boot assets in
  /boot/firmware/new failed

Status in flash-kernel package in Ubuntu:
  New

Bug description:
  Get this error after upgrade to 25:10: piboot-try: New boot assets in
  /boot/firmware/new failed

  ProblemType: Bug
  DistroRelease: Ubuntu 25.10
  Package: flash-kernel 3.109ubuntu6
  ProcVersionSignature: Ubuntu 6.14.0-1017.17-raspi 6.14.11
  Uname: Linux 6.14.0-1017-raspi aarch64
  ApportVersion: 2.33.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: config-disk (/dev/mmcblk0p1)
  Date: Wed Nov  5 17:03:02 2025
  ImageMediaBuild: 20241007.1
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=<set>
  SourcePackage: flash-kernel
  UpgradeStatus: Upgraded to questing on 2025-11-05 (0 days ago)

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




More information about the foundations-bugs mailing list