I’m trying to manage my wireless LAN interface using wpa_supplicant on my i.MX8 running Yocto Scarthgap. I can scan for available networks and connect successfully using the wpa_cli utility. However, when I try to save the current network configuration to the .conf file to persist it, wpa_supplicant fails to start on reboot due to an incorrect file format. Steps I followed before reboot to connect to an AP

> add_network
0
CTRL-EVENT-NETWORK-ADDED 0

> > set_network 0 ssid "MyNetwork"
OK
> set_network 0 psk "MyPassPhrase"
OK
> enable_network 0
OK
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
Trying to associate with SSID 'MyNetwork'
.....
CTRL-EVENT-CONNECTED - Connection to xxxxxx completed [id=0 id_str=]

> > save_config
OK
> quit

This is what my .conf file in /etc/wpa_supplicant/wpa_supplicant-wlan0.conf looks like after I run save_config .

ctrl_interface=/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1
filter_ssids=1
ignore_old_scan_res=1

network={
	ssid="MyNetwork"
	psk=*
}

On reboot systemd failed to start wpa_supplicant service

root@imx8qxp:~# journalctl -xe -u wpa_supplicant@wlan0.service 
Jul 09 16:03:46 imx8qxp systemd: Started WPA supplicant daemon (interface-specific version). 
-- Subject: A start job for unit wpa_supplicant@wlan0.service has finished successfully 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- A start job for unit wpa_supplicant@wlan0.service has finished successfully. 
--  
-- The job identifier is 100. 
Jul 09 16:03:46 imx8qxp systemd: wpa_supplicant@wlan0.service: Main process exited, code=exited, status=255/EXCEPTION 
-- Subject: Unit process exited 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- An ExecStart= process belonging to unit wpa_supplicant@wlan0.service has exited. --  -- The process' exit code is 'exited' and its exit status is 255. 
Jul 09 16:03:46 imx8qxp systemd: wpa_supplicant@wlan0.service: Failed with result 'exit-code'. -- Subject: Unit failed 
-- Defined-By: systemd 
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel  
--  
-- The unit wpa_supplicant@wlan0.service has entered the 'failed' state with result 'exit-code'.

On further investigation by trying to start wpa_supplicant manually

root@imx8qxp:~# wpa_supplicant -B -dd -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
Line 9: Invalid PSK '*'.
Line 9: failed to parse psk '*'.
Line 10: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant-wlan0.conf'.

I did try to manually generate the passphrase using the command wpa_passphrase SSID PASSWORD > /etc/wpa_supplicant/wpa_supplicant-wlan0.conf and there were no issues with it after reboot. I get this error only when trying to save network config from wpa_cli. I also tried recreating it on an ubuntu 24 machine but could not successfully reproduce the issue. While the obvious solution is to use wpa_passphrase directly, I'm interested in understanding why this issue occurs in the first place. Despite searching online, I haven’t come across anyone experiencing this exact problem. Could it be that I’m missing a step when saving the network configuration using wpa_cli? What causes this behaviour, and is there a correct way to persist network settings without manually trying to write to the file? I don't prefer using the wpa_passphrase command because I ultimately want to use wpa_ctrl C APIs and would not prefer messing with the .conf files in the application layer.

