JetPack 6.1 installation stalls on Internet connection failure

I’m running SDK Manager 2.2.0.12021 x86_64 on Ubuntu 22.04.5 and upgrading Jetson Orin AGX Developer Kit to JetPack 6.1 through USB-C port. The Linux image was flashed successfully and it boots fine. I configured the Ethernet network manually to set a fixed IP address to 192.168.0.42, DNS to 205.171.3.25, the same as other PCs on my local network. Jetson is accessible on my LAN, but it can’t access Internet:

ping: yahoo.com: Temporary failure in name resolution

This produces Internet connection failure message in SDK Manager. What is the solution?

BTW, I had the same problem with default automatic settings in IPv4 tab.


After some wasted time and no discernible changes in Ubuntu configuration on the Jetson, Internet connection works. I would much prefer a repeatable procedure than some obscure magic.

Unfortunately, installation can not proceed, due to bad script run remotely by SDK Manager:

Internet connection check failure.
command < ssh -F /dev/null -o PreferredAuthentications=password -o PubkeyAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ConnectTimeout=5 nick@192.168.0.42 'ping -c 3 nvidia.com || wget --spider -T 5 -t 1 www.nvidia.com' > terminated with error, exitCode: 255.

I tried this on my desktop:

paul@desktop:~$ ping -c 3 www.nvidia.com
PING e33907.a.akamaiedge.net (23.46.228.170) 56(84) bytes of data.
64 bytes from a23-46-228-170.deploy.static.akamaitechnologies.com (23.46.228.170): icmp_seq=1 ttl=56 time=32.8 ms
64 bytes from a23-46-228-170.deploy.static.akamaitechnologies.com (23.46.228.170): icmp_seq=2 ttl=56 time=33.0 ms
64 bytes from a23-46-228-170.deploy.static.akamaitechnologies.com (23.46.228.170): icmp_seq=3 ttl=56 time=32.6 ms

--- e33907.a.akamaiedge.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 32.644/32.806/32.976/0.135 ms
paul@desktop:~$ ping -c 3 nvidia.com
PING nvidia.com (34.194.97.138) 56(84) bytes of data.

--- nvidia.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2029ms

It seems that using nvidia.com in the script instead of www.nvidia.com is the source of this problem. This issue was already raised in Anyone able to ping nvidia.com? and SDK Manager fails, can't ping nvidia.com posts. Perhaps it’s time to make a correction in Internet connection test script.


I chose “Ignore” button and installation failed. Now Jetson doesn’t see Internet again. Pretty horrible experience. Should I try JetPack 6.0 instead? Is it more solid?


Reboot doesn’t help, but this sequence does:

sudo dhclient -r
sudo dhclient

What is the problem?

Hi,

I am not quite sure if I understand your comment.

This produces Internet connection failure message in SDK Manager. What is the solution?

Why is “Jetson cannot reach Internet” related to sdkmanager installation? Sdkmanager is running on the x86 host PC and by default it installs package to Jetson through USB connection. No Internet is involved.

Not true. SDK Manager is using apt on Jetson through SSH to install SDK components. apt can’t pull packages from repositories without Internet. Internet connection failure message in SDK Manager is there for a reason.

If I remember correctly, it is the host that runs sdkmanager that requires to have Internet.

The sdkmanger will send the package to Jetson through USB connection as this picture.

And you shall be able to install sdk even without ethernet cable connected on your Jetson.

That’s what I hoped for, but it wasn’t the case. USB was used for flashing the OS, but Ethernet was required to install components.

What is the exact error when sdkmanager told you there is error? Could you share me the full error log by clicking the export logs button on sdkm?

I’m past that installation stage. Here is my post with a solution I used to fix OS configuration problem on Jetson: networking - Ubuntu 22.04 on Nvidia Jetson temporary failure in name resolution - Ask Ubuntu

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