No target operating system supported on Ubuntu [16|18].04?

I’ve just received a new development laptop, and when attempting to install the DRIVE SDKs for “DRIVE AGX Developer Kit (E3550)” using SDK Manager, I get a “Not supported on Ubuntu 18.04” message under both “Linux” and “QNX” in the “Target Operating System” area. Proceeding to Step 2 is not possible (button is disabled).

Reformatted my laptop to run Ubuntu 16.04 LTS: same results (“Not supported under Ubuntu 16.04”).

Funny thing is, just a few days ago I was perfectly able to install the target operating system support files… what happened?!

Also, just in case it helps, I’m logging in using my partners.nvidia.com account.

Hi emiliot367q,

SDK Manager does support Ubuntu 16.04
Could you do me two flavors:

  • make sure your SDK Manager is up-to-date
  • provide me the output of ``` cat /etc/lsb-release ```

Thanks,

Hello HaoTsui,

thanks for your support:

1.- My SDK Manager seems to be up to date (0.9.13.4763)
2.- These are the contents of /etc/lsb-release:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"

Also, I’ve checked and my bistro installation is x86_64 as advised by the SDK Manager documentation:

Linux emilio-VirtualBox 4.15.0-50-generic #54~16.04.1-Ubuntu SMP Wed May 8 15:55:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Thanks for your help.

Hi, I have a similar issue. After updating to SDKmanager 0.9.13.4763, my partners.nvidia.com account claims that both Linux and QNX are “unsupported” on Ubuntu 16.04 and Ubuntu 18.04. If I sign in using a using my developer.nvidia.com account, I am permitted to install Linux (my dev account has no QNX permissions) on Ubuntu 16.04.

How can we rectify this? Thanks.

Dear ryanuz25n,
Was QNX and Linux available for all previous versions? Thanks.

Dear emiliot367q,
Could you please try to install your developer.nvidia.com account? Thanks.

Hi SteveNV,

Yes, I was previously able to access QNX using my partners account in a recent, older version of SDKmanager.

Thanks!

Dear ryanuz25n,

Could you help to check below?

  • Login with his NVOnline account, check the membership information per below instruction and send the screenshot https://docs.nvidia.com/sdk-manager/user-account-membership/index.html
  • Upload ~/.nvsdkm/sdkm.log

Hi SteveNV,

The forum does not appear to provide a mechanism for uploading files.

The screenshot I’ve taken of the membership information screen includes the following entries–

  • D5.1Q 5.1.3.0 DRIVE 5.1 QNX SDK DRIVE OS (ID 441)
  • D5.1L 5.1.0.0 DRIVE 5.1 Linux PDK DRIVE OS (ID 412)

The log included below appears to confirm these IDs.
The .nvsdkm/sdkm.log file includes some identifying information, so I’ve excerpted what I would guess to be the relevant part.

