[Bug 2127473] Re: [SRU] Update linux-firmware-nvidia-tegra to 38.2.2

Dave Jones 2127473 at bugs.launchpad.net
Tue Dec 9 23:00:14 UTC 2025 

Ravi's asked me to take a look at sponsoring the noble upload. The diff
looks reasonable (or at least as reasonable as binary blob packages ever
do!), though I'm a bit concerned about the test plan...

1. The test plan talks about a noble image for one board, and a jammy
image for one other board. It would appear no testing can be done for
the current plucky and questing uploads because there are no
corresponding images (what happens if users attempt to upgrade a noble
image to plucky or questing?), and jammy is marked won't fix anyway (is
that part of the test plan still relevant?)

2. The firmware files which are touched (according to the other info
section) appear to cover rather more than just bluetooth and wifi (e.g.
nvenv, nvjpg, presumably for video / image encode/decode, and a whole
bunch of encryption stuff), but the test plan only seems to check
bluetooth and wifi functionality?

3. The test plan talks about riverside-proposed; but I'd assume
validators should be grabbing the package to test from $series-proposed
(e.g. noble-proposed)

Could someone take a look at the test plan again, and see if these
concerns can be addressed?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2127473

Title:
  [SRU] Update linux-firmware-nvidia-tegra to 38.2.2

Status in linux-firmware-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-firmware-nvidia-tegra source package in Jammy:
  Won't Fix
Status in linux-firmware-nvidia-tegra source package in Noble:
  New
Status in linux-firmware-nvidia-tegra source package in Plucky:
  Fix Committed
Status in linux-firmware-nvidia-tegra source package in Questing:
  Fix Committed
Status in linux-firmware-nvidia-tegra source package in Resolute:
  Fix Released

