Uboot fails to find / after latest kernel update

after installing the updates from this night, uboot fails to boot.
The last lines on the screen are:
…is now current device
Scanning nvme 0:4…
Failed to load ‘/’
Booting: nvme 0:4

Any idea, hint? Hardware is a MBP 16.

TIA, Matze

Those messages are normal. It rather looks like your kernel isn’t booting. There was an upstream kernel regression which might be affecting you. Try pressing Esc when those messages show to get into the GRUB menu, select the older kernel, and see if that works. If it does, you can use grubby to configure that as the default boot kernel until the next update drops which should hopefully fix the issue.

Ahh, ok, that seems to be indeed the issue … I used the solution from the grub bug 4 weeks ago to get into the system again. I then tried to install/switch to the 16k kernel and was wondering why there was no kernel found. I will wait patiently for the next update :wink:
Thanks for the info.

With the most recent kernel the default is now actually 4K, which has limitations like no full USB support. So that explains why it didn’t work for you. Once the new kernel build succeeds in 3 hours or so, you should be able to install 16K.

btw is there already a bug on file to get rid of the confusing and unhelpful “Failed to load '/’” message?

If not, could someone file it please? The message has confused people before (example 1, example 2) and this was said a month ago: “This is normal, the “failed to load /” that you’re seeing there is just a spurious message that happens on every system. It is confusing though, and something we should eventually fix.”

Help fixing u-boot issues is always appreciate :slight_smile:

@macknife The new kernel should be live now, hopefully that works well for you now!

If I remember correctly that messages comes from Fedora patches to the standard distro boot scripts. I did the bare minimum to prevent that from booting from the first ESP which breaks multiple alternative OS installs on apple silicon.
I don’t have a good idea how to handle this. On easy approach might be to ensure the new std boot works on apple silicon and just switch to that.
The fedora-asahi-remix u-boot spec files and patches are in Overview - fedora-asahi/uboot-tools - Pagure.io