missing kernel in rootfs image

missing kernel in rootfs image

[Joshua Immanuel]

[-- Attachment #1: Type: text/plain, Size: 675 bytes --]

Hello all,
	While trying to generate my custom rootfs image, I added the
linux_yocto_3.0.bbappend file to my custom layer and specified the
KMACHINE, SRCREV and COMPATIBLE_MACHINE variables. I find the generated
kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.

But, the rootfs image does not contain the kernel (in /boot directory).
My machine configuration file has the following kernel specific lines

        PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
        PREFERRED_VERSION_linux-yocto ?= "3.0%"
        
Am I missing something?

Regards
Joshua
-- 
Joshua Immanuel
HiPro IT Solutions Private Limited
http://hipro.co.in

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: missing kernel in rootfs image

[Joshua Immanuel]

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Tue, 2012-02-21 at 15:10 +0530, Joshua Immanuel wrote:
>         While trying to generate my custom rootfs image, I added the
> linux_yocto_3.0.bbappend file to my custom layer and specified the
> KMACHINE, SRCREV and COMPATIBLE_MACHINE variables. I find the
> generated
> kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.
> 
> But, the rootfs image does not contain the kernel (in /boot
> directory).
> My machine configuration file has the following kernel specific lines
> 
>         PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>         PREFERRED_VERSION_linux-yocto ?= "3.0%" 

Can someone explain the work flow behind the process of installing the
kernel into the rootfs image? My custom image has the IMAGE_INSTALL for
"task-core-boot". In turn, the task-core-boot recipe DEPENDS on
"virtual/kernel" this ensures that the kernel is staged. 

But, I am not sure which recipe/class is responsible for installing the
kernel in the final rootfs image. Should I explicitly add the
"linux-yocto" to RDEPENDS? 

Please guide me. 

Regards
Joshua
-- 
Joshua Immanuel
HiPro IT Solutions Private Limited
http://hipro.co.in

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: missing kernel in rootfs image

[Bruce Ashfield]

On 12-02-24 03:29 AM, Joshua Immanuel wrote:
> On Tue, 2012-02-21 at 15:10 +0530, Joshua Immanuel wrote:
>>          While trying to generate my custom rootfs image, I added the
>> linux_yocto_3.0.bbappend file to my custom layer and specified the
>> KMACHINE, SRCREV and COMPATIBLE_MACHINE variables. I find the
>> generated
>> kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.
>>
>> But, the rootfs image does not contain the kernel (in /boot
>> directory).
>> My machine configuration file has the following kernel specific lines
>>
>>          PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>>          PREFERRED_VERSION_linux-yocto ?= "3.0%"
>
> Can someone explain the work flow behind the process of installing the
> kernel into the rootfs image? My custom image has the IMAGE_INSTALL for
> "task-core-boot". In turn, the task-core-boot recipe DEPENDS on
> "virtual/kernel" this ensures that the kernel is staged.
>
> But, I am not sure which recipe/class is responsible for installing the
> kernel in the final rootfs image. Should I explicitly add the
> "linux-yocto" to RDEPENDS?

Are you past this issue yet ? I'm not sure, since you did have some
other email that looked to be past this .. or maybe they weren't.

Darren went through the process of documenting these variables and
was looking into some related issues. Darren: is this something that
you ran into ?

Cheers,

Bruce

>
> Please guide me.
>
> Regards
> Joshua
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: missing kernel in rootfs image

[Darren Hart]

On 02/24/2012 06:45 AM, Bruce Ashfield wrote:
> On 12-02-24 03:29 AM, Joshua Immanuel wrote:
>> On Tue, 2012-02-21 at 15:10 +0530, Joshua Immanuel wrote:
>>>          While trying to generate my custom rootfs image, I added the
>>> linux_yocto_3.0.bbappend file to my custom layer and specified the
>>> KMACHINE, SRCREV and COMPATIBLE_MACHINE variables. I find the
>>> generated
>>> kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.
>>>
>>> But, the rootfs image does not contain the kernel (in /boot
>>> directory).
>>> My machine configuration file has the following kernel specific lines
>>>
>>>          PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>>>          PREFERRED_VERSION_linux-yocto ?= "3.0%"
>>
>> Can someone explain the work flow behind the process of installing the
>> kernel into the rootfs image? My custom image has the IMAGE_INSTALL for
>> "task-core-boot". In turn, the task-core-boot recipe DEPENDS on
>> "virtual/kernel" this ensures that the kernel is staged.
>>
>> But, I am not sure which recipe/class is responsible for installing the
>> kernel in the final rootfs image. Should I explicitly add the
>> "linux-yocto" to RDEPENDS?
> 
> Are you past this issue yet ? I'm not sure, since you did have some
> other email that looked to be past this .. or maybe they weren't.
> 
> Darren went through the process of documenting these variables and
> was looking into some related issues. Darren: is this something that
> you ran into ?


What sort of image are you creating (live, ext3, cpio)? You want to look
at the do_install() for the linux-yocto recipe. The bits you're
interested in are in meta/classes/kernel.bbclass in the
kernel_do_install() function. I suggest instrumenting that and sorting
out where things are going wrong from there.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Re: missing kernel in rootfs image

[Joshua Immanuel]

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

On Fri, 2012-02-24 at 09:45 -0500, Bruce Ashfield wrote:
> > Can someone explain the work flow behind the process of installing
> > the kernel into the rootfs image? My custom image has the
> > IMAGE_INSTALL for "task-core-boot". In turn, the task-core-boot
> > recipe DEPENDS on "virtual/kernel" this ensures that the kernel is
> > staged.
> >
> > But, I am not sure which recipe/class is responsible for installing
> > the kernel in the final rootfs image. Should I explicitly add the
> > "linux-yocto" to RDEPENDS?
> 
> Are you past this issue yet ? I'm not sure, since you did have some
> other email that looked to be past this .. or maybe they weren't. 

I'm not sure how to put this. When I added the "linux-yocto" to
RDEPENDS_task* I was able to get the kernel image in the rootfs image
(ext3 image). But on the next compilation (i mean when I did $ bitbake
custom-image again) it complained dependency failed for task-*. So, I
ended up removing the line from RDEPENDS_task* but the final rootfs
image retained the kernel file in it.

I am in a confusion of which one to blame. I guess, the only way to
rebuild the tasks for custom-image is to remove tmp and sstate-cache
directories and build again.

        $ bitbake -c clean task-*
        $ bitbake -c clean custom-image    
        
The above commands doesn't completely re-build the tasks listed for
custom-image. So, I guess the problem still exists.

Regards
Joshua
-- 
Joshua Immanuel
HiPro IT Solutions Private Limited
http://hipro.co.in

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]