JetPack 2.1 Not pushing/installing after flashing


I’m running Ubuntu 14.04 64-bit in my host machine and I’m trying to run JetPack 2.1. I’m executing the .run file with my non-root user. Flashing TK1 finishes ok and I see this:

Finished Flashing OS
Determining the IP address of target...

Waiting 30 seconds to make sure target is fully up
# Host found: line 1 type RSA
# Host found: line 2 type ECDSA
/home/martin/.ssh/known_hosts updated.
Original contents retained as /home/martin/.ssh/known_hosts.old
# SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
# SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
Identity added: /home/martin/.ssh/id_rsa (/home/martin/.ssh/id_rsa)
scp -o PubkeyAuthentication=no -o ConnectTimeout=30 -o StrictHostKeyChecking=no /home/martin/.ssh/ ubuntu@
 8.1.4                                    100%  395      0.4KB/s    00:00                     
ubuntu@tegra-ubuntu:~$ b /home/ubuntu/.ssh/authorized_keys
ubuntu@tegra-ubuntu:~$ exit
Connection to closed

Then, the installation gets stuck forever. I have tried deleting the .ssh folder on the host without any luck.

Also, if I set “no action” for flashing (so I start the process pushing and installing CUDA), it also gets stuck while installing files:

ubuntu@'s password:
Copying cuda-repo-l4t-r21.3-6-5-local_6.5-50_armhf.deb file to target...
ubuntu@'s password:
    568,399,644 100%  256.53MB/s    0:00:02 (xfr#1, to-chk=0/1)

sent 95,496 bytes   received 166,944 bytes   13,458.46 bytes/sec  
total size is 568,399,644 speedup is 2,165.83

And that is the last thing I see.

If it is of any help, when I access the TK1 (via ssh or directly), the default user:ubuntu, pass:ubuntu user account doesn’t have root privileges. When I try to sudo anything I get:

sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

And I can’t find the root user password (to login as root).

Any ideas?

Sometimes if flash was done when the host had insufficient space the flash truncates and may cause something similar. Strangeness may also occur if the file system underlying your Linux host is not a native Linux type, e.g., people have had issues when not realizing they can’t build and install from an NTFS partition. Is there anything unusual about your host, e.g., running on a VM or using a non-Linux file system underneath it? Was there plenty of space on the host during flash (30GB spare hard drive would probably guarantee enough space)?

NOTE: Ubuntu does not use user root and is designed to not allow login directly to root. sudo is required. Default password for ubuntu being ubuntu (don’t expose this to a public network).

@linuxdev: thanks a lot for the suggestion about the diskspace. I could fix the described installation issue with Ubuntu 16.04 on the host, trying to install Jetpack 3.3 on a TX2

@NVidia: Would be great if you could add a diskspace check to the installer.

Thanks for the suggestion, the diskspace check if not accurate for flashing function will be implemented in coming JetPack release.

You might want to also add a check for ext4 (or any native system would do, e.g., reiserfs, XFS, ext2, ext3, so on…the best would be to see if the rootfs directory is NTFS, VFAT, FAT32, or FUSE…none of which will work in the end, but all of which will flash without complaint).

Sample in bash:

fstype=$(df -T . | tail -n 1 | awk '{print $2}')
freespace=$(df -T . | tail -n 1 | awk '{print $5}')