Ubuntu Core 22 for Jetson (Jammy)¶

2026-05 Release Notes

Purpose¶

This is the General Availability release of Ubuntu Core 22 for Jetson. All release assets are provided by Canonical.

Images¶

Ubuntu images can be downloaded from https://ubuntu.com/download/nvidia-jetson:

Ubuntu Core 22:
- https://cdimage.ubuntu.com/releases/jammy/release/nvidia-tegra/ubuntu-core-22-arm64+tegra-jetson.img.xz
- Image SHA256SUM: a051ca3667e6410ec6dd4b4bf048dcfac0c4b3bd8b49552530f455a7e052b881
Boot firmware 36.5:
- https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v5.0/release/Jetson_Linux_r36.5.0_aarch64.tbz2
- Image SHA256SUM: 414e58d97ac4b84fb02cbca621d46598f0bc8b811b6b9c3ad778b04e8d321ca7

Hardware Platforms Tested¶

Release Highlights¶

First Ubuntu Core image release for Tegra platforms
Full Disk Encryption and secure boot support. Full Disk Encryption will be automatically enabled when hardware support is detected. For enabling secure boot, refer to the secure boot instructions
Strictly confined applications
OTA updates
Canonical QA team has been running intensive testing of this release in order to qualify it as Ubuntu certified on the three hardware platforms referenced below:

Features not supported in this release¶

Issue	Description
2070419	Wake-up from S5 using RTC alarm (Orin SoC)
2070428	WOL from power off isn’t supported, and WOL from suspend mode isn’t fully operational

Tests skipped or adapted during the certification¶

The following tests have been excluded from the CQA tests

Issue	Description
2071401 skipped	RTC clock 1 (skipped) : the development kits don’t have an external battery included
2071402 adapted	Thermal zones : Some of them aren’t readable on Nano and require a specific workaround on AGX
2071403 skipped	`CAAM` cryptography tests are only applicable to NXP devices
2071404 skipped	`MCRC` cryptography tests are only applicable to TI devices
2071405 skipped	`sa2ul` cryptography tests are only applicable to TI devices
2071407 skipped	`Crypto: no hwrng support` for Linux
2071416 skipped	MTD is only accessible in case of Recovery Mode boot
2071418 adapted	Tests have been adapted to match the detection of 2 SPI controllers with 2 CS per SPI
2071419 skipped	Write to EEPROM tests are not allowed on the development kits as that would break them
2071422 skipped	SPI physical tests were skipped because that requires defining a specific PIN MUX configuration
2073232 adapted	Orin doesn’t support waking up from offline mode, `rtcwake` tests have been adapted to test only resuming from suspend
2091263 skipped	`NVIDIA SOC i2c adapter 0` does not support detection commands

Known issues¶

Issue	Description
2061598	On an Orin NX development kit, the very first flash of the QSPI boot firmware might fail due to a write protection bit being set. In this case you need to perform an initrd flash of the QSPI firmware (only necessary once to fix this issue) by following these instructions: https://docs.nvidia.com/jetson/archives/r36.4.3/DeveloperGuide/IN/QuickStart.html#to-flash-the-jetson-developer-kit-operating-software. After this operation, every subsequent flash of the QSPI firmware will work the usual way.
2071414	Netplan.io package doesn’t support `WPA2-PSK-SHA256` in its current Jammy version. While the corrective patch is already available on the latest Ubuntu version (1.1.2), the Jammy backport should get released later on this year.
2039983	On AGX development kit, power cycling the device using an external power switch introduces a noise in the serial input buffer that can, depending on the nature of the power switch, pause the GRUB menu, or directly launch the default entry (action = ‘Enter’).
2081138	As part of the compliance tests for camera, we figured out that running `gst-device-monitor-1.0 Video/Source` would not list any device. This is because `gst-plugins-good1.0` is released as v1.20 in Jammy, while this issue was resolved with a patch available with 1.24.
2081139	Similarly, the command `gst-device-monitor-1.0` will output a few “GStreamer-CRITICAL” when a camera is connected to the devkit. This is because the tool will send a `VIDIOC_QUERYCAP` instead of a `VIDIOC_SUBDEV_QUERYCAP` for a sub device. This needs to be fixed first in `gst-plugins-good1.0` before getting released in Ubuntu.
2091684	When a monitor is connected to the device, the gstreamer transcoding might be considerably slower than without.
2083007	On AGX, after installing the `nvpmodel` snap, all CPU governor tests on policy 8 failed. That’s because the snap will install and apply the default related model.
2083009	Similarly, on NX, after installing the `nvpmodel` snap, all CPU governor tests on policy 4 failed
2150448	While running the gstreamer image capture pipelines described in the tegra snap samples repository, the pipeline can return an error code of 1 even though the image gets captured correctly. This is due to a bug in the nvarguscamerasrc plugin that will fail to clean up the pipeline correctly.
NA	Running LXD and Docker on the same host can cause connectivity issues. This is something to keep in mind after installing Nvidia Container runtime.

Report Bugs¶

If a bug is found in a specific snap, bugs should be reported against that specific snap using the contact on that snap’s page on https://snapcraft.io. If a generic Ubuntu Core system bug is discovered, please report it to snapd under https://bugs.launchpad.net/snapd/+filebug. For firmware related issues, report a bug in the launchpad project.