[Bug 2127473] Re: [SRU] Update linux-firmware-nvidia-tegra to 38.2.2
Dave Jones
2127473 at bugs.launchpad.net
Mon Dec 15 12:03:21 UTC 2025
> 1a. Indeed there are no plucky or questing images, as there are no
> customized kernel for those series. There's more context about
> upgrades in
> https://bugs.launchpad.net/ubuntu/+source/nvidia-tegra-defaults/+bug/2127100
> but basically, that's something we are planning to prevent in
> ubuntu-release-upgrader for the time being.
Okay, sounds like a plan is in place there.
> 1b. I am gonna remove the Jammy/Orin part as indeed it is not relevant
> anymore.
> 3. Correct, I am going to rephrase the test plan.
Thanks -- the test plan does look better, but...
> 2. That's true indeed, but bluetooth is the only features that can be
> tested with the image out of the box. Testing advanced features like
> nvenv, nvjpeg, etc requires to install additional userspace packages
> which are not in Ubuntu, as described in
> https://canonical-ubuntu-for-jetson.readthedocs-hosted.com/classic/installation-noble/#install-nvidia-proprietary-software.
>
> Note that this noble upload fixes the following bugs:
> - https://bugs.launchpad.net/riverside/+bug/2122501
> - https://bugs.launchpad.net/riverside/+bug/2122571 (but this requires
> a 4K monitor connected, which explains why the test plan doesn't
> mention it)
That doesn't explain why the test plan doesn't mention it -- if an SRU
potentially affects some piece of hardware, or some functionality
available from the package being SRU'd, then that needs including in the
test plan, regardless of whether that's available "out of the box".
The test plan should mention that piece of hardware is a pre-requisite
for executing (that portion of) the test plan, but just because it's not
standard doesn't mean we omit it.
If the features require software not available in Ubuntu, that *might*
be an exception (we have no obligation to ensure operation of software
we have no control over), so I can see the omission of nvenc / nvjpg
testing as acceptable. But base functionality that is potentially
affected, like that mentioned in LP: #2122571, should be included in the
test plan.
--
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 (noble):
* Boot a Jetson AGX Thor from daily Ubuntu for Jetson image (https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-server/noble/daily-preinstalled/current/noble-preinstalled-server-arm64+tegra-jetson.img.xz)
* 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 noble-proposed
* 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
[ 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