Jetpack 5.1.1 / 5.1 (Rev. 1) installation fails on Jetson AGX Xavier

I am trying to flash Jetpack 5.1.1 / 5.1 REv. 1 on an AGX Xavier DevKit. I get the below error during flashing:

Installation logs are attached.

SDKM_logs_JetPack_5.1_(rev._1)_Linux_for_Jetson_AGX_Xavier_modules_2023-04-05_22-45-54.zip (176.5 KB)

We checked the logs, and found that you flashed the device emmc with following command:
sudo ./nvsdkmanager_flash.sh --nv-auto-config --username imperiumdrive

However, the Jetson board also has an NVME storage attached to it. After flashing, the board was booted up with NVME storage.

Could you remove the NVME drive first, and try again?

Or you can refer to below instruction to flash NVME drive: Flashing Support — Jetson Linux Developer Guide documentation (nvidia.com)

Thanks

Thanks @kayccc for your reply!

I removed the NVME drive and then reflashed the Jetson in Manual setup and got the same exact error. Logs below.
SDKM_logs_JetPack_5.1.1_Linux_for_Jetson_AGX_Xavier_modules_2023-04-06_11-39-11.zip (160.6 KB)

When I picked Automatic Setup, I get the below error:

What am I doing wrong?

Are you using VM or host PC? Which Ubuntu OS version?

Can it work by using “Manual setup”?

Hi sandiprmlc0,

The log shows that the nvme storage is still attached to the Jetson board.

11:43:20.545 - info: Filesystem Type Size Used Avail Use% Mounted on
11:43:20.545 - info: udev devtmpfs 7.8G 0 7.8G 0% /dev
11:43:20.546 - info: tmpfs tmpfs 1.6G 3.0M 1.6G 1% /run
11:43:20.546 - info: /dev/nvme0n1p1 ext4 915G 764G 105G 88% /
11:43:20.546 - info: tmpfs tmpfs 7.8G 115M 7.7G 2% /dev/shm
11:43:20.546 - info: tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
11:43:20.546 - info: tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
11:43:20.546 - info: /dev/loop0 squashfs 128K 128K 0 100% /snap/bare/5
11:43:20.546 - info: /dev/loop2 squashfs 117M 117M 0 100% /snap/core/14784
11:43:20.546 - info: /dev/loop3 squashfs 56M 56M 0 100% /snap/cups/872
11:43:20.546 - info: /dev/loop1 squashfs 149M 149M 0 100% /snap/chromium/2406
11:43:20.546 - info: /dev/loop4 squashfs 56M 56M 0 100% /snap/core18/2714
11:43:20.546 - info: /dev/loop5 squashfs 165M 165M 0 100% /snap/gnome-3-28-1804/161
11:43:20.546 - info: /dev/loop7 squashfs 9.8M 9.8M 0 100% /snap/htop/3654
11:43:20.546 - info: /dev/loop6 squashfs 350M 350M 0 100% /snap/gnome-3-38-2004/137
11:43:20.546 - info: /dev/loop8 squashfs 46M 46M 0 100% /snap/snap-store/638
11:43:20.546 - info: /dev/nvme0n1p2 vfat 952M 6.1M 946M 1% /boot/efi
11:43:20.546 - info: /dev/loop9 squashfs 56M 56M 0 100% /snap/core18/2721
11:43:20.546 - info: /dev/loop10 squashfs 117M 117M 0 100% /snap/core/14946
11:43:20.546 - info: /dev/loop11 squashfs 113M 113M 0 100% /snap/slack/67
11:43:20.546 - info: /dev/loop12 squashfs 66M 66M 0 100% /snap/sublime-text/116
11:43:20.546 - info: /dev/loop14 squashfs 9.8M 9.8M 0 100% /snap/htop/3605
11:43:20.547 - info: /dev/loop15 squashfs 82M 82M 0 100% /snap/gtk-common-themes/1534
11:43:20.547 - info: /dev/loop16 squashfs 50M 50M 0 100% /snap/snapd/18357
11:43:20.547 - info: /dev/loop17 squashfs 292M 292M 0 100% /snap/code/123
11:43:20.547 - info: /dev/loop18 squashfs 92M 92M 0 100% /snap/gtk-common-themes/1535
11:43:20.547 - info: /dev/loop20 squashfs 219M 219M 0 100% /snap/gnome-3-34-1804/77
11:43:20.547 - info: /dev/loop21 squashfs 135M 135M 0 100% /snap/cmake/1288
11:43:20.547 - info: /dev/loop22 squashfs 256K 256K 0 100% /snap/gtk2-common-themes/13
11:43:20.547 - info: /dev/loop23 squashfs 149M 149M 0 100% /snap/chromium/2415
11:43:20.547 - info: /dev/loop24 squashfs 219M 219M 0 100% /snap/gnome-3-34-1804/90
11:43:20.547 - info: /dev/loop25 squashfs 392M 392M 0 100% /snap/gimp/383
11:43:20.547 - info: /dev/loop26 squashfs 46M 46M 0 100% /snap/snap-store/599
11:43:20.547 - info: /dev/loop27 squashfs 116M 116M 0 100% /snap/slack/68
11:43:20.547 - info: /dev/loop28 squashfs 73M 73M 0 100% /snap/core22/583
11:43:20.547 - info: /dev/loop29 squashfs 66M 66M 0 100% /snap/sublime-text/118
11:43:20.547 - info: /dev/loop30 squashfs 50M 50M 0 100% /snap/snapd/18596
11:43:20.547 - info: /dev/loop31 squashfs 68M 68M 0 100% /snap/sublime-merge/22
11:43:20.547 - info: /dev/loop32 squashfs 135M 135M 0 100% /snap/cmake/1282
11:43:20.547 - info: /dev/loop33 squashfs 64M 64M 0 100% /snap/core20/1852
11:43:20.547 - info: /dev/loop34 squashfs 64M 64M 0 100% /snap/core20/1828
11:43:20.547 - info: /dev/loop35 squashfs 56M 56M 0 100% /snap/cups/836
11:43:20.547 - info: /dev/loop36 squashfs 67M 67M 0 100% /snap/sublime-merge/14
11:43:20.548 - info: /dev/loop37 squashfs 165M 165M 0 100% /snap/gnome-3-28-1804/194
11:43:20.548 - info: /dev/loop38 squashfs 522M 522M 0 100% /snap/gimp/393
11:43:20.549 - info: /dev/loop39 squashfs 347M 347M 0 100% /snap/gnome-3-38-2004/119
11:43:20.549 - info: tmpfs tmpfs 1.6G 20K 1.6G 1% /run/user/125
11:43:20.550 - info: /dev/loop40 squashfs 73M 73M 0 100% /snap/core22/607
11:43:20.550 - info: /dev/loop13 squashfs 292M 292M 0 100% /snap/code/124
11:43:20.550 - info: tmpfs tmpfs 1.6G 56K 1.6G 1% /run/user/1000
11:43:20.550 - info: /dev/sda vfat 16M 58K 16M 1% /media/imperiumdrive/L4T-README
11:43:20.550 - info:

