JetPack 4.5 Production Release with L4T 32.5

@ArtofWar Can you check this post

Please change the second deb line to

deb https://repo.download.nvidia.com/jetson/t194 32.5 main

Thanks, i was running on Ubutu and it was having error connecting to server. Change back to unity and apt update works.

As per the doc OTA Updates the listed packages in the docs . Is there any way, i can choose not to update certain parts, like i do not want to update kernel-DTB’s , as i have already flashed my kernel with certain Nvidia Compatible hardware like MIPI-CSI Cameras and i do not want to go over the process of reflashing the kernel with Cmaera Drivers yet again !

Hello
I am trying to install Jetpack 4.5 cleanly to my Xavier AGX using SDKManager1.4 which was released newly.
SDKManager failed to install CUDA/CUDA-X AI and others after flashing jetson OS.

By checking Terminal log, i found out that apt-get update does not work.
error logs are below.
Any help will be appreciated…

ammr@xavier45:~$ sudo apt-get update
Get:1 file:/var/cuda-repo-10-2-local-10.2.89 InRelease
Ign:1 file:/var/cuda-repo-10-2-local-10.2.89 InRelease
Get:2 file:/var/cuda-repo-10-2-local-10.2.89 Release [574 B]
Get:2 file:/var/cuda-repo-10-2-local-10.2.89 Release [574 B]
Ign:3 https://repo.download.nvidia.com/jetson/common r32.5 InRelease
Ign:4 https://repo.download.nvidia.com/jetson/t194 r32.5 InRelease
Err:5 https://repo.download.nvidia.com/jetson/common r32.5 Release
Could not handshake: An unexpected TLS packet was received. [IP: 157.197.97.27 443]
Err:7 https://repo.download.nvidia.com/jetson/t194 r32.5 Release
Could not handshake: An unexpected TLS packet was received. [IP: 157.197.97.27 443]
Hit:8 http://ports.ubuntu.com/ubuntu-ports bionic InRelease
Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB]
Hit:10 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease
Hit:11 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease
Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages [1,176 kB]
Get:13 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages [1,496 kB]
Reading package lists… Done
E: The repository ‘https://repo.download.nvidia.com/jetson/common r32.5 Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository ‘https://repo.download.nvidia.com/jetson/t194 r32.5 Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I was able to boot into NFS by disabling oem-config

Flashing for NFS as root and Flashing from NFS features both requires booting into root file system hosted on NFS. Sometime due to the speed of network and the PC that NFS is hosted on, one might see that booting into NFS appears to get stuck for a long time while bringing up OEM-Config.

As a work around one can disable OEM-Config and create a default user which will make the boot to NFS file system by-pass the OEM-Config step.

One can follow the instructions at section Configuring NFS Root on Linux Host to configure the NFS server but add below step to disable OEM-Config after creating the root file system but before copying the root file system to NFS (refer to Setting Up the Root File System instruction on creating a root file system )

Step to disable OEM-Config and create a default username and password:

Step 1: Download and untar the attached file inside Linux_for_Tegra
l4t_create_default_user.tar.gz (2.5 KB)

Step 2: ./l4t_create_default_user.sh -u ubuntu -p ubuntu

After executing above steps, you can copy the root file system to your NFS.

If you are flashing form NFS, you can then follow the steps https://docs.nvidia.com/jetson/l4t/#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/flashing.html#wwpID0E0XG0HA

@Andrey1984 , please check this post regarding OEM setup during boot to NFS

1 Like

@dusty_nv
in certain cases using 20.04 In order to run cuda/gpu we need to [patch the gcc version], as otherwise there might be errors due to the gcc-9 (CUDA incompatible with my gcc version - Stack Overflow)

MAX_GCC_VERSION=8
sudo apt install gcc-$MAX_GCC_VERSION g++-$MAX_GCC_VERSION
sudo ln -s /usr/bin/gcc-$MAX_GCC_VERSION /usr/local/cuda/bin/gcc 
sudo ln -s /usr/bin/g++-$MAX_GCC_VERSION /usr/local/cuda/bin/g++

@suhash Thank you for sharing!
it works with the user creation script after copying the rootfs reated by sdkmanager atx86_64 host PC to jetson ssd over the network so that jetson boot will happen from other jetson. also it is handy as it also allows to chroot to the other jetson filesystem from local jetson

 # rsync -avzhprt  192.168.x.x:/path/rootfs_nx /path/

The original post states:

VPI 1.0 documentation will be available on Jan 22nd.

The official VPI docs are still on 0.4.4 as far as I can see: VPI - Vision Programming Interface: Main Page

I would like to check out the docs to see if it is worth upgrading, since I heavily rely on opencv types, and the new release is advertised to have better interop.

Is there an updated ETA? Right now I feel like a small child at christmas, checking every morning only to be disappointed :(

Hi @tobias.fischer1, the online VPI docs are showing as version 1.0 for me - if after refreshing, they still show as version 0.4.4 for you, you may want to clear your browser’s cache.

I can’t use USB camera on Jetpack 4.5.
I could use USB camera on jetpack 4.4.1.
Cheese : abnormal termination.
USB camera is logicool C910.
Please advice me.
Thanks.

Hi, I had to flash back to 4.4.1, since 4.5 failed repeatedly. Any ideas on what to do?

I’m sorry.

I can Use USB camera on my code.
I mistook a parameter.

But Chesse terminate abnormaly.
Thanks.

I am using Xavier Nx device and Jetpack 4.4 with TensorRT 7.1.3. I checked TensorRT 7.2.x is released for x86 architectures but not for the Jetson devices. Is there any way to use TensorRT 7.2.2 on Jetson devices right now or should we wait for the release of Jetpack 4.6 or 5 ?

I am using JetPack 4.5 and it appears that my AGX now no longer supports WiFi (M.2 adapter) or USB 3.0 web cams like the Logitech BRIO. Can anyone check this to verify if it is the JetPack 4.5 release or some other issue. I also found that a lot of docker applications break even though it says that Docker is supported.

I followed the steps to get my AGX running and booting off of the NVMe SSD (M.2) instead of the 32 gb onboard flash so I’m wondering if that could be the issue as well.

Any advice or tips on things to check? If there are critical issues how soon do you guys think they might get resolved? Is there a site to upload bug reports for the JetPack releases?

Hi ismetdagli,

Please wait for the next release.

1 Like

Hi michael4,

Please help to open a new topic for your issue, we will support you through there,

Thank you for clarifying it out. Do you any estimated date for the next release?

In summer timeframe.

1 Like

Hi! What are the changes in jetpack 4.5.1 from 4.5. Can I use the l4t-base for 4.5 (32.5) in jetpack 4.5.1 or should I wait for the new base image in the container registry. I am asking because when the jetpack went from 4.4 to 4.4.1 there was a new l4t-base image for 4.4.1.
Thank you!!