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
Hi,
I still observe this bug with the 20101005 pre-installed image for OMAP4 on the
Blaze board.
I did specify root=/dev/mmcblk1p2 at the first boot, but it took the label of
/dev/mmcblk0p2 (eMMC) instead.
Did the bug really get fixed, or hasn't the fix made its way to the
released images yet?
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
Many thanks!
I won't be available to test it before Tuesday though. If anyone gets a
chance to do it before, be my guest!
Thanks again for this fix!
Michael.
--
SD card pre-installed image issue on OMAP4 Blaze board
https://bugs.launchpad.net/bugs/652143
You received this bug notification
** Tags added: armel
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Also affects: jasper-initramfs (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: jasper-initramfs (Ubuntu Maverick)
Assignee: (unassigned) = Oliver Grawert (ogra)
** Changed in: jasper-initramfs (Ubuntu Maverick)
Milestone: None = ubuntu-10.10
** Changed
