systemd seems to be missing a service. systemd-sysusers.service now it appears based on the bitbake that its removed because of musl. However it remains in some service files... causing an error to be

#dunfell

A ticket has been open for backporting the fix: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14971

#dunfell

In this case I have no idea unfortunately. Does a regular kernel work? Alex

#dunfell #patch #yocto #raspberrypi #linux

Hello Alex, Sorry for late reply. Actually i madert- image by setting the preferred virtual/kernel type. PREFERRED_PROVIDER_virtual/kernel = "linux-raspberrypi-rt" and bake the recipe for following ta

#dunfell #patch #yocto #raspberrypi #linux

Thanks, I applied the patches locally and it fixed the issue for me. Markus

#dunfell

Thanks, I'll check it out.

#dunfell

Look into the logs in the rootfs build area and it might reveal the underlying problem perhaps some missing library or qemu user mode crash could be the reason

#dunfell

<richard.purdie@...> wrote: I'll cherry-pick those changes and test on autobuilder. Steve

#dunfell

There were changes in bitbake: https://git.yoctoproject.org/poky/commit/bitbake/lib/bb/utils.py?id=273b124bf6acd77b074fde2421be331721a68c11 https://git.yoctoproject.org/poky/commit/bitbake/lib/bb/util

#dunfell

Hello, I try to use yocto SSTATE_MIRROR with a custom distribution (RDK: https://developer.rdkcentral.com/) and enabled yocto multilib support. The sstate directory is created by my build server and p

#dunfell

I am trying to build rcar-image-minimal for RCar S4, while bitbake I'm getting do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed error. I tried using cleanall and cleansstate but

#dunfell

In my setup I have: KERNEL_IMAGETYPES=fitImage (coming from KERNEL_IMAGETYPE of my machine configuration) KERNEL_IMAGETYPE_FOR_MAKE=Image (used only internally by kernel.bbclass and setting to Image b

#dunfell

Interesting... What is the difference between variables ${KERNEL_IMAGETYPES} and ${KERNEL_IMAGETYPE_FOR_MAKE} ? Zee _______ <frederic.martinsons@...> wrote:

#dunfell

Hello, I'm currently migrating our system from warrior to dunfell and I have an issue on fitImage support for aarch64 architecture. We use KERNEL_IMAGETYPE = "fitImage" and INITRAMFS_IMAGE_BUNDLE = "1

#dunfell

It is not possible to say what went wrong if I cannot see the changes you did, what commands you type, and what is the outcome (vs. what you expect). So you need to publish your code somewhere, and de

#dunfell #patch #yocto #raspberrypi #linux

Hello Alex Because i had cloned linux-yocto for 4.12 as stated in (https://docs.yoctoproject.org/3.1.20/kernel-dev/kernel-dev-common.html#using-traditional-kernel-development-to-patch-the-kernel) but

#dunfell #patch #yocto #raspberrypi #linux

There is a version mismatch. If you want to patch the 5.4 kernel, why is the bbappend for 4.12? Alex

#dunfell #patch #yocto #raspberrypi #linux

Hello List i want to apply rt-patch in raspberry-pi by following (using-traditional-kernel-development-to-patch-the-kernel) So in order to achieve that i created my own meta-layer and put that patch i

#dunfell #patch #yocto #raspberrypi #linux

Hi, After applying the patch to the source, I suppose you built the kernel (and is just missing in your email) ? If not that is a quite important step missing ;) Besides that: 1) preempt-rt patch is o

#patch #rpi #yocto #bitbake #dunfell

Hello All I want to apply similar kernel version rt-patch in my rpi-basic-image for my raspberrypi4-64 machine. So, I tried to apply rt-patch for a standard rasbian image (5.15.61-v8+) but not got suc

#patch #rpi #yocto #bitbake #dunfell