All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <sgarman@zenlinux.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: bzImage not included in rootfs
Date: Thu, 11 Sep 2014 10:58:27 -0700	[thread overview]
Message-ID: <5411E2C3.3080807@zenlinux.com> (raw)
In-Reply-To: <A0F68394C677A9428EE03709453BAAEC7959C76C@BRS-Exch02.haemo.net>

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



  reply	other threads:[~2014-09-11 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 12:08 bzImage not included in rootfs Chiz Chikwendu
2014-09-11 17:58 ` Scott Garman [this message]
2014-09-11 18:45   ` Chiz Chikwendu
2014-09-11 18:44 ` Darren Hart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5411E2C3.3080807@zenlinux.com \
    --to=sgarman@zenlinux.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.