[yocto] This one can't be me...

[Bodke, Kishore K]

>-----Original Message-----
>From: yocto-bounces at yoctoproject.org [mailto:yocto-
>bounces at yoctoproject.org] On Behalf Of Paul D. DeRocco
>Sent: Wednesday, April 03, 2013 1:50 PM
>To: 'Darren Hart'
>Cc: yocto at yoctoproject.org
>Subject: Re: [yocto] This one can't be me...
>
>> From: Darren Hart [mailto:dvhart at linux.intel.com]
>>
>> Are you building with the rm work setting? Otherwise, that
>> should not be
>> empty unless you have more than one linux-yocto* directory
>> and the other is populated.
>
>That option is off, and there is no other linux-yocto* directory.
>
>> If not, verify rm work is not on and just build the kernel:
>>
>> $ bitbake linux-yocto -c cleansstate
>> $ bitbake linux-yocto
>
>The first line says there is no do_cleanstate task for linux-yocto, and so
>the second line finds nothing to do. Is there another way to force that?
>

It's surprising that you don't see anything under 
/home/pauld/yocto-atom/build/tmp/work/cedartrail_nopvr-poky-linux/linux-yoct
o-3.0.32+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+1e79e03d115ed177882
ab53909a4f3555e434833-r4.1/linux-cedartrail-nopvr-standard-build

It means that Kernel is not getting build for you?
How come you were able to generate the .hddimg and trying to boot?

Do you have the rootfs under build/tmp/work/Cedartrail*/core-image-sato/?

Thanks
Kishore.


>> Nothing in there suggests any other failure than it just didn't find a
>> block device. I didn't see anything in there about loading the initrd
>> though (I think there usually is...). Check to make sure the
>> initrd file does indeed exist on the boot drive.
>
>Yes, it does.
>
>--
>
>Ciao,               Paul D. DeRocco
>Paul                mailto:pderocco at ix.netcom.com
>
>_______________________________________________
>yocto mailing list
>yocto at yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto