tiomap-dev team mailing list archive

[Launchpad Bug Tracker <652143@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug by Michael Opdenacker (michael-opdenacker):

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.

** Affects: jasper-initramfs (Ubuntu)
     Importance: Undecided
         Status: New

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