Hi, (since this is a long post, i divided it to sections) TL;DR I have a networking issue in my Yocto dist; Somehow, my ethernet device won't work with systemd-networkd, but will work with /etc/networ

#yocto #systemd

Hi all, While trying to build core-image-base, I'm facing with the error "could not invoke dnf. command". Is there any solutions for this? Log file error: ERROR: Could not invoke dnf. Command '/home/t

#yocto #systemd

Hi, I want to add a feature auto login using sysvinit as init function in yocto. So I have created a new layer named "meta-autologin" and added in the bitbake layers. Now I have updated the local.conf

#yocto #systemd

Hello all, I've set up a kiosk using matchbox window manager running Chromium (Debian Buster). It works great! Next I try to set up power savings by setting IdleAction=suspend in /etc/systemd/logind.c

#systemd

Hi, Thanks for this explanation! Hmm. I would rather see FOO_append += "bar" being used every time when spaces are expected. It's way too easy to forget the extra space which causes annoying and hard

#sdk #systemd

I agree it's a bit confusing at first (I was doing the same long time ago, before bitbake -e was even showing the history of evaluation), but everybody who uses bitbake often should learn this simple

#sdk #systemd

Yes, quite likely. Tough reason why += doesn't work is a mystery to me :) I hack things until "bitbake -e" shows the right things for the recipes. -Mikko

#sdk #systemd

Hi, (lets keep this on the list too) You can add _class-[target|native|nativesdk] to all variables to override defaults. Verify with "bitbake -e". Hope this helps, -Mikko

#sdk #systemd

> DEPENDS_class-target += "systemd" You surely meant DEPENDS_append_class-target = " systemd" here

#sdk #systemd

Hi, Make the systemd dependency for target only, e.g. DEPENDS_class-target += "systemd" etc. There may be relevant use cases to build some of systemd components or tools to native or nativesdk targets

#sdk #systemd

Hello, I have a recipe that builds a library. The recipe specifies an additional package "${PN}-systemd" along with other systemd related variables and finally it instructs that the package should be

#sdk #systemd

Got it figured out, Seems that the default values from meta/recipes-core/systemd/systemd-serialgetty.bb for SERIAL_CONSOLES in are being processed instead of the expansion in our layer. Even though SE

#systemd #yocto

Thank you for the quick reply, in our machin confif only SERIAL_CONSOLE is set, it is: But yocto then uses that to set SERIAL_CONSOLES In bitbake -e I see SERIAL_CONSOLE and SERIAL_CONSOLES set to :

#systemd #yocto

what is SERIAL_CONSOLES variable set to ? this should be machine setting.

#systemd #yocto

We have a build using warrior it boots up well but has a very long boot time of around 95 sec. Using systemd-analyze I notice that we the boot takes a long time before getting to multi-user.target. As

#systemd #yocto