A warning and/or bug to squash:
apt update this morning on my Xavier NX, I saw the host of upgrades available for the various
nvidia-l4t-* packages and happily ran
apt upgrade to get the latest versions. (I was upgrading from 32.4.2.) Upon power cycling, my install no longer boots. I’m troubleshooting now, but be advised there may still be some kinks in the package-manager-driven upgrade system.
After finding this post (which I was unaware of initially) and following the links regarding upgrading from a previous JetPack version, I see the instructions follow
apt upgrade with
apt install nvidia-jetpack, which I did not do. I’m unsure if this is related to my inability to boot.
Worst case scenario I’ll just reflash with the new version directly, but I felt like someone ought to know.
Thank you jmlilly4
If you are upgrading from JetPack 4.4 DP, you will need to upgrade L4T as you did
sudo apt update
sudo apt upgrade
and then install nvidia-jetpack again
sudo apt install nvidia-jetpack
We will be correcting the documentation in L4T documentation to mention this extra step (install nvidia-jetpack) in case you are upgrading full JetPack.
Please refer here for instructions to upgrade JetPack:
Thank you. I’ve reflashed my SD card and will know to add that step in the future; luckily not much work was lost.
I have a lingering worry this may trip others up before long - folks who will see package updates in the apt repos and proceed to run upgrades without ever thinking the consult the L4T documentation. I don’t know enough about apt to think of an obvious fix for that. Maybe a big warning screen as a post-upgrade hook?
We were able to repdroduce the issue even after following the steps i provided. We are looking into fixing it.
Please refer to this link to workaround this issue. Really sorry for inconvenience.
Hi, I got a error after upgrading JetPack when I use MobaXterm to connect Jetson NX.
Xlib: extension “NV-GLX” missing on display “localhost:13.0”.
I see this one as well.
I had created a Docker Image based on deepstream-l4t:5.0-dp-20.04 to run the deepstream python apps demos on my xavier nx with Jetpack4.4 DP. It worked perfectly. But when I switched to the 4.4. release (I flashed a new SD card) running the same code (/opt/nvidia/deepstream/deepstream-5.0/sources/python/apps/deepstream-test1-usbcam# python3 deepstream_test_1_usb.py /dev/video0) I got the following error and do not know how to fix it:
InferContext[UID 1]: Info from NvDsInferContextImpl::buildModel() <nvdsinfer_context_impl.cpp:1588> [UID = 1]: Trying to create engine from model files
Warning, setting batch size to 1. Update the dimension after parsing due to using explicit batch size.
ERROR: [TRT]: Network has dynamic or shape inputs, but no optimization profile has been defined.
ERROR: [TRT]: Network validation failed.
ERROR: Build engine failed from config file
I switched back to the 4.4. DP and with my image from dockerhub, it still worked there.
OpenCV component is already compatible with CUDA and cuDNN?
DeepStream 5.0 Developer Preview is not supported on JetPack 4.4 production release. For using DeepStream 5.0 DP, you will need to be on JetPack 4.4 DP.
JetPack 4.4 production release supports DeepStream 5.0 production release (expected end of this month)
But in case if I need to use opencv with gpu aceleration it will be necessary recompile opencv?
Thank you for the clarification.
Yes, you will have to recompile it, and version 4.3.0 is incompatible. It’s easiest to build from master since that has the necessary fixes already.
Does JetPack 4.4 support for TensorFlow?
Yes. You can get TensorFlow wheels from here:
Also, we have released Tensorflow container for JetPack 4.4 on NGC
Thank you and sorry to bother you again.
JetPack 4.4 support for TensorFlow in python.
Does JetPack 4.4 support for TensorFlow in C, is there any C API?
@AastaLLL, would you be able to help here with TF C API question.
Is this BSP source package includes cboot source code ? if not can you provide the link for latest cboot ?