@kayccc I am using a host PC with Ubuntu 20.04 and the latest SDK manager. It doesn’t work with Manual Setup - says that only Automatic Setup is possible.

@EdwardZhou That’s strange! I physically removed the NVMe drive from the device…
It seems like the SDK manager is detecting the drive from the previous failed install and preventing a new clean installation.

@sandiprmlc0 , can you please manually ssh connect to 192.168.55.100 and check the Jetson system?
From the log, seems it is an amd64 platform OS instead of arm64 OS. The Jetson OS should be arm64 platform OS.

dpkg: error processing archive /opt/nvidia/deb_repos/cudnn-local-tegra-repo-ubuntu2004-8.6.0.166_1.0-1_arm64.deb (–unpack):
11:45:10.943 - info: NV_L4T_CUDNN_RUNTIME_TARGET_POST_INSTALL_COMP@JETSON_AGX_XAVIER_TARGETS: package architecture (arm64) does not match system (amd64)

@kayccc @EdwardZhou I tried to run the Automatic Setup and I get the following error:

Detected selected device is in super speed (USB 3.x). ‘Automatic Setup’ does not support the device in super speed. Please change to ‘Manal Setup’ to continue

When I try to SSH to 192.168.55.100 using the username and password previously configured, I simply enter the a local shell on my host machine.

Note that this Jetson was flashed and working previously with the /home mapped to the NVMe SSD. The old SSD was corrupted causing the Jetson to not boot up into the OS. I replaced it with a new SSD and now trying to reflash the Jetson so I can set up a clean new system.

Just made another attempt with the Manual Setup and got the failed dependencies error again. Logs attached.

How can I wipe out everything and do a clean install on the Jetson?

SDKM_logs_JetPack_5.1.1_Linux_for_Jetson_AGX_Xavier_modules_2023-04-12_10-59-48.zip (214.5 KB)

What is the exact part gets failure? The flash part or the installation of sdk?

Your log says the flash process is done.

Yes the flash was successful but the installation of SDK components fails.

I see that the target arch (arm64) does not match the system (amd64). But my host computer is amd64 (standard desktop PC). I never had this issue before as I always used a desktop computer to flash the Jetsons.

From the host PC, with the Jetson fully running, can you “ping 192.168.55.1”? If so, can you “ssh 192.168.55.1” (from the host PC).

FYI, the host PC is supposed to be amd64. However, the Jetson is supposed to be arm64. If you connect to 192.168.55.100, then you are testing that the virtual wired interface is valid, but you need to change to 192.168.55.1 to reach the Jetson itself.

@linuxdev You are correct! I am able to SSH to the Jetson at 192.168.55.1 and I can see that the OS is installed:

$ cat /etc/nv_tegra_release 
# R35 (release), REVISION: 3.1, GCID: 32827747, BOARD: t186ref, EABI: aarch64, DATE: Sun Mar 19 15:19:21 UTC 2023

I am now wondering how I can successfully install the NVIDIA SDK components on the Jetson…

What you are seeing is that the Jetson has been flashed correctly, and won’t need another flash (at least not unless you have other reasons for it). You are running L4T R35.3.1.

Note that when you install via SDK Manager that it flashes first in recovery mode, and when flash completes, then the Jetson automatically reboots. It is only after reboot and completion of the first boot account setup that optional components get installed. SDKM will use ssh to that account to work on installing the rest of the components. I don’t know which packages to install if skipping use of sdkmanager, but there are some “apt-get” commands which will do the job if the correct repositories were set up (and probably they are set up).

What isn’t obvious is that you can uncheck various steps in SDKM. You can uncheck “flash” and can uncheck installation of components to the host PC. With networking available between host PC and Jetson, and with the Jetson fully booted and ready for ssh login, you can then run SDKM with just the requested optional install components (e.g., CUDA), and then it will install those without reflashing. You’d name the 192.168.55.1 address (which is default) or perhaps the wired ethernet address if you want to use that (you’d have to know which address that is). The account name/pass you added at first boot will be the login credentials.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.