Built **Yocto** (Poky fido branch) Linux distro for **Raspberry Pi 2** following this excellent tutorial [Part 1](http://www.embarcados.com.br/raspberry-pi-2-qt5-yocto-parte-1/). Now trying to run Chromium. Added [meta-browser](http://layers.openembedded.org/layerindex/branch/master/layer/meta-browser/) to my bblayers.conf Added chromium recipes to my .bb image file. Was able to compile and build my image but getting these errors when trying to run: root@raspberrypi2:/usr/bin/chromium# ./chrome [527:527:0624/195537:FATAL:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. Aborted ### --no-sandbox root@raspberrypi2:/usr/bin/chromium# ./chrome --no-sandbox [528:528:0624/195641:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. [528:528:0624/195641:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: root@raspberrypi2:/usr/bin/chromium# [530:530:0624/195641:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif. [530:530:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe ^C ### DISPLAY=:0.0 root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox [531:531:0624/195652:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. [531:531:0624/195652:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0 root@raspberrypi2:/usr/bin/chromium# [533:533:0624/195652:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif. [533:533:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe ^C ### --use-gl=egl > *I'd be very interested to have it working with hardware acceleration* root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox --use-gl=egl [534:534:0624/195901:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. [534:534:0624/195901:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0 root@raspberrypi2:/usr/bin/chromium# [536:536:0624/195901:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif. [536:536:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe ^C Any pointers are welcome.

In a **yocto-base Linux distribution** is available the program timedatectl and it is necessary to set the timezone. To do that exist the command:

timedatectl set-timezone

The execution of the command timedatectl list-timezones to get the list of all timezones available outputs a list empty:

> timedatectl list-timezones
UTC

The distribution doesn't include any file /usr/share/zoneinfo or /usr/zoneinfo. I think I miss installing something but I don't know what.. Thanks

I'm developing a custom Linux distribution with yocto (Zeus Release). I'm using systemd-timesyncd as NTP Client. I need to substitute its default configuration file (/etc/systemd/timesyncd.conf) with a custom configuration file. I know that the NTP client systemd-timesyncd is installed into the image by the recipe meta/recipes-core/systemd/systemd_245.6.bb. In the recipe are present the followed lines:

PACKAGECONFIG ??= " \
    ...
    timesyncd \
    ...
"

and others. Furthermore in the same recipe it is defined the configuration file timesyncd.conf by the followed lines:

CONFFILES_${PN} = "${sysconfdir}/systemd/coredump.conf \
    ...
    ${sysconfdir}/systemd/timesyncd.conf \
    ...
"

I have found [this post](https://stackoverflow.com/questions/77915145/bitbake-way-to-add-a-system-conf-setting) which explains how to substitute the default configuration file /etc/systemd/system.conf by an other defined by a user. Since the two configuration files (timesyncd.conf and system.conf) are installed in the same folder, /etc/systemd/, I have created an append file /recipes-core/systemd/systemd-conf_%.bbappend and followed the other steps well described in the post, but, after the image building, the timesyncd.conf remains the default one and it is not substitute by my custom configuration file. So, how can I substitute the default timesyncd.conf file in the yocto image?

Here is quick description what im trying to achieve, building this mender yocto image for raspberry pi want to encrypt the root partition, while secure boot, need to add the init script which can decrypt the LUKS encrypted rootfs partition. Poky layer already has core-image-minimal-initramfs which can be bundled in linux kernel, the problem is im not able to add the init script from custom layer, have no idea how to achieve it This is the poky layer content core-image-minimal-initramfs.bb # Simple initramfs image. Mostly used for live images. SUMMARY = "Small image capable of booting a device." DESCRIPTION = "Small image capable of booting a device. The kernel includes \ the Minimal RAM-based Initial Root Filesystem (initramfs), which finds the \ first 'init' program more efficiently." INITRAMFS_SCRIPTS ?= "\ initramfs-framework-base \ initramfs-module-setup-live \ initramfs-module-udev \ initramfs-module-install \ initramfs-module-install-efi \ " PACKAGE_INSTALL = "${INITRAMFS_SCRIPTS} ${VIRTUAL-RUNTIME_base-utils} udev base-passwd ${ROOTFS_BOOTSTRAP_INSTALL}" # Do not pollute the initrd image with rootfs features IMAGE_FEATURES = "" # Don't allow the initramfs to contain a kernel PACKAGE_EXCLUDE = "kernel-image-*" IMAGE_NAME_SUFFIX ?= "" IMAGE_LINGUAS = "" LICENSE = "MIT" IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}" inherit core-image IMAGE_ROOTFS_SIZE = "8192" IMAGE_ROOTFS_EXTRA_SPACE = "0" # Use the same restriction as initramfs-module-install COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|aarch64.*|loongarch64.*)-(linux.*|freebsd.*)' the is meta-mender/meta-mender-core/recipe-core tree, ihave added this core-image-minimal-initramfs.bbappend and initLUKSdecrpyt.sh /meta-mender/meta-mender-core/recipes-core$ tree . ├── initrdscripts │   ├── core-image-minimal-initramfs.bbappend │   ├── files │   │   ├── init-install-efi-mender.sh │   │   └── initLUKSdecrypt.sh │   ├── initramfs-module-install_%.bbappend │   ├── initramfs-module-install-efi_%.bbappend │   └── initramfs-module-install.inc 8 directories, 12 files this is code in core-image-minimal-initramfs.bbappend file,here the do_install is not getting called. FILESEXTRAPATHS:prepend := "${THISDIR}/files:" SRC_URI += "file://initLUKSdecrypt.sh" PACKAGE_INSTALL += "cryptsetup" do_install:append:mender-uboot(){ bbwarn "WorkDIR=${WORKDIR} Destination=${D}" install -m 0755 ${WORKDIR}/initLUKSdecrypt.sh ${D}/init.d/initLUKSdecrypt.sh } So add the code in initramfs-module-install_%.bbappend, the do_install gets called but while final pacakging gets error. require initramfs-module-install.inc do_install:append:mender-efi-boot() { install -m 0755 ${WORKDIR}/init-install-efi-mender-altered.sh ${D}/init.d/install.sh } FILESEXTRAPATHS:prepend := "${THISDIR}/files:" SRC_URI := " file://initLUKSdecrypt.sh " do_install() { bbwarn "WorkDIR=${WORKDIR} Destination=${D}" install -m 0755 ${WORKDIR}/initLUKSdecrypt.sh ${D}/../package/init.d/ } Error logs: ERROR: Task (/home/john/meta-mender-community/yocto-raspberrypi4/build/../../kas/demos/meta-mender-raspberrypi-wifi/recipes-raspberrypi/images/core-image-raspberrypi-wifi.bb:do_image_bootimg) failed with exit code '1' ERROR: core-image-minimal-initramfs-1.0-r0 do_rootfs: Unable to install packages. Command '/home/john/meta-mender-community/yocto-raspberrypi4/build/tmp/work/raspberrypi4_64-poky-linux/core-image-minimal-initramfs/1.0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/john/meta-mender-community/yocto-raspberrypi4/build/tmp/work/raspberrypi4_64-poky-linux/core-image-minimal-initramfs/1.0/opkg.conf -t /home/john/meta-mender-community/yocto-raspberrypi4/build/tmp/work/raspberrypi4_64-poky-linux/core-image-minimal-initramfs/1.0/temp/ipktemp/ -o /home/john/meta-mender-community/yocto-raspberrypi4/build/tmp/work/raspberrypi4_64-poky-linux/core-image-minimal-initramfs/1.0/rootfs --force_postinstall --prefer-arch-to-version --add-exclude kernel-image-* --add-exclude kernel-image-* install base-passwd busybox cryptsetup initramfs-framework-base initramfs-module-install initramfs-module-install-efi initramfs-module-setup-live initramfs-module-udev run-postinsts udev' returned 255: * opkg_solver_install: No candidates to install initramfs-module-install (null)! ERROR: Logfile of failure stored in: /home/john/meta-mender-community/yocto-raspberrypi4/build/tmp/work/raspberrypi4_64-poky-linux/core-image-minimal-initramfs/1.0/temp/log.do_rootfs.10642 ERROR: Task (/home/john/meta-mender-community/yocto-raspberrypi4/build/../poky/meta/recipes-core/images/core-image-minimal-initramfs.bb:do_rootfs) failed with exit code '1' don't know what im missing.

I am trying to cross-compile a program with the "gpiod" library. My host pc has Ubuntu 18.04 and the target platform I am cross-compiling for is a Board with IMX8X SOM. I found source code at https://variwiki.com/index.php?title=MX8_GPIO&release=RELEASE_DUNFELL_V1.3_VAR-SOM-MX8X and I wanted to compile it, following the paragraph "2.2 libgpiod C Application". The OS used in my board is the "dunfell" distro compiled with Yocto. The cross-compiler I am using is also created as sdk withing the Yocto environments (aarch64-fslc-linux-gcc). When I compiled, I firstly obtained "fatal error: gpiod.h: No such file or directory" So, this library is not included by default in the provided toolchain. So I tried to install the (cross)library in my pc, following the instructions at https://www.beyondlogic.org/an-introduction-to-chardev-gpio-and-libgpiod-on-the-raspberry-pi/ , but it did not work. The second error I get is /opt/fslc-wayland/3.1/sysroots/x86_64-fslcsdk-linux/usr/libexec/aarch64-fslc-linux/gcc/aarch64-fslc-linux/9.3.0/real-ld: cannot find -lgpiod collect2: error: ld returned 1 exit status These are my compilation flags: CFLAGS = -Wall -I$(INCLUDE) --sysroot=${SDKTARGETSYSROOT} -Og -lgpiod I am new to this kind of issues and I hope I am making trivial mistakes. Thanks in advance if someone is able to help!

I am working on a project using a yocto build for a compulab module for the imx8 processor. It contains a ft5x06 touchscreen, connected to using a custom out-of-tree usb-i2c bridge module. This all works fine in normal use. When running a chromium webapp, sometimes the touchscreen goes non-responsive. I can still interact with the screen using a mouse and keyboard. If I run evtest, the touchscreen appears to still be responsive, but the chromium kiosk window does not register it. I am running wayland underneath. It is possible the custom driver is causing issues, but the fact that it still functions under evtest makes me sceptical. As an aside, chromium seems to trigger gpu errors. I don't know if this could be related or not.

[ 1815.795710] gcmkONERROR: status=-3(gcvSTATUS_OUT_OF_MEMORY) @ _GFPAlloc(491)

dmesg does not show anything useful. I've noticed that sometimes plugging in a mouse and scrolling is enough to get it working again (this worked 3 out of 4 times I have reproduced the issue). The issue is intermittent and not easily repeatable. I'm looking for any advice or suggestions of how to approach debugging this.

**The goal is to sign the mender yocto image and run it on secure boot enabled raspberry pi**. I have raspberrypi-4 and the yocto image from mender (open source OTA platform). To give a quick try here is the link: **Image and Modified Files ** of generated image flash to sd card using **rasbperry pi imager **, sign with private key and **step-2** flash secure-boot-recovery pieeprom via rpiboot and boot. Referred to **Secure Boot Example Readme ** enabled secure boot on rasberrypi-4. **Step-1 Generate private key for generating signed images** Source python virtual environment, install the pycryptodmex and generate private key, then export variable KEY_FILE. source path/to/python/virtual_env/activate pip install pycryptodomex openssl genrsa 2048 > private.pem export KEY_FILE=$(pwd)/private.pem **Step-2 Secure-boot-recovery for flashing signed pieeprom to raspberrypi-4** Once the private key is generated, cloned the secure boot git reposistory and complied to get rpiboot binary. git clone https://github.com/raspberrypi/usbboot secure-boot cd secure-boot git submodule update --init make To enabled rpiboot mode, updated the program_rpiboot_gpio=5 in secure-boot/secure-boot-recovery/config.txt and connected it GND pin, then connected the raspberrypi-4 to host with usb type-C Then in secure boot directory sign the pieeprom image with generate private key in step-1 and flash it to eeprom. cd secure-boot-recovery ../tools/update-pieeprom.sh -k "${KEY_FILE}" cd .. ./rpiboot -d secure-boot-recovery Now secure boot is enabled on raspberrypi-4 it will only run signed images and refereeing to document **Raspberry Pi 4 Boot Security ** raspberrypi4 expects singed boot.img. **Step-3 Process to create a signed mender yocto image** In this process the mender yocto image is modified, the mender yocto image create a sdcard flashable imagename.sdimg which contain boot partition, Root A/B partition and data parition, so to flash boot files to boot partition it creates imagename.bootimg and then it is packaged to imagename.sdimg, to make it work with rasberrypi-4 secure boot enabled i modified files two yocto recipe file **mender-bootimg.bbclass** and **mender-part-images.bbclass** from **classes ** here are the modified files **Image and Modified Files ** that made **imagename.bootimg** to **boot.img** also added the image signing code by refereeing **sign.sh** script secure-boot/secure-boot-example and **rpi-eeprom-digest.sh** script secure-boot/tools/rpi-eeprom. Dependencies: python virtual env and kas need to be installed source /path/to/python/venv/activate pip install kas mkdir mender-raspberrypi4 && cd mender-raspberrypi4 git clone https://github.com/theyoctojester/meta-mender-community -b scarthgap cd meta-mender-community mkdir my-raspberrypi4 && cd my-raspberrypi4 After modification of files to build image **Build Command** kas build ../kas/demos/raspberrypi4-64-wifi.yml After build is complete flash imagename.sdimg to sdcard using raspberry pi Imager, below are the boot logs captured serially where got the error complaining boot.img not found on sdcard, please let me know if anything I'm missing in it. **Errors Logs:** 2.62 RPi: BOOTLOADER release VERSION:69471177 DATE: 2025/05/08 TIME: 16:21:35 2.62 BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1746717695 serial 7c2 2.36 Unsupported boot order 6 2.61 Boot mode: SD (01) order f254 2.82 SD HOST: 200000000 CTL0: 0x00800000 BUS: 400000 Hz actual: 390625 HZ div6 2.83 SD HOST: 200000000 CTL0: 0x00800f00 BUS: 400000 Hz actual: 390625 HZ div6 2.98 OCR c0ff8000 CID: 000353444a554c494580d5b740550127 CSD: 400e00325b59000076b27f800a404000 2.98 SD: bus-width: 4 spec: 2 SCR: 0x02358043 0x00000000 2.99 SD HOST: 200000000 CTL0: 0x00800f04 BUS: 50000000 Hz actual: 50000000 HZ2 3.00 MBR: 0x0000c000, 206848 type: 0x0c 3.01 MBR: 0x00040000, 770048 type: 0x83 3.01 MBR: 0x000fc000, 770048 type: 0x83 3.01 MBR: 0x001b8000, 262144 type: 0x83 3.21 Trying partition: 0 3.49 type: 16 lba: 49152 'mkfs.fat' ' V ^ ' clusters 51603 (4) 3.05 rsc 4 fat-sectors 200 root dir cluster 1 sectors 32 entries 512 3.06 FAT16 clusters 51603 3.06 [sdcard] autoboot.txt not found 3.06 Select partition rsts 0 C(boot_partition) 0 EEPROM config 0 result 1 3.71 Trying partition: 1 3.76 type: 16 lba: 49152 'mkfs.fat' ' V ^ ' clusters 51603 (4) 3.08 rsc 4 fat-sectors 200 root dir cluster 1 sectors 32 entries 512 3.08 FAT16 clusters 51603 3.89 secure-boot 3.91 Loading boot.img ... 3.09 boot.sig 3.09 hash: b70a74e651e9bde92dd921ac6b26c9704077bcec431518c384aafd0c39f98fc7 3.10 ts: 1750829740 3.10 rsa2048: 7937a7eeacf12d1433011cc1fcbd57901e0d0796fafce03d811a44e54f255f8c 3.15 [sdcard] boot.img not found 3.53 Error 6 loading boot.img 3.55 Boot mode: USB-MSD (04) order f25 3.17 PCI0 init 3.17 PCI0 reset 3.34 PCIe scan 00001106:00003483 3.46 XHCI-STOP 3.46 xHC0 ver: 256 HCS: 05000420 fc000031 00e70004 HCC: 002841eb 3.47 USBSTS 11 3.47 xHC0 ver: 256 HCS: 05000420 fc000031 00e70004 HCC: 002841eb 3.48 xHC0 ports 5 slots 32 intrs 4 3.18 USB2[3] 400202e1 connected 3.33 USB2 root HUB port 1 init 3.53 DEV [01:00] 2.16 000000:01 class 9 VID 2109 PID 3431 3.53 HUB init [01:00] 2.16 000000:01

I have managed to build images for my own compiled Linux kernel source code using Yocto. Yocto has produced image files according to: http://www.crashcourse.ca/wiki/index.php/Yocto_Project_Quick_Start Example from above link: $ ls -F core-image-minimal-beagleboard-20121120113536.rootfs.jffs2 core-image-minimal-beagleboard-20121120113536.rootfs.tar.bz2 core-image-minimal-beagleboard.jffs2@ core-image-minimal-beagleboard.tar.bz2@ MLO-beagleboard@ MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0* modules-3.4.11-yocto-standard-r4.3-beagleboard.tgz README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt u-boot-beagleboard.bin@ u-boot-beagleboard-v2011.06+git6+b1af6f532e0d348b153d5c148369229d24af361a-r3.bin* u-boot.bin@ uImage@ uImage-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a555 4b81cc8ad23267d-r4.3-beagleboard-20121120113536.bin uImage-beagleboard.bin@ x-load-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0.bin.ift* x-load-beagleboard.bin.ift@ $ How do I use these Images to produce an SD card that can boot the Linux dist Yocto has produced? Partioning etc? How do I use my Yocto images?

I’m having some trouble with hostapd and nl80211. When I try to launch hostapd, this is what I get:

# /etc/init.d/hostapd start
Starting HOSTAP Daemon: Configuration file: /etc/hostapd.conf
nl80211: Driver does not support authentication/association or connect commands
nl80211 driver initialization failed.
hostapd_free_hapd_data: Interface wlan0 wasn't started

Is this due to the Wi-Fi driver (RTL8812au) or the nl80211 driver? I’m working on an ARM-based device with an i.MX6 processor. The driver is cross-compiled. Something strange: iwconfig works:

# iwconfig 
wlan0     unassociated  Nickname:""
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

But when I run iw list, nothing happens. Can someone help me with this problem? Additional info: - Yocto and custom BSP on the i.MX6 board - Kernel version: 3.14.28 - Linux distribution: Poky 1.8.1 - Wi-Fi USB key: Edimax EW-7811USC

I asked this question on StackOverflow before but got told here is the right spot to ask. Since im new to Yocto I ran into some problems trying to boot my intel-corei7-64 core-image-minimal from HDD. I used dd to put it on the hard drive but while booting it stops with a Kernel panic:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0)

I tried a lot and searched for a solution. First of all I had to do a grub-install and configured the grub.cfg file in the boot partition to list the Image in GRUB but I am not getting any further than that point. In some forums they said its meaning that the initramfs is missing. I dont think that the image itself is broken because it works on a usb flash drive. My grub.cfg looks like this:

set default="0"
set timeout="30"

menuentry 'Yocto' {
        insmod part_msdos
        insmod part_gpt
        insmod ext2
        insmod all_video
        set root='(hd0,gpt2)'
        linux /boot/bzImage-4.19.40-intel-pk-standard root=/dev/sda2
}

Would be great if you guys could help me fixing the boot error. I am pretty much helpless at this point. Best regards Alex

I have a custom Linux distro built with Yocto/Poky on branch thud. I'm using opkg as software to manage my packages updates on my embedded systems. I have hundreds of systems running and wanted to upgrade an important package on them (my-custom-package). On the vast majority of them, everything went fine but on 4 systems I'm facing these errors :

root@hostname:~# opkg -v
opkg version 0.3.6 (libsolv 0.6.35)

root@hostname:~# opkg upgrade my-custom-package -V 2
opkg_conf_parse_file: Loading conf file /etc/opkg/arch.conf.
opkg_conf_parse_file: Supported arch all priority (1)
opkg_conf_parse_file: Supported arch any priority (6)
opkg_conf_parse_file: Supported arch noarch priority (11)
opkg_conf_parse_file: Supported arch armv5hf-vfp priority (16)
opkg_conf_parse_file: Supported arch armv5thf-vfp priority (21)
opkg_conf_parse_file: Supported arch armv5ehf-vfp priority (26)
opkg_conf_parse_file: Supported arch armv5tehf-vfp priority (31)
opkg_conf_parse_file: Supported arch armv6hf-vfp priority (36)
opkg_conf_parse_file: Supported arch armv6thf-vfp priority (41)
opkg_conf_parse_file: Supported arch armv7ahf-vfp priority (46)
opkg_conf_parse_file: Supported arch armv7at2hf-vfp priority (51)
opkg_conf_parse_file: Supported arch armv7ahf-neon priority (56)
opkg_conf_parse_file: Supported arch armv7at2hf-neon priority (61)
opkg_conf_parse_file: Supported arch cortexa9hf-vfp priority (66)
opkg_conf_parse_file: Supported arch cortexa9hf-neon priority (71)
opkg_conf_parse_file: Supported arch cortexa9t2hf-vfp priority (76)
opkg_conf_parse_file: Supported arch cortexa9t2hf-neon priority (81)
opkg_conf_parse_file: Supported arch cortexa9t2hf-neon-mx6sx priority (86)
opkg_conf_parse_file: Supported arch cortexa9hf-neon-mx6sx priority (91)
opkg_conf_parse_file: Supported arch udooneo priority (96)
opkg_conf_parse_file: Loading conf file /etc/opkg/opkg.conf.
pkg_hash_load_feeds:
pkg_hash_load_status_files:
pkg_info_preinstall_check: Updating file owner list.



opkg_configure_packages: Configuring unpacked packages.
opkg_configure_packages: Reordering packages before configuring them...
Collected errors:
 * Solver encountered 3 problem(s):
 * Problem 1/3:
 *   - nothing provides requested python3-core
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-core

 * Problem 2/3:
 *   - nothing provides requested python3-ctypes
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-ctypes

 * Problem 3/3:
 *   - nothing provides requested python3-mime
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-mime



root@hostname:~# opkg info my-custom-package
Package: my-custom-package
Version: 3.2-r3
Depends: python3-core, python3-fcntl, python3-inotify-simple, python3-psutil, python3-pymonocypher, python3-pythonping, python3-requests, python3-simplejson, python3-websocket-client
Recommends: ca-certificates, gsm-tools, iw, update-rc.d
Status: unknown ok not-installed
Section: base
Architecture: cortexa9t2hf-neon
Maintainer:
MD5Sum: 883ef1ca5659cdd77a7947662daaa115
Size: 22252
Filename: my-custom-package_3.2-r3_cortexa9t2hf-neon.ipk
Source: my-custom-package_3.2.bb
Description: my-custom-package version 3.2-r3

Package: my-custom-package
Version: 2.1-r9
Depends: python-core, python-logging, python-psutil, python-requests, python-simplejson, python-subprocess, python-websocket-client
Recommends: ca-certificates, gsm-tools, iw, update-rc.d
Status: install ok installed
Architecture: cortexa9t2hf-neon
Installed-Size: 33328
Installed-Time: 1573829351


root@hostname:~# opkg install python3-core -V2
opkg_conf_parse_file: Loading conf file /etc/opkg/arch.conf.
opkg_conf_parse_file: Supported arch all priority (1)
opkg_conf_parse_file: Supported arch any priority (6)
opkg_conf_parse_file: Supported arch noarch priority (11)
opkg_conf_parse_file: Supported arch armv5hf-vfp priority (16)
opkg_conf_parse_file: Supported arch armv5thf-vfp priority (21)
opkg_conf_parse_file: Supported arch armv5ehf-vfp priority (26)
opkg_conf_parse_file: Supported arch armv5tehf-vfp priority (31)
opkg_conf_parse_file: Supported arch armv6hf-vfp priority (36)
opkg_conf_parse_file: Supported arch armv6thf-vfp priority (41)
opkg_conf_parse_file: Supported arch armv7ahf-vfp priority (46)
opkg_conf_parse_file: Supported arch armv7at2hf-vfp priority (51)
opkg_conf_parse_file: Supported arch armv7ahf-neon priority (56)
opkg_conf_parse_file: Supported arch armv7at2hf-neon priority (61)
opkg_conf_parse_file: Supported arch cortexa9hf-vfp priority (66)
opkg_conf_parse_file: Supported arch cortexa9hf-neon priority (71)
opkg_conf_parse_file: Supported arch cortexa9t2hf-vfp priority (76)
opkg_conf_parse_file: Supported arch cortexa9t2hf-neon priority (81)
opkg_conf_parse_file: Supported arch cortexa9t2hf-neon-mx6sx priority (86)
opkg_conf_parse_file: Supported arch cortexa9hf-neon-mx6sx priority (91)
opkg_conf_parse_file: Supported arch udooneo priority (96)
opkg_conf_parse_file: Loading conf file /etc/opkg/opkg.conf.
pkg_hash_load_feeds:
pkg_hash_load_status_files:
pkg_info_preinstall_check: Updating file owner list.



opkg_configure_packages: Configuring unpacked packages.
opkg_configure_packages: Reordering packages before configuring them...
Collected errors:
 * Solver encountered 3 problem(s):
 * Problem 1/3:
 *   - nothing provides requested python3-core
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-core

 * Problem 2/3:
 *   - nothing provides requested python3-ctypes
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-ctypes

 * Problem 3/3:
 *   - nothing provides requested python3-mime
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-mime


root@hostname:~# opkg info python3-core
Package: python3-core
Version: 3.5.6-r1.0
Depends: libc6 (>= 2.28), libpython3.5m1.0 (>= 3.5.6), libreadline7 (>= 7.0), libz1 (>= 1.2.11)
Status: install ok not-installed
Section: devel/python
Architecture: cortexa9t2hf-neon
Maintainer: 
MD5Sum: 6f56b22b7993c0cf351559a944abe0df
Size: 1027792
Filename: python3-core_3.5.6-r1.0_cortexa9t2hf-neon.ipk
Source: python3_3.5.6.bb
Description: Python interpreter and core modules

root@hostname:~# opkg info python3-mime
Package: python3-mime
Version: 3.5.6-r1.0
Depends: python3-core
Status: install ok not-installed
Section: devel/python
Architecture: cortexa9t2hf-neon
Maintainer: 
MD5Sum: f9254dc437295edfa828ab8d68d9d5f8
Size: 10074
Filename: python3-mime_3.5.6-r1.0_cortexa9t2hf-neon.ipk
Source: python3_3.5.6.bb
Description: Python MIME handling APIs

root@hostname:~# opkg info python3-ctypes
Package: python3-ctypes
Version: 3.5.6-r1.0
Depends: libc6 (>= 2.28), libffi6 (>= 3.2.1), libpython3.5m1.0 (>= 3.5.6), python3-core
Status: install ok not-installed
Section: devel/python
Architecture: cortexa9t2hf-neon
Maintainer: 
MD5Sum: 2667c24b23434635208177d03d6efcc6
Size: 67912
Filename: python3-ctypes_3.5.6-r1.0_cortexa9t2hf-neon.ipk
Source: python3_3.5.6.bb
Description: Python C types support

So my-custom-package has several Python dependencies and opkg seems to not be able to find them. But when I run opkg info on dependencies, I get a result and opkg finds the packet. I verified on my respository if the compressed packets to download were there and everything seems fine. Also one of my problematic embedded systems runs in the same bulding as others which were installed the same day (so come from same image, same compilation,...). I'm used to update packages with opkg from remote. I encountered this kind of issue just once about 6 months ago on a single system but, as it was an upgrade of a non critical package, I just ignored the issue. I tried opkg clean but no success. I've read the man page to look for some helping commands but none seems to have an effect. EDIT: Another interesting things:

root@hostname:~# opkg download python3-core
Downloading https://my-repository/ipks/v2/cortexa9t2hf-neon/python3-core_3.5.6-r1.0_cortexa9t2hf-neon.ipk .
Downloaded python3-core as python3-core_3.5.6-r1.0_cortexa9t2hf-neon.ipk.

So if I try to just download one of the packages opkg can't find, it works... Also, a simple opkg list-upgradable returns the same kind of errors:

root@hostname:~# opkg list-upgradable



Collected errors:
 * Solver encountered 3 problem(s):
 * Problem 1/3:
 *   - nothing provides requested python3-core
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-core

 * Problem 2/3:
 *   - nothing provides requested python3-ctypes
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-ctypes

 * Problem 3/3:
 *   - nothing provides requested python3-mime
 *
 * Solution 1:
 *   - do not ask to install a package providing python3-mime

`

Yocto System taking more time to resume from S3 sleep, it should take 2sec, but taking 12sec: Suspend entry: [ 244.086061] PM: suspend entry (deep) Low-level resume complete: [ 246.900251] Suspend exit: [ 247.970167] Display usable (login/dmesg): [ 257.556554] sshd or ACP logs visible Stage Time (sec) Suspend → Low-level resume ~2.81s Suspend → Suspend exit ~3.88s Suspend → Usable system ~13.5s How do I diagnose this and identify the part where it gets stuck for so long?

system hang with G2/G3 NIC card after resuming from S3 suspend. But it works with G1 NIC & ethernet. What is the culprit here xhci_hcd 0000:03:00.3: Controller not ready at resume -19 xhci_hcd 0000:03:00.3: PCI post-resume error -19! xhci_hcd 0000:03:00.3: HC died; cleaning up xhci_hcd 0000:03:00.4: Controller not ready at resume -19 xhci_hcd 0000:03:00.4: PCI post-resume error -19! xhci_hcd 0000:03:00.4: HC died; cleaning up xhci_hcd 0000:03:00.3: PM: dpm_run_callback(): pci_pm_resume returns -19 xhci_hcd 0000:03:00.4: PM: dpm_run_callback(): pci_pm_resume returns -19 xhci_hcd 0000:03:00.3: PM: failed to resume async: error -19 xhci_hcd 0000:03:00.4: PM: failed to resume async: error -19

I am trying to compile Ceres solver on a yocto build (for Intel Aero drone). I earlier tried pulling using the git repository at https://ceres-solver.googlesource.com/ceres-solver/ but could not get it to fetch. So I downloaded the tar.gz file myself, uploaded it on a public domain I own and tried to compile. Here is how my bb file looks as of now. LICENSE = "CLOSED" LIC_FILES_CHKSUM = "" DEPENDS = "glog gcc libeigen" SRC_URI = "http://sidj.in/wp-content/uploads/2017/06/ceres-solver-41455566ac633e55f222bce7c4d2cb4cc33d5c72.tar.gz " SRC_URI[md5sum] = "6f24d5639bbe738e6f8ca5d7a129400e" SRC_URI[sha256sum] = "005ed7405350767f22164d9fff93b3613207eeef9cbb56afbd02335542360b16" PV = "1.0" S = "${WORKDIR}/ceres-cmake" inherit cmake pkgconfig # Specify any options you want to pass to cmake using EXTRA_OECMAKE: EXTRA_OECMAKE = "" Now I see the download getting completed, but upon running the bitbake ceres command, I get an error saying that CMakelists.txt could not be found, while it is clearly in the tar.gz file. I looked at other recipes that seem to work, and feel that the do_unpack step is not the one failing. The output of the console is: Loading cache...done. Loaded 2790 entries from dependency cache. Parsing recipes...done. Parsing of 2225 .bb files complete (2219 cached, 6 parsed). 2794 targets, 109 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.30.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "intel-aero" DISTRO = "poky-aero" DISTRO_VERSION = "1.4.0-dev" TUNE_FEATURES = "m64 corei7" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "HEAD:cca8dd15c8096626052f6d8d25ff1e9a606104a3" meta-qt4 = "HEAD:fc9b050569e94b5176bed28b69ef28514e4e4553" meta-qt5 = "HEAD:9aa870eecf6dc7a87678393bd55b97e21033ab48" meta-uav = "HEAD:0f9395139b6a3c3f0f2c18a6a87f4048d0ca1a4f" meta-ros = "HEAD:4258013ec33f5ed2b0c9be12fb5902fe918fe98b" meta-intel-realsense = "HEAD:82e9dbfd8783292f42f4a6fcc7bd5b8a6b1c567a" meta-intel-aero = "HEAD:1d7e341ff35aa903c37491f94677bdacc9427f6e" meta-oe meta-python meta-networking = "HEAD:55c8a76da5dc099a7bc3838495c672140cedb78e" meta-cmu-rasl = "master:39e39bf41e915323bf7cb70cad50e67cb8b1b90e" meta-dense-visual-tracking = "HEAD:cca8dd15c8096626052f6d8d25ff1e9a606104a3" meta-intel = "HEAD:1f8dd1b00ce9c72d73583c405ec392690d9b08b7" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Running setscene task 184 of 202 (/home/thesidjway/rasl_ws/src/intel-aero/poky/meta-dense-visual-tracking/recipes-dry/ceres/ceres.bb, do_populate_lic_setscene) NOTE: recipe ceres-1.0-r0: task do_populate_lic_setscene: Started NOTE: recipe ceres-1.0-r0: task do_populate_lic_setscene: Succeeded NOTE: Executing RunQueue Tasks NOTE: Running task 711 of 722 (ID: 4, /home/thesidjway/rasl_ws/src/intel-aero/poky/meta-dense-visual-tracking/recipes-dry/ceres/ceres.bb, do_fetch) NOTE: recipe ceres-1.0-r0: task do_fetch: Started NOTE: recipe ceres-1.0-r0: task do_fetch: Succeeded NOTE: Running task 712 of 722 (ID: 0, /home/thesidjway/rasl_ws/src/intel-aero/poky/meta-dense-visual-tracking/recipes-dry/ceres/ceres.bb, do_unpack) NOTE: recipe ceres-1.0-r0: task do_unpack: Started NOTE: recipe ceres-1.0-r0: task do_unpack: Succeeded NOTE: Running task 713 of 722 (ID: 1, /home/thesidjway/rasl_ws/src/intel-aero/poky/meta-dense-visual-tracking/recipes-dry/ceres/ceres.bb, do_patch) NOTE: recipe ceres-1.0-r0: task do_patch: Started NOTE: recipe ceres-1.0-r0: task do_patch: Succeeded NOTE: Running task 714 of 722 (ID: 5, /home/thesidjway/rasl_ws/src/intel-aero/poky/meta-dense-visual-tracking/recipes-dry/ceres/ceres.bb, do_generate_toolchain_file) NOTE: recipe ceres-1.0-r0: task do_generate_toolchain_file: Started NOTE: recipe ceres-1.0-r0: task do_generate_toolchain_file: Succeeded NOTE: Running task 716 of 722 (ID: 6, /home/thesidjway/rasl_ws/src/intel-aero/poky/meta-dense-visual-tracking/recipes-dry/ceres/ceres.bb, do_configure) NOTE: recipe ceres-1.0-r0: task do_configure: Started Log data follows: | DEBUG: Executing python function sysroot_cleansstate | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing shell function do_configure | CMake Error: The source directory "/home/thesidjway/rasl_ws/src/intel-aero/poky/build/tmp/work/x86_64-linux/ceres/1.0-r0/ceres-cmake" does not appear to contain CMakeLists.txt. | Specify --help for usage, or press the help button on the CMake GUI. | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure (log file is located at /home/thesidjway/rasl_ws/src/intel-aero/poky/build/tmp/work/x86_64-linux/ceres/1.0-r0/temp/log.do_configure.9002) NOTE: recipe ceres-1.0-r0: task do_configure: Failed NOTE: Tasks Summary: Attempted 716 tasks of which 711 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/thesidjway/rasl_ws/src/intel-aero/poky/meta-dense-visual-tracking/recipes-dry/ceres/ceres.bb, do_configure Summary: There was 1 ERROR message shown, returning a non-zero exit code. Am I doing something stupid or wrong?

My Linux distribution uses the redis database. At boot the redis-server needs about 80 seconds to load the dataset. The following is a log that shows what I have written:

redis-server: 249:M 17 Oct 2022 16:29:55.173 * DB loaded from append only file: 79.442 seconds

If a Python program tries querying the database before the redis-server has finished the loading in memory operation, it is raised the Exception: redis.exceptions.BusyLoadingError. The Exception description is: Redis is loading the dataset in memory and is compliant with the context that I have described (that is the database is loading data in memory). Because I'm using the default configuration of redis-server in this moment I don't know exactly what is the type of persistence used by redis-server. The file redis.conf is very long so, here, I report settings that I think are most important:

...
########################### SNAPSHOTTING  ###########################
#
# Save the DB on disk:
#
#   save  
#
#   Will save the DB if both the given number of seconds and the given
#   number of write operations against the DB occurred.

# OE: tune for a small embedded system with a limited # of keys.
save 120 1
save 60 100
save 30 1000

######################### APPEND ONLY MODE #########################
# OE: changed default to enable this
appendonly yes

# The name of the append only file (default: "appendonly.aof")
appendfilename "appendonly.aof"
...

These settings (in particular appendonly yes) seem indicate that the persistence type used by the database is: Append Only File (AOF). I think these settings are causing this long loading time. Is it possible to use settings that avoid a too long loading time at boot?

Does Yocto Linux load manage the cores on a multiple core CPU? Tried looking for info on forums, etc. Can't find a definite answer. Thanks!

I'm struggling to understand boot process on Yocto linux (Dizzy) which I got as pre-built image. It boots in xfce; pidof /sbin/init shows "1" which should mean that it's SysVinit. However, there is no /etc/inittab file and systemd process is started. I just want to change default runlevel to 3.

On my yocto distribution I can't mount USB key with exfat filesystem. If I execute the command:

> blkid /dev/sda         
/dev/sda: LABEL="my-label" UUID="FC4D-5949" BLOCK_SIZE="512" TYPE="exfat"

So I'm sure that the USB filesystem is exfat, but when I try to execute the mount command I get the following error:

> mount /dev/sda /media
mount: /media: unknown filesystem type 'exfat'.

If I execute the command cat /proc/filesystems ([here](https://unix.stackexchange.com/questions/230755/how-can-i-know-if-my-kernel-has-exfat-support/230757#230757) I have found the cat command) I can find that the list of file systems supported by the kernel is:

> cat /proc/filesystems 
nodev   sysfs
nodev   tmpfs
nodev   bdev
nodev   proc
nodev   cgroup
nodev   cgroup2
nodev   cpuset
nodev   devtmpfs
nodev   debugfs
nodev   tracefs
nodev   securityfs
nodev   sockfs
nodev   bpf
nodev   pipefs
nodev   ramfs
nodev   hugetlbfs
nodev   rpc_pipefs
nodev   devpts
        ext3
        ext2
        ext4
        vfat
        msdos
        iso9660
nodev   nfs
nodev   nfs4
nodev   cifs
nodev   smb3
nodev   autofs
nodev   overlay
nodev   efivarfs
nodev   mqueue
        btrfs

exfat is missing. Could someone explained me how can I mount an exfat USB in my yocto distribution?

To enable the mount of USB key formatted with file system ntfs I have created the following configuration fragment file:

CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y

This file sets the parameters CONFIG_NTFS_FS and CONFIG_NTFS_RW used by the kernel build. To compile the kernel I have used the command:

bitbake -C compile virtual/kernel

With this modification of the kernel config my distribution is able to execute the mount of an ntfs USB by the command:

> mount /dev/sda /media/sda

where /dev/sda is the device associated with the USB key, and /media/sda is the mount point. The file system is mounted but read-only. This is showed by the following command:

# mount | grep media
/dev/sda on /media/sda type ntfs (ro,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1)

In the fragment file I have set CONFIG_NTFS_RW=y, so why the ntfs file system of a USB key is mounted read-only? ___ **EDIT** If I execute the command dmesg I obtain the following message:

> dmesg
...
(device sda): load_system_files(): Volume is dirty.  Mounting read-only.  Run chkdsk and mount in Windows.

I have followed the info written in the previous message: - I have inserted the USB on a Windows system - The Windows system has executed a scanfix of the USB After that I have execute correctly the mount R/W of the USB on my Linux system:

> mount -t ntfs /dev/sda /media/sda
> mount | grep media
/dev/sda on /media/sda type ntfs (rw,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_multiplier=1)

At this point if I try to write on the USB I get the following error:

> touch /media/sda/write_ntfs.txt
touch: cannot touch '/media/sda/write_ntfs.txt': Permission denied

The same if I try to change the permission of a file present on the USB:

> chmod 777 /media/sda/filename.csv
chmod: changing permissions of '/media/sda/filename.csv': Operation not supported

So, despite the output of the command mount, seems that the mount of the USB is yet read-only!