Semi-pilot error. I should be using the -VFAT images, which I just figured out after two hours spent trying to fix the other one. This is not documented on the wiki obviously and is a post-beta change, so it will urgently require attention as anyone following the instructions from beta will fall into the same trap (and not know how to fix it). I've pulled down the VFAT images onto a fast remote box and confirmed with kpartx that they look better. Since it's go-no-go I will stay up now and do some testing once they come down on ES. Assume that the below is not a problem because the images do contain boot.scr and partitioning looks more reasonable in the VFAT ones. Jon. On 06/28/2013 02:48 AM, Jon Masters wrote: > Hey folks, > > A few issues with the RC2 image running on PandaBoard (ES): > > 1). It doesn't boot at all. This is because the image contains a weird > partition layout, not aligned, etc. MLO never has a chance. The SD Card > had this as the first partition: > > /dev/sdb1 1953 1001953 500000+ 83 Linux > > Which I fixed to look as it should: > > /dev/sdb1 * 2048 411647 204800 6 FAT16 > > At which point the MLO actually loads, as does u-boot.img, etc. > > 2). Unless I am missing something, there is nothing within boot/boot.scr > on the root ext4 filesystem for ext4load to pull in, but that could be > pilot error. So let me know about that one. > > If it's just the first item, then there's no need to make an RC4 because > the instructions (that have to be run anyway) can include making a > correctly aligned filesystem with the correct constraints on size, > filesystem type, etc. required for MLO. I did note this on IRC yesterday > that MLO is finnicky and I did have a reason (as you see). > > Jon. > _______________________________________________ > arm mailing list > arm@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/arm > _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
