On Sun Oct 20, 2024 at 12:34 AM CEST, Pascal Hambourg wrote: > On 19/10/2024 at 23:58, Holger Wansing wrote: > > > > 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). > > In Diederik's report the partition table is GPT, not MSDOS. Indeed the > default disk label (partition table) for the arm64 architecture is GPT, > regardless of whether the sub-architecture is EFI or not (see > <https://salsa.debian.org/installer-team/partman-partitioning/-/blob/master/lib/disk-label.sh>).
Correct, I always use GPT partitioning. AFAIUI, UEFI requires GPT, but GPT does not require UEFI. And as it happens to be the case, I have one device which actually does use UEFI (I think; and GRUB) and another one which doesn't. This was likely the result of some experiment just to see what would happen. I do not recall any details about what or why I did (it). The 'cs21' device is a (different) Rock64 (rk3328): ``` diederik@cs21:~$ ls -lh /boot/ total 242M ... -rw-r--r-- 1 root root 285K sep 30 21:08 config-6.1.0-26-arm64 drwxr-xr-x 4 root root 16K jan 1 1970 efi drwxr-xr-x 2 root root 4,0K okt 9 18:02 extlinux drwxr-xr-x 5 root root 4,0K okt 9 18:03 grub -rw-r--r-- 1 root root 30M okt 9 18:02 initrd.img-6.1.0-26-arm64 -rw-r--r-- 1 root root 83 sep 30 21:08 System.map-6.1.0-26-arm64 -rw-r--r-- 1 root root 32M sep 30 21:08 vmlinuz-6.1.0-26-arm64 ``` I have 4 kernels installed, but listing them all isn't useful. And now the partition stuff: ``` root@cs21:~# parted -s /dev/mmcblk1 print Model: MMC NCard (sd/mmc) Disk /dev/mmcblk1: 61.9GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 32.8kB 16.8MB 16.7MB primary 2 16.8MB 256MB 239MB fat16 primary boot, esp 3 256MB 61.9GB 61.6GB ext4 primary root@cs21:~# lsblk -o +PARTFLAGS,FSTYPE /dev/mmcblk1 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS PARTFLAGS FSTYPE mmcblk1 179:0 0 57.6G 0 disk ├─mmcblk1p1 179:1 0 16M 0 part ├─mmcblk1p2 179:2 0 228M 0 part /boot/efi vfat └─mmcblk1p3 179:3 0 57.4G 0 part / ext4 ``` And 'quartz64a' is a Pine64 Quartz64 Model A (rk3566): ``` root@quartz64a:~# parted -s /dev/mmcblk1 print Model: MMC A3A562 (sd/mmc) Disk /dev/mmcblk1: 124GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 32.8kB 3670kB 3637kB loader1_part 2 8389kB 12.6MB 4194kB loader2_part 3 12.6MB 16.8MB 4194kB trust_part 4 16.8MB 134MB 117MB efi_part 5 134MB 124GB 124GB ext4 root_part legacy_boot root@quartz64a:~# lsblk -o +PARTFLAGS,FSTYPE /dev/mmcblk1 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS PARTFLAGS FSTYPE mmcblk1 179:0 0 115.2G 0 disk ├─mmcblk1p1 179:1 0 3.5M 0 part ├─mmcblk1p2 179:2 0 4M 0 part ├─mmcblk1p3 179:3 0 4M 0 part ├─mmcblk1p4 179:4 0 112M 0 part └─mmcblk1p5 179:5 0 115.1G 0 part / 0x4 ext4 ``` FTR: I cannot think of any reason why the device type would matter. And the Quartz64-A has those other partitions, but doesn't use them. Just some other experiment with the 'official' Rockchip partition layout. And I just changed the 'legacy_boot' flag to 'boot' on the SDcard with which I did my test, which then (apparently) also triggers the 'esp' flag and it booted with that too. So it looks like it just needs some indication (flag) of what the boot device is, but it doesn't (seem to) matter which one. Cheers, Diederik
signature.asc
Description: PGP signature
