On 19/10/2024 at 20:37, Pascal Hambourg wrote :
On 19/10/2024 at 16:54, Diederik de Haas wrote:
I already had a hunch why that may be and that's when I examined the
SDcard with `lsblk` and later with `fdisk`. Went into `fdisk`'s expert
menu and enabled the boot flag on partition 2 (`/boot`).
Plugged the SDcard into my Rock64 again and booted up and then it
succeeded \o/
IOW: It was so, so close from working ... but it needs the 'boot' flag.
Do you mean the "legacy BIOS bootable flag" (legacy_boot in parted) ?
Unfortunately partman does not manage it. IIRC the "$bootable{ }" flag
in recipes is translated into parted "boot" flag, but on GPT the "boot"
flag means the same as "esp" (this is a huge mess) and partman clears
them if the partition method is not "efi". It should not be hard to
write a patch to translate the "$bootable{ }" flag into the
"legacy_boot" flag instead of the "boot" flag on GPT.
Patch translating '$bootable{ }' in recipes into the 'legacy_boot' flag
on GPT:
<https://salsa.debian.org/pham/partman-auto/-/commit/f196cb9981fb0e27f43bb9a2b14a4550e53027f7>
("Add support for legacy_boot flag on GPT")
If this is merged, I should probably add support for 'legacy_boot' to
partman-base (for display) and partman-partitioning (for manual toggle) too.
Q: Is the 'legacy_boot' flag also needed on arm64/efi platforms ?
