Closed macmpi closed 1 year ago
@pelwell, @timg236, is this a bootrom issue on older pis, or can it be fixed in bootcode.bin or start.elf files?
It's somewhere deep in the filesystem abstractions of start*.elf.
thanks :+1:
Thanks for reporting the issue
Hopefully firmware will get a permanent fix at some point, but at least one main source of catch-22 should be gone with next release. :wink:
There is a quite maddening side effect of default
boot
partition label together with a longstanding firmware bug uncovered by @pelwell : https://github.com/raspberrypi/firmware/issues/1529#issuecomment-774102402That partition naming prevents use of
boot
directory name inside it, for anything essential to boot the system from FAT partition... Not a major problem for PiOS but has adverse consequence for other distribution that may be installed after.Agreed, root of problem is in firmware side, but as this does not seem to get resolved, here is a typical consequential use-case if default Pi OS image use that
boot
label.rpi-imager
or manually), and runs fine on his device: all good.boot
directory inside FAT partition.All this because first-off media generation had that colliding
boot
label... definitely not an obvious guess!Would it be possible to consider another non-colliding label name for that default FAT partition (
FATboot
or something), until that firmware bug is eventually fixed?