Sdkmanager will not let me select a Linux distro?

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

I am trying to use the SDK Manager but when I select my target host (NX) the Linux selection bar is grayed out.

Looking at ~/.nvsdkm/sdkm.log I see:

11:27:00.343 - info:
11:27:00.343 - info: validating release: DRIVE OS 5.1.9.0 PDK
11:27:00.344 - error: Not NVOnline user
11:27:00.344 - warn: No access to release DRIVE OS 5.1.9.0 PDK. Message invalid level3 json path
11:27:00.344 - info:
11:27:00.344 - info: validating release: DRIVE OS 5.1.6.0 PDK
11:27:00.344 - error: Not NVOnline user
11:27:00.344 - warn: No access to release DRIVE OS 5.1.6.0 PDK. Message invalid level3 json path
11:27:00.344 - info:
11:27:00.344 - info: validating release: DRIVE OS 5.1.6.0 SDK
11:27:00.345 - error: Not NVOnline user
11:27:00.345 - warn: No access to release DRIVE OS 5.1.6.0 SDK. Message invalid level3 json path
11:27:00.345 - info:
11:27:00.345 - info: validating release: DRIVE OS 5.1.3.0 PDK
11:27:00.345 - error: Not NVOnline user
11:27:00.345 - warn: No access to release DRIVE OS 5.1.3.0 PDK. Message invalid level3 json path
11:27:00.345 - info:
11:27:00.346 - info: validating release: DRIVE OS 5.1.3.0 SDK
11:27:00.346 - error: Not NVOnline user
11:27:00.346 - warn: No access to release DRIVE OS 5.1.3.0 SDK. Message invalid level3 json path
11:27:00.346 - info:
11:27:00.346 - info: validating release: DRIVE OS 5.0.13.2 (with DRIVE AV)
11:27:00.346 - error: Not NVOnline user
11:27:00.346 - warn: No access to release DRIVE OS 5.0.13.2 (with DRIVE AV). Message invalid level3 json path
11:27:00.360 - info: Validate l3 url successfully
11:27:00.360 - info:
11:27:00.360 - info: validating release: JetPack 3.3.3
11:27:00.741 - info: Validate l3 url successfully
11:27:00.741 - info:
11:27:00.741 - info: validating release: JetPack 3.3.2
11:27:01.089 - info: Validate l3 url successfully
11:27:01.089 - info:
11:27:01.090 - info: validating release: JetPack 3.3.1
11:27:01.090 - info: Validate l3 url successfully
11:27:01.091 - info:
11:27:01.091 - info: validating release: JetPack 4.2.3
11:27:01.091 - info: Validate l3 url successfully
11:27:01.092 - info:
11:27:01.092 - info: validating release: JetPack 4.2.2
11:27:01.092 - info: Validate l3 url successfully
11:27:01.093 - info:
11:27:01.093 - info: validating release: JetPack 4.2.1
11:27:01.629 - info: Validate l3 url successfully
11:27:01.629 - info:
11:27:01.630 - info: validating release: JetPack 4.2
11:27:01.876 - info: Validate l3 url successfully
11:27:01.877 - info: Event: Login Progress: Loading and processing available products…
11:27:01.883 - info:
11:27:01.883 - info: validating release: DeepStream
11:27:02.130 - info: Validate l3 url successfully
11:27:02.130 - info:
11:27:02.131 - info: validating release: DeepStream
11:27:02.391 - info: Validate l3 url successfully
11:27:02.392 - info:
11:27:02.392 - info: validating release: DeepStream
11:27:02.667 - info: Validate l3 url successfully
11:27:02.667 - info:
11:27:02.667 - info: validating release: DeepStream
11:27:02.911 - info: Validate l3 url successfully
11:27:03.164 - info: Selecting Jetson product
11:27:03.167 - info: step1 load in ms: 6470.279999999999
11:27:03.168 - info: Web server configuration build version 1003D584J23C is set
11:27:03.213 - info: Checking for update with mainRepoURL: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
11:27:03.407 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/pisymbol/.nvsdkm/dist successfully.
11:27:03.963 - info: sdkml2_sdkmanager_linux_deb.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/SDKMANAGER/Linux/sdkml2_sdkmanager_linux_deb.json has been downloaded to /home/pisymbol/.nvsdkm/dist successfully.
11:27:03.966 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.json
11:27:03.977 - info: [updater] no SDK Manager client update available.
11:27:06.870 - info: Selecting Jetson product
11:27:47.248 - info: == second-instance == /opt/nvidia/sdkmanager/sdkmanager /snapshot/main/headless.bundle.js
11:27:47.959 - info: cleaning up engine
11:27:47.959 - info: installManager cleanup
11:27:47.960 - info: cleanning up the downloader and worker
11:27:47.960 - info: [Worker] destroying
11:27:47.963 - info: The overall duration (Download + Install) is 0.000s

I did successfully login via external browser link. But I do see those error messages which are strange. Is there something wrong with my account?

2

This is the incorrect software for the Jetson series. “Drive” is for some much more powerful hardware used in autonomous vehicles (think full automobiles, not drones). Make sure you select the right login.

3

Perhaps. But that doesn’t explain SDK manager’s behavior of not offering me any Linux dstros to install. Manual flash goes through but doesn’t yield a bootable system so far.

5

Hi alexander,

Can you please package and attach ~/.nvsdkm/ directory and the screenshot when Linux selection bar is grayed out?

6

See attached.nvsdkm.zip (26.6 KB)

7

Hi alexander,

JetPack installation is only supported on Ubuntu 16.04 and 18.04 host. It seems that you are running a different Linux distro.

8

That’s not it. I flashed dozens of TX2 with this exact machine (the distro is in fact 18.04 or based on it).

I am getting a warning now about the host machine not having at least 8GB of RAM? Could that be related?

I don’t want to reinstall 18.04 on a machine that already has an 18.04 run-time. Moreover, why would the SDK CARE about the host’s distro provided all the binaries are running? Is it actively checking that? (I doubt it a part from startup).

9

Hi alexander,

Please check if SDKManager "Not supported on Linux" helps.

1 Like
10

The binaries are essentially creating an entire operating system in an image. I don’t have a specific case, but tools creating content have to be compatible in version and capabilities. You’d need to know of a specific case to say why some particular package must be running and of a given release.

12

They are creating images of binaries, not building them from source. It should just work with minimal change.