microsoft / microsoft/onnxruntime

About NVIDIA Jetson TX1/TX2/Nano/Xavier/Orin Builds

Open
#23,113 5 comments 0 reactions 1 assignee View on GitHub

@yf711 is already working on this.

Since Dec 15, 2024.

platform:jetson
Dominant language
C++
Stars
21.9k
Forks
4.2k
Avg merge
4d 11h
Merged PRs (30d)
184

Description

Hello

In https://onnxruntime.ai/docs/build/eps.html#nvidia-jetson-tx1tx2nanoxavierorin

It is written that CUDA 12.x is only available to Jetson Orin and newer series (CUDA compute capability >= 8.7)

When I look at The following table shows the CUDA UMD and CUDA Toolkit version compatibility on NVIDIA JetPack 5.x release: section in https://docs.nvidia.com/cuda/cuda-for-tegra-appnote/index.html#upgradable-package-for-jetson

I do not observe such a constraint.

Moreover when I try to install Cuda 11.8 on Nvdia Xavier Dev Board(compute capability 7.2) with Jetpack 5.1.2 with these lines

wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/arm64/cuda-keyring_1.0-1_all.deb
sudo dpkg -i cuda-keyring_1.0-1_all.deb
sudo apt-get update
sudo apt-get -y install cuda

It automatically installs Cuda 12.2.
This is not consistent with the statement CUDA 12.x is only available to Jetson Orin and newer series (CUDA compute capability >= 8.7)

When I explore https://elinux.org/Jetson_Zoo#ONNX_Runtime I observe that for Jetpack 5.1.2(Python 3.8) onnxruntime 1.18.0 is available.
But after installing the package from the .whl file into a python 3.8 venv we get Libraray errors at runtime regarding to the GLIBCXX versions.
Is this .whl file OK. Or should we build onnxruntime from the source?

If we need to build from the source, the default gcc on Jetpack 5.1.2 is not enough; we need gcc 11.
I am unsure if using gcc11 on Jetpack 5.1.2 is safe.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.