Let's try to answer the past questions here: 1) Only Orin devices are compatible with Jammy images for proper booting. Thor is only supported beginning with Noble images (and corresponding kernel). There are no plans to change that. 2) We are collaborating with NVIDIA to publish Jetson custom kernels, but this follows NVIDIA's release schedule, which differs from the Ubuntu one. Consequently, we are limiting our focus to LTS images. NVIDIA has plans to release a noble kernel compatible with both Thor and Orin, but that won't happen before mid 2026. In the meantime, we need a solution to temporarily block the release upgrade mechanism from Jammy to Noble. But indeed doing it in ubuntu-release-upgrader would be a better choice, thanks for the suggestion. 3) Similarly, we'll also need to temporarily block release upgrades from Noble, until we have a Resolute custom kernel.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127100 Title: [SRU] Fix kernel cmdline for Thor systems, drop incorrect chmod, block jammy do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-tegra-defaults/+bug/2127100/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
