Apt get update fails for Nvidia repos on Jetson AGX (Ubuntu 18.04)

I have a Jetson AGX and I’m unable to get any Nvidia-related updates to run on it. Here are the contents of my /etc/apt/sources.list.d/nvidia-l4t-apt-source.list :

deb https://repo.download.nvidia.com/jetson/common r32.4 main
deb https://repo.download.nvidia.com/jetson/t194 r32.4 main

If I comment out these sources, the update runs successfully for the other sources. If I leave them uncommented, here is the output of ‘sudo apt update’:

Hit:1 http://packages.ros.org/ros/ubuntu bionic InRelease
Hit:2 http://archive.canonical.com/ubuntu bionic InRelease                                                                                                        
Hit:3 http://ports.ubuntu.com/ubuntu-ports bionic InRelease                                                                                                       
Ign:4 https://repo.download.nvidia.com/jetson/common r32.4 InRelease                                                                                    
Hit:5 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease                                                                                     
Ign:6 https://repo.download.nvidia.com/jetson/t194 r32.4 InRelease                                                                                      
Hit:7 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease                                                                                   
Err:8 https://repo.download.nvidia.com/jetson/common r32.4 Release                                                                
  Could not handshake: Error in the pull function. [IP: 96.6.42.9 443]
Hit:9 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease                                                              
Err:10 https://repo.download.nvidia.com/jetson/t194 r32.4 Release                                                                 
  Could not handshake: Error in the pull function. [IP: 96.6.42.9 443]
Ign:11 https://s3.amazonaws.com/autonomoustuff-repo bionic InRelease                                                             
Hit:12 https://s3.amazonaws.com/autonomoustuff-repo bionic Release
Ign:13 https://s3.amazonaws.com/autonomoustuff-repo bionic Release.gpg
Reading package lists... Done
E: The repository 'https://repo.download.nvidia.com/jetson/common r32.4 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.4 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.

The system time is synchronized, I’ve tried ‘apt clean’, and I can get to Index.

Hi,
Could you try Jetpack 4.6.2? Would be great if you can use later release instead of Jetpack 4.4

I’m using a Jetson AGX Xavier with a Diamond Systems Elton carrier board - if I do the upgrade, will it ‘lose’ any of the hardware customization? It looks like the Elton BSP is designed for r32.4.3. Is that version just not supported anymore?

Actually, the only reason I wanted to do an update anyway is because I am having this same issue: https://forums.developer.nvidia.com/t/changing-mtu-size/68774/11 and hoped updating would fix it. There is a kernel patch linked in this topic as well, but I am not sure how to apply it.

Hi,
You would need to apply the patch to kernel source code and rebuild/replace kernel image. Does the carrier board vendor provide the method to build kernel?

The source code is in
https://developer.nvidia.com/embedded/L4T/r32_Release_v4.3/Sources/T186/public_sources.tbz2

But it is for default developer kit. In general custom carrier boards have different hardware layout and would need some patches from vendor.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.