Iβm trying to upgrade from JetPack 6.2 to 7.2 on my Jetson Orin Nano Super. However, the installation keeps crashing while installing packages, forcing me to open a shell. It opens the shell at root@ubuntu-server:/var/snap/subiquity/6808. Perhaps this indicates something? How can I fix this?
I have been following this guide;
Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.
If this was an incorrect assessment, please send me a direct message.
Disclaimer: this moderation suggestion and message were generated with AI assistance.
Hi,
Please check if you can re-trigger ISO installation. If not, we would suggest download the packages from release page and run the l4t_initrd_flash.sh command to upgrade to Jetpack 7.2 r39.2: Quick Start β NVIDIA Jetson Linux Developer Guide
after looking closer it like the nano is misreporting its P3767-0005 compatible-spec as jetson-orin-nx-devkit-16gb (crash.log:12665), so nvidia-l4t-bootloader fails board matching (βdoes not match any known boardsβ, crash.log:45683) since thatβs not actually a real configuration
so the 39.2.0 update regressed this boardβs TegraPlatformCompatSpec value from 3767--0005--1--jetson-orin-nano-devkit-super- to the invalid 3767--0005--1--jetson-orin-nx-devkit-16gb-
Having the same issue, trying to install Jetpack 7.2 to NVMe on Orin Nano Super (previously at 6.2). Thanks for any insight you can offer! Hereβs a screenshot of the error from the crash log.
using the direct flash method with the SDK manager, but stopping after Jetson Linux was fully flashed and not letting it install the runtimes/SDK components (that part wouldnβt work for me)
going back and trying the ISO USB install method again
but at that point to be honest, why bother with the ISO USB
I tried that as well. Used sdk manager to flash 7.2 without runtime components, got a completely bootable Jetson Orin Nano on 7.2. Then used the 7.2 USB stick and tried to flash that exact same orin, and got the old exit status 127 error. So, had the same idea as you, but even that did not work for me. Yes, you can make it work with the sdk manager, but there are many reasons many people want a clean install from a USB.
I donβt know if this will help anyone or not, but I was struggling mightily with the exit status 127 error. What I found for me it was a strong function of the specific USB thumb drive used. I had a random stack of thumb drives and went through them. Half of them would consistently give the error when trying to flash the SD card, and half would not.