feat: Jetson Orin Nano support — GPU detection fails, k3s panics on iptables

[realkim93]

Problem

nemoclaw onboard fails on Jetson Orin Nano Super (8GB, JetPack 6.x, kernel 5.15.148-tegra) with two issues:

1. GPU not detected: nvidia-smi --query-gpu=memory.total returns [N/A] on Jetson (unified memory), so detectGpu() returns null and preflight reports "No GPU detected".

2. k3s panic on startup: The OpenShell gateway container ships iptables v1.8.10 in nf_tables mode, but the Tegra kernel lacks nft_chain_filter and related modules. The k3s network policy controller panics immediately:

   iptables v1.8.10 (nf_tables): RULE_INSERT failed (No such file or directory): rule in chain FORWARD
   panic: ...network_policy_controller.go:412
   

3. Default model too large: The default Ollama model nemotron-3-nano:30b does not fit in 8GB unified memory.

Expected behavior

nemoclaw onboard should detect the Jetson GPU, start the gateway successfully, and default to a model that fits in the available memory.

Environment

• Device: NVIDIA Jetson Orin Nano Super Developer Kit
• Memory: 8GB unified (CPU/GPU shared)
• OS: Ubuntu 22.04, kernel 5.15.148-tegra
• JetPack: 6.x
• NemoClaw: latest (npm)
• nvidia-smi output: Orin (nvgpu), memory.total: [N/A]

[wscurran]

Thanks for reporting these issues with NemoClaw on Jetson Orin Nano, I appreciate you providing detailed information about the problems, including the specific errors and hardware configuration.

[wscurran]

Thanks for reporting these issues with NemoClaw on Jetson Orin Nano, I appreciate you providing detailed information about the problems, including the specific errors and hardware configuration.

[wscurran]

These are well-documented blockers — the unified memory [N/A] from nvidia-smi, the iptables-nft vs legacy mismatch on Tegra kernels, and the default model size for 8GB unified memory are exactly the kinds of Jetson-specific issues that need to be handled as a platform target. Jetson/Orin support is on our roadmap; closing to consolidate under that effort. This issue will be a useful reference when we get there.