From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Greylist: delayed 411 seconds by postgrey-1.34 at layers.openembedded.org; Thu, 11 Sep 2014 12:15:02 UTC Received: from mail1.bemta12.messagelabs.com (mail1.bemta12.messagelabs.com [216.82.251.16]) by mail.openembedded.org (Postfix) with ESMTP id 6CD7C6FE64 for ; Thu, 11 Sep 2014 12:15:02 +0000 (UTC) Received: from [216.82.250.19:25933] by server-16.bemta-12.messagelabs.com id AA/B7-10985-CA091145; Thu, 11 Sep 2014 12:08:12 +0000 X-Env-Sender: chiz.chikwendu@Haemonetics.com X-Msg-Ref: server-6.tower-87.messagelabs.com!1410437290!24935204!1 X-Originating-IP: [12.94.3.150] X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5406 invoked from network); 11 Sep 2014 12:08:11 -0000 Received: from unknown (HELO mail.haemonetics.com) (12.94.3.150) by server-6.tower-87.messagelabs.com with AES128-SHA encrypted SMTP; 11 Sep 2014 12:08:11 -0000 Received: from BRS-EXCH02.haemo.net ([169.254.2.195]) by BRS-Exch01.haemo.net ([169.254.1.211]) with mapi id 14.03.0195.001; Thu, 11 Sep 2014 08:08:10 -0400 From: Chiz Chikwendu To: "Openembedded List (openembedded-core@lists.openembedded.org)" Thread-Topic: bzImage not included in rootfs Thread-Index: Ac/NuQqbyNbec55cRIGxKCHHjsJZBg== Date: Thu, 11 Sep 2014 12:08:09 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.50.1.77] MIME-Version: 1.0 Cc: "darren.hart@intel.com" Subject: bzImage not included in rootfs X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 12:15:10 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_A0F68394C677A9428EE03709453BAAEC7959C76CBRSExch02haemon_" --_000_A0F68394C677A9428EE03709453BAAEC7959C76CBRSExch02haemon_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 =3D "zImage" This should override the kernel settings and build the kernel into the root= fs. I tried it, however it is not working for me. Can anyone help? Thanks, Chiz --_000_A0F68394C677A9428EE03709453BAAEC7959C76CBRSExch02haemon_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 a= bout setting the parameter:

RDEPENDS_kernel-base =3D “zImage”

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

Can anyone help?

Thanks,
Chiz

