Apologies -- this one slipped under my radar. This isn't a valid error message: it's a side-effect of the shared u-boot script used for Classic and Core images.
The u-boot script for the pi (https://git.launchpad.net/ubuntu/+source /flash-kernel/tree/bootscript/all/bootscr.rpi) attempts to load a u-boot environment named "boot.sel". If it finds it, it knows it's operating on Ubuntu Core and needs to adjust kernel, initrd, etc. paths to the currently unpacked kernel snap (or to the newly unpacked one if it's "trying" a new kernel). If it can't load this file (incidentally causing "Failed to load '//uboot/ubuntu/boot.sel'" to appear on the console), it knows it's on Classic and proceeds assuming everything's under the root of the boot partition. Anyway, it can be safely ignored: it's not an error, but normal for the u-boot sequence on Classic up to Focal. From Groovy onwards, we're no longer using u-boot in the sequence so you won't see any of this output (unless you opt to use u-boot, which you still can for now). ** Changed in: u-boot (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914878 Title: At boot on Pi4 with 20.04.02 i get: Failed to load '//uboot/ubuntu/boot.sel' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1914878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
