Arndale cannot boot with OE rootfs

Bug #1208815 reported by Fathi Boudra
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Image Tools
Confirmed
Undecided
Unassigned

Bug Description

When we use OE, we don't have initrd/UUID and fallback to pass root=/dev/mmcblk0p3 to the kernel.
It's based on mmc_option value provided by the hardware configuration (mmc_id: '0:2').

At U-Boot stage, the value is correct and we load from mmc 0:2.
At the kernel stage, the value becomes incorrect because Arndale has eMMC and rootfs can be found on /dev/mmcblk1p3.

Since the boot commands are calculated based on the same mmc_id parameter, Arndale can't boot in this use case.

Fathi Boudra (fboudra)
Changed in linaro-image-tools:
status: New → Confirmed
Revision history for this message
Milo Casagrande (milo) wrote :

A workaround for this has been integrated in the Linaro Image Tools 2013.08 release.

Changed in linaro-image-tools:
milestone: none → 2013.08
milestone: 2013.08 → 2013.09
Fathi Boudra (fboudra)
Changed in linaro-image-tools:
milestone: 2013.09 → 2013.10
Fathi Boudra (fboudra)
Changed in linaro-image-tools:
milestone: 2013.10 → 2013.12
Milo Casagrande (milo)
Changed in linaro-image-tools:
milestone: 2013.12 → 2014.01
Milo Casagrande (milo)
Changed in linaro-image-tools:
milestone: 2014.01 → 2014.02
Fathi Boudra (fboudra)
Changed in linaro-image-tools:
milestone: 2014.02 → 2014.03
Fathi Boudra (fboudra)
Changed in linaro-image-tools:
milestone: 2014.03 → 2014.04
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.