Repository navigation
Conversation
jetson-stats 4.3.2 has no entry for L4T 36.5.0, so jtop and the ARK UI show no JetPack version. Version 7 installs from a wheel, which never runs its service installer, so provisioning runs `jtop --install-service` itself. Its unit no longer waits for multi-user.target, and jtop reads the power mode once at startup, so a drop-in starts it after nvpmodel, as on JetPack 7 and in ARK-OS's installer.
v1.5.0 streams the camera through the hardware H.264 encoder on modules that have one, and carries v1.4.0's fix for the Services page corrupting a saved config.
nvfb.sh deletes /etc/nv/nvfirstboot straight after generating the SSH host keys. A power cut before writeback left empty keys and no guard, so nvfb never ran again and sshd never started, although flash.sh had already said the unit was safe to power off.
The initrd carries the kernel's NVMe and PCIe modules. An NVIDIA initrd update would replace them while the held ARK kernel stays, so the board could not load the drivers for its rootfs.
NVIDIA's sample rootfs enables rpcbind, which listens on port 111 on every interface, the Wi-Fi hotspot included. Nothing in the image uses it, and JetPack 7's rootfs does not ship it.
This branch has not been deployed
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.
Summary
6.2.2.9 for JetPack 6, into
jetpack6. It moves ARK-OS from v1.3.1 to v1.5.0 and jetson-stats from 4.3.2 to 7.3.0, and fixes SSH dying after a power cut early in the first boot. It also holds the initrd with the kernel and turns rpcbind off. The changelog sections for all three products are in.Draft until the release round has run on the PAB.
Problem
jetson-stats 4.3.2 has no entry for L4T 36.5.0, so jtop and the ARK UI show no JetPack version.
A power cut within 20 s of the flash printing "First boot complete … Safe to power off" leaves a unit whose sshd never starts.
nvfb.shdeletes its run-once guard straight after generating the host keys, and the deletion reaches the disk before the keys' data does. The next boot finds three empty keys and no guard. 6.2.2.7's fix clears empty keys inside nvfb's retry loop, which then never runs again.nvidia-l4t-initrdis not held, though its initrd carries the NVMe and PCIe modules built for the held kernel.NVIDIA's rootfs enables rpcbind, which listens on port 111 on every interface, the Wi-Fi hotspot included. Nothing in the image uses it.
Solution
jetson-stats 7 installs from a wheel, which never runs its service installer, so provisioning runs
jtop --install-service. A drop-in starts jtop after nvpmodel, as on JetPack 7 and in ARK-OS's installer.ARK-OS v1.5.0 encodes the camera stream on NVENC where the module has it, and carries v1.4.0's fix for the Services page corrupting a saved config.
nvfb.shnow syncs before it drops its guard, so sshd starts only once everything nvfb wrote is on the disk. JetPack 7'sssh-keygen -Adrop-in is not carried over. It recovers only after the keys are lost, it gives the unit new host keys, and on 22.04 it also creates a DSA key.The initrd joins the held boot chain, and the build removes rpcbind's units from the rootfs.
Bench results on a PAB with an Orin NX 16GB, from a full local build: