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