Date   

[meta-rockchip][PATCH v7 6/6] WIP NanoPi-M4: activate BT support

Yann Dirson
 

From: Yann Dirson <yann@...>

Take the firmware from rbwifibt, as a compatible one does not seem to
be available in broadcom-bt-firmware.

Disclaimer: I have only been able to scan/pair with devices, I could
not establish a connection. However, with the same board I've had the
same results with the board vendor's own FriendlyCore image.
---
conf/machine/include/nanopi-m4.inc | 6 +++++-
recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg | 6 ++++++
2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/conf/machine/include/nanopi-m4.inc b/conf/machine/include/na=
nopi-m4.inc
index cb27928..3bd5c97 100644
--- a/conf/machine/include/nanopi-m4.inc
+++ b/conf/machine/include/nanopi-m4.inc
@@ -3,7 +3,7 @@
=20
require rk3399.inc
=20
-MACHINE_FEATURES +=3D "usbhost serial wifi"
+MACHINE_FEATURES +=3D "usbhost serial wifi bluetooth"
=20
KMACHINE =3D "nanopi-m4"
KERNEL_DEVICETREE =3D "rockchip/rk3399-nanopi-m4.dtb"
@@ -26,3 +26,7 @@ SERIAL_CONSOLES =3D "1500000;ttyS2"
=20
# wifi firmware
MACHINE_EXTRA_RRECOMMENDS +=3D "linux-firmware-bcm4356"
+
+# bluetooth firmware
+#MACHINE_EXTRA_RRECOMMENDS +=3D "broadcom-bt-firmware-bcm4356a2"
+MACHINE_EXTRA_RRECOMMENDS +=3D "rkwifibt-firmware-ap6356-bt"
diff --git a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg b/reci=
pes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
index d42b744..d45e879 100644
--- a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
+++ b/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
@@ -14,3 +14,9 @@ CONFIG_REALTEK_PHY=3Dm
CONFIG_WLAN_VENDOR_BROADCOM=3Dy
CONFIG_BRCMFMAC=3Dm
CONFIG_BRCMFMAC_SDIO=3Dy
+
+# AP6356S BT
+CONFIG_BT_HCIUART=3Dm
+CONFIG_SERIAL_DEV_BUS=3Dy
+CONFIG_SERIAL_DEV_CTRL_TTYPORT=3Dy
+CONFIG_BT_HCIUART_BCM=3Dy
--=20
2.30.2


[meta-rockchip][PATCH v7 5/6] WIP Import rkwifibt-firmware from vendor's meta-rockchip

Yann Dirson
 

From: Yann Dirson <yann@...>

As far as the AP6356S in NanoPi-m4 is concerned, the included wifi firmwa=
re
is for Rockchip's kernel tree, but for Bluetooth firmware this seems to b=
e
the proper "upstream" package.

Changes from Rockchip's version:
- use /lib/firmware/brcm/, not /system/etc/firmware/
- include LICENSE.rockchip in package tree

The chip powers on:

[ 4.695193] Bluetooth: hci0: BCM: chip id 101
[ 4.696142] Bluetooth: hci0: BCM: features 0x2f
[ 4.697882] Bluetooth: hci0: BCM4354A2
[ 4.698345] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
[ 4.701994] Bluetooth: hci0: BCM4356A2 'brcm/BCM4356A2.hcd' Patch
[ 5.464146] Bluetooth: hci0: BCM4356 37.4MHz AMPAK AP6356-0055
[ 5.464813] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0266

It is able to pair with devices, but connect fails.
---
.../rkwifibt-firmware/files/LICENSE.rockchip | 41 +++++++
.../rkwifibt-firmware/rkwifibt-firmware.bb | 110 ++++++++++++++++++
2 files changed, 151 insertions(+)
create mode 100644 recipes-kernel/rkwifibt-firmware/files/LICENSE.rockch=
ip
create mode 100644 recipes-kernel/rkwifibt-firmware/rkwifibt-firmware.bb

diff --git a/recipes-kernel/rkwifibt-firmware/files/LICENSE.rockchip b/re=
cipes-kernel/rkwifibt-firmware/files/LICENSE.rockchip
new file mode 100644
index 0000000..69b445b
--- /dev/null
+++ b/recipes-kernel/rkwifibt-firmware/files/LICENSE.rockchip
@@ -0,0 +1,41 @@
+Copyright (c) 2020, Rockchip Electronics Co.Ltd
+All rights reserved.
+
+Redistribution. Redistribution and use in binary form, without
+modification, are permitted provided that the following conditions are
+met:
+
+* Redistributions must reproduce the above copyright notice and the
+ following disclaimer in the documentation and/or other materials
+ provided with the distribution.
+
+* Neither the name of Rockchip Electronics Co.Ltd, its products
+ nor the names of its suppliers may be used to endorse or promote produ=
cts
+ derived from this Software without specific prior written permission.
+
+* No reverse engineering, decompilation, or disassembly of this software
+ is permitted.
+
+Limited patent license. Rockchip Electronics Co.Ltd grants a world-wide,
+royalty-free, non-exclusive license under patents it now or hereafter
+owns or controls to make, have made, use, import, offer to sell and
+sell ("Utilize") this software, but solely to the extent that any
+such patent is necessary to Utilize the software alone, or in
+combination with an operating system licensed under an approved Open
+Source license as listed by the Open Source Initiative at
+http://opensource.org/licenses. The patent license shall not apply to
+any other combinations which include this software. No hardware per
+se is licensed hereunder.
+
+DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
+CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
+BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
+OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
+TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
+USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGE.
diff --git a/recipes-kernel/rkwifibt-firmware/rkwifibt-firmware.bb b/reci=
pes-kernel/rkwifibt-firmware/rkwifibt-firmware.bb
new file mode 100644
index 0000000..870177b
--- /dev/null
+++ b/recipes-kernel/rkwifibt-firmware/rkwifibt-firmware.bb
@@ -0,0 +1,110 @@
+# Copyright (C) 2019, Fuzhou Rockchip Electronics Co., Ltd
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+SUMMARY =3D "Rockchip WIFI/BT firmware files"
+SECTION =3D "kernel"
+
+LICENSE =3D "LICENSE.rockchip"
+LIC_FILES_CHKSUM =3D "file://LICENSE.rockchip;md5=3Dd63890e209bf038f44e7=
08bbb13e4ed9"
+
+PV_append =3D "+git${SRCPV}"
+
+SRCREV =3D "af2cf8772078b0246ac805e7ed78a62cf8f21993"
+SRC_URI =3D " \
+ git://github.com/rockchip-linux/rkwifibt.git \
+ file://LICENSE.rockchip;subdir=3Dgit \
+"
+#SRC_URI =3D "git://github.com/JeffyCN/mirrors.git;branch=3Drkwifibt;"
+
+S =3D "${WORKDIR}/git"
+
+inherit allarch deploy
+
+do_install() {
+ install -d ${D}/lib/firmware/brcm/
+ install -m 0644 ${S}/firmware/broadcom/all/*/* \
+ -t ${D}/lib/firmware/brcm/
+ install -d ${D}/lib/firmware/rtlbt/
+ install -m 0644 ${S}/realtek/RTL*/* -t ${D}/lib/firmware/rtlbt/
+}
+
+PACKAGES =3D+ " \
+ ${PN}-ap6181-wifi \
+ ${PN}-ap6212a1-wifi \
+ ${PN}-ap6212a1-bt \
+ ${PN}-ap6236-wifi \
+ ${PN}-ap6236-bt \
+ ${PN}-ap6255-wifi \
+ ${PN}-ap6255-bt \
+ ${PN}-ap6354-wifi \
+ ${PN}-ap6354-bt \
+ ${PN}-ap6356-wifi \
+ ${PN}-ap6356-bt \
+ ${PN}-rtl8723ds-bt \
+"
+
+FILES_${PN}-ap6181-wifi =3D " \
+ lib/firmware/brcm/fw_bcm40181a2_apsta.bin \
+ lib/firmware/brcm/fw_bcm40181a2.bin \
+ lib/firmware/brcm/nvram_ap6181.txt \
+"
+
+FILES_${PN}-ap6212a1-wifi =3D " \
+ lib/firmware/brcm/fw_bcm43438a1_apsta.bin \
+ lib/firmware/brcm/fw_bcm43438a1.bin \
+ lib/firmware/brcm/nvram_ap6212a.txt \
+"
+FILES_${PN}-ap6212a1-bt =3D " \
+ lib/firmware/brcm/bcm43438a1.hcd \
+"
+
+FILES_${PN}-ap6236-wifi =3D " \
+ lib/firmware/brcm/fw_bcm43436b0_apsta.bin \
+ lib/firmware/brcm/fw_bcm43436b0.bin \
+ lib/firmware/brcm/nvram_ap6236.txt \
+"
+FILES_${PN}-ap6236-bt =3D " \
+ lib/firmware/brcm/BCM4343B0.hcd \
+"
+
+FILES_${PN}-ap6255-wifi =3D " \
+ lib/firmware/brcm/fw_bcm43455c0_ag.bin \
+ lib/firmware/brcm/nvram_ap6255.txt \
+"
+FILES_${PN}-ap6255-bt =3D " \
+ lib/firmware/brcm/BCM4345C0_ap.hcd \
+ lib/firmware/brcm/BCM4345C0.hcd \
+"
+
+FILES_${PN}-ap6354-wifi =3D " \
+ lib/firmware/brcm/fw_bcm4354a1_ag.bin \
+ lib/firmware/brcm/nvram_ap6354.txt \
+"
+FILES_${PN}-ap6354-bt =3D " \
+ lib/firmware/brcm/bcm4354a1.hcd \
+"
+
+FILES_${PN}-ap6356-wifi =3D " \
+ lib/firmware/brcm/fw_bcm4356a2_ag.bin \
+ lib/firmware/brcm/nvram_ap6356.txt \
+ lib/firmware/brcm/nvram_ap6356s.txt \
+"
+FILES_${PN}-ap6356-bt =3D " \
+ lib/firmware/brcm/BCM4356A2.hcd \
+"
+
+FILES_${PN}-rtl8723ds-bt =3D " \
+ lib/firmware/rtlbt/rtl8723d_config \
+ lib/firmware/rtlbt/rtl8723d_fw \
+"
+
+FILES_${PN} =3D "*"
+
+# Make it depend on all of the split-out packages.
+python () {
+ pn =3D d.getVar('PN')
+ firmware_pkgs =3D oe.utils.packages_filter_out_system(d)
+ d.appendVar('RDEPENDS_' + pn, ' ' + ' '.join(firmware_pkgs))
+}
+
+INSANE_SKIP_${PN} +=3D "arch"
--=20
2.30.2


[meta-rockchip][PATCH v7 4/6] NanoPi-M4: activate Wifi support

Yann Dirson
 

From: Yann Dirson <yann@...>

---
conf/machine/include/nanopi-m4.inc | 5 ++++-
recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg | 5 +++++
2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/conf/machine/include/nanopi-m4.inc b/conf/machine/include/na=
nopi-m4.inc
index a14b705..cb27928 100644
--- a/conf/machine/include/nanopi-m4.inc
+++ b/conf/machine/include/nanopi-m4.inc
@@ -3,7 +3,7 @@
=20
require rk3399.inc
=20
-MACHINE_FEATURES +=3D "usbhost serial"
+MACHINE_FEATURES +=3D "usbhost serial wifi"
=20
KMACHINE =3D "nanopi-m4"
KERNEL_DEVICETREE =3D "rockchip/rk3399-nanopi-m4.dtb"
@@ -23,3 +23,6 @@ IMAGE_BOOT_FILES ?=3D "\
"
=20
SERIAL_CONSOLES =3D "1500000;ttyS2"
+
+# wifi firmware
+MACHINE_EXTRA_RRECOMMENDS +=3D "linux-firmware-bcm4356"
diff --git a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg b/reci=
pes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
index f3a2abf..d42b744 100644
--- a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
+++ b/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
@@ -9,3 +9,8 @@ CONFIG_PWRSEQ_SIMPLE=3Dy
=20
# RTL8211E
CONFIG_REALTEK_PHY=3Dm
+
+# AP6356S Wifi
+CONFIG_WLAN_VENDOR_BROADCOM=3Dy
+CONFIG_BRCMFMAC=3Dm
+CONFIG_BRCMFMAC_SDIO=3Dy
--=20
2.30.2


[meta-rockchip][PATCH v7 3/6] linux-firmware: import variables file for ap4356s firmware from armbian

Yann Dirson
 

From: Yann Dirson <yann@...>

This is required for wifi support on nanopi-m4 with kernel 5.10.

This is dependant on poky commit commit 698fd81c551b52ff7f4a26e42d9acf9ad=
4ce5639,
"linux-firmware: include all relevant files in -bcm4356".

This file was fetched from
https://github.com/armbian/firmware/commit/9c800d7e16616dd30cfd854f26e563=
fb675e3f8a

Signed-off-by: Yann Dirson <yann@...>
---
.../files/brcmfmac4356-sdio.txt | 126 ++++++++++++++++++
.../linux-firmware/linux-firmware_%.bbappend | 13 ++
2 files changed, 139 insertions(+)
create mode 100644 recipes-kernel/linux-firmware/files/brcmfmac4356-sdio=
.txt
create mode 100644 recipes-kernel/linux-firmware/linux-firmware_%.bbappe=
nd

