Jetpack 7.2 installation exit 100 for apt-get install nvidia-l4t-bootloader

@wichiu

I have JETSON ORIN NANO 8GB SUPER Developer Kit

I’ll continue working with our engineering team to help resolve this issue as soon as possible.
I’m sorry again for the disappointing experience you’ve had getting your Jetson up and running.

Thanks.

Will there be any timeline can be given? It will be help me to decide whether to wait or to buy some other board?

Actually, a related fix was implemented and validated before, but your results show that the issue remains unresolved on your device.
I’ll follow up with our internal team to confirm whether your case can be addressed in the next release or sooner.
I don’t have a confirmed timeline yet, so I cannot give you a reliable date to base your decision on.
I’ll update you here once I have confirmation.

@wichiu By anychance can I deploy using ubuntu virtual machine? Or do i need physical ubuntu machine?

For this recovery, please use a PC running Ubuntu natively. We do not recommend an Ubuntu VM for flashing, as USB connection issues can interrupt the process. A dual-boot Windows/Ubuntu PC is also an option; simply boot into Ubuntu to perform the recovery.

Hi @venkatgig

Sorry to jump in. I am checking this issue too.

This issue is actually strange in some parts. May I double check the photo of your board?
And is it a fresh new one but not a used one?

And the first thing you did right after this is installing sdcard with ISO image to it?

@WayneWWW

Thanks for the response.

Please see the attached photo.

No, it is not the fresh one. I bought it in Jan 2025, and I was using it using microSD by flashing using balenaEtcher. Recently, it got crashed, so I bought NVMe SSD and installing it.

Could you flip back on the other side and take picture too?

@WayneWWW

just want to point out that the key item we want to check is under your WD SSD which has the serial number and shall have the NVIDIA logo.

@WayneWWW

@WayneWWW Any update? Any timeline on the release? or alternative way to use using microSD balena etcher?

No, what we are sure now is when this issue happened, then you could only rely on external Ubuntu host PC to make it work.

What I was checking here was why this issue would happen. The used device is one of the possible reason. However, we won’t know how was that board got in used before delivered to you.

The sdcard was never a method that fully reflash the board. The previous state on that board would affect.

Only the method to flash it from external host would truly reflash a jetson.

@WayneWWW

BTW, if I am using ubuntu option, i need to install using SDK manager setup right?

https://docs.nvidia.com/jetson/orin-nano-devkit/user-guide/latest/setup_bsp.html

Starting with JetPack 7.2, SD Card images are no longer supported. Do not flash the Jetson ISO to a microSD card — write it to a USB flash drive, then use it to install Jetson Linux onto your microSD card or NVMe SSD.

https://docs.nvidia.com/jetson/orin-nano-devkit/user-guide/latest/quick_start.html

You guys used to support. Thats how I used to run this jetson. Suddenly you guys stopped this option.

Yes, sdkmanager is the true method to really flash the board.

All the other methods still depend on previous state of your carrier board + SOM.

The reason that sdcard image got some changed was because that one was not a real ISO image. To support ISO image, there were some changes.

But anyway, ISO image or sdcard image do not serve the same role as sdkmanager.

@WayneWWW Is there any other way to highlight this particular issue to your management, so that it get fixed soon? Cos, I am kinda feel wasted my money by buying this board (suddenly removing the support for direct SD card flashing and now no timeline on the bug).

Of course, i can write about this in reddit and all other social media channels by sharing the experience and tagging the NVIDIA management.

Same here. ISO on flash drive instead of needing [ an x86 machine with Ubuntu and SDK Manager ] was supposed to be a major feature of 7.2 (and its soon thereafter 7.2.1 release since 7.2.0 also had issues), and the issue of incorrect entries in the configuration file re: board name has been identified ( talking about Orin Nano here ) but the downloadable ISO file has not been corrected to reflect the needed board name. What gives ? 7.2.1 released early August, now mid-October, and users still getting a run around. Technical QA of 7.2.1 appears to have been rather weak, and now just frustrating users with fix not applied and downloadable re: the board name in the config file. This does not look good on Nvidia for sure.

I haven’t managed to have an “installed system” upgrading from previous L4T OSes.

But while installing the device (using the ISO), I was able to enter a second shell (ctl + alt + F2), then enter into the /target/etc/nv_boot_control.conf and replace the TNSPEC and COMPATIBLE_SPEC values before the nv-bootloader package is installed.

I had to wait a little so the file got populated into the /target directory, but once set, I’ve copied it
cp -p /target/etc/nv_boot_control.conf{,.orig}

chattr +i /target/etc/nv_boot_control.conf

The last command to forbid any later modification of the file (unsure if really needed). This must be discarded on the installed system on the next boot with:
chattr -i /etc/nv_boot_control.conf

There is another issue before reboot, but if the installer went to 100%, it should be safe to reboot and find a properly installed jetson unit.