We’re pleased to announce that a developer preview release of JetPack 3.2 is now available for Jetson TX1 and TX2!
Highlights include support for TensorFlow models in TensorRT 3.0 GA, up to 15% perf/W improvement for DL applications, out-of-the-box kernel support for Docker, and support for Ubuntu 16.04 on your host PC (Ubuntu 14.04 on your host PC will also work, except cross-development packages for OpenCV and VisionWorks will be unavailable on that host PC). With JetPack 3.2, NVIDIA has also enabled Jetson TX2i for industrial environments. For more info, please view the full Release Notes.
Have the issues with OpenCV and CUDA9 been resolved in this production release? What OpenCV modules are included with this release of Jetpack 3.2? It’d be nice to know before flashing. Thanks.
Hi Mepix, the configuration with OpenCV is still the same as the Developer Preview, as the issues weren’t resolved upstream, however you can re-build from source with GPU enabled if you so desire.
Hi Honey_Patouceul, it looks like the log was from apt-get update, in this case it’s doubtful the packages have been tampered with or are otherwise unsecure, is the error able to be ignored and the update completed ok?
I can confirm I have the same issue when I do apt_get update after doing a fresh install of JetPack 3.2. I believe apt-get upgrade still works for the other repositories.
I wouldn’t expect much upgrade from a local repository, but it would be nice to get it signed so that we won’t see this error any longer. Is there a way to fix it ?
We confirmed that the packages are signed, however it appears that you haven’t added a public key. Without a public key added to your system, you will encounter the warnings/errors. Can you try adding a public key and verify that the behavior is corrected?
As per the JetPack 3.2 Release Notes, the L4T kernel has been configured with the proper flags such that you can install docker.io, however we haven’t officially tested nvidia-docker yet. One of my colleagues has a bash script for enabling GPU sharing within docker containers located here:
When I tried to install 3.2 b196 (the new package), it seems to want to install multimedia api 28.1 instead of 28.2 (which gets installed with b157). is this a regression?
Hi Wahaj, the officially supported method is to re-flash with JetPack so it automatically updates the kernel and L4T BSP with the updated NVIDIA drivers, CUDA toolkit, ect. It is recommended that you backup your modified files before doing this so you can copy them back over after flashing, as the partition will be reformatted.
Unofficially, if your Jetson TX2 currently has the JetPack 3.2 Developer Preview on it, which is pretty similar, there is a small chance that if you manually update to the new kernel and the L4T drivers, it may work for you. However you would still want to backup your files first and it will probably take you more time to achieve than just reflashing and restoring your files.