I ran into a problem where the kernel needs to load a vfat module in order to read /boot
but the module is on /boot, so it goes to emergency mode. So you need to create a separate
vfat partition for MLO and u-boot.img and leave /boot as ext. Make the vfat partition p1
and turn on the bootable flag. (Or else recompile the kernel with vfat built in, not a
On Mar 1, 2015, at 2:30 AM, Sergio Durigan Junior
> On Sunday, March 01 2015, Scott M. Jones wrote:
> I would have thought the first .dtb you were using was the correct one
> for you.
Yeah, me too. That's why I wasn't even bothering trying the -ab one.
> I'm surprised the LABEL=_/ option doesn't work. Maybe run
> blkid and double check the UUID? Can you post the partition table? I
> only see p1 - p3.
I already double-checked (or triple-checked now :-) the UUID;
The partition table is:
Disk /dev/mmcblk0: 14.9 GiB, 16021192704 bytes, 31291392 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: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 1001471 999424 488M 6 FAT16
/dev/mmcblk0p2 1001472 1251327 249856 122M 83 Linux
/dev/mmcblk0p3 1251328 3985407 2734080 1.3G 83 Linux
Nothing really fancy. The first partition contains the u-boot + MLO +
the Linux kernel files. The other ones are exactly the last two
partitions in the original image.
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible