Hey everyone, I’m having some trouble with my NVIDIA Orin NX Developer Kit. I ran the install jetson script and it’s throwing an error. Not sure what’s going on — has anyone else run into issues with this? The script just seems to fail partway through.
Welcome to the forum! A few things would help narrow this down — could you share the exact error output from the script? Without seeing what specifically failed, it’s hard to know if it’s a dependency issue, a flash problem, or something else. Also, which exact “install jetson” script are you using? There are a few different ones floating around (SDK Manager, the NVIDIA-provided flash scripts, third-party ones, etc.). If you can paste the terminal output here, that’d be great.
Thanks for the reply. So I’m on kernel version 5.10.192-tegra-35.5.0-20240613202628, and yeah it’s definitely an Orin NX Developer Kit. I didn’t save the actual error output unfortunately — I closed the terminal before thinking to copy it. I can try running it again but I wanted to check if there’s a known issue with this kernel version first before I go through the whole process again. The script ran for a bit and then just… stopped with some red text. Sorry I can’t be more specific right now.
No worries, but yeah — that error output is going to be pretty essential for diagnosing this. That kernel version (5.10.192-tegra, JetPack 35.5.0) should be fine for most workflows, so I don’t think the kernel itself is the issue offhand. Before you re-run it, one thing: I’ve sent you a private message with a request for some additional verification of your board — please check your inbox when you have a moment. In the meantime, when you run the script again, could you redirect the output to a file so we don’t lose it? Something like:
./install_jetson.sh 2>&1 | tee install_log.txt
That way we’ll capture both stdout and stderr. Paste the relevant error section here once you’ve got it.
Just to set expectations — right now we’re in a bit of a holding pattern. Without the actual error output from the script, I can’t determine the root cause or point you to a specific fix. It could be anything from a missing dependency, to a device tree mismatch, to a flashing failure at a particular partition. Once you re-run and capture that output (and check your private messages for the other item I mentioned), we can pick this back up and dig into it properly. Don’t hesitate to post the logs here when you’re ready.