diff --git a/recipes-kernel/linux-firmware/files/brcmfmac4356-sdio.txt b/=
recipes-kernel/linux-firmware/files/brcmfmac4356-sdio.txt
new file mode 100644
index 0000000..a8c1ff8
--- /dev/null
+++ b/recipes-kernel/linux-firmware/files/brcmfmac4356-sdio.txt
@@ -0,0 +1,126 @@
+# Sample variables file for BCM94356Z NGFF 22x30mm iPA, iLNA board with =
PCIe for production package
+NVRAMRev=3D$Rev: 492104 $
+#4356 chip =3D 4354 A2 chip
+sromrev=3D11
+boardrev=3D0x1102
+boardtype=3D0x073e
+boardflags=3D0x02400201
+#0x2000 enable 2G spur WAR
+boardflags2=3D0x00802000
+boardflags3=3D0x0000000a
+#boardflags3 0x00000100 /* to read swctrlmap from nvram*/
+#define BFL3_5G_SPUR_WAR 0x00080000 /* enable spur WAR in 5G band */
+#define BFL3_AvVim 0x40000000 /* load AvVim from nvram */
+macaddr=3D00:90:4c:1a:10:01
+ccode=3DX2
+regrev=3D205
+antswitch=3D0
+pdgain5g=3D4
+pdgain2g=3D4
+tworangetssi2g=3D0
+tworangetssi5g=3D0
+paprdis=3D0
+femctrl=3D10
+vendid=3D0x14e4
+devid=3D0x43ec
+manfid=3D0x2d0
+#prodid=3D0x052e
+nocrc=3D1
+otpimagesize=3D502
+xtalfreq=3D37400
+rxgains2gelnagaina0=3D0
+rxgains2gtrisoa0=3D7
+rxgains2gtrelnabypa0=3D0
+rxgains5gelnagaina0=3D0
+rxgains5gtrisoa0=3D11
+rxgains5gtrelnabypa0=3D0
+rxgains5gmelnagaina0=3D0
+rxgains5gmtrisoa0=3D13
+rxgains5gmtrelnabypa0=3D0
+rxgains5ghelnagaina0=3D0
+rxgains5ghtrisoa0=3D12
+rxgains5ghtrelnabypa0=3D0
+rxgains2gelnagaina1=3D0
+rxgains2gtrisoa1=3D7
+rxgains2gtrelnabypa1=3D0
+rxgains5gelnagaina1=3D0
+rxgains5gtrisoa1=3D10
+rxgains5gtrelnabypa1=3D0
+rxgains5gmelnagaina1=3D0
+rxgains5gmtrisoa1=3D11
+rxgains5gmtrelnabypa1=3D0
+rxgains5ghelnagaina1=3D0
+rxgains5ghtrisoa1=3D11
+rxgains5ghtrelnabypa1=3D0
+rxchain=3D3
+txchain=3D3
+aa2g=3D3
+aa5g=3D3
+agbg0=3D2
+agbg1=3D2
+aga0=3D2
+aga1=3D2
+tssipos2g=3D1
+extpagain2g=3D2
+tssipos5g=3D1
+extpagain5g=3D2
+tempthresh=3D255
+tempoffset=3D255
+rawtempsense=3D0x1ff
+pa2ga0=3D-147,6192,-705
+pa2ga1=3D-161,6041,-701
+pa5ga0=3D-194,6069,-739,-188,6137,-743,-185,5931,-725,-171,5898,-715
+pa5ga1=3D-190,6248,-757,-190,6275,-759,-190,6225,-757,-184,6131,-746
+subband5gver=3D0x4
+pdoffsetcckma0=3D0x4
+pdoffsetcckma1=3D0x4
+pdoffset40ma0=3D0x0000
+pdoffset80ma0=3D0x0000
+pdoffset40ma1=3D0x0000
+pdoffset80ma1=3D0x0000
+maxp2ga0=3D76
+maxp5ga0=3D74,74,74,74
+maxp2ga1=3D76
+maxp5ga1=3D74,74,74,74
+cckbw202gpo=3D0x0000
+cckbw20ul2gpo=3D0x0000
+mcsbw202gpo=3D0x99644422
+mcsbw402gpo=3D0x99644422
+dot11agofdmhrbw202gpo=3D0x6666
+ofdmlrbw202gpo=3D0x0022
+mcsbw205glpo=3D0x88766663
+mcsbw405glpo=3D0x88666663
+mcsbw805glpo=3D0xbb666665
+mcsbw205gmpo=3D0xd8666663
+mcsbw405gmpo=3D0x88666663
+mcsbw805gmpo=3D0xcc666665
+mcsbw205ghpo=3D0xdc666663
+mcsbw405ghpo=3D0xaa666663
+mcsbw805ghpo=3D0xdd666665
+mcslr5glpo=3D0x0000
+mcslr5gmpo=3D0x0000
+mcslr5ghpo=3D0x0000
+sb20in40hrpo=3D0x0
+sb20in80and160hr5glpo=3D0x0
+sb40and80hr5glpo=3D0x0
+sb20in80and160hr5gmpo=3D0x0
+sb40and80hr5gmpo=3D0x0
+sb20in80and160hr5ghpo=3D0x0
+sb40and80hr5ghpo=3D0x0
+sb20in40lrpo=3D0x0
+sb20in80and160lr5glpo=3D0x0
+sb40and80lr5glpo=3D0x0
+sb20in80and160lr5gmpo=3D0x0
+sb40and80lr5gmpo=3D0x0
+sb20in80and160lr5ghpo=3D0x0
+sb40and80lr5ghpo=3D0x0
+dot11agduphrpo=3D0x0
+dot11agduplrpo=3D0x0
+phycal_tempdelta=3D255
+temps_period=3D15
+temps_hysteresis=3D15
+rssicorrnorm_c0=3D4,4
+rssicorrnorm_c1=3D4,4
+rssicorrnorm5g_c0=3D1,2,3,1,2,3,6,6,8,6,6,8
+rssicorrnorm5g_c1=3D1,2,3,2,2,2,7,7,8,7,7,8
+
diff --git a/recipes-kernel/linux-firmware/linux-firmware_%.bbappend b/re=
cipes-kernel/linux-firmware/linux-firmware_%.bbappend
new file mode 100644
index 0000000..45ab311
--- /dev/null
+++ b/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
@@ -0,0 +1,13 @@
+FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
+
+SRC_URI +=3D "\
+ file://brcmfmac4356-sdio.txt \
+"
+
+BRCMDIR =3D "${nonarch_base_libdir}/firmware/brcm"
+
+do_install_append() {
+ install -m644 ${WORKDIR}/brcmfmac4356-sdio.txt ${D}${BRCMDIR}/
+}
+
+FILES_${PN}-bcm4356 +=3D "${BRCMDIR}/brcmfmac4356-sdio.*"
--=20
2.30.2


[meta-rockchip][PATCH v7 1/6] linux-yocto: add an initial NanoPi-M4 BSP

Yann Dirson
 

From: Yann Dirson <yann@...>

This patch provides "standard" and "tiny" BSP.

There is still much work to be done in dispatching feature to individual
scc files - the more boards we can support the better it will get.
Not all SoC/board features are covered yet either (esp. Wifi/Bluetooth an=
d
audio jack), and properly-woking HDMI still needs patches.

Tiny is not fully testable by itself, it can be minimally booted with
serial console (though still missing CONFIG_MULTIUSER for serial getty,
and CONFIG_INOTIFY_USER for proper udev operation) using:

PREFERRED_PROVIDER_virtual/kernel =3D "linux-yocto-tiny"
KERNEL_FEATURES_append =3D "\
ktypes/base/base.scc \
features/debug/printk.scc \
cfg/fs/ext4.scc \
cfg/8250.scc \
"

Such a tiny build is still using mainline defconfig with lots of hardware
features, and the kernel can be slimmed down even more by using:

KBUILD_DEFCONFIG =3D ""

Kernel weight using default configurations:
- standard 11MB
- tiny 5MB
- tiny with no defconfig 2.5MB

Signed-off-by: Yann Dirson <yann@...>
---
.../files/bsp/rockchip/nanopi-m4-standard.scc | 8 +++
.../files/bsp/rockchip/nanopi-m4-tiny.scc | 8 +++
.../linux/files/bsp/rockchip/nanopi-m4.cfg | 11 +++
.../linux/files/bsp/rockchip/nanopi-m4.scc | 5 ++
.../linux/files/bsp/rockchip/rk3399.cfg | 70 +++++++++++++++++++
.../linux/files/bsp/rockchip/rk3399.scc | 5 ++
.../linux/files/bsp/rockchip/rockchip.cfg | 50 +++++++++++++
.../linux/files/bsp/rockchip/rockchip.scc | 6 ++
recipes-kernel/linux/linux-yocto%.bbappend | 6 ++
9 files changed, 169 insertions(+)
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-sta=
ndard.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-tin=
y.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rk3399.cfg
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rk3399.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rockchip.cfg
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rockchip.scc

diff --git a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-standard.s=
cc b/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-standard.scc
new file mode 100644
index 0000000..7d28b2b
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-standard.scc
@@ -0,0 +1,8 @@
+# SPDX-License-Identifier: MIT
+define KMACHINE nanopi-m4
+define KTYPE standard
+define KARCH arm
+define KMETA_EXTERNAL_BSP t
+
+include ktypes/standard/standard.scc nopatch
+include nanopi-m4.scc
diff --git a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-tiny.scc b=
/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-tiny.scc
new file mode 100644
index 0000000..fe1f5b8
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-tiny.scc
@@ -0,0 +1,8 @@
+# SPDX-License-Identifier: MIT
+define KMACHINE nanopi-m4
+define KTYPE tiny
+define KARCH arm
+define KMETA_EXTERNAL_BSP t
+
+include ktypes/tiny/tiny.scc nopatch
+include nanopi-m4.scc
diff --git a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg b/reci=
pes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
new file mode 100644
index 0000000..f3a2abf
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
@@ -0,0 +1,11 @@
+CONFIG_MFD_RK808=3Dy
+CONFIG_COMMON_CLK_RK808=3Dy
+
+CONFIG_REGULATOR_RK808=3Dy
+CONFIG_REGULATOR_FAN53555=3Dy
+
+CONFIG_MMC_BLOCK=3Dy
+CONFIG_PWRSEQ_SIMPLE=3Dy
+
+# RTL8211E
+CONFIG_REALTEK_PHY=3Dm
diff --git a/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.scc b/reci=
pes-kernel/linux/files/bsp/rockchip/nanopi-m4.scc
new file mode 100644
index 0000000..f4267aa
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.scc
@@ -0,0 +1,5 @@
+# SPDX-License-Identifier: MIT
+
+kconf hardware nanopi-m4.cfg
+
+include rk3399.scc
diff --git a/recipes-kernel/linux/files/bsp/rockchip/rk3399.cfg b/recipes=
-kernel/linux/files/bsp/rockchip/rk3399.cfg
new file mode 100644
index 0000000..42adfd1
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/rk3399.cfg
@@ -0,0 +1,70 @@
+# A72 errata, all past revisions
+CONFIG_ARM64_ERRATUM_1319367=3Dy
+# A53 errata, all patched on boot when needed
+CONFIG_ARM64_ERRATUM_826319=3Dy
+CONFIG_ARM64_ERRATUM_827319=3Dy
+CONFIG_ARM64_ERRATUM_824069=3Dy
+CONFIG_ARM64_ERRATUM_819472=3Dy
+
+# cru
+CONFIG_CLK_RK3399=3Dy
+
+CONFIG_PL330_DMA=3Dy
+CONFIG_I2C_RK3X=3Dy
+CONFIG_SERIAL_8250_DW=3Dy
+
+# usb
+CONFIG_PHY_ROCKCHIP_INNO_USB2=3Dy
+CONFIG_PHY_ROCKCHIP_TYPEC=3Dy
+
+# ethernet
+CONFIG_NET_VENDOR_STMICRO=3Dy
+CONFIG_STMMAC_ETH=3Dm
+CONFIG_STMMAC_PLATFORM=3Dm
+CONFIG_DWMAC_ROCKCHIP=3Dm
+CONFIG_PHYLIB=3Dm
+
+# display
+CONFIG_ROCKCHIP_DW_HDMI=3Dy
+CONFIG_ROCKCHIP_DW_MIPI_DSI=3Dy
+CONFIG_ROCKCHIP_ANALOGIX_DP=3Dy
+CONFIG_ROCKCHIP_CDN_DP=3Dy
+CONFIG_PHY_ROCKCHIP_DP=3Dy
+CONFIG_DRM_DW_HDMI=3Dm
+CONFIG_DRM_DW_HDMI_I2S_AUDIO=3Dm
+CONFIG_DRM_DW_HDMI_CEC=3Dm
+CONFIG_DRM_DW_MIPI_DSI=3Dm
+CONFIG_DRM_PANFROST=3Dm
+
+# HDMI audio
+CONFIG_DRM_DW_HDMI_AHB_AUDIO=3Dm
+
+CONFIG_VIDEO_DEV=3Dm
+CONFIG_V4L_MEM2MEM_DRIVERS=3Dy
+CONFIG_VIDEO_ROCKCHIP_RGA=3Dm
+
+CONFIG_V4L2_H264=3Dm
+CONFIG_MEDIA_CONTROLLER_REQUEST_API=3Dy
+CONFIG_VIDEO_HANTRO=3Dm
+CONFIG_VIDEO_HANTRO_ROCKCHIP=3Dy
+CONFIG_VIDEO_ROCKCHIP_VDEC=3Dm
+
+# usb
+CONFIG_USB_DWC2=3Dy
+CONFIG_USB_DWC3=3Dy
+CONFIG_USB_DWC3_DUAL_ROLE=3Dy
+
+# sd/mmc
+CONFIG_MMC=3Dy
+CONFIG_MMC_SDHCI=3Dy
+CONFIG_MMC_SDHCI_PLTFM=3Dy
+CONFIG_MMC_DW=3Dy
+CONFIG_MMC_DW_ROCKCHIP=3Dy
+CONFIG_MMC_SDHCI_OF_ARASAN=3Dy
+
+# temperature sensors
+CONFIG_THERMAL=3Dy
+CONFIG_THERMAL_OF=3Dy
+CONFIG_ROCKCHIP_THERMAL=3Dm
+CONFIG_IIO=3Dy
+CONFIG_ROCKCHIP_SARADC=3Dm
diff --git a/recipes-kernel/linux/files/bsp/rockchip/rk3399.scc b/recipes=
-kernel/linux/files/bsp/rockchip/rk3399.scc
new file mode 100644
index 0000000..9b1a88e
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/rk3399.scc
@@ -0,0 +1,5 @@
+# SPDX-License-Identifier: MIT
+
+kconf hardware rk3399.cfg
+
+include rockchip.scc
diff --git a/recipes-kernel/linux/files/bsp/rockchip/rockchip.cfg b/recip=
es-kernel/linux/files/bsp/rockchip/rockchip.cfg
new file mode 100644
index 0000000..05a397d
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/rockchip.cfg
@@ -0,0 +1,50 @@
+CONFIG_CPU_ISOLATION=3Dy
+CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=3Dy
+CONFIG_HZ_250=3Dy
+CONFIG_CPU_IDLE=3Dy
+CONFIG_ARM_CPUIDLE=3Dy
+
+CONFIG_ARCH_ROCKCHIP=3Dy
+CONFIG_COMMON_CLK_ROCKCHIP=3Dy
+CONFIG_REGULATOR=3Dy
+CONFIG_REGULATOR_FIXED_VOLTAGE=3Dy
+CONFIG_REGULATOR_PWM=3Dy
+CONFIG_I2C=3Dy
+CONFIG_FW_LOADER=3Dy
+CONFIG_PHY_ROCKCHIP_EMMC=3Dy
+CONFIG_PINCTRL=3Dy
+CONFIG_PINCTRL_ROCKCHIP=3Dy
+CONFIG_ROCKCHIP_IODOMAIN=3Dy
+CONFIG_ROCKCHIP_PM_DOMAINS=3Dy
+
+CONFIG_SPI=3Dy
+CONFIG_SPI_ROCKCHIP=3Dm
+
+CONFIG_PWM=3Dy
+CONFIG_PWM_ROCKCHIP=3Dy
+
+CONFIG_DRM_KMS_HELPER=3Dm
+CONFIG_DRM_FBDEV_EMULATION=3Dy
+CONFIG_ROCKCHIP_IOMMU=3Dy
+CONFIG_DRM_ROCKCHIP=3Dm
+CONFIG_DRM_BRIDGE=3Dy
+
+CONFIG_SND=3Dy
+CONFIG_SND_SOC=3Dy
+CONFIG_SND_HDA_CODEC_HDMI=3Dm
+CONFIG_SND_SOC_ROCKCHIP=3Dm
+CONFIG_SND_SOC_ROCKCHIP_I2S=3Dm
+CONFIG_SND_SOC_ROCKCHIP_SPDIF=3Dm
+
+CONFIG_NVMEM=3Dy
+CONFIG_ROCKCHIP_EFUSE=3Dm
+
+CONFIG_CPU_FREQ=3Dy
+CONFIG_CPU_FREQ_THERMAL=3Dy
+CONFIG_HWMON=3Dy
+CONFIG_THERMAL_HWMON=3Dy
+
+CONFIG_CRYPTO_HW=3Dy
+CONFIG_CRYPTO_DEV_ROCKCHIP=3Dm
+
+CONFIG_MMC_BLOCK_MINORS=3D32
diff --git a/recipes-kernel/linux/files/bsp/rockchip/rockchip.scc b/recip=
es-kernel/linux/files/bsp/rockchip/rockchip.scc
new file mode 100644
index 0000000..800f105
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/rockchip.scc
@@ -0,0 +1,6 @@
+# SPDX-License-Identifier: MIT
+
+kconf hardware rockchip.cfg
+
+include cfg/dmaengine.scc
+include features/mmc/mmc-block.cfg
diff --git a/recipes-kernel/linux/linux-yocto%.bbappend b/recipes-kernel/=
linux/linux-yocto%.bbappend
index 7702e3f..9658681 100644
--- a/recipes-kernel/linux/linux-yocto%.bbappend
+++ b/recipes-kernel/linux/linux-yocto%.bbappend
@@ -1,3 +1,9 @@
+FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:"
+
+SRC_URI_append =3D "\
+ file://bsp;type=3Dkmeta;subdir=3Dkernel-meta \
+"
+
COMPATIBLE_MACHINE_marsboard-rk3066 =3D "marsboard-rk3066"
COMPATIBLE_MACHINE_rock2-square =3D "rock2-square"
COMPATIBLE_MACHINE_radxarock =3D "radxarock"
--=20
2.30.2


