Rock64 Debian 11 (Bullseye) install problem
(07-05-2022, 04:46 PM)t4_4t Wrote: Rockchip's 'u-boot' requires 16MB of free space at the top of the media for installation.
On the other hand, the 'partitioning-tools' included with 'debian-installer' does not take any of the above requirements into account.
As with a standard x86-PC, only 1MB of space is allocated at the top of the media.
Allocation of 'u-boot' space must be done intentionally by the user at the time of partitioning.
----
In short, unless you do something about it, you will end up with a partition allocation that has no space for the 'u-boot' installation.
If the 'u-boot' installation operation is performed on media configured as described above, the original data will of course be destroyed.
As an example, 'debian-installer' or 'Armbian' or 'Other-distribution' are all partitioned with the first 16MB of free space on the media.
We recommend that you compare this with the image you have created.
Thanks for the info. I used the (Debian Bulseye) debian-installer and apparently only 1MB precedes the /boot partition.
It seems to boot and run fine; what do you suggest?
My partition info:
Code:
# fdisk -l
Disk /dev/mmcblk1: 29.11 GiB, 31255953408 bytes, 61046784 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 296D4F2A-EF97-4DC6-B59D-80AFCF64E47A
Device Start End Sectors Size Type
/dev/mmcblk1p1 2048 999423 997376 487M Linux filesystem
/dev/mmcblk1p2 999424 59043839 58044416 27.7G Linux filesystem
/dev/mmcblk1p3 59043840 61044735 2000896 977M Linux swap(07-05-2022, 04:46 PM)t4_4t Wrote: Rockchip's 'u-boot' requires 16MB of free space at the top of the media for installation.
On the other hand, the 'partitioning-tools' included with 'debian-installer' does not take any of the above requirements into account.
As with a standard x86-PC, only 1MB of space is allocated at the top of the media.
Allocation of 'u-boot' space must be done intentionally by the user at the time of partitioning.
----
In short, unless you do something about it, you will end up with a partition allocation that has no space for the 'u-boot' installation.
If the 'u-boot' installation operation is performed on media configured as described above, the original data will of course be destroyed.
As an example, 'debian-installer' or 'Armbian' or 'Other-distribution' are all partitioned with the first 16MB of free space on the media.
We recommend that you compare this with the image you have created.
I went back and examined what u-boot-install-rockchip does on my Rock64. And it does indeed require at least the first 8,467,720 bytes.
So it looks like I'm starting over from scratch. Thanks for bringing this to my attention.
