After installing JetPack3.0, host computer is not able to apt-get update

Hello,

I just installed a new Ubuntu 14.04 on my laptop, and downloaded the JetPack3.0. Followed instructions, and finished it successfully.

However when I try to apt-get update on the host computer I get the following error:

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/restricted/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/multiverse/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/universe/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-security/main/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-security/restricted/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-security/multiverse/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-security/universe/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 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://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/universe/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/restricted/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/multiverse/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/main/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/restricted/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/multiverse/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/universe/binary-arm64/Packages  404  Not Found [IP: 91.189.88.162 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.

There has been posts about this on this forum, but none of them has the solution. Please notice that this is not the Date problem with the release files. For some reason ubuntu mirrors does not have binary-arm64 packages.

Any ideas/help greatly appreciated.

Best regards,
C.

Hi cambazz,

The 404 Not Found warnings issue seems to be a known one. The workaround is mentioned in CUDA Advanced Setup section at: http://docs.nvidia.com/cuda/cuda-installation-guide-linux/#advanced-setup

Please get it try.

Thanks

I ran into the same problem.

Follow the instruction, I looked into the files and added [arch=amd64,i386] to architecture restricted entry as guided in http://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html#advanced-setup

But I still getting errors when running “apt-get update” for URLs, such as

Err:28 http://us.archive.ubuntu.com/ubuntu xenial/main arm64 Packages
Err:54 http://us.archive.ubuntu.com/ubuntu xenial-updates/main arm64 Packages
Err:78 http://us.archive.ubuntu.com/ubuntu xenial-backports/main arm64 Packages
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/main/binary-arm64/Packages  
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages  
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-arm64/Packages

I don’t see those “arm64” entries defined in /etc/apt/sources.list, nor in the files under /etc/apt/source.list.d subfolder with files pointing to other folders.

Any idea how to fix those errors like “404 Not Found [IP: 2001:67c:1562::19 80]”?

That repository has only the desktop PC flavor of packages, whereas the arm64 is for the Jetson. Is this running from your PC or is it running from the Jetson? Would you post a copy of your sources.list from both the PC (I’m assuming the host is Ubuntu, ignore this if not Ubuntu) and the Jetson?

Have you added [arch=amd64,i386] for each line in /etc/apt/sources.list starting with 'deb ’ ? (for deb-src it would have no sense). That worked for me.

@linuxdev, it’s running on PC. I didn’t notice the problem until I wanted to install VLC for a test of remote access to rtsp server. I realized I couldn’t run “apt-get update” due to the missing package.

@Honey_Patouceul, yes, I added [arch=amd64,i386] and fixed the problem.

For example, change
deb http://archive.ubuntu.com/ubuntu xenial universe
into
deb [arch=amd64,i386] http://archive.ubuntu.com/ubuntu xenial universe

Thank you guys for the help.

I face errors installing tensorflow forum source on my host due to ARM packages:

ERROR: /home/gustav/.cache/bazel/_bazel_gustav/0efb90387e9af20adf0714a85702521f/external/jpeg/BUILD:126:12: Illegal ambiguous match on configurable attribute "deps" in @jpeg//:jpeg:
@jpeg//:k8
@jpeg//:armeabi-v7a
Multiple matches are not allowed unless one is unambiguously more specialized.
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted:

I had the same “Not Found” problem, and it went away with @Honey_Patouceul solution:

Have you added [arch=amd64,i386] for each line in /etc/apt/sources.list starting with 'deb '

It is also explained on the NVIDIA documentation:
https://docs.nvidia.com/cuda/cuda-installation-guide-linux/#advanced-setup

Find on that page “Not Found”.

Thanks for your help!

Here’s the process we documented for when this happens:

https://developer.ridgerun.com/wiki/index.php?title=Fix_broken_APT_after_JetPack_installation

The URL doesn’t mention from host PC or Jetson, but is it correct to say this is only from the host PC?

Yes, from the host PC. Thanks, I’ve updated with a note.