JetPack 3.2: unmet dependencies for cuda-tools etc.

Hi all,
I am opening a new topic because I read all around the forum but no resolution actually worked.
I have downloaded the jetpack 3.2 on a clean ubuntu 16.04 installation (tried the same on 14.04) through virtual box.
Just for your info, the host pc does NOT have nvidia cards, is an enterprise pc with integrated VGA.
I suppose it should not be a problem, at least at this step. Correct?

I started the installation on the ubuntu system and it goes flowlessly until the cuda-tools installation. this is the content of the cuda_host_9.0.log file, after the installation error:

GSelecting previously unselected package cuda-repo-ubuntu1604-9-0-local.
(Reading database ... 202849 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) ...
Setting up cuda-repo-ubuntu1604-9-0-local (9.0.252-1) ...

The public CUDA GPG key does not appear to be installed.
To install the key, run this command:
sudo apt-key add /var/cuda-repo-9-0-local/7fa2af80.pub

OK
Get:1 file:/var/cuda-repo-9-0-local InRelease
Ign:1 file:/var/cuda-repo-9-0-local InRelease
Get:2 file:/var/cuda-repo-9-0-local Release [574 B]
Get:2 file:/var/cuda-repo-9-0-local Release [574 B]
Get:3 file:/var/cuda-repo-9-0-local Release.gpg [819 B]
Get:3 file:/var/cuda-repo-9-0-local Release.gpg [819 B]
Hit:4 http://archive.canonical.com/ubuntu xenial InRelease
Get:5 file:/var/cuda-repo-9-0-local Packages [18.4 kB]
Hit:6 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
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-9-0 : Depends: cuda-samples-9-0 (>= 9.0.252) but it is not going to be installed
Depends: cuda-documentation-9-0 (>= 9.0.252) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Get:1 file:/var/cuda-repo-9-0-local InRelease
Ign:1 file:/var/cuda-repo-9-0-local InRelease
Get:2 file:/var/cuda-repo-9-0-local Release [574 B]
Get:2 file:/var/cuda-repo-9-0-local Release [574 B]
Hit:3 http://archive.canonical.com/ubuntu xenial InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
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-cross-aarch64-9-0 : Depends: g++-aarch64-linux-gnu but it is not going to be installed
cuda-toolkit-9-0 : Depends: cuda-samples-9-0 (>= 9.0.252) but it is not going to be installed
Depends: cuda-documentation-9-0 (>= 9.0.252) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

No way to get rid of this. What does it mean?
It seems all installed packages are not correct.

I edited the sources.list following one of the most common suggestion in the forum, specifying the reference architecture:

# deb cdrom:[Ubuntu 16.04.4 LTS _Xenial Xerus_ - Release amd64 (20180228)]/ xenial main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb [arch=amd64,i386] http://us.archive.ubuntu.com/ubuntu/ xenial main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial main restricted

## Major bug fix updates produced after the final release of the
## distribution.
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb [arch=amd64,i386] http://us.archive.ubuntu.com/ubuntu/ xenial universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb [arch=amd64,i386] http://us.archive.ubuntu.com/ubuntu/ xenial multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ xenial-updates multiverse

Of course I run the apt-get update successfully.

Any suggestion?

Thanks

Hi,

Based on the log, error occurs when installing CUDA tool-kit on the host.
Have you installed any CUDA tool-kit on the host Ubuntu before?

To give further information, could you share the system information with us by this command?

uname -a

Thanks.

Hi,
no previous installation, we bought the TX2 and I was trying to make it working.
it is a clean ubuntu 16.04 installation downloaded from osboxes.org and started on virtualbox.

osboxes@osboxes:~$ uname -a
Linux osboxes 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

VMs are a big problem. But…what do you get from:

sudo apt-get install g++-aarch64-linux-gnu

Your VM may need to add packages JetPack wouldn’t expect to be missing when going to a VM.

Hi,
it is a continuous dependencies missing message…

