Jetson AGX Orin 64GB DevKit Sdkmanager fails downloading packages

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

I get all sorts of download errors when using SDK manager.

Off the shelf installation on Ubuntu 20.04 via the 2.2.0 amd64 deb package. No errors during installation. Started sdkmanager on commandline, logged in to developer account successfully.

Errors are here:
16:03:59 : CUDA Runtime - target: download https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-5.1.4/Jetson_514_b17/./cuda-repo-l4t-11-4-local_11.4.19-1_arm64.deb failed, retrying 3…

16:03:59 INFO: wait for 16.517 sec before retry https://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-5.1.4/Jetson_514_b17/./cuda-repo-l4t-11-4-local_11.4.19-1_arm64.deb

16:03:59 ERROR: TensorRT Runtime - target: Head request failed to retrieve file size. Server error: 200 - OK . Url: https://developer.download.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-5.1.4/Jetson_514_b17/nv-tensorrt-local-repo-l4t-8.5.2-cuda-11.4_1.0-1_arm64.deb?__token__=exp=1735657738~hmac=84ddf2e11e94bbb3f9df68ae2af4e3b93ec31b72fc9ca3ee35081bda5a5aa50f Could be because 1) Url is invalid, 2) request requires cookies

16:03:59 ERROR: TensorRT Runtime - target: Download ‘TensorRT Runtime’ failure

16:03:59 ERROR: TensorRT Runtime - target: Head request failed to retrieve file size. Server error: 200 - OK . Url: https://developer.download.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-5.1.4/Jetson_514_b17/nv-tensorrt-local-repo-l4t-8.5.2-cuda-11.4_1.0-1_arm64.deb?__token__=exp=1735657738~hmac=84ddf2e11e94bbb3f9df68ae2af4e3b93ec31b72fc9ca3ee35081bda5a5aa50f Could be because 1) Url is invalid, 2) request requires cookies

16:03:59 ERROR: TensorRT Runtime - target: Download ‘TensorRT Runtime’ failure

16:03:59 ERROR: TensorRT Runtime - target: download failed

And now, if someone might ask:

  • YES, my network is working, I can download these URLs in Firefox etc. - only SDKmanager is too stupid to work properly.
  • I need SDKmanager to flash my Jetson Orin DevKit - it broke when upgrading to 36.4 jetson linux (display black)
  • Flashing with flash.sh failed too, display blank…
  • I wonder whether these kits and all the software around it is just all totally broken, seeing a lot of posts on these forums.
  • Sorry if I cannot give you more infos, SDKmanager also does not show me more and does not allow me to do more to trace down the error
  • Capable NVIDIA staff should be able to reproduce the error I guess - it’s just off the shelf sdkmanager for me
3

Oh no! carolyuu failed the Turing test…

4

Come on? Really! NVIDIA is THE AI company out there - at least claiming that - and we cannot even get a screen output of the Jetson board running (you forgot that you actually did graphics cards once?), we cannot write an SDKmanager that can actually pass a login cookie to a download URL? and we cannot write a proper AI bot that responds to my question instead of posting something completely(!!!) off topic??? (maybe the poor guy was human…?)

5

We got same issue reporting earlier. Still fixing this.

6

Thanks!

On the note of the black screen: I tried to revert back to Jetson Linux 34.1 which came with the DevKit. All works fine there. I could flash it with flash.sh and when booting this version everything is fine.

So it seems there are two issues:

1.) 36.4 has a bug with the display (something must have changed with the resolution/display detect etc.) - that makes it just be black (I have standard Samsung HD monitor). The bug appears when flashing from scratch, or when updating from 34.1

2.) The sdkmanager does not apply the login cookie to nvidia developer account

7

Hi,

I can comment on the first issue here.

Actually rel-34.1 should not be used anymore. It is basically a preview version for Orin that has been released for like 2 years ago (earliest version). And we have lots of bugs fixed now and then.
I am not saying that 36.4 has no problem. Just to make sure the comparison is correct. Maybe you should use rel-35.6 first and see if the monitor is fine there.

There are some users reporting rel-36.4 having some display issues. But as you know such issue could be picky monitor one so it is hard for me (yes, I am checking those issues) to gather enough info at this moment. For example, my monitors are fine and can show the GUI even in rel-36.4. It seems to be a specific case that would reproduce issue.

8

Hi, I’ve tested with the 35.6. and my monitors seem fine there - no issues at all.

For the 36.4, monitor goes blank after boot (seeing console messages, and then going blank, but having signal somehow). When reconnecting the HDMI cable I see the login screen GUI for about 1s, then black again. Could not find any useful error logs in the Xorg log. Using a DP to HDMI Adaptor. But as this works with the older releases, I don’t think the adapter nor the monitor is a problem per se.

Are there any differences in Xorg config, resolution, monitor modes etc. in the 36.4. compared to 35.6? Perhaps thats a start to narrow down the search.

Also - any updates on the SDKmanager issue with the downloads missing the session cookie?

9

Maybe you could also share out the xorg log for me to check.

From what I’ve heard from other users. The problem here is related to DP-HDMI adapter. Looks like only this usecase would trigger this error. What kind of adapter are you using there? Could you provide brand name?

Also - any updates on the SDKmanager issue with the downloads missing the session cookie?

This one should be fixed now.

10

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