Repository navigation
feat(jetson): JetPack 7 / Ubuntu 24.04 (noble) package - #117
Open
AlexKlimaj wants to merge 2 commits into
Open
AlexKlimaj wants to merge 2 commits into
AlexKlimaj wants to merge 2 commits into
Conversation
Build ark-os-jetson-noble on ubuntu-24.04-arm (Python 3.12), treat L4T R36+ VBUS_DET as pinmuxed so JP7 matches JP6, and install jtop 7.2.1 with PEP 668 --break-system-packages on noble. The jammy (JetPack 6) package is unchanged.
pip no longer drops jtop.service; 7.x requires `jtop --install-service`. Without it system-manager reports Jetson hardware as Not available.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
ark_jetson_kernel#109 flashes JetPack 7.2.1 / L4T R39.2.1 (Ubuntu 24.04 noble).
provision.shthere cannot install ARK-OS because onlyark-os-jetson-jammyis published, and a jammy venv will not run on noble's Python 3.12.packaging/build.shalready listednoble:3.12as a jetson baseline, marked untested. This makes it real.What
jetson/noblematrix leg onubuntu-24.04-armso PRs and tags produceark-os-jetson-noble_<ver>_arm64.deb.install_ark_os.sh: detect PEP 668 (EXTERNALLY-MANAGED) and pass--break-system-packagesso jtop can still be a system install on 24.04.JETSON_STATS_VERSIONto 7.2.1 (maps L4T R39.2.1 / JP 7.2.1, includes the Orin JP7 GPU/tegrastats fixes). 4.3.2 reports Jetpack as not detected on JP7.R36appears. Shared helperl4t_compat.py.extras/install_ros2.shrefuses noble (Humble is Jammy-only; use Jazzy).The jammy (JetPack 6) package path is unchanged.
Follow-up in ark_jetson_kernel
Once CI attaches a noble deb (PR artifact, or a
draft-*/v*release):provision.shcurrently hardcodesark-os-jetson-jammyand only searches that prefix on fallback.ark-os-jetson-nobleand bumpJETSON_STATS_VERSIONto 7.2.1 to matchpackaging/versions.env.Tested
l4t_compatparse of R35 / R36 / R39 (R35 still drives VBUS as GPIO; R36+ skip).# R39 (release), REVISION: 2.1, Ubuntu 24.04.4, Python 3.12.3): PEP 668 present, polkit 124,libssl3t64, gpiochip/i2c/can present. Full.debinstall waits on the noble CI artifact.