Bug description:
  [ Impact ]

   * Updates the /lib/firmware files for the NVIDIA Tegra Jetson Orin devices with Jetson Linux v38.2.2
   * Includes new firmware files for NVIDIA Tegra Jetson Thor devices
   * Firmware updates are necessary to guarantee full compatibility with the linux-nvidia-tegra kernel for noble
   * The target series for this change are noble
   * Most importantly, this update ships firmware for display and bluetooth

  [ Test Plan ]

  Thor:
   * Boot a Jetson AGX Thor from current Ubuntu for Jetson early access image (https://people.canonical.com/~platform/images/nvidia-tegra/ubuntu-24.04-preinstalled-server-thor-arm64+jetson.img.xz)
   * Update to latest packages and reboot
   * Run "$ sudo apt install -y bluez && sudo hciconfig" and observe the following output:

  hci0: Type: Primary Bus: USB
          BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
          DOWN
          RX bytes:0 acl:0 sco:0 events:0 errors:0
          TX bytes:0 acl:0 sco:0 commands:0 errors:0

   * Install linux-firmware-nvidia-tegra from riverside-proposed; This is currently the resolute version but it's fine to install it on a noble image
   * Reboot, run "$ sudo hciconfig" and observe something along the following:

  ubuntu at ubuntu:~$ sudo hciconfig
  hci0:	Type: Primary  Bus: USB
   BD Address: C0:BF:BE:85:53:09  ACL MTU: 1021:8  SCO MTU: 255:12
   UP RUNNING
   RX bytes:1541 acl:0 sco:0 events:109 errors:0
   TX bytes:2528 acl:0 sco:0 commands:109 errors:0

  Orin:
   * Boot a Jetson AGX Orin from current Ubuntu for Jetson GA image (https://cdimage.ubuntu.com/releases/jammy/release/nvidia-tegra/ubuntu-22.04-preinstalled-server-arm64+tegra-jetson.img.xz)
   * Update to latest packages, reboot, see that there is a WLAN interface (e.g. wlP1p1s0) by running
  ip link
   * Install linux-firmware-nvidia-tegra from riverside-proposed;
   * Reboot, check the WLAN interface (e.g. wlP1p1s0) is still listed

  [ Where problems could occur ]

   * A firmware file update can introduce a regression. The impact will
  be limited on the Jetson devices only, and this should be detected by
  our automated test jobs during the SRU process.

  [ Other Info ]

   * 38.2.2 is related to Nvidia Jetpack 7.0 release: https://docs.nvidia.com/jetson/archives/r38.2.1/ReleaseNotes/Jetson_Linux_Release_Notes_r38.2.1.pdf
   * firmware files that got updated:
  /lib/firmware/display-t234-dce.bin
  /lib/firmware/nvhost_nvdla020.fw
  /lib/firmware/nvhost_nvdla030.fw
  /lib/firmware/nvhost_nvjpg013.fw
  /lib/firmware/nvhost_ofa012.fw
  /lib/firmware/nvhost_vic042.fw
  /lib/firmware/nvidia/ga10b/NETC_img_prod_encrypted.bin
  /lib/firmware/nvidia/ga10b/acr-gsp.data.encrypt.bin.prod
  /lib/firmware/nvidia/ga10b/acr-gsp.manifest.encrypt.bin.out.bin.prod
  /lib/firmware/nvidia/ga10b/acr-gsp.text.encrypt.bin.prod
  /lib/firmware/nvidia/ga10b/fecs_encrypt_prod.bin
  /lib/firmware/nvidia/ga10b/fecs_pkc_sig_encrypt.bin
  /lib/firmware/nvidia/ga10b/gpccs_encrypt_prod.bin
  /lib/firmware/nvidia/ga10b/gpccs_pkc_sig_encrypt.bin
  /lib/firmware/nvidia/ga10b/gpmu_ucode_next_prod_desc.bin
  /lib/firmware/nvidia/ga10b/gpmu_ucode_next_prod_image.bin
  /lib/firmware/nvidia/ga10b/pmu_pkc_prod_sig.bin
  /lib/firmware/nvidia/ga10b/safety-scheduler.data.encrypt.bin.prod
  /lib/firmware/nvidia/ga10b/safety-scheduler.manifest.encrypt.bin.out.bin.prod
  /lib/firmware/nvidia/ga10b/safety-scheduler.text.encrypt.bin.prod
  /lib/firmware/nvidia/tegra234/nvdla.bin
  /lib/firmware/nvidia/tegra234/nvenc.bin
  /lib/firmware/nvidia/tegra234/nvjpg.bin
  /lib/firmware/nvidia/tegra234/ofa.bin
  /lib/firmware/nvidia/tegra234/vic.bin
  /lib/firmware/nvpva_020.fw
  /lib/firmware/rtl8822cu_fw
  /lib/firmware/tegra23x/nvhost_nvdec050_desc_prod.bin
  /lib/firmware/tegra23x/nvhost_nvenc080.fw
  /lib/firmware/tegra23x/nvhost_nvjpg013.fw
  /lib/firmware/tegra23x/nvhost_tsec_desc.fw
  /lib/firmware/tegra23x/nvhost_tsec_riscv.fw

   * firmware files that got newly added for Thor platforms:
  /lib/firmware/display-t264-dce.bin
  /lib/firmware/nvhost_vic051.fw
  /lib/firmware/nvhost_vic051.fw.desc
  /lib/firmware/nvidia/gb10b/NETA_fecs_riscv_desc.bin
  /lib/firmware/nvidia/gb10b/NETA_gpccs_riscv_desc.bin
  /lib/firmware/nvidia/gb10b/NETA_img_prod_encrypted.bin
  /lib/firmware/nvidia/gb10b/NETD_fecs_riscv_desc.bin
  /lib/firmware/nvidia/gb10b/NETD_gpccs_riscv_desc.bin
  /lib/firmware/nvidia/gb10b/NETD_img_prod_encrypted.bin
  /lib/firmware/nvidia/gb10b/fecs_riscv_pkc_sig_encrypt.bin
  /lib/firmware/nvidia/gb10b/g_c85b6_gb10b_riscv_desc.bin
  /lib/firmware/nvidia/gb10b/g_c85b6_gb10b_riscv_image_prod_encrypted.bin
  /lib/firmware/nvidia/gb10b/g_c85b6_gb10b_riscv_pkc_ls_sig.bin
  /lib/firmware/nvidia/gb10b/g_fecs_riscv_gb10b_NETA_pkc_ls_sig.bin
  /lib/firmware/nvidia/gb10b/g_gpccs_riscv_gb10b_NETA_pkc_ls_sig.bin
  /lib/firmware/nvidia/gb10b/g_nvdec_t264_riscv_prod_desc.bin
  /lib/firmware/nvidia/gb10b/g_nvdec_t264_riscv_prod_image_prod_encrypted.bin
  /lib/firmware/nvidia/gb10b/g_nvdec_t264_riscv_prod_pkc_ls_sig.bin
  /lib/firmware/nvidia/gb10b/g_nvenc_t264_riscv_eb_desc.bin
  /lib/firmware/nvidia/gb10b/g_nvenc_t264_riscv_eb_image_prod_encrypted.bin
  /lib/firmware/nvidia/gb10b/g_nvenc_t264_riscv_eb_pkc_ls_sig.bin
  /lib/firmware/nvidia/gb10b/g_nvjpg_t264_riscv_eb_desc.bin
  /lib/firmware/nvidia/gb10b/g_nvjpg_t264_riscv_eb_image_prod_encrypted.bin
  /lib/firmware/nvidia/gb10b/g_nvjpg_t264_riscv_eb_pkc_ls_sig.bin
  /lib/firmware/nvidia/gb10b/g_ofa_t264_riscv_eb_desc.bin
  /lib/firmware/nvidia/gb10b/g_ofa_t264_riscv_eb_image_prod_encrypted.bin
  /lib/firmware/nvidia/gb10b/g_ofa_t264_riscv_eb_pkc_ls_sig.bin
  /lib/firmware/nvidia/gb10b/gpccs_riscv_pkc_sig_encrypt.bin
  /lib/firmware/nvpva_030.fw
  /lib/firmware/rtl8852cu_config
  /lib/firmware/rtl8852cu_fw
  /lib/firmware/nvidia/tegra264/vic.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nvidia-tegra/+bug/2127473/+subscriptions

More information about the Ubuntu-sponsors mailing list