missing kernel in rootfs image
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
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Quoted 6 lines · Joshua Immanuel
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 andCOMPATIBLE_MACHINEvariables. I find the generated
kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.
Quoted 6 lines
But, the rootfs image does not contain the kernel (in /boot directory).
My machine configuration file has the following kernel specific linesPREFERRED_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
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Quoted 14 lines · Joshua Immanuel
Quoted 6 lines · Joshua Immanuel
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 andCOMPATIBLE_MACHINEvariables. I find the generated
kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.Quoted 6 lines
But, the rootfs image does not contain the kernel (in /boot directory).
My machine configuration file has the following kernel specific linesPREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" PREFERRED_VERSION_linux-yocto ?= "3.0%"
Quoted 8 lines
Can someone explain the work flow behind the process of installing the kernel into the rootfs image? My custom image has the
IMAGE_INSTALLfor "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
Quoted 12 lines
Please guide me.
Regards
Joshua_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 24 lines · Bruce Ashfield
Quoted 14 lines · Joshua Immanuel
Quoted 6 lines · Joshua Immanuel
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 andCOMPATIBLE_MACHINEvariables. I find the generated
kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.Quoted 6 lines
But, the rootfs image does not contain the kernel (in /boot directory).
My machine configuration file has the following kernel specific linesPREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto" PREFERRED_VERSION_linux-yocto ?= "3.0%"
Quoted 8 lines
Can someone explain the work flow behind the process of installing the kernel into the rootfs image? My custom image has the
IMAGE_INSTALLfor "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?
Quoted 6 lines
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.
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 6 lines · Bruce Ashfield
Quoted 6 lines
Can someone explain the work flow behind the process of installing the kernel into the rootfs image? My custom image has the
IMAGE_INSTALLfor "task-core-boot". In turn, the task-core-boot recipe DEPENDS on "virtual/kernel" this ensures that the kernel is staged.
Quoted 6 lines
Quoted 3 lines
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
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in