--_000_A0F68394C677A9428EE03709453BAAEC7959C76CBRSExch02haemon_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Greylist: delayed 478 seconds by postgrey-1.34 at layers.openembedded.org; Thu, 11 Sep 2014 18:06:26 UTC Received: from masterfoo.zenlinux.com (masterfoo.zenlinux.com [50.116.21.172]) by mail.openembedded.org (Postfix) with ESMTP id 973C865D58 for ; Thu, 11 Sep 2014 18:06:26 +0000 (UTC) Received: from [192.168.1.12] (c-50-139-96-211.hsd1.or.comcast.net [50.139.96.211]) by masterfoo.zenlinux.com (Postfix) with ESMTPSA id 53BD91EA35 for ; Thu, 11 Sep 2014 10:58:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=zenlinux.com; s=dkim; t=1410458309; bh=ER9RQnq4mTOVf4MN0hnm4SLC+rNgJPIS9fA7+9MT7gI=; h=Date:From:To:Subject:References:In-Reply-To:From; b=D7pyfUzrIOpVZXQRiPoxIVDsk82IdQ8Eksn61iij0MTcMZWuvy8icy3zOVMUoE4/A 78DwLVSKX32bk4NA/SAQNH1X2rB8kzYbbg/eUXGI4Xdbaa3pzfbieZ0UnPQyYE/bMw js3e3CBftCHTMJa2H7cHo065NYIYqu01/sxNp7uI= Message-ID: <5411E2C3.3080807@zenlinux.com> Date: Thu, 11 Sep 2014 10:58:27 -0700 From: Scott Garman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: openembedded-core@lists.openembedded.org References: In-Reply-To: X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.3.9 (masterfoo.zenlinux.com [0.0.0.0]); Thu, 11 Sep 2014 10:58:29 -0700 (PDT) X-Virus-Scanned: clamav-milter 0.98.4 at masterfoo X-Virus-Status: Clean Subject: Re: bzImage not included in rootfs X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 18:06:35 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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 before trying to generate it again. Scott From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mail.openembedded.org (Postfix) with ESMTP id 80298617B8 for ; Thu, 11 Sep 2014 18:47:52 +0000 (UTC) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 11 Sep 2014 11:35:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,506,1406617200"; d="scan'208";a="590006740" Received: from agalvare-mobl1.amr.corp.intel.com (HELO [10.254.78.160]) ([10.254.78.160]) by fmsmga001.fm.intel.com with ESMTP; 11 Sep 2014 11:44:13 -0700 User-Agent: Microsoft-MacOutlook/14.4.3.140616 Date: Thu, 11 Sep 2014 11:44:14 -0700 From: Darren Hart Sender: "Hart, Darren" To: Chiz Chikwendu , "Openembedded List (openembedded-core@lists.openembedded.org)" Message-ID: Thread-Topic: bzImage not included in rootfs References: In-Reply-To: Mime-version: 1.0 Subject: Re: bzImage not included in rootfs X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 18:48:02 -0000 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable From: Chiz Chikwendu Date: Thursday, September 11, 2014 at 5:08 To: "Openembedded List (openembedded-core@lists.openembedded.org)" Cc: Darren Hart 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. >=20 >I have built an image with poky build environment. >=20 >I noticed that the kernel=B9s bzImage is not included in the rootfs. > >How do I get the system to include =B3bzImage=B2 in the rootfs >(boot/bzImage-)? >=20 >I=B9ve done some research, and I saw a note about setting the parameter: >RDEPENDS_kernel-base =3D =B3zImage=B2 >=20 >This should override the kernel settings and build the kernel into the >rootfs. I tried it, however it is not working for me. >=20 >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 +=3D "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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Greylist: delayed 391 seconds by postgrey-1.34 at layers.openembedded.org; Thu, 11 Sep 2014 18:52:38 UTC Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.98]) by mail.openembedded.org (Postfix) with ESMTP id 9481E617B8 for ; Thu, 11 Sep 2014 18:52:38 +0000 (UTC) Received: from [216.82.253.243:31584] by server-2.bemta-7.messagelabs.com id 86/57-05570-0FDE1145; Thu, 11 Sep 2014 18:46:08 +0000 X-Env-Sender: chiz.chikwendu@Haemonetics.com X-Msg-Ref: server-2.tower-171.messagelabs.com!1410461132!21055596!4 X-Originating-IP: [12.94.3.150] X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3096 invoked from network); 11 Sep 2014 18:46:07 -0000 Received: from unknown (HELO mail.haemonetics.com) (12.94.3.150) by server-2.tower-171.messagelabs.com with AES128-SHA encrypted SMTP; 11 Sep 2014 18:46:07 -0000 Received: from BRS-EXCH02.haemo.net ([169.254.2.195]) by BRS-Exch01.haemo.net ([169.254.1.211]) with mapi id 14.03.0195.001; Thu, 11 Sep 2014 14:45:35 -0400 From: Chiz Chikwendu To: Scott Garman , "openembedded-core@lists.openembedded.org" Thread-Topic: [OE-core] bzImage not included in rootfs Thread-Index: Ac/NuQqbyNbec55cRIGxKCHHjsJZBgAUnlOAAAe7+YA= Date: Thu, 11 Sep 2014 18:45:34 +0000 Message-ID: References: <5411E2C3.3080807@zenlinux.com> In-Reply-To: <5411E2C3.3080807@zenlinux.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.50.1.77] MIME-Version: 1.0 Subject: Re: bzImage not included in rootfs X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 18:52:41 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Scott, Thanks for your help.=20 I went another route. In my layer, I created an image.bb file.=20 The .bb file tells yocto to include the kernel in the rootfs. I do this wit= h the command: IMAGE_INSTALL +=3D kernel-image IMAGE_INSTALL +=3D kernel-module This installs the kernel image and module in the rootfs.=20 I can also try your suggested method.=20 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). >=20 > I have built an image with poky build environment. >=20 > =20 >=20 > I noticed that the kernel's bzImage is not included in the rootfs. >=20 > How do I get the system to include "bzImage" in the rootfs (boot/bzImage-= )? >=20 > =20 >=20 > I've done some research, and I saw a note about setting the parameter: >=20 > RDEPENDS_kernel-base =3D "zImage" >=20 > =20 >=20 > 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 =3D "" 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 before trying to generate it again. Scott --=20 _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core