[meta-rockchip][PATCH v7 2/6] linux-yocto: add workaround to disable VOPL usage on HDMI

Yann Dirson
 

From: Yann Dirson <yann@...>

There is a known issue in mainline kernel making the machine unusable
once a HDMI screen is plugged. This patch lets VOPB be alone to use
the HDMI port and avoids the issue while providing wupport for the larges=
t
set of video modes, at the expense of double-screen support.
---
.../files/bsp/rockchip/hdmi-no-vopl.patch | 65 +++++++++++++++++++
.../linux/files/bsp/rockchip/rockchip.scc | 2 +
2 files changed, 67 insertions(+)
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/hdmi-no-vopl.=
patch

diff --git a/recipes-kernel/linux/files/bsp/rockchip/hdmi-no-vopl.patch b=
/recipes-kernel/linux/files/bsp/rockchip/hdmi-no-vopl.patch
new file mode 100644
index 0000000..72ed753
--- /dev/null
+++ b/recipes-kernel/linux/files/bsp/rockchip/hdmi-no-vopl.patch
@@ -0,0 +1,65 @@
+From 92d9cf4e6c2767c8c5aa8d97e684f2f77d950e7d Mon Sep 17 00:00:00 2001
+From: Jonas Karlman <jonas@...>
+Date: Sun, 19 Jul 2020 16:35:11 +0000
+Subject: [PATCH] HACK: dts: rockchip: do not use vopl for hdmi
+Upstream-Status: Inappropriate [other]
+
+---
+ arch/arm/boot/dts/rk3288.dtsi | 9 ---------
+ arch/arm64/boot/dts/rockchip/rk3399.dtsi | 9 ---------
+ 2 files changed, 18 deletions(-)
+
+diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dt=
si
+index 03e86d012edd..746acfac1e92 100644
+--- a/arch/arm/boot/dts/rk3288.dtsi
++++ b/arch/arm/boot/dts/rk3288.dtsi
+@@ -1104,11 +1104,6 @@ vopl_out: port {
+ #address-cells =3D <1>;
+ #size-cells =3D <0>;
+=20
+- vopl_out_hdmi: endpoint@0 {
+- reg =3D <0>;
+- remote-endpoint =3D <&hdmi_in_vopl>;
+- };
+-
+ vopl_out_edp: endpoint@1 {
+ reg =3D <1>;
+ remote-endpoint =3D <&edp_in_vopl>;
+@@ -1249,10 +1244,6 @@ hdmi_in_vopb: endpoint@0 {
+ reg =3D <0>;
+ remote-endpoint =3D <&vopb_out_hdmi>;
+ };
+- hdmi_in_vopl: endpoint@1 {
+- reg =3D <1>;
+- remote-endpoint =3D <&vopl_out_hdmi>;
+- };
+ };
+ };
+ };
+diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/=
dts/rockchip/rk3399.dtsi
+index a855805649ef..418d16b0b648 100644
+--- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
++++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
+@@ -1640,11 +1640,6 @@ vopl_out_edp: endpoint@1 {
+ remote-endpoint =3D <&edp_in_vopl>;
+ };
+=20
+- vopl_out_hdmi: endpoint@2 {
+- reg =3D <2>;
+- remote-endpoint =3D <&hdmi_in_vopl>;
+- };
+-
+ vopl_out_mipi1: endpoint@3 {
+ reg =3D <3>;
+ remote-endpoint =3D <&mipi1_in_vopl>;
+@@ -1816,10 +1811,6 @@ hdmi_in_vopb: endpoint@0 {
+ reg =3D <0>;
+ remote-endpoint =3D <&vopb_out_hdmi>;
+ };
+- hdmi_in_vopl: endpoint@1 {
+- reg =3D <1>;
+- remote-endpoint =3D <&vopl_out_hdmi>;
+- };
+ };
+ };
+ };
diff --git a/recipes-kernel/linux/files/bsp/rockchip/rockchip.scc b/recip=
es-kernel/linux/files/bsp/rockchip/rockchip.scc
index 800f105..4d61509 100644
--- a/recipes-kernel/linux/files/bsp/rockchip/rockchip.scc
+++ b/recipes-kernel/linux/files/bsp/rockchip/rockchip.scc
@@ -4,3 +4,5 @@ kconf hardware rockchip.cfg
=20
include cfg/dmaengine.scc
include features/mmc/mmc-block.cfg
+
+patch hdmi-no-vopl.patch
--=20
2.30.2


[meta-rockchip][PATCH v7 0/6] kmeta BSP for nanopi-m4

Yann Dirson
 

From: Yann Dirson <yann@...>

With this version the most board features work (Wifi requires recent
poky master for a linux-firmware fix), except for the audio jack and
possibly Bluetooth support (the WIP patches are mostly here for
discussion).

I'm not especially happy with the BT support:
- it uses the rkwifibt repo because I don't have any other BT firmware
for this chip
- I was not able to get it to work on the board I have (even with vendor
image with legacy kernel), so I may have a problem with this particular
piece of hardware. At least it can do discover and pairing, maybe wide=
r
testing will be useful.


Changes in v7:
- use "KMETA_EXTERNAL_BSP" and "nopatch" in the BSP definition to get the
patches properly applied, as discussed in
https://lists.yoctoproject.org/g/yocto/topic/82769152
- remove WIP tag from "add workaround to disable VOPL usage on HDMI" than=
ks
to this

Changes in v6:
- support for Wifi and BT

Changes in v5:
- removed AP6356S-related config options, will come later with proper
wifi/bt support
- removed CONFIG_SND_SOC_RK3288_HDMI_ANALOG which turns out not to be
needed for HDMI audio
- new patch to get HDMI to work

Changes in v4:
- install our bsp files in bsp/rockchip/ rather than directly in bsp/
- also add "serial" to MACHINE_FEATURES

Changes in v3:
- relocate the bsp files into files/ so we don't have to add linux-yocto/
to FILESEXTRAPATHS for all other kernels
- removed the "don't force KCONFIG_MODE to alldefconfig" (not needed fina=
lly,
and causing interferences in default setup)
- add "usbhost" to MACHINE_FEATURES to enable lsusb and friends
- better hardware coverage (though still no wifi/bt/audio, and buggy hdmi=
)

Yann Dirson (6):
linux-yocto: add an initial NanoPi-M4 BSP
linux-yocto: add workaround to disable VOPL usage on HDMI
linux-firmware: import variables file for ap4356s firmware from
armbian
NanoPi-M4: activate Wifi support
WIP Import rkwifibt-firmware from vendor's meta-rockchip
WIP NanoPi-M4: activate BT support

conf/machine/include/nanopi-m4.inc | 9 +-
.../files/brcmfmac4356-sdio.txt | 126 ++++++++++++++++++
.../linux-firmware/linux-firmware_%.bbappend | 13 ++
.../files/bsp/rockchip/hdmi-no-vopl.patch | 65 +++++++++
.../files/bsp/rockchip/nanopi-m4-standard.scc | 8 ++
.../files/bsp/rockchip/nanopi-m4-tiny.scc | 8 ++
.../linux/files/bsp/rockchip/nanopi-m4.cfg | 22 +++
.../linux/files/bsp/rockchip/nanopi-m4.scc | 5 +
.../linux/files/bsp/rockchip/rk3399.cfg | 70 ++++++++++
.../linux/files/bsp/rockchip/rk3399.scc | 5 +
.../linux/files/bsp/rockchip/rockchip.cfg | 50 +++++++
.../linux/files/bsp/rockchip/rockchip.scc | 8 ++
recipes-kernel/linux/linux-yocto%.bbappend | 6 +
.../rkwifibt-firmware/files/LICENSE.rockchip | 41 ++++++
.../rkwifibt-firmware/rkwifibt-firmware.bb | 110 +++++++++++++++
15 files changed, 545 insertions(+), 1 deletion(-)
create mode 100644 recipes-kernel/linux-firmware/files/brcmfmac4356-sdio=
.txt
create mode 100644 recipes-kernel/linux-firmware/linux-firmware_%.bbappe=
nd
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/hdmi-no-vopl.=
patch
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-sta=
ndard.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4-tin=
y.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rk3399.cfg
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rk3399.scc
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rockchip.cfg
create mode 100644 recipes-kernel/linux/files/bsp/rockchip/rockchip.scc
create mode 100644 recipes-kernel/rkwifibt-firmware/files/LICENSE.rockch=
ip
create mode 100644 recipes-kernel/rkwifibt-firmware/rkwifibt-firmware.bb

--=20
2.30.2


Opencv build generates Pseudo Abort

Morten Bruun
 

Hi,

When building on the new hardknott branch I often get the error below, so far the solution is to delete the tmp directory. Any suggestions?

debug_logfile: fd 2
pid 6668 [parent 6667], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 6667.
creat for ' <path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/package/usr/lib/stMOsGHa' replaces existing 11214613 [' <path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/package/usr/lib/libopencv_xfeatures2d.so.4.5.2'].
creat for ' <path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/package/usr/lib/stUxt79H' replaces existing 11214665 [' <path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/package/usr/lib/libopencv_sfm.so.4.5.2'].
creat for ' <path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/package/usr/lib/staYWmKL' replaces existing 11214480 [' <path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/package/usr/lib/libopencv_imgproc.so.4.5.2'].
db cleanup for server shutdown, 00:12:21.579
memory-to-file backup complete, 00:12:21.579.
db cleanup finished, 00:12:21.579
debug_logfile: fd 2
pid 4234 [parent 4192], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 4192.
db cleanup for server shutdown, 00:19:10.704
memory-to-file backup complete, 00:19:10.705.
db cleanup finished, 00:19:10.705
debug_logfile: fd 2
pid 17609 [parent 17585], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 17585.
path mismatch [3 links]: ino 12076677 db
' <path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/package/usr/src/debug/opencv/4.5.2-r0/contrib/modules/intensity_transform/include/opencv2/intensity_transform.hpp' req
'<path>/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/opencv/4.5.2-r0/contrib/modules/intensity_transform/include/opencv2/intensity_transform.hpp'.
db cleanup for server shutdown, 10:55:44.549
memory-to-file backup complete, 10:55:44.549.
db cleanup finished, 10:55:44.549

/Morten


Make busybox's syslog.cfg depend on VIRTUAL-RUNTIME_base-utils-syslog #dunfell

Volker Vogelhuber
 

I'm working with Yocto Dunfell. I just wanted to remove syslog
from the busybox package by setting VIRTUAL-RUNTIME_base-utils-syslog
to an empty string. But it seems like the syslog.cfg is added to the SRC_URI
independent of the VIRTUAL-RUNTIME_base-utils-syslog which in turn will
enable syslogd again. Wouldn't it be better to include syslog.cfg in
SRC_URI only if VIRTUAL-RUNTIME_base-utils-syslog is set to busybox-syslog?

So something like

${@["", "file://syslog.cfg"][(d.getVar('VIRTUAL-RUNTIME_base-utils-syslog') == 'busybox-syslog')]}


Re: Understanding kernel patching in linux-yocto

Yann Dirson
 

Le mer. 12 mai 2021 à 20:33, Diego Santa Cruz
<Diego.SantaCruz@...> a écrit :

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Bruce Ashfield via lists.yoctoproject.org
Sent: 12 May 2021 16:25
To: Yann Dirson <yann.dirson@...>
Cc: Yocto discussion list <yocto@...>
Subject: Re: [yocto] Understanding kernel patching in linux-yocto

On Wed, May 12, 2021 at 10:07 AM Yann Dirson
<yann.dirson@...> wrote:

Thanks for those clarifications!

Some additional questions below

Le mer. 12 mai 2021 à 15:19, Bruce Ashfield <bruce.ashfield@...> a
écrit :

On Wed, May 12, 2021 at 7:14 AM Yann Dirson <yann.dirson@blade-
group.com> wrote:

I am currently working on a kmeta BSP for the rockchip-based NanoPI
M4
[1], and I'm wondering how I should be providing kernel patches, as
just add ing "patch" directives in the .scc does not get them applied
unless the particular .scc gets included in KERNEL_FEATURES (see [2]).

From an old thread [3] I understand that the patches from the standard
kmeta snippets are already applied to the tree, and that to get the
patches from my BSP I'd need to reference it explicitly in SRC_URI
(along with using "nopatch" in the right places to avoid the
already-applied patches to get applied twice).

I have the feeling that I'm lacking the rationale behind this, and
would need to understand this better to make things right in this BSP.
Especially:
- at first sight, having the patches both applied to linux-yocto and
referenced in yocto-kernel-cache just to be skipped on parsing looks
like both information duplication and parsing of unused lines
At least some of this is mentioned in the advanced section of the
kernel-dev manual, but I can summarize/reword things here, and
I'm also doing a presentation related to this in the Yocto summit at
the end of this month.

The big thing to remember, is that the configuration and changes
you see in that repository, are not only for yocto purposes. The
concepts and structure pre-date when they were first brought in
to generate reference kernels over 10 years ago (the implementation
has changed, but the concepts are still the same). To this day,
there still are cases that they are used with just a kernel tree and
cross toolchain.

With that in mind, the meta-data is used for many different things

