TorizonOS Quarterly release and linux kernel version

Technical Support
, ,
1

Hello,

I build customised TorizonOS images using torizoncorebuilder (there are filesystem customisations, device tree overlays and an out of tree submodule). In my images/ directory i usually store downloaded os image from Download Links | Toradex Developer Center (Torizon OS 7 section e.g.)

In the build directory i have a linux kernel source code checked out as a submodule.

I’m looking to update my device OS to the latest Torizon OS, but i forgot how i used to figure out which linux kernel version should i point to. Currently i’m building using torizon-docker-verdin-am62-Tezi_7.3.0+build.18.tar and v6.6.94 (1acf4bc73f948578ade5f1231a63f6902dc3c361).

If i follow this page Build Custom Torizon OS Images | Toradex Developer Center and checkout latest on toradex_ti-linux-6.6.y , last commit is from 08 May 2026 (whereas Torizon OS release was published in february) so that seems kind of sketchy.. Is there a way to confirm the right kernel version without scouring through the yocto manifest files?

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.

Based on the sources, the proper way to determine the correct kernel version for building external kernel modules is to understand the Device Tree Overlays version information(1).

Kernel Version Alignment

The Device Tree Overlays branch matches perfectly with the Kernel branch(1). For upstream based modules, the branch is master, and for downstream based modules it is toradex_5.15-2.<n>.x-imx(1).

Determining the Right Kernel Version

From the documentation, when building external kernel modules with TorizonCore Builder, the tool automatically handles kernel version alignment(2). The build process uses the kernel source that corresponds to your specific Torizon OS image.

Recommended Approach

Rather than manually trying to match kernel versions, I recommend using TorizonCore Builder’s integrated approach(2):

  1. Use the build command approach - This generates a custom Torizon OS image with external kernel modules built automatically(2)
  2. Let TorizonCore Builder handle version matching - The tool ensures compatibility between your base image and the kernel source(2)

Alternative Method

If you need to verify the exact kernel version, you can check the kernel version information as referenced in the Device Tree Overlays documentation, which points to the Kernel Version Information section for specific branch details(1).

The discrepancy you’re seeing with commit dates might be related to the difference between when code was committed versus when releases were tagged and published.

To avoid version mismatches, I’d recommend sticking with TorizonCore Builder’s automated kernel module building process rather than manually managing kernel source 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

Greetings @stasgil

last commit is from 08 May 2026 (whereas Torizon OS release was published in february) so that seems kind of sketchy..

I don’t see why you would consider this “sketchy”. We do official releases on a quarterly basis, but our team continually develops and commits to our Linux kernel source. It’s like the main Linux kernel, there are continual commits by the community as a whole, between releases there as well.

Is there a way to confirm the right kernel version without scouring through the yocto manifest files?

If you want the exact commit that was used for your 7.3.0 version just checkout out the commit hash for that release. For example you shared 1acf4bc73f948578ade5f1231a63f6902dc3c361, which looks like a commit hash. If i check our Linux kernel repo for this I can find this commit: Making sure you're not a bot!

Which should be the exact commit that was used for this release of Torizon OS.

Best Regards,
Jeremias

4

To me building a version with the latest kernel checkout instead of a version which was used for quarterly release seemed “sketchy”, because I figured some testing is done for the TorizonOS using a specific kernel version, so it feels safer to use the same kernel version as in the release, but it was simply an assumption, as I don’t really know your processes. Also i typed my question in a bit of a rush, so apologies for the verbiage.

My question was, how do i find out which kernel version tag was used for TorizonOS 7.6.1?

And also, is the answer by the torizon AI, that torizoncorebuilder automatically checks out the correct kernel version based on the image used in the build true? In which case my question would be void :slight_smile:

5

My question was, how do i find out which kernel version tag was used for TorizonOS 7.6.1?

From the “Download Links” page go to the oedeploy url for whatever release you’re interested in. For example for Verdin AM62 on 7.6.1 it would be this: Index of torizoncore-oe-prod-frankfurt/scarthgap-7.x.y/release/38/verdin-am62/torizon/torizon-docker/oedeploy

On this page you can download the file .kernel_scmversion. This file contains a git commit hash. This is the git commit hash of the Linux kernel that was used to build this release.

And also, is the answer by the torizon AI, that torizoncorebuilder automatically checks out the correct kernel version based on the image used in the build true?

No it’s not completely true. TorizonCore Builder can extract the Linux headers from the OS that are used for compiling Linux kernel modules. Keep in mind these are just the headers though, it’s not the entire Linux source. So, if you need the whole Linux kernel source to compile a module found in the actual kernel source, then that’s different. You would need to check that out yourself.

Best Regards,
Jeremias