I get this message before I get configparser.NoSectionError: No section: 'Rootfs' File '/usr/lib/python3.7/site-packages/pyanaconda/threading.py"

#yocto

Hi, I apply a few small patches in linux-raspberrypi to use a custom logo depending on an environment variable MY_VENDOR_NAME: I have added MY_VENDOR_NAME to BB_ENV_EXTRAWHITE, and based on the value

#yocto #raspberrypi #linux

Found the missing element: CONFIG_NETFILTER_XT_MATCH_CONNTRACK, i.e. kernel-module-xt-conntrack It is not listed in the RRECOMMENDS in the iptables recipe explicitly, presumably it should be since it

#yocto

Yes, the kernel is typically provided by the BSP vendor through the BSP layer, and they define the kernel version in use. The security concerns still apply though: if there is a vulnerability in their

#yocto

Hi, _append in most cases require a leading space, i.e. you want: DISTRO_FEATURES_append = " pam" Let us know if that fixes it. Quentin

#yocto

I am trying to print using Yocto, but I am clueless on how to enable the printing. The printer I am using is HP Deskjet 2135 Ink Advantage. CUPS version: 2.2.8 HPLIP version: 3.15.6 Avahi version: 0.8

#cups #linux #yocto

Hi, when i am trying to add meta-python from meta-openembedded i am getting following error i have kept meta-openembedded,meta-raspberrypi into same branch dunfell /Raspberrypi4-yocto$ bitbake-layers

#yocto

Hi, I was struggling for days about playing a simple wav file with aplay on a raspberry 3b+ jack 3.5mm output. I had built-in snd_bcm2835 and all the required modules and when booting the raspberry, I

#yocto #raspberrypi

Hi, when i am trying to add meta-python from meta-openembedded i am getting following error i have kept meta-openembedded,meta-raspberrypi into same branch dunfell /Raspberrypi4-yocto$ bitbake-layers

#linux #raspberrypi #yocto

Hello, I'm trying to generate a simple genericx86_64 with Yocto 2.7 Warrior. Problem is that my hddimg is completely messed up upon generation. I have not made any particular configuration apart from

#yocto

Am soory paul, But i was actually trying to check if sdimage is generated or not. I was unaware of . wic. bz2 image. So suggested the above commands. Sorry pankaj. Thanks Siddhartha V

#linux #yocto

hello sir, Thanks for the reply. I searched for what you have suggested, but it looks like I am missing something here. I didn't see kernel.conf file I have shared my bblayers.conf details also , plea

#yocto #raspberrypi #linux

they can live together, but you need to tweak the linking pieces, however, I wonder why rpm-native is coming into play for a target package

#yocto

You did nothing wrong, precisely. core-image-base is a base image that doesn’t do much beyond boot into a working command line environment. If you want a working toolchain (gcc and friends) on the ima

#apt #linux #yocto

I read the codes about sstate_cache. Let me briefly talk about how it work . I am not sure if it is right. Example,we have setscene tasks A_setsscene, B_setcene. and Task C ,D are not setscene task. A

#yocto

Hi, Thanks for all the efort that has gone into Yocto, esp the documentation. I've setup a new machine definition (x86_64 arch), custom BSP, custom kernel and image. Initially I had trouble establishi

#yocto

Hi, I'm pretty new on yocto project/tools and I'm trying to build a simple image for running a raspberry PI 3. The raspberry starts well and works well with eth0 network interface. However wlan0 inter

#raspberrypi #yocto

Not sure if there is a dedicated layer for firecracker, but you can start with QEMU/KVM which is supported and then extend/customise it

#linux #yocto

Thanks for the link, I will check it out.

#yocto

Hi, Following up on my earlier email; it seems that a BSP layer targeting the Firecracker VM model could/should pay some dividends. Recapping the Firecracker 'board' model is: "only 5 emulated devices

#linux #yocto