Hi,

I've just upgraded from Zeus to Hardknott with the kernel 5.10.59, the
/run/log/journal was running out of space and crashed, is it a kernel
issue or Hardknott build issue?

I never seen that issue in Zeus, I thought that systemd-journald
should be capable of detecting the space, if it is no log space, stop
writing rather crashing the tmpfs

[13749.397288] systemd-journald[97]: Failed to open runtime journal:
No space left on device
[13749.439047] systemd-journald[97]: File
/run/log/journal/4ba2cd613d004916863e30730800bb69/system.journal
corrupted or uncleanly shut down, renaming and replacing.

Thank you.

Kind regards,

- jh

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
File already exists in database: google/protobuf/descriptor.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
GeneratedDatabase()->Add(encoded_file_descriptor, size):

Switch to static linkage per upstream recommendation.

Signed-off-by: Sinan Kaya <okaya@...>
---
recipes-devtools/protobuf-c/protobuf-c_%.bbappend | 1 +
1 file changed, 1 insertion(+)
create mode 100644 recipes-devtools/protobuf-c/protobuf-c_%.bbappend

diff --git a/recipes-devtools/protobuf-c/protobuf-c_%.bbappend b/recipes-devtools/protobuf-c/protobuf-c_%.bbappend
new file mode 100644
index 0000000..7e62ff6
--- /dev/null
+++ b/recipes-devtools/protobuf-c/protobuf-c_%.bbappend
@@ -0,0 +1 @@
+EXTRA_OECONF:append:class-nativesdk = " --disable-shared"
--
2.17.1

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
File already exists in database: google/protobuf/descriptor.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
GeneratedDatabase()->Add(encoded_file_descriptor, size):

Switch to static linkage per upstream recommendation.

Signed-off-by: Sinan Kaya <okaya@...>
---
recipes-devtools/grpc/grpc_%.bbappend | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 recipes-devtools/grpc/grpc_%.bbappend

diff --git a/recipes-devtools/grpc/grpc_%.bbappend b/recipes-devtools/grpc/grpc_%.bbappend
new file mode 100644
index 0000000..cbccf74
--- /dev/null
+++ b/recipes-devtools/grpc/grpc_%.bbappend
@@ -0,0 +1,2 @@
+EXTRA_OECMAKE:remove:class-nativesdk = "-DBUILD_SHARED_LIBS=ON"
+EXTRA_OECMAKE:append:class-nativesdk = " -DBUILD_SHARED_LIBS=OFF"
--
2.17.1

Dynamically linked protoc.exe is failing as follows:

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
File already exists in database: google/protobuf/descriptor.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
GeneratedDatabase()->Add(encoded_file_descriptor, size):

Switch to static linkage per upstream recommendation.

Signed-off-by: Sinan Kaya <okaya@...>
---
recipes-devtools/protobuf/protobuf_%.bbappend | 1 +
1 file changed, 1 insertion(+)
create mode 100644 recipes-devtools/protobuf/protobuf_%.bbappend

diff --git a/recipes-devtools/protobuf/protobuf_%.bbappend b/recipes-devtools/protobuf/protobuf_%.bbappend
new file mode 100644
index 0000000..7e62ff6
--- /dev/null
+++ b/recipes-devtools/protobuf/protobuf_%.bbappend
@@ -0,0 +1 @@
+EXTRA_OECONF:append:class-nativesdk = " --disable-shared"
--
2.17.1

On 8/15/21 10:36 PM, Zoran wrote:

You are using systemd with the wrong defconfig setup, my best guess.
cgroup option in the config must be set to Y while using systemd:
CONFIG_CGROUP=Y .
Zee
_______
On Mon, Aug 16, 2021 at 6:24 AM JH <jupiter.hce@...> wrote:

Hi,

I upgrade Zeus to Hardknott, the kernel version is 5.10.4
(oe-user@oe-host) (arm-oe-linux-gnueabi-gcc (GCC) 10.2.0, GNU ld (GNU
Binutils) 2.36.1.20210209), it was failed to boot the kernel :

---------------

[ 9.418302] systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No
such file or directory
[ 9.431805] systemd[1]: Failed to mount cgroup at
/sys/fs/cgroup/systemd: No such file or directory
[!!!!!!] Failed to mount API filesystems.
[ 9.463151] systemd[1]: Freezing execution.

What could I be missing?

Look at kernel kconfig options that should be enabled here
https://cgit.freedesktop.org/systemd/systemd/tree/README#n38

Thank you.

Kind regards,

- jh

You are using systemd with the wrong defconfig setup, my best guess.

cgroup option in the config must be set to Y while using systemd:
CONFIG_CGROUP=Y .

