I am writing to you in order to obtain advice and clarifications regarding best practices for multiple issues.
Context: We have 5+ ZED Box Orin NX 16gb (with ZED X cameras); 2 of them had just returned from warranty and the state appears as new (we didn’t note the old serials in order to compare them but this is probably not relevant); The image and version they come with is different from the latest flash image found in your docs: 36.4.4 vs 36.4.3;
I want to know if it’s a good idea to make a flash backup of the factory image since it is 36.4.4 and the L4T have correct priorities set and it’s upgrade safe, but I’ve also encountered the following issues and have specific questions as well:
NEW ZED Boxes (36.4.4): ZED_Diagnostic reports that I have both SDK and GMSL driver installed but there’s no camera being detected, even after zed_x_daemon and nvargus restart + reboot (even tried all 4 camera cable splits); (No SDK / driver reinstall was done so far - wanted to clarify first what’s the actual issue, if any); The attached ZED_Diagnostic data is from here.
Why does the official post flash procedure recommend apt upgrade (without any hold or priority set) when from my experience this breaks the system by upgrading to 36.4.7 - which is not supported! What’s the correct procedure to have a stable system and installation starting from a flash?
See attached screenshot - it just happened after a reboot command on a new ZED Box - so far I’ve only installed epiphany-browser and anydesk!
After flashing a ZED Box (with JetPack 6.2 and 36.4), I’m unable to use the WIFI and fixing it took long enough that I gave up trying and just used the wireless from my attached MikroTik - but the factory 36.4.4 image comes with a working WIFI. (I tried the usual recommended WIFI fixes after flashing but without success)
One of the ZED Boxes (same version as others) has a non working reboot! Each reboot = shutdown; it’s not a first generation ZED Box - it doesn’t get fixed by flashing and the issue did not replicate on other ZED Boxes - any idea what’s the issue and how to fix it? (I even tried to flash the QSPI but the reboot was not fixed)
Thank you for your attention and we hope to solve and clarify all of the above!
Should I always run: “sudo apt update” + “sudo apt upgrade -y” right after flashing, before “sudo apt install nvidia-jetpack”? No need to lock packages or set priorities in any way? Why would I even keep Ubuntu Software Updater? We need a stable working environment that won’t brick itself at the next upgrade.
Please advice on the best and full correct flash + post flash procedure in order to run the latest stable, recommended versions. After reaching this step and having everything installed with the latest correct versions, is it recommended and possible to create a flash image in order to use it directly?
Regarding the reinstalling of the SDK and drivers on the factory images:
Even if the name of the pkg did autocomplete on TAB, there was an error when trying to uninstall it and reinstalling the SDK + driver did not fix anything; there’s also a bug with the nvargus service install - after each reinstall it triplicates a line in the service.
* P.S. Please advice regarding this issue as well as it happens randomly and reconnecting the camera is not a viable option - even more - it happened on the ZED Box that doesn’t have a working reboot so I can’t do much but restart services.. Download STEREOLABS-Screenshot 2025-11-26 145440.png | LimeWire
EDIT: The other returned ZED Box has ZED SDK 5.1 and the ZED X camera is working without any issues! One notable difference is a script on Desktop called - sdk_installer.run; Why are they different and should the working one be kept like this without flashing it?