osboxes@osboxes:~$ sudo apt-get install g++-aarch64-linux-gnu
[sudo] password for osboxes: 
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:
 g++-aarch64-linux-gnu : Depends: gcc-aarch64-linux-gnu (>= 4:5.3.1-1ubuntu1) but it is not going to be installed
                         Depends: g++-5-aarch64-linux-gnu (>= 5.3.1-3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

I tried also to install gcc-aarch64-linux-gnu, but it depends (among others) on gcc-5-aarch64-linux-gnu which depends on binutils-aarch64-linux-gnu (>= 2.26) which depends on

The following packages have unmet dependencies:
 binutils-aarch64-linux-gnu : Depends: binutils (= 2.26-8ubuntu2) but 2.26.1-1ubuntu1~16.04.6 is to be installed
E: Unable to correct problems, you have held broken packages.

any suggetsion?

Is there anywhere the precise (and up-to-date) list of requirements the physical machine has to match in order to perform a successful installation?
Here it does not specifies anything apart ubuntu version. Should I have a specific hw components in the physical machine?

Thanks

If you install Ubuntu 16.04 at your physical machine -that will resolve the issue, highly likely, in my opinion. VM installations are known to have issues, that in some cases can be resolved. But that could turn out to be time consuming and require manual adjustments.

VMs are terrible…but what do you get from:

sudo apt-get install build-essential

Hello Linuxdev,
the package is already there:

osboxes@osboxes:~$ sudo apt-get install build-essential
Reading package lists... Done
Building dependency tree       
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

At this point I don’t know. VMs tend to do odd things which seem to have no explanation unless you know the details of the VM. All I can suggest is to check each missing dependency one at a time and pay attention if it is the native architecture or if it is a foreign architecture.

FYI, any x86_64 PC is “native” with 64-bit x86, and although 32-bit x86 is well supported it is technically a foreign architecture (for an x86_64 PC to support 32-bit x86 it needs compatibility libraries, linker, so on).

The part where foreign architecture becomes important is when you install or run programs meant to be x86_64 execution, but with output to arm64/aarch64/ARMv8-a. You will receive packages on the host which are meant to cross compile examples…in which case it is expected to see installing x86_64 programs without output in aarch64. You have to be careful about package names to know this is cross platform and not purely aarch64.

Hi,

It’s recommended to run JetPack on a physical machine rather than VM.
We didn’t test the installation from VM and it may have some unsolved issues.

Thanks.

Hello,
I have similar problems with running JetPack on a physical machine
I have downloaded the jetpack 3.3(b39) on a ubuntu 16.04.4 LTS(Xenial Xerus).
The pc has nvidia GeForce GTX cards.

I started the installation on the ubuntu but could not install the cuda-tools. This is the content of the cuda_host_9.0.log file, after the installation error:

(Reading database ... 217574 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
Get:1 file:/var/cuda-repo-9-0-local  InRelease
Ign:1 file:/var/cuda-repo-9-0-local  InRelease
Get:2 file:/var/cuda-repo-9-0-local  Release [574 B]
Get:2 file:/var/cuda-repo-9-0-local  Release [574 B]
Hit:3 http://jp.archive.ubuntu.com/ubuntu xenial InRelease
Ign:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Hit:8 https://download.docker.com/linux/ubuntu xenial InRelease
Ign:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Ign:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
Ign:9 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  InRelease
Hit:10 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Release
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Err:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
  404  Not Found
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Hit:12 http://ppa.launchpad.net/webupd8team/atom/ubuntu xenial InRelease
Reading package lists...
E: Failed to fetch http://jp.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
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-9-0 : Depends: cuda-samples-9-0 (>= 9.0.176) but it is not going to be installed
                    Depends: cuda-documentation-9-0 (>= 9.0.176) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Get:1 file:/var/cuda-repo-9-0-local  InRelease
Ign:1 file:/var/cuda-repo-9-0-local  InRelease
Get:2 file:/var/cuda-repo-9-0-local  Release [574 B]
Get:2 file:/var/cuda-repo-9-0-local  Release [574 B]
Hit:4 http://jp.archive.ubuntu.com/ubuntu xenial InRelease
Ign:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Hit:8 https://download.docker.com/linux/ubuntu xenial InRelease
Ign:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Ign:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
Ign:9 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  InRelease
Hit:10 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64  Release
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Err:5 http://jp.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
  404  Not Found
Ign:6 http://jp.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:7 http://jp.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Hit:12 http://ppa.launchpad.net/webupd8team/atom/ubuntu xenial InRelease
Reading package lists...
E: Failed to fetch http://jp.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
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-cross-aarch64-9-0 : Depends: g++-aarch64-linux-gnu but it is not going to be installed
 cuda-toolkit-9-0 : Depends: cuda-samples-9-0 (>= 9.0.176) but it is not going to be installed
                    Depends: cuda-documentation-9-0 (>= 9.0.176) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

I edited the sources.list following the common suggestions in the forum:

deb http://old-releases.ubuntu.com/ubuntu/ xenial main restricted

It improved some of “404 Not Found” error, but eventually unmet dependencies showed up.

Could you offer a suggestion? Thank you in advance.