[meta-freescale] Wandboard won't boot morty or morty-next

Fabio Berton fabio.berton at ossystems.com.br
Tue Apr 25 07:57:27 PDT 2017

This issue was fixed on master and morty branches. We're using wic tool 
to create images, so the final image will be suffix .wic.gz and not 
.sdcard.gz and has only one partition. So, you don't need to change 
extlinux/extlinux.conf file.

Fabio Berton

On 04/24/2017 09:34 PM, paul at conspiracy.net wrote:
> Thanks that will get me moving until I get a change to fix it or someone who has a clue how to do it correctly submits a patch.
> Paul
> On 4/24/2017 5:45 PM, Trevor Woerner wrote:
>> On Mon, Apr 24, 2017 at 5:45 PM, paul at conspiracy.net
>> <paulfax at conspiracy.net> wrote:
>>> Have a wanboard solo and built morty and morty-next (synced apr 24) core-image-minimal and the image tries to mount the root on partition 1.
>>> VFS: Mounted root (vfat filesystem) on device 179:1.
>>> From the change list it looks like that should be the only one partition on the SD but it still has the dos partition with the image and dtb's  and then the ext partition so it can't populate dev or find init.   Did not know if if this is a know
>>> issue, or that something in the migration that seems to have happened in October is not complete.
>>> Krogoth boots and runs fine.
>> I've been seeing the same issue on master as well. To fix, mount your
>> uSD card's first partition on your host machine. Edit the file
>> extlinux/extlinux.conf. The last line reads:
>>     APPEND root=PARTUUID=${uuid} rootwait rw console=${console}
>> Change it to:
>>     APPEND root=/dev/mmcblk2p2 rootwait rw console=${console}

More information about the meta-freescale mailing list