Problems after booting Torizon OS 7.3.0 (Yocto build)

Technical Support
, , ,
1

Hi everyone!

Recently, we’ve been working on updating our system from Torizon OS 6.6.1 to TorizonCore 7.3.0.
We previously built Torizon 6.8.2 with our custom display driver without any issues. However, when attempting to build TorizonCore 7.3.0, the build process completes successfully, but the image shows several errors after booting.

We have attached the dmesg and journalctl logs for reference.
It’s worth mentioning that we used the “vanilla” torizon-docker image, following the official documentation:
Build TorizonCore from Source with Yocto Project/OpenEmbedded

The manifest we used was:

repo init -u git://git.toradex.com/toradex-manifest.git -b refs/tags/7.3.0 -m torizon/default.xml

We also tried building the same image on both Ubuntu 24.04 and Ubuntu 20.04, obtaining the same result in both cases.

Could you please help us identify what might be missing or misconfigured for TorizonCore 7.3.0?

Thanks in advance for your support!

dmesg (35.4 KB)

journalctl (150.2 KB)

Best regards,

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Common Issues When Moving from Torizon OS 6.x to 7.x

Based on your description of building TorizonCore 7.3.0 with a custom display driver, there are several key considerations when migrating from Torizon OS 6.x to 7.x versions.

1. Kernel and Device Tree Version Compatibility

The most common issue when upgrading major versions is device tree compatibility (1). Custom device trees and drivers that worked in Torizon OS 6.x may not be compatible with 7.x due to kernel version differences (1).

Recommended approach:

  • Re-base your custom device tree on the version provided in the Linux source tree for 7.3.0 rather than porting your old device tree (1)
  • Ensure your custom display driver is compatible with the kernel version used in Torizon OS 7.3.0 (1)

2. Manifest Path Changes

Note that the path to manifest files has changed for Torizon 7 (2). The manifest files were previously torizoncore/<manifest>.xml and are now torizon/<manifest>.xml (2).

Your command appears correct:

repo init -u git://git.toradex.com/toradex-manifest.git -b refs/tags/7.3.0 -m torizon/default.xml

(2)

3. Testing with Base Image First

To isolate the issue, test with the unmodified base tarball image first (1):

  • Deploy the vanilla torizon-docker image without your custom display driver
  • If the base image boots successfully, the issue is likely with your custom driver compatibility
  • If the base image also shows errors, there may be a broader compatibility issue (1)

4. Custom Layers Requirements

For Torizon OS builds, all custom layers must be version controlled by Git due to how layer revision information is included with OSTree (2). Ensure your custom display driver layer follows this requirement.

5. Build Environment Considerations

You mentioned testing on both Ubuntu 24.04 and Ubuntu 20.04. The Yocto Project has specific distribution version requirements, and not all distribution/Yocto version combinations are supported (3). If your distribution is not supported, you may get warnings during the first bitbake command (3).

Next Steps

  1. Test the vanilla image: Deploy the unmodified torizon-docker build to verify the base system works
  2. Update your custom driver: Ensure compatibility with the kernel version in Torizon OS 7.3.0
  3. Re-base device tree: Start with the 7.3.0 device tree and carefully apply your customizations
  4. Check logs: The boot errors in your dmesg and journalctl logs will provide specific clues about what’s failing

Without access to the specific error logs you mentioned, these are the most common issues encountered when upgrading between major Torizon OS versions.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Hi @Isaga!

Could you please share more details about the errors you’re facing? I’ve reviewed the log files, but the failure is not very clear since there is a lot of information.

Also, I noticed some journalctl errors related to mounting a device. Are you using an SD card or a USB stick? If so, could you let me know what it’s used for?

Best regards.

4

Hi Lucas !

Thank you for your response!

The primary problem is that the D-Bus system message bus fails to start repeatedly with the error:

Failed to start message bus: Could not get UID and GID for username "messagebus"

This causes a cascade of service failures including:

  • systemd-networkd

  • systemd-resolved

  • systemd-timesyncd

  • NetworkManager

  • ModemManager

  • Avahi

  • udisks2

It appears that essential system users and groups are missing from the built image:

  • messagebus (critical for D-Bus)

  • systemd-timesync

  • systemd-resolve

  • systemd-network

  • polkitd

  • avahi

  • And system groups like: disk, tty, utmp, systemd-journal, etc.

yes, we have aUSB stick connected. We use this USB drive for testing purposes and to install OS images during our development/testing proces

What’s particularly concerning is that this is a completely “vanilla” build. We haven’t added or removed any packages, modified any device trees, or made any custom configurations beyond following the official documentation. This suggests that the system users and groups are simply not being created during the build process, which should happen automatically in a standard TorizonCore build.

Are there additional configuration steps required in local.conf or layer configurations that differ from 6.x versions?

Could this be related to the base-passwd or systemd recipes in the 7.3.0 release?

Best regards,

5

Hi @Isaga!

Sorry for the delayed reply.

Have you tried installing the Torizon OS 7.3.0 image using the Toradex Easy Installer?

I ask that to try to nail down the issue. If the image present on our feeds is working, we could assume that there is some issue with the Yocto build.

Best regards.