Post Installation not working

Autonomous Machines Jetson & Embedded Systems Jetson TX1
1

I’m running JetPack-L4T-2.3.1-linux-x64.run and the post installation step is hanging when trying to install cuda. Prior to the filesystem being flashed onto my TX1 I add proxy info to etc/apt/apt.conf, home/ubuntu/.bashrc, and edit etc sudoers to keep http_proxy and https_proxy. These files are on the host under 64_TX1/Linux_for_tegra_64_tx1/rootfs. I have verified the edited files get put on the TX1 properly. The window that pops up eventually stops with the info:

Package libfreeimage-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Connection to xxx.xxx.xxx.xxx closed.
dpkg-query: package ‘cuda-toolkit-8-0’ is not installed and no information is available
dpkg-query: package ‘libfreeimage-dev’ is not installed and no information is available
dpkg-query: package ‘libopenmpi-dev’ is not installed and no information is available
dpkg-query: package ‘openmpi-bin’ is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
1
Error: CUDA cannot be installed on device. This may be caused by other apt-get command running on device when installing CUDA. Please use apt-get command in a terminal to make sure following packages are installed correctly on device before continuing:

At this point I try to run apt-get install cuda-toolkit-8-0 which also doesn’t work:

ubuntu@tegra-ubuntu:/etc/apt/sources.list.d$ sudo apt-get install cuda-toolkit-8-0
[sudo] password for ubuntu:
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
cuda-toolkit-8-0 : Depends: cuda-samples-8-0 (>= 8.0.34) but it is not going to be installed
Depends: cuda-documentation-8-0 (>= 8.0.34) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Nothing so far has gotten me past this point.

2

Maybe your internet connection failed to pass through a firewall or proxy.
I faced similar problems and had to ask my network admin for a temporary direct connection, or install at home. wget was working, but it wasn’t enough for the install.

In latest JetPack release, there is no network tool installed by default (no longer firefox) that allows to perform an identification for some network systems. So it may help to install firefox, or at least ftp, to be able to authenticate later behind your proxy or firewall.

3

One other requirement I think people sometimes miss is that for JetPack ethernet the WiFi can’t be used during install…only use the wired ethernet during the install.

4

I understand it’s the proxy which is why I explained how I added the proxy info to the rootfs on the host ubuntu box before it was flashed to the device. Getting out from behind my proxy isn’t a simple task where I work. All the .deb files get downloaded through the proxy yet something else is still broken in the install.

5

You might ssh into the Jetson from the host just to see if you can get any error messages on networking. From the Jetson you could try “ping google.com” just to see if DNS works and if a route out works (assuming the Jetson directly or indirectly has public net access).

6

I my case, DNS was ok, I was able to receive files with wget from www.google.com.
But for other protocols, such as http or ftp, I had to authenticate for getting apt working on distant repositories.
It would be a nice improvement if next JetPack versions could manage such situations. Each time I flash a new version, I have to make a request to my admin, while I could provide the info once in the setup process (access is granted for enough time to complete install).
In console mode, I use ftp to a fake ftp site, just to authenticate. Thus my advice to install it after setup for having apt working in console mode.