Sync with 4.12.20 kernel changes in oe-core. Signed-off-by: Anuj Mittal <anuj.mittal@...> --- meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.12.bbappend | 4 ++-- 1 file changed, 2 insertions(

Sync with stable kernel release 4.14.24 in oe-core. Signed-off-by: Anuj Mittal <anuj.mittal@...> --- meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend | 8 ++++---- 1 file changed, 4

Sync with stable kernel release 4.15.7 in oe-core. Signed-off-by: Anuj Mittal <anuj.mittal@...> --- meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.15.bbappend | 8 ++++---- 1 file changed, 4 i

You can inherit update-rc.d class and define INITSCRIPT_NAME/PARAMS in your recipe. https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-classes-update-rc.d

The error is probably coming from meta/recipes-core/initrdscripts/initramfs-framework/init. You can pass a boot parameter 'init_fatal_sh' and that should help you drop to a shell and debug this proble

Hi, Does the image boot up if you select 'boot'? Do you eventually get options to select storage media after all these 'not found' messages if you select 'install'? Can you share the logs? Thanks, Anu

This error suggests that you are using an older version of meta-java. You should try to use the latest. Thanks, Anuj

This shows how to do it from a recipe. For a more up-to-date documentation: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-classes-extrausers INHERIT is used in a configuratio

Oh okay, thanks. I got confused because of the commit message. Thanks, Anuj

Hi Bruce, Should this have been 4.15? Thanks, Anuj

I think it gets included by default using DISTRO_FEATURES_DEFAULT. So using DISTRO_FEATURES_remove = " nfs" should work. However, you may also want to define your own set of values for your distro for

You're probably not using the correct user space DRI driver and/or xorg configuration. Maybe check out meta-ti layer to see if that works ... Thanks, Anuj

Are you using proprietary drivers? If libegl is coming from mesa, it will probably not work with proprietary drivers. Can you provide more details about your setup? Which layer(s) are you using etc. a

Oh yes, you're right. I was trying something out & didn't clean before sending. It should be: bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'glx', d) However, I think it'll probably still fail fo

Yes, glx in libepoxy should be disabled if it is not in DISTRO_FEATURES. glx depends on gl and x11 so if it is to be enabled, both of them should be present. However, x11 without glx and just egl shou

You can specify a local.conf.sample and have TEMPLATECONF point to the directory with that file in it. Please see scripts/oe-setup-builddir in poky/meta to see how it is picked up. Thanks, Anuj

I hope that this machine name, colibri-imx6, isn't being used in some other included layer as well ... meta-freescale-3rdparty/conf/machine/colibri-imx6.conf? Can you try changing the name? Thanks, An

Hi Satya, This is a very old version. Please update to one of the latest supported releases. This generally means that the bb file that this is an append for, wasn't found in any of the layers. Thanks

Hi Issac, Have you defined BBPATH in your layer.conf correctly? Thanks, Anuj

I tried this and I can see the correct values. Which version of poky/OE-core are you using? Can you try to bitbake -c cleansstate and build modutils-initscripts again?