bzImage not included in rootfs

bzImage not included in rootfs

[Chiz Chikwendu]

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

I am new to Openembedded (and yocto).

I have built an image with poky build environment.



I noticed that the kernel's bzImage is not included in the rootfs.

How do I get the system to include "bzImage" in the rootfs (boot/bzImage-)?



I've done some research, and I saw a note about setting the parameter:

RDEPENDS_kernel-base = "zImage"



This should override the kernel settings and build the kernel into the rootfs. I tried it, however it is not working for me.



Can anyone help?

Thanks,
Chiz

[-- Attachment #2: Type: text/html, Size: 3454 bytes --]

Re: bzImage not included in rootfs

[Scott Garman]

On 09/11/2014 05:08 AM, Chiz Chikwendu wrote:
> I am new to Openembedded (and yocto).
> 
> I have built an image with poky build environment.
> 
>  
> 
> I noticed that the kernel’s bzImage is not included in the rootfs.
> 
> How do I get the system to include “bzImage” in the rootfs (boot/bzImage-)?
> 
>  
> 
> I’ve done some research, and I saw a note about setting the parameter:
> 
> RDEPENDS_kernel-base = “zImage”
> 
>  
> 
> This should override the kernel settings and build the kernel into the
> rootfs. I tried it, however it is not working for me.

Hi Chiz,

Which MACHINE are you building for? This is probably something that is
set in the machine's BSP, since some hw platforms use bootloaders which
look for the kernel in a separate flash disk than the rootfs, so for
those devices there's no need to put the kernel in the rootfs.

If you're building one of the qemu machine targets, note that in
meta/conf/machine/include/qemu.inc there is:

# Don't include kernels in standard images
RDEPENDS_kernel-base = ""

Finally, where are you trying to set RDEPENDS_kernel-base in your
example above? I'm assuming in your local.conf file? I believe that
should be the place to do it so that it overrides the machine
configuration's definition.

Finally, make sure you've cleared the build cache for the image
generation by running bitbake -c cleanall <image-name> before trying to
generate it again.

Scott

Re: bzImage not included in rootfs

[Chiz Chikwendu]

Hi Scott,

Thanks for your help. 

I went another route. In my layer, I created an image.bb file. 
The .bb file tells yocto to include the kernel in the rootfs. I do this with the command:
IMAGE_INSTALL += kernel-image
IMAGE_INSTALL += kernel-module

This installs the kernel image and module in the rootfs. 
I can also try your suggested method. 

Chiz Chikwendu
Sr. Hardware Engineer
Tel: 781-356-9739


-----Original Message-----
From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Scott Garman
Sent: Thursday, September 11, 2014 1:58 PM
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] bzImage not included in rootfs

On 09/11/2014 05:08 AM, Chiz Chikwendu wrote:
> I am new to Openembedded (and yocto).
> 
> I have built an image with poky build environment.
> 
>  
> 
> I noticed that the kernel's bzImage is not included in the rootfs.
> 
> How do I get the system to include "bzImage" in the rootfs (boot/bzImage-)?
> 
>  
> 
> I've done some research, and I saw a note about setting the parameter:
> 
> RDEPENDS_kernel-base = "zImage"
> 
>  
> 
> This should override the kernel settings and build the kernel into the
> rootfs. I tried it, however it is not working for me.

Hi Chiz,

Which MACHINE are you building for? This is probably something that is
set in the machine's BSP, since some hw platforms use bootloaders which
look for the kernel in a separate flash disk than the rootfs, so for
those devices there's no need to put the kernel in the rootfs.

If you're building one of the qemu machine targets, note that in
meta/conf/machine/include/qemu.inc there is:

# Don't include kernels in standard images
RDEPENDS_kernel-base = ""

Finally, where are you trying to set RDEPENDS_kernel-base in your
example above? I'm assuming in your local.conf file? I believe that
should be the place to do it so that it overrides the machine
configuration's definition.

Finally, make sure you've cleared the build cache for the image
generation by running bitbake -c cleanall <image-name> before trying to
generate it again.

Scott

-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: bzImage not included in rootfs

[Darren Hart]

From:  Chiz Chikwendu <chiz.chikwendu@Haemonetics.com>
Date:  Thursday, September 11, 2014 at 5:08
To:  "Openembedded List (openembedded-core@lists.openembedded.org)"
<openembedded-core@lists.openembedded.org>
Cc:  Darren Hart <darren.hart@intel.com>
Subject:  bzImage not included in rootfs


>I am new to Openembedded (and yocto).

Hi Chiz,

For future reference, when sending email to public open source mailing
lists, it's a good idea to use plain text and avoid HTML. Some lists will
actually block all HTML email.

> 
>I have built an image with poky build environment.
> 
>I noticed that the kernel¹s bzImage is not included in the rootfs.
>
>How do I get the system to include ³bzImage² in the rootfs
>(boot/bzImage-)?
> 
>I¹ve done some research, and I saw a note about setting the parameter:
>RDEPENDS_kernel-base = ³zImage²
> 
>This should override the kernel settings and build the kernel into the
>rootfs. I tried it, however it is not working for me.
> 
>Can anyone help?

The kernel image is installed in /boot by the "kernel-image" package. Most
images do not include this by default as many targets boot with the kernel
located on a separate system partition.

See the documentation for how to add new packages to existing image
recipes using variables like:

CORE_IMAGE_EXTRA_INSTALL += "kernel-image"

http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html#usingpoky
-extend-customimage-localconf

--
Darren Hart
Intel Open Source Technology Center