Consolidating the various piboot-try "new assets failed" bugs under this
one, targetting to resolute, and marking other tasks invalid (I don't
think this was the earliest report, but it's the one I'm using
regardless).
For the sake of clarity, at this point the state of this is as follows:
1. If you're seeing the "new boot assets" failed on every login: that's
expected but does *not* indicate that the system is repeatedly testing
new boot assets. It's simply in the state where the newest boot assets
failed (for whatever reason) to boot, and the system has fallen back to
the known good assets.
2. So far we have confirmed reports of this from users on a 3B, 3B+,
Zero 2W, and a couple of 4B models. Haven't heard from any Pi 5 users
yet, but that's already plenty of boards affected.
3. I haven't received any useful journal output so far, so my guess is
that whatever happened during the unsuccessful boot, it didn't get to
the point where it could mount the root filesystem, so nothing useful
got written to the journal.
4. That means it's time for serial console output! I'm putting together
some comprehensive instructions, and hoping someone out there can use
them to get me some useful boot data because so far I've failed to
reproduce this locally (with all the aforementioned boards -- in other
words, mine all boot rev 1011 of the kernel happily).
** Changed in: ubuntu
Status: Confirmed => Invalid
** Also affects: flash-kernel (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: piboot-try (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: Ubuntu Resolute
Importance: Undecided
Status: New
** Changed in: Ubuntu Resolute
Status: New => Invalid
** Changed in: flash-kernel (Ubuntu Resolute)
Status: New => Invalid
** Changed in: piboot-try (Ubuntu Resolute)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: flash-kernel (Ubuntu)
Assignee: Dave Jones (waveform) => (unassigned)
** Changed in: piboot-try (Ubuntu Resolute)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2155094
Title:
RPi 3B, Zero 2W, 4B: New boot assets in /boot/firmware/new failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2155094/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
