[yocto] Booting .hddimg from USB failed -> ramdisk not found /dev/ram0 - HELP!

nick xerofoify at gmail.com
Thu Jan 8 09:50:09 PST 2015


Simon,
Why are you not linking your kernels to the core-image-sato build.
This seems to be the issue.
Regards Nick

On 2015-01-08 05:59 AM, Simon Bolek wrote:
> Thank you Nick. I will try that, but this is not the point. I am trying to
> figure out why
> *bitbake core-image-sato *
> does not create /dev/ram nodes, although linux-yocto has them defiined in
> .config file.
> 
> I also created:
> mylayer/recipes-kernel/linux/linux_yocto_3.4.bbapend
> mylayer/recipes-kernel/linux/linux_yocto_3.10.bbapend
> mylayer/recipes-kernel/linux/linux_yocto_3.14.bbapend
> 
> with the following content:
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> SRC_URI += "file://ramdisk.cfg"
> 
> and
> mylayer/recipes-kernel/linux/files/ramdisk.cfg
> 
> with content:
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_COUNT=16
> CONFIG_BLK_DEV_RAM_SIZE=4096
> 
> and afterwards run the commands:
> bitbake linux-yocto -c cleansstate
> bitbake linux-yocto
> bitbake core-image-sato
> 
> again. Same result, no /dev/ram nodes under rootfs.
> 
> What am i doing wrong?
> 
> thank you
> simon:-)
> 
> On Thu, Jan 8, 2015 at 2:03 AM, nick <xerofoify at gmail.com> wrote:
> 
>> Simon,
>> Can you boot this on standard computer with qemu.
>> Try that first and report back if that works.
>> Nick
>>
>> On 2015-01-07 04:59 PM, Simon Bolek wrote:
>>> Hello folks!
>>>
>>> I have the following problem/question.
>>> 1) I built a standard .hddimg core-image-sato genericx86 on ubuntu 14.10
>>> 2) Afterwards, this .hddimg was deployed to USB device (USB-ZIP method)
>>> 3) Tried to boot Atom PC from the USB Device -> *ERROR: cound not found
>>> ramdisk*
>>>
>>> so initrd is trying to find /dev/ram0 which does not exist in the image.
>> I
>>> checked rootfs and there is nothing under
>>>
>> ../poky/build/tmp/work/genericx86-poky-linux/core-image-sato/1.0-r0/rootfs/dev
>>>
>>> I googled this up and there is a thread telling to check the .config file
>>> for *CONFIG_BLK_DEV_RAM *settings*.*
>>> I have the following entries in:
>>>
>> ../poky/build/tmp/work/genericx86-poky-linux/linux-yocto/3.10.35+gitAUTOINC+7df9ef8ee4_2ee37bfe73-r0/linux-genericx86-standard-build/.config
>>> ...
>>> CONFIG_BLK_DEV_RAM=y
>>> CONFIG_BLK_DEV_RAM_COUNT=16
>>> CONFIG_BLK_DEV_RAM_SIZE=4096
>>> ...
>>>
>>> I also *bitbake core-image-sato -c cleansstate* twice already.
>>> I also* bitbake core-image-sato -c menuconfig *once more and
>>> afterwards *bitbake
>>> linux-yocto* again.
>>> I also tried IRC channels, but no answer so far...
>>>
>>> Can anyone help me? How can i force bitbake to create /dev/ram0 under
>>> rootfs?
>>> Or maybe there is another trick to boot the image from USB?
>>>
>>> best regards
>>> simon:-)
>>>
>>> Viele Grüsse
>>> Simon Bolek
>>>
>>> mit freundlichem Gruss / best regards / pozdrawiam / atentamente
>>> Simon P. Bolek
>>> ------------------------------------------------------
>>> Dipl. Inf. Simon P. Bolek
>>> SAP Consultant
>>> Business Mobile and IVI Solutions
>>> mailto: simon.bolek at arcom-ivi.de
>>> http://www.arcom-ivi.de/
>>> XING: https://www.xing.com/profile/SimonP_Bolek
>>>
>>>
>>>
>>
> 



More information about the yocto mailing list