Zee
_______

Hi,

I upgrade Zeus to Hardknott, the kernel version is 5.10.4
(oe-user@oe-host) (arm-oe-linux-gnueabi-gcc (GCC) 10.2.0, GNU ld (GNU
Binutils) 2.36.1.20210209), it was failed to boot the kernel :

---------------

[ 9.418302] systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No
such file or directory
[ 9.431805] systemd[1]: Failed to mount cgroup at
/sys/fs/cgroup/systemd: No such file or directory
[!!!!!!] Failed to mount API filesystems.
[ 9.463151] systemd[1]: Freezing execution.

What could I be missing?

Thank you.

Kind regards,

- jh

Hello all,

I'm building my project for qemux86-64 and Raspberry Pi 4. Currently, when booted, it displays a textual root shell. I can work with it in both qemu and Raspi and all is good. Now I want to change my image to display a graphical terminal when booted.

On qemu, this already works. In Raspberry Pi, not yet. It still provides me the textual root shell.

On Raspberry Pi, `/var/log/Xorg.0.log` contains the following:
```
[ 1049.676] (II) LoadModule: "fbdev"
[ 1049.681] (WW) Warning, couldn't open module fbdev
[ 1049.681] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 1049.681] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 1049.684] (WW) Falling back to old probe method for modesetting
[ 1049.684] (EE) open /dev/dri/card0: No such file or directory
[ 1049.684] (WW) Falling back to old probe method for modesetting
[ 1049.684] (EE) open /dev/dri/card0: No such file or directory
[ 1049.684] (EE) No devices detected.
```

`/dev/fb0` does exist, so something like a framebuffer does at least seem to exist.

So how can I install the fbdev module on my Raspberry Pi? I looked around a bit and found this: https://elinux.org/RPi_Xorg_rpi_Driver I tried it out and installed the `/usr/lib/xorg/modules/drivers/fbdev_drv.so` file provided in the page, but it's 32bit armhf architecture. My Raspi image is built for aarch64 architecture, so it naturally doesn't run there.

I googled a bit and there seem to be quite a few technologies around to hw-accelerate output rendering. Read about EGL, GLX, OpenGL and DRI. Are some of these options available on RasperryPi or qemux86_64? I runqemu with the kvm option. Booting is fast, but the GUI terminal window doesn't even catch the keypresses in time.

My image is a core-image-minimal with IMAGE_FEATURES x11-base. (https://gitlab.com/manuel_wagesreither/bora-proj/-/blob/master/meta-manwag/recipes-core/images/bora-image.bb)

The distro is a modified Poky with DISTRO_FEATURES x11. (https://gitlab.com/manuel_wagesreither/bora-proj/-/blob/master/meta-manwag/conf/distro/bora-device.conf) To work around https://github.com/agherzan/meta-raspberrypi/issues/228 I made DISTRO_FEATURES_append = " opengl".

Thank you all for your input!

Manuel

On Sun, Aug 15, 2021 at 6:56 AM Alexander Kanavin
<alex.kanavin@...> wrote:

On Sun, 15 Aug 2021 at 03:30, Khem Raj <raj.khem@...> wrote:

Please report the problems to mailing list and we can try to help if
they do not work with musl. We do support systemd/musl combination and
try to keep it working
this will limit testing this combination.

This change is prompted by the recent period where musl patches wouldn't even apply to systemd, which broke half of AUH upgrade attempts.

Interesting, outside AB we build extended world on musl and it works
well. systemd porters usually port the patches as needed for musl

You need to enable systemd/musl on the autobuilder matrix first, if testing the feature is a concern.

yes, I think thats a fair point, I will bring this up.

Alex

From: Bruce Ashfield <bruce.ashfield@...>

5.4 has been dropped from oe-core release/development, so we switch
the alt-config to use 5.10.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta-poky/conf/distro/include/poky-distro-alt-test-config.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-poky/conf/distro/include/poky-distro-alt-test-config.inc b/meta-poky/conf/distro/include/poky-distro-alt-test-config.inc
index 9c2d7753a1..0de2013826 100644
--- a/meta-poky/conf/distro/include/poky-distro-alt-test-config.inc
+++ b/meta-poky/conf/distro/include/poky-distro-alt-test-config.inc
@@ -2,7 +2,7 @@
DISTRO_FEATURES:append = " pam"

# Use the LTSI Kernel
-PREFERRED_VERSION_linux-yocto = "5.4%"
+PREFERRED_VERSION_linux-yocto = "5.10%"

# Ensure the kernel nfs server is enabled
KERNEL_FEATURES:append:pn-linux-yocto = " features/nfsd/nfsd-enable.scc"
--
2.19.1

From: Bruce Ashfield <bruce.ashfield@...>

5.4 has been removed from oe-core, so we drop our associated
bbappend.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
.../linux/linux-yocto_5.4.bbappend | 23 -------------------
1 file changed, 23 deletions(-)
delete mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend
deleted file mode 100644
index 290aa323eb..0000000000
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend
+++ /dev/null
@@ -1,23 +0,0 @@
-KBRANCH:genericx86 = "v5.4/standard/base"
-KBRANCH:genericx86-64 = "v5.4/standard/base"
-KBRANCH:edgerouter = "v5.4/standard/edgerouter"
-KBRANCH:beaglebone-yocto = "v5.4/standard/beaglebone"
-
-KMACHINE:genericx86 ?= "common-pc"
-KMACHINE:genericx86-64 ?= "common-pc-64"
-KMACHINE:beaglebone-yocto ?= "beaglebone"
-
-SRCREV_machine:genericx86 ?= "31db2b47ac7d8508080fbb7344399b501216de66"
-SRCREV_machine:genericx86-64 ?= "31db2b47ac7d8508080fbb7344399b501216de66"
-SRCREV_machine:edgerouter ?= "706efec4c1e270ec5dda92275898cd465dfdc7dd"
-SRCREV_machine:beaglebone-yocto ?= "706efec4c1e270ec5dda92275898cd465dfdc7dd"
-
-COMPATIBLE_MACHINE:genericx86 = "genericx86"
-COMPATIBLE_MACHINE:genericx86-64 = "genericx86-64"
-COMPATIBLE_MACHINE:edgerouter = "edgerouter"
-COMPATIBLE_MACHINE:beaglebone-yocto = "beaglebone-yocto"
-
-LINUX_VERSION:genericx86 = "5.4.94"
-LINUX_VERSION:genericx86-64 = "5.4.94"
-LINUX_VERSION:edgerouter = "5.4.58"
-LINUX_VERSION:beaglebone-yocto = "5.4.58"
--
2.19.1

From: Bruce Ashfield <bruce.ashfield@...>

both -rt and -standard have been updated to 5.13, so we switch out
defaults.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta-poky/conf/distro/poky.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index c7c46cd226..ae0c52178a 100644
--- a/meta-poky/conf/distro/poky.conf
+++ b/meta-poky/conf/distro/poky.conf
@@ -19,8 +19,8 @@ POKY_DEFAULT_EXTRA_RRECOMMENDS = "kernel-module-af-packet"

DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${POKY_DEFAULT_DISTRO_FEATURES}"

-PREFERRED_VERSION_linux-yocto ?= "5.10%"
-PREFERRED_VERSION_linux-yocto-rt ?= "5.10%"
+PREFERRED_VERSION_linux-yocto ?= "5.13%"
+PREFERRED_VERSION_linux-yocto-rt ?= "5.13%"

SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-${TUNE_PKGARCH}-${MACHINE}"
SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
--
2.19.1

From: Bruce Ashfield <bruce.ashfield@...>

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta-poky/conf/distro/poky-tiny.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-poky/conf/distro/poky-tiny.conf b/meta-poky/conf/distro/poky-tiny.conf
index c25e50c73a..b8f5f21a31 100644
--- a/meta-poky/conf/distro/poky-tiny.conf
+++ b/meta-poky/conf/distro/poky-tiny.conf
@@ -43,7 +43,7 @@ FULL_OPTIMIZATION="-Os -pipe ${DEBUG_FLAGS}"
# Distro config is evaluated after the machine config, so we have to explicitly
# set the kernel provider to override a machine config.
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
-PREFERRED_VERSION_linux-yocto-tiny ?= "5.10%"
+PREFERRED_VERSION_linux-yocto-tiny ?= "5.13%"

# We can use packagegroup-core-boot, but in the future we may need a new packagegroup-core-tiny
#POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
--
2.19.1

From: Bruce Ashfield <bruce.ashfield@...>

Richard,

This is a follow on to my oe-core series that drops the 5.4 recipes.

I haven't had any issues with 5.10/5.13 in my local testing, but I do
expect we'll find something during integration.

Cheers,

Bruce

The following changes since commit ababb195496f1d16d8b082e1bc6d87a177d2b2a6:

conf/machine: bump qemu preferred versions to 5.13 (2021-08-15 10:44:27 -0400)

are available in the Git repository at:

git://git.yoctoproject.org/poky-contrib zedd/kernel-yocto
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (4):
poky/poky-tiny: set default kernel to 5.13
poky: set default kernel to 5.13
yocto-bsp: drop 5.4 bbappend
poky-alt: switch default kernel to 5.10

.../include/poky-distro-alt-test-config.inc | 2 +-
meta-poky/conf/distro/poky-tiny.conf | 2 +-
meta-poky/conf/distro/poky.conf | 4 ++--
.../linux/linux-yocto_5.4.bbappend | 23 -------------------
4 files changed, 4 insertions(+), 27 deletions(-)
delete mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend

--
2.19.1

Am So, 15. Aug 2021, um 03:39, schrieb Khem Raj:

On 8/14/21 5:29 AM, Manuel Wagesreither wrote:

Am Fr, 13. Aug 2021, um 23:59, schrieb Steve Sakoman:

On Fri, Aug 13, 2021 at 11:29 AM Manuel Wagesreither <ManWag@...> wrote:

Hello all,

I updated the layers of my project to the current dunfell branch tips. See here: https://gitlab.com/manuel_wagesreither/bora-proj/-/commit/de631634d7556987d2551d0cedca8f67530bc78d

Since then, the build is failing with the following message:
```
ERROR: ParseError at /home/manuel/bora-proj/meta-openembedded/meta-oe/conf/layer.conf:104: unparsed line: 'DEFAULT_TEST_SUITES:pn-meta-oe-ptest-image = " ${PTESTTESTSUITE}"'
```

Indeed this line, and even more the one after look strange.
https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/conf/layer.conf#L104

Note that you are using the master branch of meta-oe ^^^^^^^^

If you use the dunfell branch you won't have this issue.

Steve

I feel like an idiot right now. Thank you! With dunfell it builds indeed.

Now I have to deal with the following:
```
ERROR: Layer multimedia-layer is not compatible with the core layer which only supports these series: dunfell (layer is compatible with honister)
```

https://github.com/openembedded/meta-openembedded/blob/dunfell/meta-multimedia/conf/layer.conf#L34

says it works with dunfell releases and depends on core and meta-python
layers. So I wonder what release are you using for core

My bad again. I had the modified layer.conf still in my meta-oe directory, and this prevented kas from switching to the new commit. Fixed this and build now runs.

Manuel

Am Sa, 14. Aug 2021, um 12:14, schrieb Robert Berger:

On 14/08/2021 00:28, Manuel Wagesreither wrote:

Hello all,

I updated the layers of my project to the current dunfell branch tips. See here: https://gitlab.com/manuel_wagesreither/bora-proj/-/commit/de631634d7556987d2551d0cedca8f67530bc78d

Since then, the build is failing with the following message:
```
ERROR: ParseError at /home/manuel/bora-proj/meta-openembedded/meta-oe/conf/layer.conf:104: unparsed line: 'DEFAULT_TEST_SUITES:pn-meta-oe-ptest-image = " ${PTESTTESTSUITE}"'
```

There was an OVERRIDE syntax change and this is what are seeing.
Some layers, like meta-openembedded incorporated this change into their
master branch. So either you need to update all your layers as well, or
you need to use meta-openembedded with a branch/commit before the change.

Regards,

Robert

Alright, thanks for the info. Did they switch from the underline _ to a colon : as seperator? Guess underline was becoming ambigous.

Manuel

On 8/14/21 5:29 AM, Manuel Wagesreither wrote:

Am Fr, 13. Aug 2021, um 23:59, schrieb Steve Sakoman:

On Fri, Aug 13, 2021 at 11:29 AM Manuel Wagesreither <ManWag@...> wrote:

Hello all,

I updated the layers of my project to the current dunfell branch tips. See here: https://gitlab.com/manuel_wagesreither/bora-proj/-/commit/de631634d7556987d2551d0cedca8f67530bc78d

Since then, the build is failing with the following message:
```
ERROR: ParseError at /home/manuel/bora-proj/meta-openembedded/meta-oe/conf/layer.conf:104: unparsed line: 'DEFAULT_TEST_SUITES:pn-meta-oe-ptest-image = " ${PTESTTESTSUITE}"'
```

Indeed this line, and even more the one after look strange.
https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/conf/layer.conf#L104

Note that you are using the master branch of meta-oe ^^^^^^^^

If you use the dunfell branch you won't have this issue.

Steve

I feel like an idiot right now. Thank you! With dunfell it builds indeed.
Now I have to deal with the following:
```
ERROR: Layer multimedia-layer is not compatible with the core layer which only supports these series: dunfell (layer is compatible with honister)
```

https://github.com/openembedded/meta-openembedded/blob/dunfell/meta-multimedia/conf/layer.conf#L34

says it works with dunfell releases and depends on core and meta-python layers. So I wonder what release are you using for core

I guess I'll have to analyze the layers .conf file to see where that comes from.
Thanks, Manuel