Hi Nick, attached is my kernel .bbappend and .cfg files of linux kernel recipe of my own layer. In original meta layer nothing was changed.
However, I spent last night trying to resolve the problem and found out that standard core-sato-image was missing meta/recipes-core/initrdscripts I added that to the local.conf file and also added grub to it. I wonder how 'install' was possible without those scripts, well, never mind. After building .hddimg again i was able to boot and install the image from USB device to atom-pc. Installation seemed to work without problems BUT after removing the usb device, boot FAILED: *not bootable device* - I was crying out loud, belive me!, gave up and went directly to bed... The same(built and generated at the same bitbake run) iso image is working in virtual box like a charm. There must be a difference/bug somewhere. Vbox is creating partitions on hda, atom-pc has sda. Should not be a problem, but still a difference. Could you help me on that? There are 3 Partitions on /dev/sda: /dev/sda1 - boot partition (no asterix in partition table visible, but no asterix on Vbox partition table as well) /dev/sda2 - rootfs /dev/sda3 - swap However, I will open another thread for this. thank you and best regards simon:-) On Fri, Jan 9, 2015 at 3:17 AM, nick <xerofo...@gmail.com> wrote: > Simon, > Please send me your kernel bb recipes as there is probably an issue in > them. > Regards, > Nick > > On 2015-01-08 03:58 PM, Simon Bolek wrote: > > NIck, thank you. what do you mean by that? I followed the instructions > from > > here: > > > http://www.yoctoproject.org/docs/1.7/kernel-dev/kernel-dev.html#changing-the-configuration > > is there something there I might be missing? Where is the part, 'linking > > your kernels to the core-image-sato build' that you are talking about? > > > > thank you and best regards > > simon:-) > > > > On Thu, Jan 8, 2015 at 6:50 PM, nick <xerofo...@gmail.com> wrote: > > > >> 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 <xerofo...@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.bo...@arcom-ivi.de > >>>>> http://www.arcom-ivi.de/ > >>>>> XING: https://www.xing.com/profile/SimonP_Bolek > >>>>> > >>>>> > >>>>> > >>>> > >>> > >> > > >
linux-yocto_3.4.bbappend
Description: Binary data
ramdisk.cfg
Description: Binary data
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto