# Nativesdk-util-linux do\_package fatel QA Errors

**URL:** <https://hub.mender.io/t/nativesdk-util-linux-do-package-fatel-qa-errors/5225>\
**Category:** General Discussions\
**Created:** [September 1, 2022, 8:59pm UTC](https://hub.mender.io/t/nativesdk-util-linux-do-package-fatel-qa-errors/5225 "2022-09-01T20:59:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![moh-dev](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@moh-dev](https://hub.mender.io/u/moh-dev)\
**Post date:** [September 1, 2022, 8:59pm UTC](https://hub.mender.io/t/nativesdk-util-linux-do-package-fatel-qa-errors/5225/1 "2022-09-01T20:59:30Z")

</div>

I am trying to build a yocto image with mender for Colibri IMX8X.

In my local.conf I have added the following:

```auto
MENDER_STORAGE_DEVICE = "/dev/mmcblk0"
MENDER_STORAGE_TOTAL_SIZE_MB = "7264"

MENDER_FEATURES_ENABLE_append = " mender-uboot mender-image-sd"
MENDER_FEATURES_DISABLE_append = " mender-grub mender-image-uefi"
TORADEX_BSP_VERSION = "toradex-bsp-5.4.0"

# This really saves a lot of disk space!
INHERIT += "rm_work"

# The name of the disk image and Artifact that will be built.
# This is what the device will report that it is running, and different updates
# must have different names because Mender will skip installation of an Artifact
# if it is already installed.
MENDER_ARTIFACT_NAME = "release-1"

INHERIT += "mender-full"

DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""

```

I have created a patch for colibri-imx8x\_defconfig

```auto
diff --git a/configs/colibri-imx8x_defconfig b/configs/colibri-imx8x_defconfig
index 256159b060..156f9d00f2 100644
--- a/configs/colibri-imx8x_defconfig
+++ b/configs/colibri-imx8x_defconfig
@@ -2,8 +2,10 @@ CONFIG_ARM=y
 CONFIG_ARCH_IMX8=y
 CONFIG_SYS_TEXT_BASE=0x80020000
 CONFIG_SYS_MALLOC_F_LEN=0x8000
-CONFIG_ENV_SIZE=0x2000
-CONFIG_ENV_OFFSET=0xFFFFDE00
+CONFIG_ENV_SIZE=0x4000
+CONFIG_ENV_OFFSET=0x800000
+CONFIG_ENV_OFFSET_REDUND=0x1000000
+CONFIG_SYS_REDUNDAND_ENVIRONMENT=y
 CONFIG_DM_GPIO=y
 CONFIG_BOOTAUX_RESERVED_MEM_BASE=0x88000000
 CONFIG_BOOTAUX_RESERVED_MEM_SIZE=0x08000000

```

When I try to bake my image I get the following error:

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/2/29ae1b0a229f1f9b768666fd526ca95a9ac6a4cc.png)

---

<div class="post-metadata">

**Author:** ![HatsyRei](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/hatsyrei/32/1707_2.png) [@HatsyRei](https://hub.mender.io/u/HatsyRei)\
**Post date:** [September 8, 2022, 10:07am UTC](https://hub.mender.io/t/nativesdk-util-linux-do-package-fatel-qa-errors/5225/2 "2022-09-08T10:07:26Z")

</div>

Apalis iMX8 user. Our team managed to build images with Mender for Apalis iMX8, but met this exact issue when attempting to build our Yocto SDK. These issues seem to stem from meta-toradex-bsp-common’s additions to util-linux.

[https://git.toradex.com/cgit/meta-toradex-bsp-common.git/tree/recipes-core/util-linux/util-linux\_%25.bbappend?h=dunfell-5.x.y](https://git.toradex.com/cgit/meta-toradex-bsp-common.git/tree/recipes-core/util-linux/util-linux_%25.bbappend?h=dunfell-5.x.y)

We haven’t looked deeper into the issue, but managed to apply a workaround by adding:

> FILES\_${PN} += " ${systemd\_unitdir}/system "

to the bbappend recipe, after which we were able to get the SDK built without issues. It is unclear to us whether configuring Mender caused these errors to surface, or if it is simply an oversight by Toradex, or a mix of both.

---

<div class="post-metadata">

**Author:** ![moh-dev](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@moh-dev](https://hub.mender.io/u/moh-dev)\
**Post date:** [September 9, 2022, 1:00pm UTC](https://hub.mender.io/t/nativesdk-util-linux-do-package-fatel-qa-errors/5225/3 "2022-09-09T13:00:23Z")

</div>

> [@HatsyRei](#):
>
> > FILES\_${PN} += " ${systemd\_unitdir}/system "

That does seem to work. The error only seems to occur once the mender layers are included.

---

<div class="post-metadata">

**Author:** ![moh-dev](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@moh-dev](https://hub.mender.io/u/moh-dev)\
**Post date:** [September 12, 2022, 6:43pm UTC](https://hub.mender.io/t/nativesdk-util-linux-do-package-fatel-qa-errors/5225/4 "2022-09-12T18:43:50Z")

</div>

I was able to get the image installed on the device but I am seeing a strange issue. My mender client version is showing as “unknown” even though it should be 2.6.1. Also when I run /usr/bin/mender --version

I see:  
unknown runtime: go1.16.8

Is this something you have seen before. I build the image using the hardknott branch.

---

<div class="post-metadata">

**Author:** ![lramirez](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/lramirez/32/1195_2.png) [@lramirez](https://hub.mender.io/u/lramirez)\
**Post date:** [October 19, 2022, 2:03pm UTC](https://hub.mender.io/t/nativesdk-util-linux-do-package-fatel-qa-errors/5225/5 "2022-10-19T14:03:17Z")

</div>

Hey @moh-dev,

We don’t have any branch for `hardknott`, but for `dunfell` and `kirkstone`. Also, I am curious, is there any reason you are building 2.6.1? Our latest release is 3.4 and our latest LTS is 3.3, I would recommend switching to these versions first to check if the problem was solved there.