Hi all,
Pascal Hambourg <pas...@plouf.fr.eu.org> wrote (Sat, 19 Oct 2024 20:37:14
+0200):
> Hi Diederik,
>
> First, thank you for the detailed test report !
>
> On 19/10/2024 at 16:54, Diederik de Haas wrote:
> > 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.
>
> > I'll (later) do another install attempt to verify whether it actually
> > should NOT have created a boot partition or that I just mis-remembered.
>
> All existing arm* recipes always created a separated ext2 /boot
> partition, so I kept it in the new arm64 recipes. If this is not needed,
> the arm64 recipes can be changed so that they create a separate /boot
> partition only when partitioning with LVM, just like recipes for other
> architectures.
Sorry guys, I cannot follow you here.
This Rockchip system uses the legacy msdos partition table, right? (No UEFI,
thus no GPT).
With this partition table it should be possible and is confirmed to be
working, to set the bootable flag for a partition AFAIK (like an ext2 /boot
partition).
So, what's the problem here? What went wrong?
It should have worked, I think...
Holger
--
Holger Wansing <hwans...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
