Skip to content

fix(jetpack6): ARK-OS v1.5.0, jetson-stats 7.3.0 and first-boot SSH for 6.2.2.9 - #169

Draft
dakejahl wants to merge 6 commits into
jetpack6from
dakejahl/jetpack6-6.2.2.9
Draft

dakejahl wants to merge 6 commits into
jetpack6from
dakejahl/jetpack6-6.2.2.9

Conversation

@dakejahl

Copy link
Copy Markdown
Collaborator

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.sh deletes 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-initrd is 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.sh now syncs before it drops its guard, so sshd starts only once everything nvfb wrote is on the disk. JetPack 7's ssh-keygen -A drop-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:

  • 6.2.2.8 as released, power cut 0, 10 and 20 s after the flash's safe message: sshd dead on every next boot, with all three host keys 0 bytes. At 40 s the keys survived.
  • This branch with the sync, the same cuts: the original keys survived all three. With only the drop-in, every cut lost the keys and sshd came back with new ones.
  • First boot and a reboot: the UI shows JetPack 6.2.2 and 40W, the stream runs on NVENC at 1080p, and jtop reads 40W with nvpmodel passing. ARK-OS's opt-in services are off.
  • On first-boot conditions, jtop read the power mode on 4 of 4 boots without its drop-in and 4 of 4 with it.

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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant