Trouble Flashing Jetson TX2 using Jetpack 3.2

I am using Ubuntu 16.04 host and JetPack 3.2 to flash TX2.
Keep getting error of
“Installing CUDA Toolkit 9.0 failed.
Return Code: 1
Error installing cuda-toolkit-9-0 to host, please check /home/user/_installer/logs/cuda_host_9.0.log for more details”

Even though I tried to fix a lot of dependency problems, now my logs did not show any errors at all.
“Version: 9.0
DashedVersion: 9-0
root 9675 0.0 0.0 198516 6820 ? Ssl 11:14 0:00 /home/user/_installer/sudo_daemon -installer=9546 -d=/home/user/_installer/tmp
0
/home/user//_installer/run_command -c=“dpkg -i --force-overwrite /home/user/jetpack_download/cuda-repo-ubuntu1604-9-0-local_9.0.252-1_amd64.deb; apt-key add /var/cuda-repo-9-0-local/*.pub; apt-get update; apt-get install -y --force-yes cuda-toolkit-9-0; dpkg --add-architecture arm64;apt-get update; apt-get -y --force-yes install cuda-toolkit-9-0 cuda-cross-aarch64-9-0” -d=/home/user//_installer/tmp -l=/home/user/_installer/logs//cuda_host_9.0.log
(Reading database … 330427 files and directories currently installed.)
Preparing to unpack …/cuda-repo-ubuntu1604-9-0-local_9.0.252-1_amd64.deb …
Unpacking cuda-repo-ubuntu1604-9-0-local (9.0.252-1) over (9.0.252-1) …
Setting up cuda-repo-ubuntu1604-9-0-local (9.0.252-1) …
OK
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Ign:3 http://archive.ubuntu.com/ubuntu trusty InRelease
Ign:4 http://ports.ubuntu.com trusty InRelease
Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:6 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu xenial InRelease
Hit:7 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:8 http://archive.ubuntu.com/ubuntu trusty Release
Hit:9 http://ports.ubuntu.com trusty Release
Hit:12 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu xenial InRelease
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
cuda-toolkit-9-0 is already the newest version (9.0.252-1).
0 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu trusty InRelease
Ign:5 http://ports.ubuntu.com trusty InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:7 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu xenial InRelease
Hit:8 http://archive.ubuntu.com/ubuntu trusty Release
Hit:9 http://ports.ubuntu.com trusty Release
Hit:10 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu xenial InRelease
Reading package lists…
Reading package lists…
Building dependency tree…
Reading state information…
cuda-cross-aarch64-9-0 is already the newest version (9.0.252-1).
cuda-toolkit-9-0 is already the newest version (9.0.252-1).
0 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.”

The process in JetPack L4T Components manager 3.2 for CUDA Toolkit is always “ERROR”

Hi devin.x.zhou,

We don’t have this issue before.
Could you delete all the download package and try it again?

You can refer this similar topic: https://devtalk.nvidia.com/default/topic/1025459

I tried Jetpack 3.1 which worked. That is weird. Thank you, though!

Just quoting because this didn’t show up for everyone.

Just recieved the same problem
:
Return Code: 1
Error installing cuda-toolkit-9-0 cuda-cross-aarch64-9-0 to host, please check /home/specyfick/Downloads/_installer/logs/cuda_host_9.0.log for more details
03-14 19:23:13.0 W: One invalid entry
03-14 19:23:24.9 N: Install com.nvidia.cuda.host 9.0; Install org.opencv.middleware.ocv_64_host 3.3.1; Install com.nvidia.middleware.visionworks_host 1.6; Install com.nvidia.middleware.visionworks_host_sfm 0.90; Install com.nvidia.middleware.visionworks_host_tracking 0.88; Install com.nvidia.l4t.driver4os_64_tx2 28.2; Install com.nvidia.l4t.filesystem_64_tx2 28.2; Install com.nvidia.l4t.flash_64_tx2 28.2; Install com.nvidia.cuda.l4t_64_tx2 9.0; Install com.nvidia.cuda.compile_cuda_64_tx2 9.0; Install com.nvidia.middleware.cudnn_64_tx2 7.0; Install com.nvidia.gie.l4t_64_tx2 3.0; Install org.opencv.middleware.ocv_l4t_64_tx2 3.3.1; Install com.nvidia.middleware.visionworks_target_64_tx2 1.6; Install com.nvidia.middleware.visionworks_target_sfm_64_tx2 0.90; Install com.nvidia.middleware.visionworks_target_tracking_64_tx2 0.88; Install com.nvidia.mmapi.l4t_64_tx2 28.2;
03-14 19:24:16.5 E: Installing CUDA Toolkit 9.0 failed.

Return Code: 1
Error installing cuda-toolkit-9-0 cuda-cross-aarch64-9-0 to host, please check /home/specyfick/Downloads/_installer/logs/cuda_host_9.0.log for more details

Any ideas ?

Hi specyfick,

This error look likes your host machine problem.
Could you check your host system requirements first?
http://docs.nvidia.com/jetpack-l4t/index.html#developertools/mobile/jetpack/l4t/3.2/jetpack_l4t_install.htm

Please share your “/home/specyfick/Downloads/_installer/logs/cuda_host_9.0.log” log.
Thanks!

I’m having exactly the same problem. The cuda_host_9.0.log file says to try “apt-get update”, but this did not resolve the problem. The log file also has numerous complaints about several IP addresses:
91.189.91.26 80
91.189.91.23 80
91.189.88.162 80
all of which are “not found”. This is apparently us.archive.ubuntu.com
Any suggestions?

Probably it means DNS was not running or was blocked. Was the wired ethernet set up to PC or to router? If PC make sure your Jetson doesn’t have DNS firwalled.

If using a PC, can you ping those addresses? Can the pingable address be looked up? Example:

ping 91.189.91.26
host 91.189.91.26

If this is a message from a booted Jetson, then the same thing applies from the Jetson…see if ping works but “host” does not…this would be a DNS setup issue or firewall issue for whatever is acting as router.

Host is connected to the internet via wireless router. I’m not trying to do anything on the Jetson yet, all of this is on the host.

ping 91.189.91.26

has the following results:

64 bytes from 91.189.91.26: icmp_seq=1 ttl=55 time=47.3 ms

… (and so on with the sequence number increasing and the time varying slightly)

host 91.189.91.26

has the following results:

26.91.189.91.in-addr.arpa domain name pointer hanger.canonical.com.

Thoughts?

Your host can see and find those addresses, so if JetPack is running on the host it is not the address or network which is failing. It is something secondary related to content requested at the address.

I could easily see that it couldn’t find a particular web page (which implies a port and web server path, not just an address). Notice that each of those complaints lists port 80, but those servers redirect to https port instead (443), so perhaps the software in question is demanding port 80 and not allowing redirect (I doubt this is the issue…most of this software is smart enough to accept a port 443 redirect). I likely that failure of not being found is a specific file or location for a package, and not the server, host, or Jetson itself which is lost.

You might want to include the full log here even if it is long. More clues as to a specific package or architecture would help. Package requests usually name an architecture, and that architecture may not be on all servers, and all servers do not make available all packages.