-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FAT partition label: don't name it "boot" #669
Comments
It's somewhere deep in the filesystem abstractions of start*.elf. |
thanks 👍 |
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. 😉 |
martignoni
added a commit
to moodlebox/pi-gen-moodlebox
that referenced
this issue
Mar 31, 2023
* Fix apt gpg key install * export-image: change boot partition lable to 'bootfs' Fixes RPi-Distro#669 * Update release notes * Check that docker is not set up in rootless mode (RPi-Distro#679) Mounting binfmt_misc inside the container requires root rights. If "docker info" indicates rootless mode then fall back to "sudo docker". Allow the user to override the docker command with the DOCKER by setting the environment variable. * Ensure that deploy is always owned by user (RPi-Distro#680) Switch "docker cp" to tar streaming mode. As the receiving "tar" command is executed outside Docker the resulting directories & files are owned by the calling user. * DRY removal for docker run command line (RPi-Distro#686) Factor out the differences into variables so that there is only one implementation of the "docker run" command line to maintain. * Use tmpfs for chroot /run and /tmp --------- Co-authored-by: Serge Schneider <[email protected]> Co-authored-by: Stefan Becker <[email protected]>
wandering-andy
pushed a commit
to wandering-andy/pi-gen
that referenced
this issue
Oct 15, 2023
kayhannay
pushed a commit
to kayhannay/efalive_pi
that referenced
this issue
Feb 12, 2024
UmeshMohan-Dozee
pushed a commit
to DozeeRnD/pi-gen
that referenced
this issue
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a quite maddening side effect of default
boot
partition label together with a longstanding firmware bug uncovered by @pelwell :raspberrypi/firmware#1529 (comment)
That 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?The text was updated successfully, but these errors were encountered: