[Bug 2137611] Re: pi refuses to use new firmware every boot
George Vatsis
2137611 at bugs.launchpad.net
Sat May 2 13:51:24 UTC 2026
rpi-eeprom-update seemed to be the trick; unfortunately, I lost my terminal
output, but it did fix my issue and let me boot to an updated kernel.
On Fri, May 1, 2026 at 11:40 AM Dave Jones <2137611 at bugs.launchpad.net>
wrote:
> I suspect, given this is a Pi 4, that this is another duplicate of LP:
> #2130734 -- the base EEPROM requirement is now added as a quirk in
> ubuntu-release-upgrader, and documented in both release notes and the
> hw-support docs. If that's the case, please let me know and I can mark
> this as a duplicate.
>
> Otherwise, if this is still an issue, please try running "rpi-eeprom-
> update" and attaching the output here so we can verify this is something
> else.
>
> ** Changed in: flash-kernel (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2137611
>
> Title:
> pi refuses to use new firmware every boot
>
> Status in flash-kernel package in Ubuntu:
> Incomplete
>
> Bug description:
> Every boot no matter what I try I get
>
> 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
>
>
> this is on Raspberry Pi 4 Model B Rev 1.2 on Ubuntu 25.10 aarch64
>
> ProblemType: Bug
> DistroRelease: Ubuntu 25.10
> Package: flash-kernel 3.109ubuntu6.1
> ProcVersionSignature: Ubuntu 6.17.0-1003.3-raspi 6.17.0-rc7
> Uname: Linux 6.17.0-1003-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: Tue Jan 6 22:18:32 2026
> ImageMediaBuild: 20251007.1
> ProcEnviron:
> LANG=C.UTF-8
> PATH=(custom, no user)
> SHELL=/bin/bash
> TERM=xterm-256color
> XDG_RUNTIME_DIR=<set>
> SourcePackage: flash-kernel
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2137611/+subscriptions
>
>
--
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/2137611
Title:
pi refuses to use new firmware every boot
Status in flash-kernel package in Ubuntu:
Incomplete
Bug description:
Every boot no matter what I try I get
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
this is on Raspberry Pi 4 Model B Rev 1.2 on Ubuntu 25.10 aarch64
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: flash-kernel 3.109ubuntu6.1
ProcVersionSignature: Ubuntu 6.17.0-1003.3-raspi 6.17.0-rc7
Uname: Linux 6.17.0-1003-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: Tue Jan 6 22:18:32 2026
ImageMediaBuild: 20251007.1
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: flash-kernel
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2137611/+subscriptions
More information about the foundations-bugs
mailing list