Err:1 https://repo.download.nvidia.com/jetson/x86_64/focal r35.1/main amd64 nvsci amd64 1.0 404 Not Found

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hello,

While following the documentation to install Jetpack Debian Packages on host (How to Install JetPack :: NVIDIA JetPack Documentation) and executing this command :
sudo apt-get install cuda-cross-aarch64-11-4 cuda-cupti-cross-aarch64-11-7 cuda-sanitizer-11-7 cuda-toolkit-11-4 libnvvpi2 nsight-compute-2022.2.1 nsight-compute-addon-l4t-2022.2.1 nsight-graphics-for-embeddedlinux-2022.3.0.0 nsight-systems-2022.3.3 nvsci python3.8-vpi2 vpi2-demos vpi2-cross-aarch64-l4t vpi2-dev vpi2-samples

It downloads a few of the packages but I get a 404 for the package located there :
https://repo.download.nvidia.com/jetson/x86_64/focal/pool/main/N/NvSci/NvSci_1.0_amd64.deb

I can access there properly : Index

I did the sudo apt update but I’m still getting a 404 for the specific package aforementioned.

3

Hi,

Have you updated the source list?

https://docs.nvidia.com/jetson/jetpack/install-jetpack/index.html#jetpack-debian-packages

Edit /etc/apt/sources.list

...
deb http://repo.download.nvidia.com/jetson/x86_64/focal r35.1 main

Thanks.

4

Yes, and it’s been working since I managed to install all of the other components except nvsci , which is a package you may find in the link of my first message ( this one :
https://repo.download.nvidia.com/jetson/x86_64/focal/pool/main/N/NvSci/NvSci_1.0_amd64.deb), because this link returns a 404 error.

5

Hi,

Thanks, you are right. The NvSCI package is missing.
Let us check this issue with our internal. Will keep you updated.

Thanks.

7

Hello,

How are you doing on this?
I am installing JetPack 35.1 and the link to NvSci is still broken.

Thanks.

8

Hi,

Sorry that our internal team still check this issue.

For a WAR, could you try to install the NvSCI package with the SDK manager?

Thanks.

9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

11

Hi,

We have fixed this issue in our public apt server.
Please give it a try.

Thanks.