Ubuntu 14.04/16.04 and Jetpack 3.0

I have a very simple question regarding Jetpack 3.0

Should I expect to be able to install Jetpack 3.0 on a clean Ubuntu 14.04/16.04 machine WITHOUT the installation of Jetpack 3.0 screwing up the ability for the machine to get updates cleanly?

Where both the “about this computer” update button will cleanly get updates, and doing apt-get update doesn’t produce any errors.

Each time I’ve installed the latest version of Jetpack it has caused apt-get update to no longer function cleanly.

Instead it gives me errors like the following. The only one that I know to expect is the ‘Date’ one.

Err:41 http://us.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
404 Not Found [IP: 91.189.91.23 80]
Ign:52 http://us.archive.ubuntu.com/ubuntu xenial/universe arm64 Packages
Ign:58 http://us.archive.ubuntu.com/ubuntu xenial/multiverse arm64 Packages
Err:64 http://us.archive.ubuntu.com/ubuntu xenial-updates/main arm64 Packages
404 Not Found [IP: 91.189.91.23 80]
Ign:74 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe arm64 Packages
Ign:80 http://us.archive.ubuntu.com/ubuntu xenial-updates/multiverse arm64 Packages
Err:86 http://us.archive.ubuntu.com/ubuntu xenial-backports/main arm64 Packages
404 Not Found [IP: 91.189.91.23 80]
Ign:93 http://us.archive.ubuntu.com/ubuntu xenial-backports/universe arm64 Packages
Fetched 553 kB in 3s (147 kB/s)
Reading package lists… Done
W: Invalid ‘Date’ entry in Release file /var/lib/apt/lists/_var_nv-deep-learning-repo-ga-cuda8.0-digits5.0_Release
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

Just a note that this is the host machine I’m referring to.

One other thing I’m wondering is why on two different 16.04 machines that it messes up the Digits 5.0 that was installed via the deb package.

Here is the install process on two machines.

Installed Ubuntu 16.04 with all the updates
Installed CUDA 8.0 via the deb package
Made sure the driver was correct
Installed Digits 5.0 via the deb package
Used Digits 5.0 to train various FCN/FCN8 models, and worked great
Installed JetPack 3.0
Used Jetpack 3.0 to load it onto a TX2 (was unsuccessful, but I believe this was unrelated)
Tried using Digits again, and it wasn’t there.
Both machines indicated similar error messages as the post above when doing apt-get update.

Both Ubuntu 16.04 installs were fairly recent as I had just gotten done straightening out a hardware reset/reboot issue with the GTX Titan X. Apparently it had some issue (most likely power related) when used in a Dell Precision T5600 workstation. So I moved it to a different machine, and then stuck in a GTX 1080 TI in the T5600 which strangely worked just fine despite the same power rating. The result of all that testing/validating was two super stable machines running Ubuntu 16.04, and Digits 5.0. The only anomaly was Digits 5.0 didn’t indicate the correct name for the GTX 1080 TI, but that wasn’t too surprising as it was a brand new card without using the latest drivers.

I had a similar problem and a possible workaround was suggested here. I cannot verify that it works as I haven’t tried it yet.

https://devtalk.nvidia.com/default/topic/1000824/jetson-tx2/jetpack-3-host-install-problem/

I’ve experienced the same issue. I saw in another thread that JetPack does not support Ubuntu 16.04, although I find it hard to believe NVIDIA is that far behind.

This is a serious issue because it breaks updates for the entire Ubuntu system. Uninstalling JetPack does not fix it, although it should. In order to get updates working again, I did the following to remove the arm64 architecture. I guess I’ll have to create a 14.04 image in order to work with JetPack until NVIDIA fixes this issue.

sudo apt-get purge “.*:arm64”

dpkg --remove-architecture arm64

I didn’t get a chance to test the fix that’s been mentioned in a couple posts, but the original message was more about wondering why I was having all these issues with it regardless of whether it was 14.04 or 16.04 (I tried both).

I should be able to take a working 14.04/16.04 machine with Digits running on it, and install Jetpack 3.0 without it breaking either Digits or updates on the host machine. It’s fine if there is a little cleanup, but it needs to be documented in the install instructions. I imagine a host machine running Digits has to be a pretty common scenario. Since after all it’s used to train models that’s run on the Jetson.

That’s just my little rant about it.

I did end up creating an SSD drive image for the rootfs for the Jetson so in most cases I don’t have to resort to doing a clean install using the Jetpack. It also removes the tight drive space limitations.

I’m also going to avoid putting Jetpack on the machine running Digits.

