On 07.03.18 19:58, Matwey V. Kornilov wrote: > 2018-03-07 21:31 GMT+03:00 Alexander Graf <[email protected]>: >> >> >>> Am 07.03.2018 um 19:12 schrieb Matwey V. Kornilov >>> <[email protected]>: >>> >>> 07.03.2018 21:01, Matwey V. Kornilov пишет: >>>> >>>> Hello, >>>> >>>> I am trying to use >>>> openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-2018.03.07-Build2.1.raw to run >>>> Rock64. I use manually compiled u-boot >>>> 2018.01-rc2-02249-g19e31fac0d-dirty and see the following: >>>> >>>> => load mmc 1:1 0x02000000 efi/boot/bootaa64.efi >>>> reading efi/boot/bootaa64.efi >>>> MMC: block number 0x100008005 exceeds max(0x1dacc00) >>>> MMC: block number 0x100008005 exceeds max(0x1dacc00) >>>> Invalid FAT entry >>>> 6144 bytes read in 11 ms (544.9 KiB/s) >>>> >>>> This didn't happen when we used kiwi-7 to build JeOS at Factory. >>>> Can it be some issue with FAT16/FAT32? >>>> >>> >>> Not sure, that related, but >>> >>> EFI created by Kiwi-7 >>> >>> System ID "mkfs.fat" >>> Media byte 0xf8 (hard disk) >>> 512 bytes per logical sector >>> 4096 bytes per cluster >>> 1 reserved sector >>> First FAT starts at byte 512 (sector 1) >>> 2 FATs, 16 bit entries >>> 102400 bytes per FAT (= 200 sectors) >>> Root directory starts at byte 205312 (sector 401) >>> 512 root directory entries >>> Data area starts at byte 221696 (sector 433) >>> 51146 data clusters (209494016 bytes) >>> 63 sectors/track, 255 heads >>> 0 hidden sectors >>> 409604 sectors total >>> >>> EFI created by Kiwi-9 >>> >>> System ID "mkfs.fat" >>> Media byte 0xf8 (hard disk) >>> 512 bytes per logical sector >>> 2048 bytes per cluster >>> 1 reserved sector >>> First FAT starts at byte 512 (sector 1) >>> 2 FATs, 12 bit entries >>> 2048 bytes per FAT (= 4 sectors) >>> Root directory starts at byte 4608 (sector 9) >>> 512 root directory entries >>> Data area starts at byte 20992 (sector 41) >>> 1013 data clusters (2074624 bytes) >>> 32 sectors/track, 64 heads >>> 0 hidden sectors >>> 4096 sectors total >> >> We reduced the size of the efi partition to 2MB. Maybe that triggered a bug >> in U-Boot? >> >> Could you try to build an image with a 16mb partition instead? >> > > I've reparted drive manually and created 200mb EFI partition (FAT16). > It works well with u-boot. > It seems that u-boot doen't like FAT12.
Ok, I've changed the default EFI partition size to 16MB. I guess there's a better fix, but this way we should be quite compatible :). Alex -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
