JetPack 3.1 is a production software release for both Jetson TX1 and TX2, with Linux kernel 4.4 shared between both devices. In addition to bug fixes and improvements in the camera stack, JetPack 3.1 also includes updates to TensorRT 2.1 and cuDNN 6.0, delivering twice the inferencing performance for latency-sensitive applications. See our Parallel ForAll article, JetPack 3.1 Doubles Jetson’s Low-Latency Inference Performance.
View the full JetPack 3.1 Release Notes here, and the Release Notes for L4T here.
The kernel must be rebuilt…swap can only be added as a direct integrated feature, not as a module. Adding swap to the Image will not invalidate other features though, so just keep CONFIG_LOCALVERSION as matching the suffix of the current “uname -r” and replace the existing Image file. I always suggest backing up the original image, or better yet, adding a second boot entry to extlinux.conf to test first.
Unlike previous versions, there is a user nvidia in JetPack 3.1 . The samples etc. which were earlier in the home directory, are in ‘nvidia’ user directory this time. Though, the online install guide seems to indicate otherwise.
Is it possible the Tx1 and TX2 installations are working any differently?
FWIW I repeated steps on both users just to make sure if one of them works. No luck.
The config_swap on the kernel is disabled. This will make compiling many modules difficult on this build. Please consider releasing an update to overcome this, this is troublesome. Though, it appears it’s a small issue for linux users, it is still another hurdle.
Has anyone been successful in using the CSI camera on Tx1 with JetPack 3.1? Will be helpful if you can share any tips that helped… Given this is the LTS edition, I am keen on using this as a base to move forward, but losing more time is also hurting my project.
Just a heads-up…the issue of apt-get update overwriting libglx.so is back. Anyone wanting to fix this can copy (from the driver package) “nv_tegra/nvidia_drivers.tbz2” over to “/” of the Jetson, and upack it to fix this (verify good/bad with “sha1sum -c /etc/nv_tegra_release”):
# On the Jetson, after copy of nvidia_drivers.tbz2 to "/"...
sudo tar xvfj nvidia_drivers.tbz2
# Verify fixed:
sha1sum -c /etc/nv_tegra_release
Thanks for your kindly help! @nish_p
I use Jetpackunistaller to uninstall the whole jetpack files(64_TX1) and all the jetpack download files(jetpack_dowanloads,jetpack_doc …).Then I move JetPack-L4T-3.1-linux-x64.run to a clean folder and run it ,follow shaktiD’s suggestion.It’s a pitty,the issue also exists.I think that my host PC has run Jetpack3.0 before and has not restarted since the last running of Jetpack3.0.so,I restart my PC and run again,It works normally and the problem is resolved.