commontorizon / meta-common-torizon Goto Github PK

Booting from sdcard with USR/BOOT button pressed gives the follow log:

U-Boot SPL 2023.04-g4750afef5b (Jan 01 1970 - 00:00:00 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 1856 bytes
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
Card did not respond to voltage select! : -110
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from MMC2
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
Card did not respond to voltage select! : -110
spl: mmc init failed with error: -95
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

this is a regression, I tested on the v6.3.0, and it's not reproducible

Let's discuss here how we can create a live installer for Common Torizon.

It would be nice to be able to manage DTBOs and applied overlays in config.txt using an OStree secondary (since they live on a special partition for the Pi).

I would find it useful to be able to deploy changes either as part of the OS image, or as an additional Aktualizr secondary (rather than manual massaging via scripts that can lead to breakage on Ostree rollback events)

The About section for this repo

shows the old name TorizonCore twice.
Since now the name is Torizon OS, I suggest to update the About section accordingly.

Thanks

I see no x86_64 QEMU machine in https://github.com/commontorizon/Documentation/blob/main/BUILDING.md.

Any plans in adding it?

I've heard the guys at common Torizon want to set up a build machine, and that Toradex can provide a machine. So opening this ticket to publicly document the work being done here.

Hello,

After using "ostree admin unlock --hotfix" system doesnt boot anymore.
I used ostree admin unlock --hotfix and after that modified systemd service file and after rebooting system is stuck on splash screen.

I am using Torzion OS v6.4.0-common and running it on RaspberryPi CM4.
Here is the log:

U-Boot 2022.01 (Jan 01 1970 - 00:00:00 +0000)

DRAM: 1.9 GiB
RPI Compute Module 4 (0xb03140)
MMC: mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from FAT... OK
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@7d580000
PCIe BRCM: link down
starting USB...
No working controllers found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
1217 bytes read in 10 ms (118.2 KiB/s)

Executing script at 02400000

2783 bytes read in 20 ms (135.7 KiB/s)
WARNING: could not set bootargs FDT_ERR_NOSPACE.
24283648 bytes read in 1052 ms (22 MiB/s)
11425011 bytes read in 500 ms (21.8 MiB/s)
Moving Image from 0x80000 to 0x200000, end=1a20000

Flattened Device Tree blob at 2eff2c00

Booting using the fdt blob at 0x2eff2c00
Using Device Tree in place at 000000002eff2c00, end 000000002f002fff

Starting kernel ...

[ 1.518831] brcm-pcie fd500000.pcie: link down
Starting version 250.5+

I tried this multiple times and got same result, also i tried it without changing any file and got same result.

To fix a reboot loop on the Beagleplay the config for it kernel has:

# CONFIG_WATCHDOG is not set

We need to investigate the watchdog support.

Whould be great to have something more clean as package name like: machine-image

Currently, the Torizon Platform doesn't have any OS images for Common Torizon machines. This means that people using a Raspberry Pi or x86 for instance, cannot easily evaluate the Cloud remote updates workflow.

Setting up a public OSTree server where the Common Torizon team can push their OSTree images will overcome this limitation.

For example, if you run Weston it's does not have the right permissions to cleanup the .X11-unix and also does not have permissions to connect to x-server.

Should be good to show some logo on the bootloader, because the splash screen only is shown after the kernel on the initramfs, on slower boards nothing seems to be happening ☹️

This beagleplay-recovery-mode does not sounds correct. We need to investigate and get the actual serial number instead, as all the other models.

ERROR: initramfs-ostree-torizon-image-1.0-r0 do_rootfs: Unable to install packages. Command '/workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/opkg.conf -t /workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/temp/ipktemp/ -o /workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version --add-ignore-recommends busybox-syslog install base-passwd busybox initramfs-framework-base initramfs-module-debug initramfs-module-kmod initramfs-module-ostree initramfs-module-plymouth initramfs-module-rootfs initramfs-module-udev' returned 1:

• Solver encountered 1 problem(s):

• Problem 1/1:

• • conflicting requests
• • nothing provides kernel-module-display-connector needed by initramfs-module-kmod-1.0-r4.all

• Solution 1:

• • do not ask to install a package providing initramfs-module-kmod

• opkg_finalize_intercepts: Failed to open dir /workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/temp/ipktemp//opkg-mOl6YB/opkg-intercept-ZqkeP2: No such file or directory.

• rm_r: Failed to open dir /workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/temp/ipktemp//opkg-mOl6YB/opkg-intercept-ZqkeP2: No such file or directory.

• rm_r: Failed to open dir /workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/temp/ipktemp//opkg-mOl6YB: No such file or directory.

ERROR: Logfile of failure stored in: /workdir/torizon/build-torizon/tmp/work/verdin_imx8mp-tdx-linux/initramfs-ostree-torizon-image/1.0-r0/temp/log.do_rootfs.980282
ERROR: Task (/workdir/torizon/build-torizon/conf/../../layers/meta-common-torizon/recipes-core/images/initramfs-ostree-torizon-image.bb:do_rootfs) failed with exit code '1'

I was trying to build it for a custom board when i got this error. But i also get the same error when trying to build for below machine (verdin-imx8mp)

Build Configuration:
BB_VERSION = "2.0.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "aarch64-tdx-linux"
MACHINE = "verdin-imx8mp"
DISTRO = "torizon"
DISTRO_VERSION = "6.5.0-devel-20240125064644+build.0"
TUNE_FEATURES = "aarch64 armv8a crc cortexa53"
TARGET_FPU = ""

I am using commontorizon-manifest to build images.

Seems that the firmware is missing:
This is the error on kernel side:

wlcore: ERROR could not get configuration binary ti-connectivity/wl18xx-conf.bin: -2

I was making tests based on the v6.6.0 and the splash screen is not being show.

You can check that in the last pre-release: https://github.com/commontorizon/meta-common-torizon/releases/tag/v6.7.0-common the beagleplay entry has only 10MB, because the image was not built correctly and was no .wic file to compress.

When getting some examples of how to do stuff for Qt you can get weird intellisense issues because the cpp properties is not expecting C++17: https://github.com/toradex/vscode-torizon-templates/blob/34e86493492453eb2559a1ff6adbed0cd979013b/cppQML/.vscode/c_cpp_properties.json#L12C38-L12C38

Running on a Pi 4B, with wireless connection only.

I have configured WLAN with an appropriate wpa_supplicant.conf and an entry in /etc/systemd/network telling it to use DHCP for wlan0.

The interface comes up, and gains a correct IP address, but cannot reach the internet.
I am able to e.g. ping the router at 192.168.1.1, but ping 8.8.8.8 fails.

Further investigation reveals this is due to a missing /etc/resolv.conf as generated by systemd-resolved, which is not running.
journalctl -u systemd-resolved shows no errors or entries, and systemctl status shows it's enabled, but inactive (dead).

systemctl restart systemd-resolved or even just systemd-resolved --status seems to "wake" it up, after which resolv.conf is generated and the network connection becomes usable.

As far as I can tell, we have not made any changes to related areas of the system settings apart from adding the wlan0 entry for systemd-networkd.

Something like this:
https://community.toradex.com/t/build-error-when-building-torizon-minimal-and-xwayland-for-the-i-mx8mm/21772/3

The following error happens when trying to build torizon-core-podman for the machine qemu86-64:

ERROR: torizon-core-podman-1.0-r0 do_rootfs: Unable to install packages. Command '/home/leonardo/projects/commontorizon-builds/build-torizon-upstream/tmp/work/qemux86_64-tdx-linux/torizon-core-podman/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/leonardo/projects/commontorizon-builds/build-torizon-upstream/tmp/work/qemux86_64-tdx-linux/torizon-core-podman/1.0-r0/opkg.conf -t /home/leonardo/projects/commontorizon-builds/build-torizon-upstream/tmp/work/qemux86_64-tdx-linux/torizon-core-podman/1.0-r0/temp/ipktemp/ -o /home/leonardo/projects/commontorizon-builds/build-torizon-upstream/tmp/work/qemux86_64-tdx-linux/torizon-core-podman/1.0-r0/rootfs  --force_postinstall --prefer-arch-to-version   install aardvark-dns aktualizr aktualizr-info aktualizr-shared-prov auto-provisioning cpufrequtils curl docker-auto-prune docker-binfmt docker-compose docker-compose-up docker-integrity-checker docker-watchdog ethtool evtest fluent-bit fuse-overlayfs htop i2c-tools iproute2 iproute2-ip jq kernel-devsrc kernel-modules ldd less libpwquality mmc-utils nano neofetch netavark network-configuration nss-altfiles openssh-sftp-server os-release ostree ostree-customize-plymouth ostree-devicetree-overlays ostree-initramfs ostree-kernel packagegroup-base-extended packagegroup-core-boot packagegroup-core-full-cmdline-multiuser packagegroup-core-full-cmdline-utils packagegroup-core-ssh-openssh plymouth podman provision-device rac resize-helper rsync run-postinsts sshfs-fuse sudo systemd-analyze tdx-info torizon-conf torizon-users tzdata udev-toradex-rules usermount vim-tiny wireguard-tools zram' returned 1:
 * Solver encountered 1 problem(s):
 * Problem 1/1:
 *   - package podman-4.8.2+git-r0.core2-64 conflicts with docker provided by docker-ce-20.10.25-ce+git791d8ab87747169b4cbfcdf2fd57c81952bae6d5-r0.core2-64
 *   - package docker-binfmt-0.1-r0.all requires docker, but none of the providers can be installed
 *   - conflicting requests
 *   - conflicting requests
 * 
 * Solution 1:
 *   - do not ask to install a package providing podman

 * Solution 2:
 *   - do not ask to install a package providing docker-binfmt




ERROR: Logfile of failure stored in: /home/leonardo/projects/commontorizon-builds/build-torizon-upstream/tmp/work/qemux86_64-tdx-linux/torizon-core-podman/1.0-r0/temp/log.do_rootfs.3164891
ERROR: Task (/home/leonardo/projects/commontorizon-builds/build-torizon-upstream/conf/../../layers/meta-common-torizon/recipes-images/images/torizon-core-podman.bb:do_rootfs) failed with exit code '1'