JetPack 2.0 on Jetson TK1 - Installation doesn' t finish

hii
i performed the steps as in #15. The problem still persists.

[url]https://devtalk.nvidia.com/default/topic/898683/jetson-tk1/jetpack-2-0-on-jetson-tk1-installation-doesn-t-finish/post/4762312/#4762312[/url]

The screen shorts have been attached with the permission to /.ssh folder and command .
<JetPack_dir>/_installer/PageAction jetpack_device_info set_info jetson_ip_adress ubuntu ubuntu .

https://drive.google.com/file/d/0B4fpmUWF5h-1MVZoXzVYbXM3eFk/view?usp=sharing

Need your help please .

Are you running as root or a normal user? If you are running as root, can you please clean the environment first then run as a normal user?

I’ve the same problem. I’ve tried everything in here but the problem still same. When I run the installer without sudo permission IP entering form never comes directly stepping to finish page, when I run with permission it’s lacking the installer at Device ip, user and password forms and just cancel buton is available. I can connect via ssh and control it from host but installer can’t connect the target. I’ve flashed target for two times but it is still same.

Can you please clean up the JetPack directory, then reboot machine, and run JetPack again?
If problem still exists, please write down the steps you performed in detail, so that I can follow and reproduce.
Please run JetPack as a normal user, you will need provide password only when it prompts you in a popup xterm window.

I’ve deleted all the files created by jetpack and reboot system then start jetpack without sudo permission but this time installer directly goes Jetson TX1 ip, user and password settings screen without flashing the device or asking the target connection type (directly on router or host). The interesting part was the installer changed device type setting automatically after downloaded all the packages, from TK1 to TX1. I’m downloading all the settings for TK1 but then when it finished downloading installer is setting it to TX1. I was sure but removed all the files again then try again it was still same. After 4 try, I installed JetPack-1.2 for special to TK1 instead JetPack-2.0.

In the Component Manager, there is a dropdown list on top to specify installation for TX1/TK1. The default one is TX1. Please select TK1 before installation.

Yes I know but I’m sure I selected TK1 when I’ve started each new installation.

This is what worked for me.

I’ve gone through every permutation of post-installation steps and nothing is working.

The Post Installation terminal window always gets stuck here
nvidia@10.0.0.3’s password:
Copying cuda-repo-l4t-8-0-local_8.0.34-1_arm64.deb file to target…
nvidia@10.0.0.3’s password:

Is there a way to have the installer print a list of the commands it was going to execute so one can run them manually?

The log file is rather uninformative

_installer/logs/64_TX1> tail target_setup_progress_64_tx1.log
starting to flash 64_tx1
finish flashing 64_tx1
target ip is 10.0.0.3
starting to install cuda to 64_tx1
starting to install cuda to 64_tx1
starting to install cuda to 64_tx1

Hi shanti,

Are you running issue with TK1 or TX1? It seems you’re installing CUDA 8 to TX1.
Please put TX1 issue to TX1 board:
[url]https://devtalk.nvidia.com/default/board/164/jetson-tx1/[/url]

Thanks

Hi, I am facing issue about IP during installation. It prompt out that window that request ‘IP address/username/password’, when I key-in Jetson device IP address(192…)/ ubuntu/ubuntu accordingly,
it shows that
“Return Code:1 Error: cannot connect to device with given information, please check your input and try again. SSH : connect to host 192…port22 network is unreachable”
I tried ‘ssh ~/.ssh/id_rsa’ & ‘~/.ssh/id_rsa.pub’ -both showed that “permission denied”
then tried ‘~/.ssh/known_hosts’ it also showed "permission denied’,

anyone can help on this issue? Thank you.

Below ssh, can your host and jetson communicate ?
From your host, what gives

ping jetsonIP

where jetsonIP is your TK1 address 192…

Hi Patouceul
My host PC and Jetson are able to communicate:
After Ping TK1 address: 192…
Results:
“192… ping statistics —
31 packets transmitted, 31 received, 0% packet loss, time 30293ms
rtt min/avg/max/mdev = 1.041/2.575/6.400/1.110 ms”

seem like OK, while during installation still failed with same error, Please help?

Can you get the serial console from the TK1 DB9 connector (framing 115200 8N1) ?

Once you get it, log in and try to ssh to your host. If it prompts for accepting the host as trusted, say yes (assuming your are on a safe network).
If it fails, on TK1 try:

ssh-keygen -f ~/.ssh/known_hosts  -R hostIP

where hostIP is the IP address of your host. This will remove RSA key for that IP from your ~/.ssh/known_hosts.
Then retry to ssh into your host and say yes if prompted to trust new host.

If it still fails, post the error log here.

Furthermore, be aware that JetPack on your host requires to operate in English (other locales are not fully supported, although this might not be related to your problem), and that the install process requires your jetson to have direct access to internet (firewalls and proxies may lead to authentication problems).

Hi, I have a TX2. I’ve met the problem. Since I’ve VM and have just one cable…
But, I think we don’t have to use wire connection to install cuda etc. If you have successfully install Firmware (since you stop there, you should have). You can close Jetpack and re-run it. In the new running, you just escape the firmware installation. Jetpack will lead you to input the ip and username, password. You can start your TX2 as normal, use WiFi connection and check the ip address using ifconfig. Put all these three info in and Jetpack will run successfully.

I know this is an old post but the only way I was able to get around this issue was to run

ssh-copy-id ubuntu@"ip_address"

Hi Honey_Patouceul

about your 22th answer, if I cannot ping TX2, What should I do?

Hi jc.jang,
Can you ping your host from TX2? What’s the reason it is not pingable? No IP address or something else? The host PC must be able to ssh to TX2 manually.

Some notes…

If ping fails, then there is nothing you can do other than find out why. Sometimes traceroute to the address offers a clue…but if you are directly connected via wired ethernet between host and Jetson, then there is only one hop anyway and it is no different than ping.

If a GUI application wants to use ssh and is missing the package ssh-askpass, then it won’t be able to ask for the password, and otherwise working system will appear to be failing…but command line ssh would work since you can see password requests.

ssh-copy-id removes a need for entering a password…but requires you to login while running it initially. If no network, then no login (and no possibilities for success).

Ordinary ssh on command line has an option of “-v” (or more verbose, “-vv” or “-vvv”). No network implies “-v” has no purpose…it requires the end point to be reachable.

Some hosts simply do not enable ssh by default for login to the host…they normally do enable login to a remote host by having an ssh client…one does not need to operate an ssh daemon in order to go to a remote host…the Jetson has ssh daemon by default. ssh backwards to the host from Jetson might run into a disabled or firewalled ssh. However, no network implies this won’t matter.

So is ping completely dead in both directions? What kind of network cable setup is this, e.g., external router or direct to host? If it is an external router then there is a strong chance you have something like requiring a MAC address to be entered before the router will allow use. This would explain a lot if it is the case.