Hey Andreas, Thanks for confirming this!
I adjusted the test plan accordingly. ** Description changed: [ Impact ] * Updates the /lib/firmware files for the NVIDIA Tegra Jetson Orin and Thor devices with Jetson Linux v39.2.0 * 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. It also include firmware files for various accelerators (such as nvenc, nvjpg, ...), which would require specific installation of packages not in Ubuntu, as described in https://canonical-ubuntu-for-jetson.readthedocs-hosted.com/classic/installation-noble/#install-nvidia-proprietary-software * Update license terms * Update script that packages new orig tarball to work for rel38+ * Include missing firmware file from nvidia-l4t-openrm [ Test Plan ] - noble: * Boot a Jetson AGX Thor and Orin from daily Ubuntu for Jetson image built with the a rel-39 aligned kernel (https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-server/noble/daily-preinstalled/current/noble-preinstalled-server-arm64+tegra-jetson.img.xz) * Connect the HDMI port to a 4K monitor, run the following command as root: "rtcwake -d /dev/rtc0 -m no -s 30 && systemctl suspend", the device will auto wake up after 30s and display output will be back * Run "$ sudo apt install -y bluez && sudo hciconfig" and observe the following output: 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 - * Install linux-firmware-nvidia-tegra from noble-proposed - * Reboot, and execute the above steps again and verify that the behaviour didn't change + * [noble] Install linux-firmware-nvidia-tegra from noble-proposed + * [resolute] Run the following commands to download the resolute package from the archive and install it locally on a device running noble: + $ dget https://launchpad.net/ubuntu/+archive/primary/+files/linux-firmware-nvidia-tegra_39.2.0-20260601141651-0ubuntu1~26.04_arm64.deb + $ sudo dpkg -i ./linux-firmware-nvidia-tegra_39.2.0-20260601141651-0ubuntu1~26.04_arm64.deb + + * Reboot, and execute the above steps again and verify that the + behaviour didn't change [ 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 ] * This update does not apply to jammy because this firmware needs to be aligned with the 39.2.0 QSPI firmware from nvidia. The kernel in jammy is incompatible with that firmware though, therefore it only applies to noble and following releases. - * We only test noble as we only build and support LTS releases up to noble currently for lack of driver support in other releases. + * We only test noble as we only build and support LTS releases up to noble currently for lack of driver support in other releases. * 39.2.0 is related to Nvidia Jetpack 7.2 release: https://docs.nvidia.com/jetson/archives/r39.2/ReleaseNotes/Jetson_Linux_Release_Notes_r39.2.pdf * firmware files that got updated: /lib/firmware/display-t234-dce.bin /lib/firmware/display-t264-dce.bin /lib/firmware/nvhost_nvjpg013.fw /lib/firmware/nvhost_ofa012.fw /lib/firmware/nvhost_vic051.fw /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/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/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/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/tegra234/nvenc.bin /lib/firmware/nvidia/tegra234/nvjpg.bin /lib/firmware/nvidia/tegra234/ofa.bin /lib/firmware/nvidia/tegra264/vic.bin /lib/firmware/nvpva_020.fw /lib/firmware/nvpva_030.fw /lib/firmware/tegra23x/nvhost_nvenc080.fw /lib/firmware/tegra23x/nvhost_tsec_desc.fw /lib/firmware/tegra23x/nvhost_tsec_riscv.fw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2156571 Title: [SRU] Update linux-firmware-nvidia-tegra to 39.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nvidia-tegra/+bug/2156571/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
