Ubuntu for Jetson 22.04 Server (Jammy)

2025-02 Release Notes

Purpose

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

Images

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

Hardware Platforms Tested

Release Highlights

Recent fixes

Issue

Description

2071409

No video output after resuming from suspend

2081141

3 Failures during v4l2 compliance test execution

2081801

No wireless device detected: fixed as wireless/bluetooth firmware files are now installed by default with linux-firmware-nvidia-tegra package in the Ubuntu image

2082057

bluetooth no default controller available

2081802

bluetooth beacon test failed

2081822

Failed to connect to any Wifi access points: wpa_supplicant is now installed by default in the Ubuntu image

2089043

Audio over DisplayPort only works when loading snd_hda_tegra and snd_hda_codec_hdmi in initramfs

2071428

On AGX, eth0 (ethernet interface) has been renamed to eno1 in order to have a predictable name

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.

2071321

Part of the stress tests executed during the certification tests are based on https://github.com/ColinIanKing/stress-ng. The following command failed to run successfully on the AGX development kit: stress-ng --af-alg 0 --timeout 30 --skip-silent --verbose. This issue is currently under investigation and should be fixed soon via a kernel package update. It does not affect the Nano/NX development kit because the related cryptography engines are not enabled with the current boot firmware version (a future release will also enable them).

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

During tests, GStreamer pipelines involving hardware encoding (nvv4l2h265enc) had slower performance than expected (3x time slower). This issue isn’t easily reproducible and still under investigation.

2083007

On AGX, after installing the nvidia-tegra-drivers-36 packages, all CPU governor tests on policy 8 failed. That’s because the packages are installing nvpmodel and applying the default related model.

2083009

Similarly, on NX, after installing the nvidia-tegra-drivers-36 packages, all CPU governor tests on policy 4 failed

2097636

While running the transcoding test pipelines described in the installation instructions: gst-launch-1.0 filesrc location=h264-reenc.mp4 ! qtdemux !   h264parse ! nvv4l2decoder ! nvv4l2av1enc ! matroskamux name=mux !   filesink location=av1-reenc.mkv -e thousands of error traces ParseObuFrameHeader: 2367: Invalid buf_idx = -1 or  offset are displayed. While this is looking suspicious, this trace isn’t actually preventing the command to finish properly and successfully.

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

To report a bug, identify the related package in https://launchpad.net/ubuntu , create a bug, then subscribe the team ubuntu-tegra to it. For firmware related issues, report a bug in the launchpad project.