2019-08-14 11:45:40.361 - info: pid listGroups success, took 3.952s
2019-08-14 11:45:40.361 - info: the PID groups that user can access:
2019-08-14 11:45:40.361 - info: { id: 412, name: D5.1L 5.1.0.0 DRIVE 5.1 Linux PDK DRIVE OS }
2019-08-14 11:45:40.361 - info: { id: 441, name: D5.1Q 5.1.3.0 DRIVE 5.1 QNX SDK DRIVE OS }
2019-08-14 11:45:40.376 - info: Retrieving Data…
2019-08-14 11:45:40.376 - info: Processing Data…
2019-08-14 11:45:40.400 - info: Loading data from server: l1url. Url: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-08-14 11:45:40.526 - info: sdkml1_repo.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json has been downloaded to /home/ryanuz25n/.nvsdkm/dist successfully.
2019-08-14 11:45:40.675 - info: sdkml2_drive_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/Linux/sdkml2_drive_linux.json has been downloaded to /home/ryanuz25n/.nvsdkm/dist successfully.
2019-08-14 11:45:40.789 - info: validating product line for target OS: Linux
2019-08-14 11:45:40.789 - info: 
2019-08-14 11:45:40.789 - info: 	validating release: DRIVE Software 9.0
2019-08-14 11:45:40.789 - warn: 		No access to pid group id -1
2019-08-14 11:45:40.789 - warn: 	No access to release DRIVE Software 9.0. 
2019-08-14 11:45:40.789 - info: 
2019-08-14 11:45:40.789 - info: 	validating release: DRIVE Software 8.0
2019-08-14 11:45:40.789 - warn: 		No access to pid group id -1
2019-08-14 11:45:40.789 - warn: 	No access to release DRIVE Software 8.0. 
2019-08-14 11:45:40.789 - info: 
2019-08-14 11:45:40.789 - info: 	validating release: DRIVE Software 8.0
2019-08-14 11:45:40.790 - warn: 		No access to pid group id 471
2019-08-14 11:45:40.790 - warn: 	No access to release DRIVE Software 8.0. 
2019-08-14 11:45:40.790 - info: 
2019-08-14 11:45:40.790 - info: 	validating release: DRIVE OS 5.1.6.0 PDK
2019-08-14 11:45:40.790 - warn: 		No access to pid group id 521
2019-08-14 11:45:40.790 - warn: 	No access to release DRIVE OS 5.1.6.0 PDK. 
2019-08-14 11:45:40.790 - info: 
2019-08-14 11:45:40.790 - info: 	validating release: DRIVE OS 5.1.6.0 SDK
2019-08-14 11:45:40.790 - warn: 		No access to pid group id 522
2019-08-14 11:45:40.790 - warn: 	No access to release DRIVE OS 5.1.6.0 SDK. 
2019-08-14 11:45:40.790 - info: 
2019-08-14 11:45:40.790 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-08-14 11:45:40.790 - warn: 		No access to pid group id 445
2019-08-14 11:45:40.790 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. 
2019-08-14 11:45:40.790 - info: 
2019-08-14 11:45:40.790 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-08-14 11:45:40.790 - warn: 		No access to pid group id 446
2019-08-14 11:45:40.790 - warn: 	No access to release DRIVE OS 5.1.3.0 SDK. 
2019-08-14 11:45:40.790 - info: 
2019-08-14 11:45:40.790 - info: 	validating release: DRIVE OS 5.1.0.0 PDK
2019-08-14 11:45:40.790 - info: 		Can access to pid group id 412
2019-08-14 11:45:40.790 - info: 
2019-08-14 11:45:40.790 - info: 	validating release: DRIVE OS 5.1.0.0 SDK
2019-08-14 11:45:40.790 - warn: 		No access to pid group id 415
2019-08-14 11:45:40.790 - warn: 	No access to release DRIVE OS 5.1.0.0 SDK. 
2019-08-14 11:45:40.790 - info: 
2019-08-14 11:45:40.790 - info: 	validating release: DRIVE OS 5.0.10.3 SDK with DriveWorks
2019-08-14 11:45:40.790 - warn: 		No access to pid group id -1
2019-08-14 11:45:40.791 - warn: 	No access to release DRIVE OS 5.0.10.3 SDK with DriveWorks. 
2019-08-14 11:45:40.791 - info: 
2019-08-14 11:45:40.791 - info: 	validating release: DRIVE OS 5.0.10.3 PDK
2019-08-14 11:45:40.791 - warn: 		No access to pid group id 356
2019-08-14 11:45:40.791 - warn: 	No access to release DRIVE OS 5.0.10.3 PDK. 
2019-08-14 11:45:40.794 - info: sdkml2_jetson_linux.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/Jetson/Linux/sdkml2_jetson_linux.json has been downloaded to /home/ryanuz25n/.nvsdkm/dist successfully.
2019-08-14 11:45:40.840 - info: validating product line for target OS: Linux
2019-08-14 11:45:40.840 - info: 
2019-08-14 11:45:40.840 - info: 	validating release: JetPack 4.2.1
2019-08-14 11:45:40.840 - warn: 		No access to pid group id -1
2019-08-14 11:45:40.840 - warn: 	No access to release JetPack 4.2.1. 
2019-08-14 11:45:40.840 - info: 
2019-08-14 11:45:40.840 - info: 	validating release: JetPack 4.2
2019-08-14 11:45:40.841 - warn: 		No access to pid group id -1
2019-08-14 11:45:40.841 - warn: 	No access to release JetPack 4.2. 
2019-08-14 11:45:40.842 - 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/ryanuz25n/.nvsdkm/dist successfully.
2019-08-14 11:45:40.863 - info: validating product line for target OS: 
2019-08-14 11:45:40.864 - info: 
2019-08-14 11:45:40.864 - info: 	validating release: SDK Manager
2019-08-14 11:45:40.864 - warn: 		Empty pid group id, need to validate l3 url
2019-08-14 11:45:40.864 - info: 			Validate l3 url successfully
2019-08-14 11:45:40.911 - info: sdkml2_drive_qnx.json from https://developer.download.nvidia.com/sdkmanager/sdkm-config/DRIVE/QNX/sdkml2_drive_qnx.json has been downloaded to /home/ryanuz25n/.nvsdkm/dist successfully.
2019-08-14 11:45:40.980 - info: validating product line for target OS: QNX
2019-08-14 11:45:40.980 - info: 
2019-08-14 11:45:40.980 - info: 	validating release: DRIVE OS 5.1.6.0 PDK
2019-08-14 11:45:40.980 - warn: 		No access to pid group id 524
2019-08-14 11:45:40.980 - warn: 	No access to release DRIVE OS 5.1.6.0 PDK. 
2019-08-14 11:45:40.980 - info: 
2019-08-14 11:45:40.980 - info: 	validating release: DRIVE OS 5.1.6.0 SDK
2019-08-14 11:45:40.980 - warn: 		No access to pid group id 525
2019-08-14 11:45:40.980 - warn: 	No access to release DRIVE OS 5.1.6.0 SDK. 
2019-08-14 11:45:40.980 - info: 
2019-08-14 11:45:40.980 - info: 	validating release: DRIVE OS 5.1.3.0 PDK
2019-08-14 11:45:40.981 - warn: 		No access to pid group id 442
2019-08-14 11:45:40.981 - warn: 	No access to release DRIVE OS 5.1.3.0 PDK. 
2019-08-14 11:45:40.981 - info: 
2019-08-14 11:45:40.981 - info: 	validating release: DRIVE OS 5.1.3.0 SDK
2019-08-14 11:45:40.981 - info: 		Can access to pid group id 441
2019-08-14 11:45:40.981 - info: 
2019-08-14 11:45:40.981 - info: 	validating release: DRIVE OS 5.0.13.2 (with DRIVE AV)
2019-08-14 11:45:40.981 - warn: 		No access to pid group id 428
2019-08-14 11:45:40.981 - warn: 	No access to release DRIVE OS 5.0.13.2 (with DRIVE AV). 
2019-08-14 11:45:40.982 - info: step1 load in ms: 582.4349999995902
2019-08-14 11:45:40.982 - info: Web server configuration build version 570D165J is set
2019-08-14 11:45:40.996 - info: Checking for update with mainRepoURL: https://developer.download.nvidia.com/sdkmanager/sdkm-config/main/sdkml1_repo.json
2019-08-14 11:45:40.996 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.json
2019-08-14 11:45:41.028 - info: [updater] no SDK Manager client update available.
2019-08-14 11:48:37.901 - info: cleaning up engine
2019-08-14 11:48:37.901 - info: installManager cleanup
2019-08-14 11:48:37.902 - info: cleanning up the downloader
2019-08-14 11:48:37.930 - info: download service terminated due to receipt of signal SIGTERM with code: null

I notice that I should have access to ID 441 under the QNX group, and the log says “Can access to pid group id 441”. However, SDKmanager still insists that Linux and QNX are “Not supported on Ubuntu16.04”.

Dear ryanuz25n,

Thank you for your update, I would like to understand:

  1. What is the exactly screen shot the user gets on Step 01? - Maybe you can still see the bundle QNX “Drive OS 5.1.3.0 SDK” and Linux “Drive OS 5.1.0.0 PDK” from the dropdown list.
  2. What is the command output of ‘lsb_release -a’?
  3. Package ~/.nvsdkm/ folder and send to analyze.

If you have a place where you can share attachments, such as Google drivers, could you please upload your data I requested there like Google Driver and share the link? Thanks.