Okay, that's recent enough that it supports the A/B facility happily. The message is indeed there "constantly" until fresh assets are tested successfully, however I should stress that doesn't mean they're being tested at every boot. This discourse post [1] explains a bit more.
You mention you've tried "sudo piboot-try --reset-new" and rebooted. Did you happen to notice what happened during the second boot when it's testing the new boot assets? A kernel panic? Failure to mount the rootfs? Something else? If possible, the output of "journalctl -b -1" *might* be informative (but only if the failing boot got to the point of actually mounting the rootfs and writing to it -- in all the cases I've seen so far that's not been the case unfortunately). [1]: https://discourse.ubuntu.com/t/rpi-3b-not-accepting-latest- firmware-to-allow-kernel-to-boot/83848/8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2156570 Title: raspberry pi 4b boot issue with firmware 7 I believe, states piboot- try, New boot assets in /boot/firmware/new failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2156570/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
