Open anonymouscowhead opened 3 months ago
u-boot-with-spl-lpi4a-main.bin the file is provided for 6.6 kernel.
u-boot-with-spl-lpi4a.bin the file is provided for 5.10 kernel.
Thanks, I did not know that. Re-tested using u-boot-with-spl-lpi4a.bin and found the same issue was introduced in a different release: 20240127 is fine, but 20240131 has the same issue with: [ 3.563934] mmcblk0: p1 p2 p3 p4 .... The physical size of the device is 1048576 blocks
Thanks, I did not know that. Re-tested using u-boot-with-spl-lpi4a.bin and found the same issue was introduced in a different release: 20240127 is fine, but 20240131 has the same issue with: [ 3.563934] mmcblk0: p1 p2 p3 p4 .... The physical size of the device is 1048576 blocks
This seems to be the expected behavior. You can run resize2fs in linux.
After upgrading from revyos u-boot 20240324 to 20240328 (u-boot-with-spl-lpi4a-main.bin) on lpi4a with stock 5.10 kernel: /dev/mmcblk0p3: The filesystem size (according to the superblock) is 7505403 blocks The physical size of the device is 1048576 blocks
Also noticed the kernel shows 4 partitions instead of 3, although only the details for 3 of them: [ 3.482832] mmcblk0boot0: mmc0:0001 Y2P032 partition 1 4.00 MiB [ 3.493513] mmcblk0boot1: mmc0:0001 Y2P032 partition 2 4.00 MiB [ 3.506909] mmcblk0rpmb: mmc0:0001 Y2P032 partition 3 16.0 MiB, chardev (246:0) [ 3.522668] mmcblk0: p1 p2 p3 p4
20240529 release has the same issue. Downgrading back to 20240324 resolves. Based on dmesg output on 20240324, the superblock is correct at 7505403 and the physical size 1048576 is incorrect.