Jetson Nano Developer Kit Not Install NVIDIA SDK

Jetson Nano Developer Kit Not Install NVIDIA SDK

sudo apt install ./sdkmanager_1.3.1-7110_amd64.deb
Reading package lists… Done
Building dependency tree
Reading state information… Done
Note, selecting ‘sdkmanager’ instead of ‘./sdkmanager_0.9.11-3405_amd64.deb’
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
sdkmanager : Depends: libgconf-2-4 but it is not installable
Depends: libcanberra-gtk-module but it is not installable
E: Unable to correct problems, you have held broken packages.

Hi @yachanagarg34, the SDK Manager tool is installed to an x86_64 PC (running Ubuntu), and not the Jetson itself. The SDK Manager tool can then flash / install packages to the Jetson over Micro-USB connection from the PC.

However, if you are using Jetson Nano Developer Kit, you can just flash the SD Card image from any PC without needing SDK Manager. The SD Card image already has all the components installed. See here for more info:

Yes, i have installed Jetson Nano Developer Kit SD Card Image (https://developer.nvidia.com/jetson-nano-sd-card-image) and after it i go to second step to install nvidia-sdk , but it shows error … and also how can i check which nvidia driver is presented in it ?

If you want to install something from jetpack, you need to find a ubuntu x86 host to install sdkmanager.

Sdkmanager does not support on device side (jetson).

Please Send me the image link

Actually it is not an "image’, it is a binary tool.

Some clarification might be useful to you, but this is not intended as “an answer”.

  • Until recently there were no SD card Jetson models. All was eMMC.
  • The eMMC models have only one method of installing.
  • The SD card model adds pre-built images to the method of eMMC install.
  • Both models have a base install requiring either recovery mode or a pre-built SD card.
  • The sdkmanager can be used for base install to any recovery mode Jetson.
  • The sdkmanager can add optional packages (such as CUDA) only with a fully booted Jetson which is not in recovery mode. Full Jetson setup must have completed prior to adding optional packages. Those packages are not part of the base install.
  • The sdkmanager is a front end to actual flash software, and is also a network utility when working with optional packages.
  • Sdkmanager can have flash unchecked, and optional packages worked with at any time. Flash is not mandatory if your system already runs.
  • You would never want to install options from sdkmanager for a different release than the version of base install. For example, if sdkmanager flashes R32.4.3, then you could not use the CUDA from the sdkmanager which flashes R32.1.
  • Sdkmanager is also capable of installing development packages on an Ubuntu 18.04 host PC.
  • Sometimes host PC or Jetson (usually PC) may need this to continue:
    • sudo apt update sudo apt --fix-broken install
    • sudo apt-get install libgconf-2-4 libcanberra-gtk-module
  • Earlier Jetson releases simply installed extras/optional packages via file copy into somewhere in “/usr/local/”.
  • More recent releases use the “.dpkg” package format.
  • Package format installs allow installing directly from the Jetson with the “apt-get” method.
  • Extras which were from earlier releases, prior to dpkg being used, could only be installed via sdkmanager.
  • Extras from recent releases can use either sdkmanager or the apt-get mechanism to install extras.

Whenever you see a message such as:

…this is a candidate for:

sudo apt update
sudo apt --fix-broken install
sudo apt-get install libgconf-2-4 libcanberra-gtk-module

…but you have to know whether to run this on host PC or on Jetson. Or perhaps both. You could run it on both and it shouldn’t hurt anything. However, if it fails, you would want to mouse copy and paste the error and post it to the forums to get help on what went wrong with the --fix-broken.