- It organizes patches / features and their configuration into
reusable blocks. At the same time documenting the changes
that we have applied to a tree
- It makes those patches and configuration blocks available to
other kernel trees (for whatever reason).
- It configures the tree during the build process, reusing both
configuration only and patch + configuration blocks
- It is used to generate a history clean tree from scratch for
each new supported kernel. Which is what I do when creating
new linux-yocto-dev references, and the new <version>/standard/*
branches in linux-yocto.
I'd think (and I take your further remarks about workflow as confirming
this), that when upgrading the kernel the best tool would be git-rebase.
Then, regenerating the linux-yocto branches would only be a akin to a
check that the metadata is in sync with the new tree you rebased ?
The best of anything is a matter of opinion. I heavily use git-rebase and
sure, you could use it to do something similar here. But the result is
the same. There's still heavy use of quilt in kernel circles. Workflows
don't change easily, and as long as they work for the maintainer, they
tend to stay put. Asking someone to change their workflow, rarely goes
over well.


If that conclusion is correct, wouldn't it be possible to avoid using the
linux-yocto branches directly, and let all the patches be applied at
do_patch time ? That would be much more similar to the standard
package workflow (and thus lower the barrier for approaching the
kernel packages).
That's something we did in the past, and sure, you can do anything.
But patching hundreds of changes at build time means constant
failures .. again, I've been there and done that. We use similar patches
in many different contexts and optional stackings. You simply cannot
maintain them and stay sane by whacking patches onto the SRC_URI.
The last impression you want when someone builds your kernel is that
they can't even get past the patch phase. So that's a hard no, to how
the reference kernels are maintained (and that hard no has been around
for 11 years now).

Also, we maintain contributed reference BSPs in that same tree, that
are yanking in SDKs from vendors, etc, they are in the thousands of
patches. So you need the tree and the BSP branches to support that.



So why not just drop all the patches in the SRC_URI ? Been there,
done that. It fails spectacularly when you are managing queues of
hundreds of potentially conflicting patches (rt, yaffs, aufs, ... etc, etc)
and then attempting to constantly merge -stable and other kernel
trees into the repository. git is the tool for managing that, not stacks
of patches. You spend your entire life fixing patch errors and refreshing
fuzz (again, been there, done that).

So why not just keep a history and constantly merge new versions
into it ? Been there, done that. You end up with an absolute garbage
history of octopus merges and changes that are completely hidden,
non-obvious and useless for collaborating with other kernel projects.
Try merging a new kernel version into those same big features, it's
nearly impossible and you have a franken-kernel that you end up trying
to support and fix yourself. All the bugs are yours and yours alone.

So that's why there's a repository that tracks the patches and the
configuration and is used for multiple purposes. Keeping the patches
and config blocks separate would just lead to even more errors as
I update one and forget the other, etc, etc. There have been various
incarnations of the tools that also did different things with the patches,
and they weren't skipped, but detected as applied or not on-the-fly,
so there are other historical reasons for the structure as well.

- kernel-yocto.bbclass does its own generic job of locating a proper
BSP using the KMACHINE/KTYPE/KARCH tags in BSP, it looks like
specifying a specific BSP file would just defeat of this: how should I
deal with this case where I'm providing both "standard" and "tiny"
KTYPE's ?
I'm not quite following the question here, so I can try to answer badly
and you can clarify based on my terrible answer.
The answer is indeed quite useful for a question that may not be that clear
:)

The tools can locate your "bsp entry point" / "bsp definition" in
your layer. Either provided by something on the SRC_URI or something
in a kmeta repository (also specified on the SRC_URI). Since
both of those are added to the search paths they check. Those
are just .scc files with a specified KMACHINE/KTYPE that match, and
as you could guess from my first term I used, they are the entry
point into building the configuration queue.

That's where you start inheriting the base configuration(s) and including
feature blocks, etc. Those definitions are exactly the same as the
internal ones in the kernel-cache repository. By default, that located
BSP definition is excluded from inheriting patches .. because as you
noted, it would start trying to re-apply changes to the tree. It is there
to get the configuration blocks, patches come in via other feature
blocks or directly on the SRC_URI.

So in your case, just provide the two .scc file with the proper
defines so they can be located, and you'll get the proper branch
located in the tree, and the base configurations picked up for those
kernel types. You'd supply your BSP specific config by making
a common file and including it in both definitions, and patches by
a KERNEL_FEATURE variable or by specifying them directly on
the SRC_URI (via .patch or via a different .scc file).
That's what I was experimenting with at the same time, and something like
this does indeed produce the expected output:

KERNEL_FEATURES_append = " bsp/rockchip/nanopi-m4-
${LINUX_KERNEL_TYPE}.scc"

However, it seems confusing, as that .scc is precisely the one that's
already selected
and used for the .cfg: it really looks like we're overriding the
default "bsp entry point"
with a value that's already the default, but with a different result.
Yes, that's one way that we've structured things as the tools evolved
to balance external BSP definitions being able to pull in the base
configuration but not patches. There are two runs of the tools, one looks
for patches (and excludes that bsp entry point) and one that builds the
config.queue (and uses the entry point). That's the balance of the multi
use nature of the configuration blocks. I could bury something deeper
in the tools to hide a bit of that, but it will break uses cases and time
has shown that it is brittle.


So my gut feeling ATM is that everything should be much more clear if
specifying the default entry point would have the same effect as leaving
the default be used, ie. having patches be applied in both cases.
The variable KMETA_EXTERNAL_BSPS was created as a knob to
allow an external definition to both be used for patches AND configuration.
But that is for fully exernal BSPs that do not include the base kernel
meta-data, since once you turn that on, you are getting all the patches
and all the configuration .. and will have the patches applied twice.
For what its worth I am using KMETA_EXTERNAL_BSPS in a BSP definition file in an in-recipe kernel metadata tree (but I guess it could be off recipe too), and that metadata tree includes scc files from yocto-kernel-cache, the trick is to add the nopatch tag when including scc files from yocto-kernel-cache for which do not want or need the patches.

With KMETA_EXTERNAL_BSPS was added I switched to that and removed the equivalent of your
KERNEL_FEATURES_append = " bsp/rockchip/nanopi-m4-${LINUX_KERNEL_TYPE}.scc"
that is kind of confusing and includes things twice.
That does look nicer that way, much closer to what I intended, thanks!

Best regards,
--
Yann Dirson <yann@...>
Blade / Shadow -- http://shadow.tech


[meta-zephyr][PATCH] zephyr-kernel-src: switch from master branch to main

Naveen Saini
 

* branch was renamed in upstream repo

It fixes do_fetch failure

Signed-off-by: Naveen Saini <naveen.kumar.saini@...>
---
recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index 8d5f176..dfc2250 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -13,7 +13,7 @@ inherit cmake
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI = "\
- git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=master;name=default \
+ git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=main;name=default \
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \
--
2.17.1


BitBake recipe cache - tasks remain available after removing inheritance #yocto #bitbake

Jindra Sindelar
 

Hello all,

I'm starting with the Yocto project (Zeus) and I made some experiments with the kernel recipe. For one of my assignments, I needed a do_kernel_configme task, but it wasn't provided by our kernel recipe (i.e. not listed in the available tasks). I searched the available layers and found that this task is defined in poky/meta/classes/kernel-yocto.bbclass. Out of fun, I tried to inherit from that class in our kernel recipe and after parsing the recipe again, the do_kernel_configme task was available.
 
Later I decided to revert all my changes and removed the inheritance of kernel-yocto.bbclass. What surprises me is that the do_kernel_configme task remains available in the kernel recipe and I can still successfully run that task. I also tried to remove the content of build/tmp/cache, which, if I understand correctly, is the cache for parsing recipes. After running BitBake again, I could see the recipe was parsed from scratch. But even after that, the do_kernel_configme task still remains available for the kernel recipe.
 
Could anyone explain this behavior? What am I missing here?
Thank you in advance


[meta-security][PATCH 4/4] lkrg-module: update 0.9.1

Armin Kuster
 

LIC_FILES_CHKSUM updated do to yr change and adding new copyrights

Signed-off-by: Armin Kuster <akuster808@...>
---
.../lkrg/{lkrg-module_0.9.0.bb => lkrg-module_0.9.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename recipes-kernel/lkrg/{lkrg-module_0.9.0.bb => lkrg-module_0.9.1.bb} (84%)

diff --git a/recipes-kernel/lkrg/lkrg-module_0.9.0.bb b/recipes-kernel/lkrg/lkrg-module_0.9.1.bb
similarity index 84%
rename from recipes-kernel/lkrg/lkrg-module_0.9.0.bb
rename to recipes-kernel/lkrg/lkrg-module_0.9.1.bb
index dbc195d..287b4e8 100644
--- a/recipes-kernel/lkrg/lkrg-module_0.9.0.bb
+++ b/recipes-kernel/lkrg/lkrg-module_0.9.1.bb
@@ -5,14 +5,14 @@ SECTION = "security"
HOMEPAGE = "https://www.openwall.com/lkrg/"
LICENSE = "GPLv2"

-LIC_FILES_CHKSUM = "file://LICENSE;md5=d931f44a1f4be309bcdac742d7ed92f9"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=5105ead24b08a32954f34cbaa7112432"

DEPENDS = "virtual/kernel elfutils"

SRC_URI = "https://www.openwall.com/lkrg/lkrg-${PV}.tar.gz \
file://makefile_cleanup.patch "

-SRC_URI[sha256sum] = "a997e4d98962c359f3af163bbcfa38a736d2a50bfe35c15065b74cb57f8742bf"
+SRC_URI[sha256sum] = "cabbee1addbf3ae23a584203831e4bd1b730d22bfd1b3e44883214f220b3babd"

S = "${WORKDIR}/lkrg-${PV}"

--
2.25.1


[meta-security][PATCH 3/4] python3-scapy: update to 2.4.5

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@...>
---
.../scapy/{python3-scapy_2.4.4.bb => python3-scapy_2.4.5.bb} | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
rename recipes-security/scapy/{python3-scapy_2.4.4.bb => python3-scapy_2.4.5.bb} (95%)

diff --git a/recipes-security/scapy/python3-scapy_2.4.4.bb b/recipes-security/scapy/python3-scapy_2.4.5.bb
similarity index 95%
rename from recipes-security/scapy/python3-scapy_2.4.4.bb
rename to recipes-security/scapy/python3-scapy_2.4.5.bb
index 23ddfce..8f36520 100644
--- a/recipes-security/scapy/python3-scapy_2.4.4.bb
+++ b/recipes-security/scapy/python3-scapy_2.4.5.bb
@@ -5,9 +5,7 @@ LICENSE = "GPLv2"

LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"

-S = "${WORKDIR}/git"
-
-SRCREV = "95ba5b8504152a1f820bbe679ccf03668cb5118f"
+SRCREV = "32cd7eb0f620d9adf171c48d55514e8326a538d7"
SRC_URI = "git://github.com/secdev/scapy.git \
file://run-ptest"

--
2.25.1


[meta-security][PATCH 2/4] opendnssec: upgrade 2.1.8 -> 2.1.9

Armin Kuster
 

From: Upgrade Helper <akuster808@...>

Signed-off-by: Armin Kuster <akuster808@...>
---
.../opendnssec/{opendnssec_2.1.8.bb => opendnssec_2.1.9.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename recipes-security/opendnssec/{opendnssec_2.1.8.bb => opendnssec_2.1.9.bb} (92%)

diff --git a/recipes-security/opendnssec/opendnssec_2.1.8.bb b/recipes-security/opendnssec/opendnssec_2.1.9.bb
similarity index 92%
rename from recipes-security/opendnssec/opendnssec_2.1.8.bb
rename to recipes-security/opendnssec/opendnssec_2.1.9.bb
index cf6bdbd..2b79609 100644
--- a/recipes-security/opendnssec/opendnssec_2.1.8.bb
+++ b/recipes-security/opendnssec/opendnssec_2.1.9.bb
@@ -10,7 +10,7 @@ SRC_URI = "https://dist.opendnssec.org/source/opendnssec-${PV}.tar.gz \
file://libdns_conf_fix.patch \
"

-SRC_URI[sha256sum] = "900a213103ff19a405e446327fbfcea9ec13e405283d87b6ffc24a10d9a268f5"
+SRC_URI[sha256sum] = "6d1d466c8d7f507f3e665f4bfe4d16a68d6bff9d7c2ab65f852e2b2a821c28b5"

inherit autotools pkgconfig perlnative

--
2.25.1


[meta-security][PATCH 1/4] clamav: upgrade to latest revision

Armin Kuster
 

From: Upgrade Helper <akuster808@...>

Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-scanners/clamav/clamav_0.104.0.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-scanners/clamav/clamav_0.104.0.bb b/recipes-scanners/clamav/clamav_0.104.0.bb
index ce5b0ea..4f20309 100644
--- a/recipes-scanners/clamav/clamav_0.104.0.bb
+++ b/recipes-scanners/clamav/clamav_0.104.0.bb
@@ -8,8 +8,8 @@ DEPENDS = "glibc llvm libtool db openssl zlib curl libxml2 bison pcre2 json-c li

LIC_FILES_CHKSUM = "file://COPYING.txt;beginline=2;endline=3;md5=f7029fbbc5898b273d5902896f7bbe17"

-# May 2nd
-SRCREV = "de0086aa918b79cd22570d0c05977a288b197e23"
+# May 15th
+SRCREV = "fe96de86bb90c489aa509ee9135f776b7a2a7eb4"

SRC_URI = "git://github.com/vrtadmin/clamav-devel;branch=dev/0.104 \
file://clamd.conf \
--
2.25.1


Re: meta-selinux issues. Depending on what I put in my local.conf, I get boot loops or can't log in.

Brian Hutchinson <b.hutchman@...>
 



On Sun, May 16, 2021, 9:07 AM Richard Purdie <richard.purdie@...> wrote:
On Sat, 2021-05-15 at 22:15 -0400, Brian Hutchinson wrote:
>
>
> On Fri, May 14, 2021 at 12:35 AM Yi Zhao <yi.zhao@...> wrote:
> >
> > On 5/14/21 9:40 AM, Brian Hutchinson wrote:
> >  
> > > Hi,
> > >
> > > Pretty new to selinux.  I've worked through a lot of issues to get this far but am stumped at the moment
> > > so any pointers, clues are appreciated.
> > >
> > > I'm trying to add selinux to my custom image.  After running into problems, I decided it was best to
> > > start with building core-image-selinux for my NXP imx8mm-evk board as a reference for getting my custom
> > > image to work.
> > >
> > > I'm using fscl-community-bsp meta-freescale Dunfell release which is building a 5.4.114 kernel.
> > >
> > > My first issues were getting kernel config options right (.config attached).  I kept booting my rootfs
> > > and sestatus would result in selinux not being enabled.
> > >
> > > After getting kernel config somewhat worked out, then I started getting either boot loops or locked out.
> > >
> > > I'll stay focused on my core-image-selinux image as hopefully if I can get it working it will help me
> > > get my custom image working too.
> > >
> > > Here is my last iteration of my local.conf that results in me not being able to log in.  With core-
> > > image-selinux image, it freezes before it gets to login prompt.  On my custom image, I get log in prompt
> > > but when I try to log in a root I get audit messages and dropped back to login prompt.
> > >
> > > local.conf for core-image-selinux:
> > >
> > > MACHINE ??= 'imx8mmevk'
> > >  DISTRO ?= 'poky'
> > >  PACKAGE_CLASSES ?= 'package_rpm'
> > >  EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
> > >  DISTRO_FEATURES_remove = " sysvinit"
> > >  DISTRO_FEATURES_append += " acl xattr pam selinux systemd"
> > >  VIRTUAL-RUNTIME_init_manager = "systemd"
> > >  DISTRO_FEATURES_BACKFILL_CONSIDERED = ""
> > >  PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-mls"
> >
> > You can try refpolicy-mcs or refpolicy-targeted. The mls policy doesn't work for systemed on dunfell.
> >  
> > //Yi
> >
>
>  Thank you very much for that!  I made that change to my core-image-selinux build and it worked!  When it
> booted I saw a systemd process take a while to finish, I assume that was the relable process.  And when I
> logged in as root, there is a significant delay before being logged in, not sure what is going on there.
>
> When I made the same change to my imx8mm-evk core-image-base image with selinux added, I saw the same
> systemd process run but it didn't take quite as long and it made the system reboot.  Once it rebooted I did
> get a login prompt but it won't let me login as root.  So something is still miss-configured and still at a
> loss as to what to look at next.

I know nothing about this but I was surprised you were using busybox login 
utilities with selinux. I'm not sure if that is well tested or not...

Cheers,

Richard

Hey Richard,  good to hear from you again (last was ELC-E).

I really didn't change anything except add selinux layer and (attempt) to follow instructions on meta-selinux README.

I guess we're the blind leading the blind.  This is my first attempt to incorporate selinux into custom image so be gentle ;).

Regards,

Brian



Re: meta-selinux issues. Depending on what I put in my local.conf, I get boot loops or can't log in.

Richard Purdie
 

On Sat, 2021-05-15 at 22:15 -0400, Brian Hutchinson wrote:


On Fri, May 14, 2021 at 12:35 AM Yi Zhao <yi.zhao@...> wrote:

On 5/14/21 9:40 AM, Brian Hutchinson wrote:
 
Hi,

Pretty new to selinux.  I've worked through a lot of issues to get this far but am stumped at the moment
so any pointers, clues are appreciated.

I'm trying to add selinux to my custom image.  After running into problems, I decided it was best to
start with building core-image-selinux for my NXP imx8mm-evk board as a reference for getting my custom
image to work.

I'm using fscl-community-bsp meta-freescale Dunfell release which is building a 5.4.114 kernel.

My first issues were getting kernel config options right (.config attached).  I kept booting my rootfs
and sestatus would result in selinux not being enabled.

After getting kernel config somewhat worked out, then I started getting either boot loops or locked out.

I'll stay focused on my core-image-selinux image as hopefully if I can get it working it will help me
get my custom image working too.

Here is my last iteration of my local.conf that results in me not being able to log in.  With core-
image-selinux image, it freezes before it gets to login prompt.  On my custom image, I get log in prompt
but when I try to log in a root I get audit messages and dropped back to login prompt.

local.conf for core-image-selinux:

MACHINE ??= 'imx8mmevk'
 DISTRO ?= 'poky'
 PACKAGE_CLASSES ?= 'package_rpm'
 EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
 DISTRO_FEATURES_remove = " sysvinit"
 DISTRO_FEATURES_append += " acl xattr pam selinux systemd"
 VIRTUAL-RUNTIME_init_manager = "systemd"
 DISTRO_FEATURES_BACKFILL_CONSIDERED = ""
 PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-mls"
You can try refpolicy-mcs or refpolicy-targeted. The mls policy doesn't work for systemed on dunfell.
 
//Yi
 Thank you very much for that!  I made that change to my core-image-selinux build and it worked!  When it
booted I saw a systemd process take a while to finish, I assume that was the relable process.  And when I
logged in as root, there is a significant delay before being logged in, not sure what is going on there.

When I made the same change to my imx8mm-evk core-image-base image with selinux added, I saw the same
systemd process run but it didn't take quite as long and it made the system reboot.  Once it rebooted I did
get a login prompt but it won't let me login as root.  So something is still miss-configured and still at a
loss as to what to look at next.
I know nothing about this but I was surprised you were using busybox login 
utilities with selinux. I'm not sure if that is well tested or not...

Cheers,

Richard


[yocto-autobuilder-helper] [PATCH] config.json: Set XZ limits to more reasonable values on autobuilder

Richard Purdie
 

The autobuilders have 128GB memory, we don't want them using 50% which is
the default, 5% should be enough. Also limit the number of threads down
from 48 to something reasonable. This may be partly causing some of our
performance issues?

Signed-off-by: Richard Purdie <richard.purdie@...>
---
config.json | 2 ++
1 file changed, 2 insertions(+)

diff --git a/config.json b/config.json
index 6533dab..cf62815 100644
--- a/config.json
+++ b/config.json
@@ -45,6 +45,8 @@
"BB_GENERATE_MIRROR_TARBALLS = '1'",
"BB_NUMBER_THREADS = '16'",
"PARALLEL_MAKE = '-j 16'",
+ "XZ_MEMLIMIT = '5%'",
+ "XZ_THREADS = '8'",
"BB_TASK_NICE_LEVEL = '5'",
"BB_TASK_NICE_LEVEL_task-testimage = '0'",
"BB_TASK_IONICE_LEVEL = '2.7'",
--
2.30.2


Re: meta-selinux issues. Depending on what I put in my local.conf, I get boot loops or can't log in.

Brian Hutchinson <b.hutchman@...>
 



On Fri, May 14, 2021 at 12:35 AM Yi Zhao <yi.zhao@...> wrote:


On 5/14/21 9:40 AM, Brian Hutchinson wrote:
Hi,

Pretty new to selinux.  I've worked through a lot of issues to get this far but am stumped at the moment so any pointers, clues are appreciated.

I'm trying to add selinux to my custom image.  After running into problems, I decided it was best to start with building core-image-selinux for my NXP imx8mm-evk board as a reference for getting my custom image to work.

I'm using fscl-community-bsp meta-freescale Dunfell release which is building a 5.4.114 kernel.

My first issues were getting kernel config options right (.config attached).  I kept booting my rootfs and sestatus would result in selinux not being enabled.

After getting kernel config somewhat worked out, then I started getting either boot loops or locked out.

I'll stay focused on my core-image-selinux image as hopefully if I can get it working it will help me get my custom image working too.

Here is my last iteration of my local.conf that results in me not being able to log in.  With core-image-selinux image, it freezes before it gets to login prompt.  On my custom image, I get log in prompt but when I try to log in a root I get audit messages and dropped back to login prompt.

local.conf for core-image-selinux:

MACHINE ??= 'imx8mmevk'
DISTRO ?= 'poky'
PACKAGE_CLASSES ?= 'package_rpm'
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
DISTRO_FEATURES_remove = " sysvinit"
DISTRO_FEATURES_append += " acl xattr pam selinux systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = ""
PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-mls"


You can try refpolicy-mcs or refpolicy-targeted. The mls policy doesn't work for systemed on dunfell.

//Yi

 
Thank you very much for that!  I made that change to my core-image-selinux build and it worked!  When it booted I saw a systemd process take a while to finish, I assume that was the relable process.  And when I logged in as root, there is a significant delay before being logged in, not sure what is going on there.

When I made the same change to my imx8mm-evk core-image-base image with selinux added, I saw the same systemd process run but it didn't take quite as long and it made the system reboot.  Once it rebooted I did get a login prompt but it won't let me login as root.  So something is still miss-configured and still at a loss as to what to look at next.

Will provide the startup logs below:

First, my local.conf:

MACHINE ??= 'imx8mmevk'
DISTRO ?= 'poky'
PACKAGE_CLASSES ?= 'package_rpm'
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
DISTRO_FEATURES_remove = " sysvinit"
DISTRO_FEATURES_append += " acl xattr pam selinux systemd"
#PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-minimum"
PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-mcs"
VIRTUAL-RUNTIME_init_manager = "systemd"
#DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
DISTRO_FEATURES_BACKFILL_CONSIDERED = ""
#VIRTUAL-RUNTIME_initscripts = ""
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
#IMAGE_INSTALL_append = " packagegroup-core-selinux"
CORE_IMAGE_EXTRA_INSTALL += " packagegroup-core-selinux"
IMAGE_FSTYPES += " tar.bz2 ext4 wic.bz2 wic.bmap"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "\
   STOPTASKS,${TMPDIR},1G,100K \
   STOPTASKS,${DL_DIR},1G,100K \
   STOPTASKS,${SSTATE_DIR},1G,100K \
   STOPTASKS,/tmp,100M,100K \
   ABORT,${TMPDIR},100M,1K \
   ABORT,${DL_DIR},100M,1K \
   ABORT,${SSTATE_DIR},100M,1K \
   ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
CONF_VERSION = "1"

DL_DIR ?= "${BSPDIR}/downloads/"
ACCEPT_FSL_EULA = "1"

This is first boot of my core-image-base build that rebooted:

[    1.202737] usbserial: USB Serial support registered for hp4x
[    1.208499] usbserial: USB Serial support registered for suunto
[    1.214436] usbserial: USB Serial support registered for siemens_mpi
[    1.223136] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/soc@0:bus@30000000/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[    1.238115] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    1.244381] i2c /dev entries driver
[    1.252319] imx2-wdt 30280000.watchdog: timeout 60 sec (nowayout=0)
[    1.258858] Bluetooth: HCI UART driver ver 2.3
[    1.263316] Bluetooth: HCI UART protocol H4 registered
[    1.268461] Bluetooth: HCI UART protocol BCSP registered
[    1.273797] Bluetooth: HCI UART protocol LL registered
[    1.278941] Bluetooth: HCI UART protocol ATH3K registered
[    1.284357] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    1.290707] Bluetooth: HCI UART protocol Broadcom registered
[    1.296391] Bluetooth: HCI UART protocol QCA registered
[    1.303363] sdhci: Secure Digital Host Controller Interface driver
[    1.309555] sdhci: Copyright(c) Pierre Ossman
[    1.314079] Synopsys Designware Multimedia Card Interface Driver
[    1.320593] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.326995] mmc1: CQHCI version 5.10
[    1.331061] mmc2: CQHCI version 5.10
[    1.366826] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.376124] ledtrig-cpu: registered to indicate activity on CPUs
[    1.383257] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    1.390030] caam 30900000.crypto: job rings = 3, qi = 0
[    1.404678] caam algorithms registered in /proc/crypto
[    1.410573] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto
[    1.420094] caam_jr 30901000.jr: registering rng-caam
[    1.430401] caam-snvs 30370000.caam-snvs: can't get snvs clock
[    1.436287] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state
[    1.444721] usbcore: registered new interface driver usbhid
[    1.450298] usbhid: USB HID core driver
[    1.456169] No fsl,qman node
[    1.459065] Freescale USDPAA process driver
[    1.463252] fsl-usdpaa: no region found
[    1.467091] Freescale USDPAA process IRQ driver
[    1.475141] optee: probing for conduit method from DT.
[    1.480307] optee: revision 3.2 (6a22e6e8)
[    1.481414] optee: dynamic shared memory is enabled
[    1.490624] optee: initialized driver
[    1.496444] mmc2: Command Queue Engine enabled
[    1.497954] wm8524-codec audio-codec: Failed to get mute line: -517
[    1.500937] mmc2: new HS400 Enhanced strobe MMC card at address 0001
[    1.507662] OF: /sound-bt-sco/simple-audio-card,cpu: could not get #sound-dai-cells for /soc@0/bus@30000000/sai@30020000
[    1.514447] mmcblk2: mmc2:0001 DG4016 7.49 GiB  
[    1.524427] asoc-simple-card sound-bt-sco: parse error -22
[    1.529081] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.534459] asoc-simple-card: probe of sound-bt-sco failed with error -22
[    1.540491] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.553232] mmcblk2gp0: mmc2:0001 DG4016 partition 4 3.52 GiB
[    1.559457] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB, chardev (237:0)
[    1.561232] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    1.568692]  mmcblk2: p1 p2
[    1.578981] NET: Registered protocol family 26
[    1.580349]  mmcblk2gp0: p1 p2
[    1.583939] NET: Registered protocol family 10
[    1.592304] Segment Routing with IPv6
[    1.596030] NET: Registered protocol family 17
[    1.601163] Bluetooth: RFCOMM TTY layer initialized
[    1.606055] Bluetooth: RFCOMM socket layer initialized
[    1.611235] Bluetooth: RFCOMM ver 1.11
[    1.614998] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    1.620315] Bluetooth: BNEP filters: protocol multicast
[    1.625547] Bluetooth: BNEP socket layer initialized
[    1.630517] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    1.636443] Bluetooth: HIDP socket layer initialized
[    1.641440] 8021q: 802.1Q VLAN Support v1.8
[    1.645644] lib80211: common routines for IEEE802.11 drivers
[    1.651428] 9pnet: Installing 9P2000 support
[    1.655735] tsn generic netlink module v1 init...
[    1.660501] Key type dns_resolver registered
[    1.665522] registered taskstats version 1
[    1.669630] Loading compiled-in X.509 certificates
[    1.698859] usb_phy_generic usbphynop1: usbphynop1 supply vcc not found, using dummy regulator
[    1.707660] usb_phy_generic usbphynop2: usbphynop2 supply vcc not found, using dummy regulator
[    1.780652] random: fast init done
[    1.788737] LDO6: supplied by regulator-dummy
[    1.793242] i2c i2c-0: IMX I2C adapter registered
[    1.799240] i2c i2c-1: IMX I2C adapter registered
[    1.805114] i2c i2c-2: IMX I2C adapter registered
[    1.810936] i2c i2c-3: IMX I2C adapter registered
[    1.815964] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 2 mkt segment 2 supported-hw 0x4 0x4
[    1.828449] mmc1: CQHCI version 5.10
[    1.832108] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    1.869469] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    1.878135] imx8mm-pinctrl 30330000.pinctrl: pin MX8MM_IOMUXC_I2C4_SDA already requested by 30a50000.i2c; cannot claim for audio-codec
[    1.890254] imx8mm-pinctrl 30330000.pinctrl: pin-140 (audio-codec) status -22
[    1.897398] imx8mm-pinctrl 30330000.pinctrl: could not request pin 140 (MX8MM_IOMUXC_I2C4_SDA) from group gpiowlfgrp  on device 30330000.pinctrl
[    1.910356] wm8524-codec audio-codec: Error applying setting, reverse things back
[    1.917856] wm8524-codec: probe of audio-codec failed with error -22
[    1.932525] input: bd718xx-pwrkey as /devices/platform/soc@0/soc@0:bus@30800000/30a20000.i2c/i2c-0/0-004b/gpio-keys.1.auto/input/input1
[    1.946584] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T01:19:14 UTC (4754)
[    1.956250] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    1.967556] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    1.974159] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    1.979590] ALSA device list:
[    1.982781] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[    1.985744]   No soundcards found.
[    2.004502] EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.012659] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.019978] devtmpfs: mounted
[    2.023749] Freeing unused kernel memory: 2880K
[    2.040759] Run /sbin/init as init process
[    2.114222] audit: type=1404 audit(4754.664:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[    2.252102] SELinux:  Permission watch in class filesystem not defined in policy.
[    2.259701] SELinux:  Permission watch in class file not defined in policy.
[    2.266668] SELinux:  Permission watch_mount in class file not defined in policy.
[    2.274162] SELinux:  Permission watch_sb in class file not defined in policy.
[    2.281386] SELinux:  Permission watch_with_perm in class file not defined in policy.
[    2.289225] SELinux:  Permission watch_reads in class file not defined in policy.
[    2.296721] SELinux:  Permission watch in class dir not defined in policy.
[    2.303606] SELinux:  Permission watch_mount in class dir not defined in policy.
[    2.311013] SELinux:  Permission watch_sb in class dir not defined in policy.
[    2.318158] SELinux:  Permission watch_with_perm in class dir not defined in policy.
[    2.325902] SELinux:  Permission watch_reads in class dir not defined in policy.
[    2.333318] SELinux:  Permission watch in class lnk_file not defined in policy.
[    2.340628] SELinux:  Permission watch_mount in class lnk_file not defined in policy.
[    2.348467] SELinux:  Permission watch_sb in class lnk_file not defined in policy.
[    2.356038] SELinux:  Permission watch_with_perm in class lnk_file not defined in policy.
[    2.364224] SELinux:  Permission watch_reads in class lnk_file not defined in policy.
[    2.372061] SELinux:  Permission watch in class chr_file not defined in policy.
[    2.379380] SELinux:  Permission watch_mount in class chr_file not defined in policy.
[    2.387211] SELinux:  Permission watch_sb in class chr_file not defined in policy.
[    2.394790] SELinux:  Permission watch_with_perm in class chr_file not defined in policy.
[    2.402968] SELinux:  Permission watch_reads in class chr_file not defined in policy.
[    2.410806] SELinux:  Permission watch in class blk_file not defined in policy.
[    2.418122] SELinux:  Permission watch_mount in class blk_file not defined in policy.
[    2.425962] SELinux:  Permission watch_sb in class blk_file not defined in policy.
[    2.433532] SELinux:  Permission watch_with_perm in class blk_file not defined in policy.
[    2.441718] SELinux:  Permission watch_reads in class blk_file not defined in policy.
[    2.449558] SELinux:  Permission watch in class sock_file not defined in policy.
[    2.456964] SELinux:  Permission watch_mount in class sock_file not defined in policy.
[    2.464881] SELinux:  Permission watch_sb in class sock_file not defined in policy.
[    2.472547] SELinux:  Permission watch_with_perm in class sock_file not defined in policy.
[    2.480811] SELinux:  Permission watch_reads in class sock_file not defined in policy.
[    2.488743] SELinux:  Permission watch in class fifo_file not defined in policy.
[    2.496140] SELinux:  Permission watch_mount in class fifo_file not defined in policy.
[    2.504066] SELinux:  Permission watch_sb in class fifo_file not defined in policy.
[    2.511724] SELinux:  Permission watch_with_perm in class fifo_file not defined in policy.
[    2.519987] SELinux:  Permission watch_reads in class fifo_file not defined in policy.
[    2.528238] SELinux: the above unknown classes and permissions will be allowed
[    2.535473] SELinux:  policy capability network_peer_controls=1
[    2.541403] SELinux:  policy capability open_perms=1
[    2.546368] SELinux:  policy capability extended_socket_class=1
[    2.552297] SELinux:  policy capability always_check_network=0
[    2.558132] SELinux:  policy capability cgroup_seclabel=1
[    2.563539] SELinux:  policy capability nnp_nosuid_transition=1
[    2.611027] audit: type=1403 audit(4755.160:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
[    2.618342] systemd[1]: Successfully loaded SELinux policy in 506.080ms.
[    2.644224] systemd[1]: System time before build time, advancing clock.
[    2.729021] systemd[1]: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 67.016ms.
[    2.748329] systemd[1]: systemd 244.5+ running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR -SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid)
[    2.770341] systemd[1]: Detected architecture arm64.

Welcome to Poky (Yocto Project Reference Distro) 3.1.7 (dunfell)!

[    2.818431] systemd[1]: Set hostname to <imx8mmevk>.
[    2.826687] random: systemd: uninitialized urandom read (16 bytes read)
[    2.833351] systemd[1]: Initializing machine ID from random generator.
[    2.840377] systemd[1]: Installed transient /etc/machine-id file.
[    3.043231] random: systemd: uninitialized urandom read (16 bytes read)
[    3.050040] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[    3.062433] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[    3.073214] systemd[1]: Created slice system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[    3.092834] random: systemd: uninitialized urandom read (16 bytes read)
[    3.101077] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[    3.121748] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    3.142242] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Dispatch Password ��…ts to Console Directory Watch.
[    3.169455] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password R��…uests to Wall Directory Watch.
[    3.192930] systemd[1]: Reached target Paths.
[  OK  ] Reached target Paths.
[    3.213846] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    3.232996] systemd[1]: Reached target Slices.
[  OK  ] Reached target Slices.
[    3.252886] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    3.277486] systemd[1]: Listening on RPCbind Server Activation Socket.
[  OK  ] Listening on RPCbind Server Activation Socket.
[    3.300937] systemd[1]: Reached target RPC Port Mapper.
[  OK  ] Reached target RPC Port Mapper.
[    3.323791] systemd[1]: Listening on Syslog Socket.
[  OK  ] Listening on Syslog Socket.
[    3.345949] systemd[1]: Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[    3.370655] systemd[1]: systemd-journald-audit.socket: Failed to create listening socket (audit 1): Operation not permitted
[    3.370910] audit: type=1400 audit(1600598638.724:4): avc:  denied  { audit_read } for  pid=1 comm="systemd" capability=37  scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=capability2 permissive=0
[    3.381893] systemd[1]: systemd-journald-audit.socket: Failed to listen on sockets: Operation not permitted
[    3.412415] systemd[1]: systemd-journald-audit.socket: Failed with result 'resources'.
[    3.420654] systemd[1]: Failed to listen on Journal Audit Socket.
[FAILED] Failed to listen on Journal Audit Socket.
See 'systemctl status systemd-journald-audit.socket' for details.
[    3.457659] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    3.481864] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    3.501997] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[    3.527382] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    3.549791] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    3.573120] systemd[1]: Mounting Huge Pages File System...
        Mounting Huge Pages File System...
[    3.596907] systemd[1]: Mounting POSIX Message Queue File System...
        Mounting POSIX Message Queue File System...
[    3.621131] systemd[1]: Mounting Kernel Debug File System...
        Mounting Kernel Debug File System...
[    3.646188] systemd[1]: Mounting Temporary Directory (/tmp)...
        Mounting Temporary Directory (/tmp)...
[    3.669201] systemd[1]: Starting Create list of static device nodes for the current kernel...
        Starting Create list of st��…odes for the current kernel...
[    3.696449] systemd[1]: Starting Start psplash boot splash screen...
        Starting Start psplash boot splash screen...
[    3.728875] systemd[1]: Starting RPC Bind...
        Starting RPC Bind...
[    3.752279] systemd[1]: Starting SELinux autorelabel service loading...
        Starting SELinux autorelabel service loading...
[    3.766897] audit: type=1404 audit(1600598639.120:5): enforcing=0 old_enforcing=1 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[    3.788003] systemd[1]: Starting SELinux init for /dev service loading...
        Starting SELinux init for /dev service loading...
[    3.812966] systemd[1]: Starting File System Check on Root Device...
        Starting File System Check on Root Device...
[    3.838411] systemd[1]: Starting Journal Service...
        Starting Journal Servi[    3.845479] systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
ce...
[    3.856066] systemd[1]: Condition check resulted in FUSE Control File System being skipped.
[    3.871557] systemd[1]: Mounting Kernel Configuration File System...
        Mounting Kernel Configuration File System...
[    3.889392] systemd[1]: Starting Apply Kernel Variables...
        Starting Apply Kernel Variables...
[    3.900053] systemd[1]: Starting udev Coldplug all Devices...
        Starting udev Coldplug all Devices...
[    3.911256] systemd[1]: Started RPC Bind.
[  OK  ] Started     3.916791] systemd[1]: Mounted Huge Pages File System.
;39mRPC Bind.
[  OK  ] Mounted Huge Pages File System.
[    3.953835] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Started Create list of sta��… nodes for the current kernel.
[FAILED] Failed to start Start psplash boot splash screen.
See 'systemctl status psplash-start.service' for details.
[DEPEND] Dependency failed for Star��…progress communication helper.
[  OK  ] Started SELinux init for /dev service loading.
[  OK  ] Started File System Check on Root Device.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Apply Kernel Variables.
        Starting Remount Root and Kernel File Systems...
[    4.193492] EXT4-fs (mmcblk2p2): re-mounted. Opts: (null)
[  OK  ] Started Remount Root and Kernel File Systems.
        Starting Flush Journal to Persistent Storage...
[    4.243991] systemd-journald[321]: Received client request to flush runtime journal.
        Starting Create System Users...
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Create System Users.
        Starting Create Static Device Nodes in /dev...
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
        Mounting /var/volatile...
        Starting udev Kernel Device Manager...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Mounted /var/volatile.
        Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
        Starting Rebuild Dynamic Linker Cache...
        Starting SELinux init service loading...
        Starting Commit a transient machine-id on disk...
        Starting Create Volatile Files and Directories...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started SELinux init service loading.
[  OK  ] Started Commit a transient machine-id on disk.
[  OK  ] Started Rebuild Dynamic Linker Cache.
        Starting Network Service...
[  OK  ] Started Create Volatile Files and Directories.
        Starting Run pending postinsts...
        Starting Rebuild Journal Catalog...
        Starting Network Time Synchronization...
        Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Network Service.
[  OK  ] Started Rebuild Journal Catalog.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Run pending postinsts.
        Starting Network Name Resolution...
        Starting Update is Completed...
[  OK  ] Started Update is Completed.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Set.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network.
[  OK  ] Reached target Host and Network Name Lookups.
[    5.399674] audit: type=1400 audit(1600598640.748:6): avc:  denied  { module_load } for  pid=648 comm="systemd-udevd" path="/lib/modules/5.4.114+gf9a9b58ef7cc/kernel/arch/arm64/crypto/crct10dif-ce.ko" dev="mmcblk2p2" ino=577 scontext=system_u:system_r:1
[    5.446185] Generic PHY fixed-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:00, irq=POLL)
[    5.461534] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[    5.474253] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    9.012772] random: crng init done
[    9.016184] random: 7 urandom warning(s) missed due to ratelimiting
[  OK  ] Started Load/Save Random Seed.
[   ***] A start job is running for SELinux ��…l service loading (27s / no limit)
[   30.793551] audit: type=1107 audit(1621001013.725:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { start } for auid=n/a uid=0 gid=0 path="/lib/systemd/system/reboot.target" cmdline="" scontext=syste1
[   30.793551]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[   30.831206] audit: type=1107 audit(1621001013.741:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { status } for auid=n/a uid=0 gid=0 path="/lib/systemd/system/reboot.target" cmdline="" scontext=syst1
[  OK  ] Stopped target Host and Network Name Lookups.
[  OK  ] Stopped target RPC Port Mapper.
[  OK  ] Stopped target System Time Synchronized.
[  OK  ] Stopped target System Time Set.
        Stopping Load/Save Random Seed...
[  OK  ] Removed slice system-getty.slice.
[  OK  ] Removed slice system-serial\x2dgetty.slice.
[  OK  ] Stopped target Network.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped Dispatch Password ��…ts to Console Directory Watch.
[  OK  ] Stopped Forward Password R��…uests to Wall Directory Watch.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Closed Syslog Socket.
[  OK  ] Stopped Commit a transient machine-id on disk.
        Stopping Network Name Resolution...
        Stopping Network Time Synchronization...
[  OK  ] Stopped Update is Completed.
[  OK  ] Stopped Rebuild Dynamic Linker Cache.
[  OK  ] Stopped Rebuild Journal Catalog.
        Stopping Update UTMP about System Boot/Shutdown...
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Network Name Resolution.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Started SELinux autorelabel service loading.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
        Stopping Network Service...
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
        Unmounting Temporary Directory (/tmp)...
        Unmounting /var/volatile...
[  OK  ] Stopped Network Service.
[  OK  ] Unmounted Temporary Directory (/tmp).
[  OK  ] Unmounted /var/volatile.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped target Swap.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped File System Check on Root Device.
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
[  OK  ] Started Reboot.
[  OK  ] Reached target Reboot.
[   31.749936] watchdog: watchdog0: watchdog did not stop!
[   31.772995] systemd-shutdown[1]: Syncing filesystems and block devices.
[   31.779924] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[   31.794460] systemd-journald[321]: Received SIGTERM from PID 1 (systemd-shutdow).
[   31.815284] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[   31.828512] systemd-shutdown[1]: Hardware watchdog 'imx2+ watchdog', version 0
[   31.837401] systemd-shutdown[1]: Unmounting file systems.
[   31.844851] [872]: Remounting '/' read-only in with options 'seclabel'.
[   31.861839] EXT4-fs (mmcblk2p2): re-mounted. Opts:  
[   31.869728] systemd-shutdown[1]: All filesystems unmounted.
[   31.875392] systemd-shutdown[1]: Deactivating swaps.
[   31.880533] systemd-shutdown[1]: All swaps deactivated.
[   31.885835] systemd-shutdown[1]: Detaching loop devices.
[   31.893753] systemd-shutdown[1]: All loop devices detached.
[   31.899354] systemd-shutdown[1]: Detaching DM devices.
[   31.904814] systemd-shutdown[1]: All DM devices detached.
[   31.910272] systemd-shutdown[1]: All filesystems, swaps, loop devices and DM devices detached.
[   31.924538] systemd-shutdown[1]: Syncing filesystems and block devices.
[   31.931348] systemd-shutdown[1]: Rebooting.
[   31.935672] imx-sdma 302b0000.dma-controller: external firmware not found, using ROM firmware
[   31.935695] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware
[   31.937033] kvm: exiting hardware virtualization
[   31.944226] cfg80211: failed to load regulatory.db
[   31.958656] imx-sdma 302c0000.dma-controller: loaded firmware 4.5
[   32.009904] imx2-wdt 30280000.watchdog: Device shutdown: Expect reboot!
[   32.017454] reboot: Restarting system


This is after the reboot.   I make it to login prompt but can't log in:

Thanks for any pointers as to what to look into next ... in the meantime I'm continuing to dig.

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.4.114+gf9a9b58ef7cc (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Thu Apr 22 11:48:16 UTC 2021
[    0.000000] Machine model: FSL i.MX8MM EVK board
[    0.000000] earlycon: ec_imx6q0 at MMIO 0x0000000030890000 (options '115200')
[    0.000000] printk: bootconsole [ec_imx6q0] enabled
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000078000000, size 640 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbdbe0500-0xbdbe1fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA32    [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000b7ffffff]
[    0.000000]   node   0: [mem 0x00000000b8000000-0x00000000b83fffff]
[    0.000000]   node   0: [mem 0x00000000b8400000-0x00000000bdffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 24 pages/cpu s58904 r8192 d31208 u98304
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 508032
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc1,115200 earlycon=ec_imx6q,0x30890000,115200 rootwait ro root=/dev/mmcblk2p2 rauc.slot=B
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 1336216K/2064384K available (16508K kernel code, 1234K rwdata, 6480K rodata, 2880K init, 1038K bss, 72808K reserved, 655360K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from start_kernel+0x2b8/0x43c with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns
[    0.008456] Console: colour dummy device 80x25
[    0.012579] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.022844] pid_max: default: 32768 minimum: 301
[    0.027543] LSM: Security Framework initializing
[    0.032140] SELinux:  Initializing.
[    0.035680] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.043062] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.052066] ASID allocator initialised with 32768 entries
[    0.056439] rcu: Hierarchical SRCU implementation.
[    0.062122] EFI services will not be available.
[    0.065890] smp: Bringing up secondary CPUs ...
[    0.070649] Detected VIPT I-cache on CPU1
[    0.070673] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.070704] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.071100] Detected VIPT I-cache on CPU2
[    0.071116] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.071134] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.071499] Detected VIPT I-cache on CPU3
[    0.071514] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.071530] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.071581] smp: Brought up 1 node, 4 CPUs
[    0.126889] SMP: Total of 4 processors activated.
[    0.131607] CPU features: detected: 32-bit EL0 Support
[    0.136780] CPU features: detected: CRC32 instructions
[    0.148802] CPU: All CPU(s) started at EL2
[    0.150074] alternatives: patching kernel code
[    0.155989] devtmpfs: initialized
[    0.163606] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.170559] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.194288] pinctrl core: initialized pinctrl subsystem
[    0.197376] DMI not present or invalid.
[    0.200809] NET: Registered protocol family 16
[    0.212008] DMA: preallocated 256 KiB pool for atomic allocations
[    0.215305] audit: initializing netlink subsys (disabled)
[    0.220944] audit: type=2000 audit(0.160:1): state=initialized audit_enabled=0 res=1
[    0.228511] cpuidle: using governor menu
[    0.232941] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.240026] Serial: AMBA PL011 UART driver
[    0.243412] imx mu driver is registered.
[    0.247304] imx rpmsg driver is registered.
[    0.256464] imx8mm-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.277600] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.281486] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.288213] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.294951] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.302495] cryptd: max_cpu_qlen set to 1000
[    0.308932] ACPI: Interpreter disabled.
[    0.310658] iommu: Default domain type: Translated  
[    0.314960] vgaarb: loaded
[    0.317804] SCSI subsystem initialized
[    0.321602] usbcore: registered new interface driver usbfs
[    0.326845] usbcore: registered new interface driver hub
[    0.332164] usbcore: registered new device driver usb
[    0.338385] mc: Linux media interface: v0.10
[    0.341527] videodev: Linux video capture interface: v2.00
[    0.347076] pps_core: LinuxPPS API ver. 1 registered
[    0.352005] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@...>
[    0.361200] PTP clock support registered
[    0.365247] EDAC MC: Ver: 3.0.0
[    0.368995] No BMan portals available!
[    0.372270] QMan: Allocated lookup table at (____ptrval____), entry count 65537
[    0.379649] No QMan portals available!
[    0.383534] No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree
[    0.389567] FPGA manager framework
[    0.392686] Advanced Linux Sound Architecture Driver Initialized.
[    0.399111] Bluetooth: Core ver 2.22
[    0.402332] NET: Registered protocol family 31
[    0.406784] Bluetooth: HCI device and connection manager initialized
[    0.413175] Bluetooth: HCI socket layer initialized
[    0.418071] Bluetooth: L2CAP socket layer initialized
[    0.423152] Bluetooth: SCO socket layer initialized
[    0.428742] clocksource: Switched to clocksource arch_sys_counter
[    0.434312] VFS: Disk quotas dquot_6.6.0
[    0.438149] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.445171] pnp: PnP ACPI: disabled
[    0.454139] thermal_sys: Registered thermal governor 'step_wise'
[    0.454143] thermal_sys: Registered thermal governor 'power_allocator'
[    0.457634] NET: Registered protocol family 2
[    0.468576] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    0.476866] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.484900] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.492368] TCP: Hash tables configured (established 16384 bind 16384)
[    0.498788] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.505483] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.512778] NET: Registered protocol family 1
[    0.517326] RPC: Registered named UNIX socket transport module.
[    0.522951] RPC: Registered udp transport module.
[    0.527670] RPC: Registered tcp transport module.
[    0.532392] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.539245] PCI: CLS 0 bytes, default 64
[    0.543524] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    0.550924] kvm [1]: IPA Size Limit: 40 bits
[    0.555485] kvm [1]: GICv3: no GICV resource entry
[    0.559695] kvm [1]: disabling GICv2 emulation
[    0.564169] kvm [1]: GIC system register CPU interface enabled
[    0.570073] kvm [1]: vgic interrupt IRQ1
[    0.574054] kvm [1]: Hyp mode initialized successfully
[    0.581948] Initialise system trusted keyrings
[    0.583683] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    0.595831] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.599436] NFS: Registering the id_resolver key type
[    0.603932] Key type id_resolver registered
[    0.608108] Key type id_legacy registered
[    0.612138] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.618870] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.626323] jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
[    0.632803] 9p: Installing v9fs 9p2000 file system support
[    0.651737] Key type asymmetric registered
[    0.652990] Asymmetric key parser 'x509' registered
[    0.657911] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.665324] io scheduler mq-deadline registered
[    0.669872] io scheduler kyber registered
[    0.678050] EINJ: ACPI disabled.
[    0.686745] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.694400] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.711570] mxs-dma 33000000.dma-controller: initialized
[    0.715066] Bus freq driver module loaded
[    0.723136] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.728520] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 34, base_baud = 1500000) is a IMX
[    0.735469] printk: console [ttymxc1] enabled
[    0.735469] printk: console [ttymxc1] enabled
[    0.744116] printk: bootconsole [ec_imx6q0] disabled
[    0.744116] printk: bootconsole [ec_imx6q0] disabled
[    0.756050] imx-drm soc@0:bus@32c00000:display-subsystem: no available port
[    0.774382] loop: module loaded
[    0.779429] imx ahci driver is registered.
[    0.786201] spi_imx 30830000.spi: probed
[    0.791041] spi-nor spi3.0: n25q256ax1 (32768 Kbytes)
[    0.796146] 7 fixed-partitions partitions found on MTD device 30bb0000.spi
[    0.803027] Creating 7 MTD partitions on "30bb0000.spi":
[    0.808347] 0x000000000000-0x000000200000 : "U-Boot"
[    0.817392] 0x000000200000-0x000000202000 : "U-Boot Env"
[    0.822719] mtd: partition "U-Boot Env" doesn't end on an erase/write block -- force read-only
[    0.833337] 0x000000202000-0x000000204000 : "U-Boot Env 2"
[    0.838833] mtd: partition "U-Boot Env 2" doesn't start on an erase/write block boundary -- force read-only
[    0.853342] 0x000000204000-0x000000205000 : "boot.scr"
[    0.858491] mtd: partition "boot.scr" doesn't start on an erase/write block boundary -- force read-only
[    0.869325] 0x000000205000-0x000000210000 : "Device Tree Blob"
[    0.875169] mtd: partition "Device Tree Blob" doesn't start on an erase/write block boundary -- force read-only
[    0.889335] 0x000000210000-0x000000e10000 : "Compressed Kernel"
[    0.897333] 0x000000e10000-0x000002000000 : "SquashFS"
[    0.906579] libphy: Fixed MDIO Bus: probed
[    0.911369] tun: Universal TUN/TAP device driver, 1.6
[    0.917120] thunder_xcv, ver 1.0
[    0.920379] thunder_bgx, ver 1.0
[    0.923645] nicpf, ver 1.0
[    0.927568] pps pps0: new PPS source ptp0
[    0.943981] libphy: fec_enet_mii_bus: probed
[    0.948772] fec 30be0000.ethernet eth0: registered PHC device 0
[    0.955242] Freescale FM module, FMD API version 21.1.0
[    0.960688] Freescale FM Ports module
[    0.964357] fsl_mac: fsl_mac: FSL FMan MAC API based driver
[    0.970062] fsl_dpa: FSL DPAA Ethernet driver
[    0.974514] fsl_advanced: FSL DPAA Advanced drivers:
[    0.979483] fsl_proxy: FSL DPAA Proxy initialization driver
[    0.985142] fsl_oh: FSL FMan Offline Parsing port driver
[    0.991222] hclge is initializing
[    0.994545] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[    1.001770] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.007125] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    1.014177] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.019958] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.025795] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.031749] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[    1.038714] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.044318] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.052151] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.058209] sky2: driver version 1.30
[    1.062731] VFIO - User Level meta-driver version: 0.3
[    1.069490] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.076027] ehci-pci: EHCI PCI platform driver
[    1.080544] ehci-platform: EHCI generic platform driver
[    1.085925] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.092128] ohci-pci: OHCI PCI platform driver
[    1.096606] ohci-platform: OHCI generic platform driver
[    1.102319] usbcore: registered new interface driver usb-storage
[    1.108398] usbcore: registered new interface driver usbserial_generic
[    1.114949] usbserial: USB Serial support registered for generic
[    1.120980] usbcore: registered new interface driver ftdi_sio
[    1.126742] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.134076] usbcore: registered new interface driver usb_serial_simple
[    1.140618] usbserial: USB Serial support registered for carelink
[    1.146727] usbserial: USB Serial support registered for zio
[    1.152400] usbserial: USB Serial support registered for funsoft
[    1.158421] usbserial: USB Serial support registered for flashloader
[    1.164795] usbserial: USB Serial support registered for google
[    1.170734] usbserial: USB Serial support registered for libtransistor
[    1.177277] usbserial: USB Serial support registered for vivopay
[    1.183298] usbserial: USB Serial support registered for moto_modem
[    1.189581] usbserial: USB Serial support registered for motorola_tetra
[    1.196214] usbserial: USB Serial support registered for novatel_gps
[    1.202584] usbserial: USB Serial support registered for hp4x
[    1.208350] usbserial: USB Serial support registered for suunto
[    1.214287] usbserial: USB Serial support registered for siemens_mpi
[    1.223024] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/soc@0:bus@30000000/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[    1.238035] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    1.244303] i2c /dev entries driver
[    1.252247] imx2-wdt 30280000.watchdog: timeout 60 sec (nowayout=0)
[    1.258789] Bluetooth: HCI UART driver ver 2.3
[    1.263246] Bluetooth: HCI UART protocol H4 registered
[    1.268391] Bluetooth: HCI UART protocol BCSP registered
[    1.273732] Bluetooth: HCI UART protocol LL registered
[    1.278876] Bluetooth: HCI UART protocol ATH3K registered
[    1.284292] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    1.290639] Bluetooth: HCI UART protocol Broadcom registered
[    1.296318] Bluetooth: HCI UART protocol QCA registered
[    1.303291] sdhci: Secure Digital Host Controller Interface driver
[    1.309482] sdhci: Copyright(c) Pierre Ossman
[    1.314003] Synopsys Designware Multimedia Card Interface Driver
[    1.320520] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.326929] mmc1: CQHCI version 5.10
[    1.331000] mmc2: CQHCI version 5.10
[    1.366873] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.376151] ledtrig-cpu: registered to indicate activity on CPUs
[    1.383270] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    1.390042] caam 30900000.crypto: job rings = 3, qi = 0
[    1.405942] caam algorithms registered in /proc/crypto
[    1.411819] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto
[    1.421344] caam_jr 30901000.jr: registering rng-caam
[    1.433702] caam-snvs 30370000.caam-snvs: can't get snvs clock
[    1.439583] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state
[    1.447997] usbcore: registered new interface driver usbhid
[    1.453577] usbhid: USB HID core driver
[    1.459387] No fsl,qman node
[    1.462287] Freescale USDPAA process driver
[    1.466475] fsl-usdpaa: no region found
[    1.470316] Freescale USDPAA process IRQ driver
[    1.478310] optee: probing for conduit method from DT.
[    1.483478] optee: revision 3.2 (6a22e6e8)
[    1.484788] optee: dynamic shared memory is enabled
[    1.494072] optee: initialized driver
[    1.499857] mmc2: Command Queue Engine enabled
[    1.501704] wm8524-codec audio-codec: Failed to get mute line: -517
[    1.504346] mmc2: new HS400 Enhanced strobe MMC card at address 0001
[    1.511056] OF: /sound-bt-sco/simple-audio-card,cpu: could not get #sound-dai-cells for /soc@0/bus@30000000/sai@30020000
[    1.518006] mmcblk2: mmc2:0001 DG4016 7.49 GiB  
[    1.527812] asoc-simple-card sound-bt-sco: parse error -22
[    1.527829] asoc-simple-card: probe of sound-bt-sco failed with error -22
[    1.532474] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.550725] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.552076] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    1.556808] mmcblk2gp0: mmc2:0001 DG4016 partition 4 3.52 GiB
[    1.570357] NET: Registered protocol family 26
[    1.570759] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB, chardev (237:0)
[    1.575300] NET: Registered protocol family 10
[    1.586931]  mmcblk2: p1 p2
[    1.587624] Segment Routing with IPv6
[    1.593504] NET: Registered protocol family 17
[    1.598166]  mmcblk2gp0: p1 p2
[    1.598390] Bluetooth: RFCOMM TTY layer initialized
[    1.606144] Bluetooth: RFCOMM socket layer initialized
[    1.611321] Bluetooth: RFCOMM ver 1.11
[    1.615088] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    1.620404] Bluetooth: BNEP filters: protocol multicast
[    1.625636] Bluetooth: BNEP socket layer initialized
[    1.630606] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    1.636532] Bluetooth: HIDP socket layer initialized
[    1.641540] 8021q: 802.1Q VLAN Support v1.8
[    1.645750] lib80211: common routines for IEEE802.11 drivers
[    1.651530] 9pnet: Installing 9P2000 support
[    1.655833] tsn generic netlink module v1 init...
[    1.660613] Key type dns_resolver registered
[    1.665652] registered taskstats version 1
[    1.669778] Loading compiled-in X.509 certificates
[    1.697518] usb_phy_generic usbphynop1: usbphynop1 supply vcc not found, using dummy regulator
[    1.706299] usb_phy_generic usbphynop2: usbphynop2 supply vcc not found, using dummy regulator
[    1.738543] random: fast init done
[    1.743680] LDO6: supplied by regulator-dummy
[    1.748187] i2c i2c-0: IMX I2C adapter registered
[    1.753876] i2c i2c-1: IMX I2C adapter registered
[    1.759408] i2c i2c-2: IMX I2C adapter registered
[    1.765205] i2c i2c-3: IMX I2C adapter registered
[    1.770237] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 2 mkt segment 2 supported-hw 0x4 0x4
[    1.782784] mmc1: CQHCI version 5.10
[    1.786418] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    1.821457] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    1.830140] imx8mm-pinctrl 30330000.pinctrl: pin MX8MM_IOMUXC_I2C4_SDA already requested by 30a50000.i2c; cannot claim for audio-codec
[    1.842264] imx8mm-pinctrl 30330000.pinctrl: pin-140 (audio-codec) status -22
[    1.849408] imx8mm-pinctrl 30330000.pinctrl: could not request pin 140 (MX8MM_IOMUXC_I2C4_SDA) from group gpiowlfgrp  on device 30330000.pinctrl
[    1.862367] wm8524-codec audio-codec: Error applying setting, reverse things back
[    1.869868] wm8524-codec: probe of audio-codec failed with error -22
[    1.880540] input: bd718xx-pwrkey as /devices/platform/soc@0/soc@0:bus@30800000/30a20000.i2c/i2c-0/0-004b/gpio-keys.1.auto/input/input1
[    1.894274] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 2021-05-14T14:03:42 UTC (1621001022)
[    1.904487] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    1.916959] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    1.923554] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    1.927624] ALSA device list:
[    1.932172] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[    1.942907]   No soundcards found.
[    1.956545] EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.964702] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.972100] devtmpfs: mounted
[    1.976098] Freeing unused kernel memory: 2880K
[    1.980716] Run /sbin/init as init process
[    2.060538] audit: type=1404 audit(1621001022.660:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[    2.197726] SELinux:  Permission watch in class filesystem not defined in policy.
[    2.205251] SELinux:  Permission watch in class file not defined in policy.
[    2.212214] SELinux:  Permission watch_mount in class file not defined in policy.
[    2.219712] SELinux:  Permission watch_sb in class file not defined in policy.
[    2.226936] SELinux:  Permission watch_with_perm in class file not defined in policy.
[    2.234775] SELinux:  Permission watch_reads in class file not defined in policy.
[    2.242268] SELinux:  Permission watch in class dir not defined in policy.
[    2.249153] SELinux:  Permission watch_mount in class dir not defined in policy.
[    2.256550] SELinux:  Permission watch_sb in class dir not defined in policy.
[    2.263695] SELinux:  Permission watch_with_perm in class dir not defined in policy.
[    2.271439] SELinux:  Permission watch_reads in class dir not defined in policy.
[    2.278853] SELinux:  Permission watch in class lnk_file not defined in policy.
[    2.286164] SELinux:  Permission watch_mount in class lnk_file not defined in policy.
[    2.294003] SELinux:  Permission watch_sb in class lnk_file not defined in policy.
[    2.301582] SELinux:  Permission watch_with_perm in class lnk_file not defined in policy.
[    2.309769] SELinux:  Permission watch_reads in class lnk_file not defined in policy.
[    2.317607] SELinux:  Permission watch in class chr_file not defined in policy.
[    2.324925] SELinux:  Permission watch_mount in class chr_file not defined in policy.
[    2.332761] SELinux:  Permission watch_sb in class chr_file not defined in policy.
[    2.340344] SELinux:  Permission watch_with_perm in class chr_file not defined in policy.
[    2.348522] SELinux:  Permission watch_reads in class chr_file not defined in policy.
[    2.356366] SELinux:  Permission watch in class blk_file not defined in policy.
[    2.363677] SELinux:  Permission watch_mount in class blk_file not defined in policy.
[    2.371516] SELinux:  Permission watch_sb in class blk_file not defined in policy.
[    2.379086] SELinux:  Permission watch_with_perm in class blk_file not defined in policy.
[    2.387272] SELinux:  Permission watch_reads in class blk_file not defined in policy.
[    2.395110] SELinux:  Permission watch in class sock_file not defined in policy.
[    2.402506] SELinux:  Permission watch_mount in class sock_file not defined in policy.
[    2.410429] SELinux:  Permission watch_sb in class sock_file not defined in policy.
[    2.418085] SELinux:  Permission watch_with_perm in class sock_file not defined in policy.
[    2.426350] SELinux:  Permission watch_reads in class sock_file not defined in policy.
[    2.434282] SELinux:  Permission watch in class fifo_file not defined in policy.
[    2.441679] SELinux:  Permission watch_mount in class fifo_file not defined in policy.
[    2.449605] SELinux:  Permission watch_sb in class fifo_file not defined in policy.
[    2.457262] SELinux:  Permission watch_with_perm in class fifo_file not defined in policy.
[    2.465535] SELinux:  Permission watch_reads in class fifo_file not defined in policy.
[    2.473773] SELinux: the above unknown classes and permissions will be allowed
[    2.481016] SELinux:  policy capability network_peer_controls=1
[    2.486938] SELinux:  policy capability open_perms=1
[    2.491912] SELinux:  policy capability extended_socket_class=1
[    2.497833] SELinux:  policy capability always_check_network=0
[    2.503675] SELinux:  policy capability cgroup_seclabel=1
[    2.509074] SELinux:  policy capability nnp_nosuid_transition=1
[    2.551979] audit: type=1403 audit(1621001023.152:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
[    2.558891] systemd[1]: Successfully loaded SELinux policy in 499.797ms.
[    2.663812] systemd[1]: Relabelled /dev, /dev/shm, /run, /sys/fs/cgroup in 67.655ms.
[    2.682911] systemd[1]: systemd 244.5+ running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR -SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid)
[    2.704939] systemd[1]: Detected architecture arm64.

Welcome to Poky (Yocto Project Reference Distro) 3.1.7 (dunfell)!

[    2.761410] systemd[1]: Set hostname to <imx8mmevk>.
[    2.963225] random: systemd: uninitialized urandom read (16 bytes read)
[    2.970024] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[    2.982383] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[    2.993074] systemd[1]: Created slice system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[    3.013209] random: systemd: uninitialized urandom read (16 bytes read)
[    3.021079] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[    3.040889] random: systemd: uninitialized urandom read (16 bytes read)
[    3.049063] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    3.073555] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Dispatch Password �…ts to Console Directory Watch.
[    3.097478] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password R��…uests to Wall Directory Watch.
[    3.120999] systemd[1]: Reached target Paths.
[  OK  ] Reached target Paths.
[    3.140900] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    3.165590] systemd[1]: Reached target Slices.
[  OK  ] Reached target Slices.
[    3.185866] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    3.210920] systemd[1]: Listening on RPCbind Server Activation Socket.
[  OK  ] Listening on RPCbind Server Activation Socket.
[    3.232948] systemd[1]: Reached target RPC Port Mapper.
[  OK  ] Reached target RPC Port Mapper.
[    3.257214] systemd[1]: Listening on Syslog Socket.
[  OK  ] Listening on Syslog Socket.
[    3.277824] systemd[1]: Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[    3.303340] systemd[1]: systemd-journald-audit.socket: Failed to create listening socket (audit 1): Operation not permitted
[    3.303603] audit: type=1400 audit(1621001023.904:4): avc:  denied  { audit_read } for  pid=1 comm="systemd" capability=37  scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=capability2 permissive=0
[    3.314517] systemd[1]: systemd-journald-audit.socket: Failed to listen on sockets: Operation not permitted
[    3.314663] systemd[1]: systemd-journald-audit.socket: Failed with result 'resources'.
[    3.353186] systemd[1]: Failed to listen on Journal Audit Socket.
[FAILED] Failed to listen on Journal Audit Socket.
See 'systemctl status systemd-journald-audit.socket' for details.
[    3.389680] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    3.414416] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    3.434353] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[    3.459379] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    3.481748] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    3.509857] systemd[1]: Mounting Huge Pages File System...
        Mounting Huge Pages File System...
[    3.533188] systemd[1]: Mounting POSIX Message Queue File System...
        Mounting POSIX Message Queue File System...
[    3.557152] systemd[1]: Mounting Kernel Debug File System...
        Mounting Kernel Debug File System...
[    3.581924] systemd[1]: Mounting Temporary Directory (/tmp)...
        Mounting Temporary Directory (/tmp)...
[    3.605283] systemd[1]: Starting Create list of static device nodes for the current kernel...
        Starting Create list of st��…odes for the current kernel...
[    3.636385] systemd[1]: Starting Start psplash boot splash screen...
        Starting Start psplash boot splash screen...
[    3.660189] systemd[1]: Starting RPC Bind...
        Starting RPC Bind...
[    3.684232] systemd[1]: Starting SELinux autorelabel service loading...
        Starting SELinux autorelabel service loading...
[    3.708354] systemd[1]: Starting SELinux init for /dev service loading...
        Starting SELinux init for /dev service loading...
[    3.740312] systemd[1]: Starting File System Check on Root Device...
        Starting File System Check on Root Device...
[    3.770209] systemd[1]: Starting Journal Service...
        Starting Journal Servi[    3.777145] systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
ce...
[    3.787527] systemd[1]: Condition check resulted in FUSE Control File System being skipped.
[    3.801674] systemd[1]: Mounting Kernel Configuration File System...
        Mounting Kernel Configuration File System...
[    3.813958] systemd[1]: Starting Apply Kernel Variables...
        Starting Apply Kernel Variables...
[    3.824163] systemd[1]: Starting udev Coldplug all Devices...
        Starting udev Coldplug all Devices...
[    3.842788] systemd[1]: Started RPC Bind.
[  OK  ] [    3.848205] systemd[1]: Mounted Huge Pages File System.
Started RPC Bind.
[    3.855211] systemd[1]: Started Journal Service.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Journal Service.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Started Create list of sta��… nodes for the current kernel.
[FAILED] Failed to start Start psplash boot splash screen.
See 'systemctl status psplash-start.service' for details.
[DEPEND] Dependency failed for Star��…progress communication helper.
[  OK  ] Started SELinux autorelabel service loading.
[  OK  ] Started SELinux init for /dev service loading.
[  OK  ] Started File System Check on Root Device.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Apply Kernel Variables.
        Starting Remount Root and Kernel File Systems...
[    4.135040] EXT4-fs (mmcblk2p2): re-mounted. Opts: (null)
[  OK  ] Started Remount Root and Kernel File Systems.
        Starting Flush Journal to Persistent Storage...
[    4.176222] systemd-journald[287]: Received client request to flush runtime journal.
        Starting Create Static Device Nodes in /dev...
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
        Mounting /var/volatile...
        Starting udev Kernel Device Manager...
[  OK  ] Mounted /var/volatile.
[  OK  ] Started udev Coldplug all Devices.
        Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
        Starting SELinux init service loading...
        Starting Create Volatile Files and Directories...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started SELinux init service loading.
        Starting Network Service...
[  OK  ] Started Create Volatile Files and Directories.
        Starting Network Time Synchronization...
        Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Network Service.
        Starting Network Name Resolution...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target System Time Set.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Reached target Timers.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
[  OK  ] Started Kernel Logging Service.
[  OK  ] Started System Logging Service.
[  OK  ] Started D-Bus System Message Bus.
[    4.923342] audit: type=1400 audit(1621001025.524:5): avc:  denied  { module_load } for  pid=312 comm="systemd-udevd" path="/lib/modules/5.4.114+gf9a9b58ef7cc/kernel/arch/arm64/crypto/crct10dif-ce.ko" dev="mmcblk2p2" ino=577 scontext=system_u:system_r:0
[    4.960809] audit: type=1400 audit(1621001025.524:6): avc:  denied  { module_load } for  pid=307 comm="systemd-udevd" path="/lib/modules/5.4.114+gf9a9b58ef7cc/kernel/arch/arm64/crypto/crct10dif-ce.ko" dev="mmcblk2p2" ino=577 scontext=system_u:system_r:0
        Starting Telephony service...
[    4.996048] audit: type=1400 audit(1621001025.524:7): avc:  denied  { module_load } for  pid=318 comm="systemd-udevd" path="/lib/modules/5.4.114+gf9a9b58ef7cc/kernel/arch/arm64/crypto/crct10dif-ce.ko" dev="mmcblk2p2" ino=577 scontext=system_u:system_r:0
[    5.032350] audit: type=1400 audit(1621001025.524:8): avc:  denied  { module_load } for  pid=319 comm="systemd-udevd" path="/lib/modules/5.4.114+gf9a9b58ef7cc/kernel/arch/arm64/crypto/crct10dif-ce.ko" dev="mmcblk2p2" ino=577 scontext=system_u:system_r:0
        Starting Login Service...
[    5.072228] Generic PHY fixed-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=fixed-0:00, irq=POLL)
[    5.088344] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[  OK  ] Started Network Name Resolution.
[    5.109578] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  OK  ] Started Telephony service.
[  OK  ] Started Login Service.
[  OK  ] Reached target Network.
[  OK  ] Reached target Host and Network Name Lookups.
        Starting Avahi mDNS/DNS-SD Stack...
        Starting Hostname Service...
        Starting Permit User Sessions...
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttymxc1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
        Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Hostname Service.
[    5.644863] audit: type=1107 audit(1621001026.231:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { status } for auid=n/a uid=0 gid=0 path="/lib/systemd/system/graphical.target" cmdline="" scontext=s0
[    5.644863]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[FAILED] Failed to start Update UTM�…about System Runlevel Changes.
See 'systemctl status systemd-update-utmp-runlevel.service' for details.

Poky (Yocto Project Reference Distro) 3.1.7 imx8mmevk ttymxc1

imx8mmevk login: [   13.913709] random: crng init done
[   13.917116] random: 7 urandom warning(s) missed due to ratelimiting
[   34.240165] WLAN_EN: disabling
[   34.243228] VSD_3V3: disabling
[   62.907654] cfg80211: failed to load regulatory.db
[   62.907942] imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware
[   62.910414] imx-sdma 302b0000.dma-controller: external firmware not found, using ROM firmware
[   62.933352] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5

imx8mmevk login: root
[   84.724596] audit: type=1107 audit(1621001104.928:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { start } for auid=n/a uid=0 gid=0 path="/lib/systemd/system/user@.service" cmdline="/lib/systemd/sy0
[   84.724596]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
Cannot execute /bin/sh: No such f[   84.764677] audit: type=1107 audit(1621001104.932:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { start } for auid=n/a uid=0 gid=0 path="/run/systemd/transient/ses0
[   84.764677]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[   84.808459] audit: type=1400 audit(1621001104.932:12): avc:  denied  { transition } for  pid=374 comm="login" path="/usr/lib/busybox/bin/sh" dev="mmcblk2p2" ino=1921 scontext=system_u:system_r:kernel_t:s0 tcontext=root:sysadm_r:sysadm_t:s0 tclass=proce0

Poky (Yocto Project Reference Distro) 3.1.7 imx8mmevk ttymxc1

imx8mmevk login: [   94.988451] audit: type=1107 audit(1621001115.197:13): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { stop } for auid=n/a uid=0 gid=0 path="/lib/systemd/system/user@.service" cmdline=0
[   94.988451]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'

imx8mmevk login: root
Last login: Fri May 14 14:05:04 UTC 2021 on ttymxc1
[  102.258579] audit: type=1107 audit(1621001122.465:14): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { start } for auid=n/a uid=0 gid=0 path="/lib/systemd/system/user@.service" cmdline="/lib/systemd/sy0
[  102.258579]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
Cannot execute /bin/sh: No such f[  102.298664] audit: type=1107 audit(1621001122.481:15): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { start } for auid=n/a uid=0 gid=0 path="/run/systemd/transient/ses0
[  102.298664]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
[  102.342430] audit: type=1400 audit(1621001122.485:16): avc:  denied  { transition } for  pid=379 comm="login" path="/usr/lib/busybox/bin/sh" dev="mmcblk2p2" ino=1921 scontext=system_u:system_r:kernel_t:s0 tcontext=root:sysadm_r:sysadm_t:s0 tclass=proce0

Poky (Yocto Project Reference Distro) 3.1.7 imx8mmevk ttymxc1

imx8mmevk login: [  112.488345] audit: type=1107 audit(1621001132.697:17): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='avc:  denied  { stop } for auid=n/a uid=0 gid=0 path="/lib/systemd/system/user@.service" cmdline=0
[  112.488345]  exe="/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'

imx8mmevk login:

3881 - 3900 of 57387