Next time that I have to use a Jetpack I’ll use a VM or a docker (if that’s even possible).

The way NVIDIA provides JetPack is fundamentally flawed. They should have their approach reviewed by someone other than who’s been leading it thus far. In general, it is far too burdensome. Multi-arch is overkill, when all that should be required is cross compilation. They should take a look at NXP i.mx6. It is much more simple, and the impact on the system is transparent rather than rolled up into a giant black box like the JetPack installer.

Further, NVIDIA should provide the bootloader, kernel/modules, and application/sample source in public git repos (again, like NXP), rather than just in release zips. Then, we developers can see what changed and why between releases. This is essential for those of us who will likely be making bootloader and kernel changes, as well as developing custom drivers.

today i get this crap on my host computer. i already reinstalled trusty 14.04 on host, then jetpack 3.1 on host and dev board twice. i have the tx1 dev kit. along all the hours and gb of downloads sheesh. i’m not doing it again lol. preparing for this i made a full disk image of my host machine after the jetpack 3.1 full install. if i need to revert, i’ll be using dd

it’s not a real special build. i took an old dell xps 8300 /8gb ram / put in ssd and 1tb hdd and evga gtx 1050 card

loaded trusty. nvidia 390 driver. 14.04 patched. installed jetpack and sublime editor.

that’s all it is. this is the second time it happened. i’m not rebuilding the whole OS and jetpack again.

if anyone has advice please do chime in.

W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-updates/restricted/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-updates/universe/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-updates/multiverse/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-backports/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-backports/restricted/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-backports/universe/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty-backports/multiverse/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/main/binary-arm64/Packages 404 Not Found [IP: 91.189.88.149 80]
, W:Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/restricted/binary-arm64/Packages 404 Not Found [IP: 91.189.88.149 80]
, W:Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/universe/binary-arm64/Packages 404 Not Found [IP: 91.189.88.149 80]
, W:Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/multiverse/binary-arm64/Packages 404 Not Found [IP: 91.189.88.149 80]
, W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/trusty/main/binary-arm64/Packages 404 Not Found [IP: 91.189.92.152 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty/main/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty/restricted/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty/universe/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/trusty/multiverse/binary-arm64/Packages 404 Not Found [IP: 91.189.91.23 80]
, E:Some index files failed to download. They have been ignored, or old ones used instead.

i fixed it with help from searching on here / following threads

http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#advanced-setup

my sources.list now looks like this and it fixed the problem according to the above instructions

deb cdrom:[Ubuntu 14.04.5 LTS Trusty Tahr - Release amd64 (20160803)]/ trusty 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/ trusty main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty main restricted

Major bug fix updates produced after the final release of the

distribution.

deb [arch=amd64,i386] http://us.archive.ubuntu.com/ubuntu/ trusty-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-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/ trusty universe
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty universe
deb [arch=amd64,i386] http://us.archive.ubuntu.com/ubuntu/ trusty-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-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/ trusty multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty multiverse
deb [arch=amd64,i386] http://us.archive.ubuntu.com/ubuntu/ trusty-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-updates multiverse

N.B. software from this repository may not have been tested as

extensively as that contained in the main release, although it includes

newer versions of some applications which may provide useful features.

Also, please note that software in backports WILL NOT receive any review

or updates from the Ubuntu security team.

deb [arch=amd64,i386] http://us.archive.ubuntu.com/ubuntu/ trusty-backports main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-backports main restricted universe multiverse

deb [arch=amd64,i386] http://security.ubuntu.com/ubuntu trusty-security main restricted
deb-src http://security.ubuntu.com/ubuntu trusty-security main restricted
deb [arch=amd64,i386] http://security.ubuntu.com/ubuntu trusty-security universe
deb-src http://security.ubuntu.com/ubuntu trusty-security universe
deb [arch=amd64,i386] http://security.ubuntu.com/ubuntu trusty-security multiverse
deb-src http://security.ubuntu.com/ubuntu trusty-security multiverse

Uncomment the following two lines to add software from Canonical’s

‘partner’ repository.

This software is not part of Ubuntu, but is offered by Canonical and the

respective vendors as a service to Ubuntu users.

deb [arch=amd64,i386] http://archive.canonical.com/ubuntu trusty partner
deb-src http://archive.canonical.com/ubuntu trusty partner

This software is not part of Ubuntu, but is offered by third-party

developers who want to ship their latest software.

deb [arch=amd64,i386] http://extras.ubuntu.com/ubuntu trusty main
deb-src http://extras.ubuntu.com/ubuntu trusty main

Try Doing “sudo apt upgrade” this solved my problem