tiomap-dev team mailing list archive

[Michael Opdenacker <michael@xxxxxxxxxxxxxxxxxx>]

The cause of the bug was found. Here are explanations written by Nicolas
Dechesne:

We discussed with canonical team on IRC, and we found the reason why pre
installed images don't work on blaze...

CONFIG_INIT_PASS_ALL_PARAMS is missing in our kernel config, as such the
root=<> arg is not set properly in initrd init program, and ogra was
relying on this parameter to detect mmcblk0 and mmcblk1.

So Michael, what that means is that when you tested this you ended up
installing uImage/uInitrd on the eMMC (mmcblk0) since this parameter was
ignored.

Since we found this too late, this won't make it in 10.10, sadly.

-- 
SD card pre-installed image issue on OMAP4 Blaze board
https://bugs.launchpad.net/bugs/652143
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.

Status in “jasper-initramfs” package in Ubuntu: Fix Released
Status in “jasper-initramfs” source package in Maverick: Fix Released

Bug description:
Hi,

I downloaded the 20100928 pre-installed Maverick image for OMAP4 to install it on my OMAP4430 Blaze board, and flashed it on an SD card.

I had to modify the MLO and u-boot.bin files in the FAT partition to support this board, but this was expected. I also replaced "root=/dev/mmcblk0p2" by "root=/dev/mmcblk1p2" to boot on the SD card (/dev/mmcblk0 corresponds to the eMMC on the Blaze board).

The board booted, and your scripts resized the second SD card partition to fill the whole available space. Then the system rebooted.

I checked the updated boot.scr script and the bootargs contained:
root=LABEL=emmcroot

emmcroot is the label of the ext3 filesystem on /dev/mmcblk0p2 (the eMMC already had its own partitions and filesystems).

This is wrong because I wanted to install Maverick on the SD card. It seems that your scripts took the label of /dev/mmcblk0p2 as it would have done on the Panda board. Could it instead take the label from the filesystem on the partition specified at the initial boot (root=/dev/mmcblk1p2 in my case)?

Any other ideas?

Thank you in advance,

Cheers,

Michael.