tiomap-dev team mailing list archive

[Launchpad Bug Tracker <652143@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package jasper-initramfs - 0.33

---------------
jasper-initramfs (0.33) maverick; urgency=low

  * make sure we use the VOLID from the actually specified root= kernel
    parameter in case a user modifies the initial boot.scr (LP: #652143)
 -- Oliver Grawert <ogra@xxxxxxxxxx>   Sat, 02 Oct 2010 02:08:13 +0200

** Changed in: jasper-initramfs (Ubuntu Maverick)
       Status: Fix Committed => Fix Released

-- 
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.