Release Notes#

NVIDIA SDK Manager 26.1#

What’s New#

  • SDK Manager now honors the company’s custom root certificate in corporate proxy and SSL inspection environments.

  • Component conflict rules are now enforced automatically, preventing incompatible SDK components from being selected together during installation

  • Large downloads now resume more reliably on slow or unstable network connections.

  • Added a pre-check for known conflicting repositories before Jetson installation begins.

  • Improved reliability of System Upgrade and flashing on Jetson Thor.

  • SDK Manager now shows target storage information on the post-flash confirmation dialog, making it easier to verify your intended device.

  • Other bug fixes and stability improvements.

Known Issues#

  • Some SDK components can have conflicts that cause an installation error when another release is already installed. If this occurs, uninstall the previously installed SDK, then install the new version.

  • If the CUDA installation fails, run sudo apt purge for all installed CUDA and nvcc related packages, then run SDK Manager again.

  • SDK Manager supports installation on Network File System (NFS) with ext4 type. Installations on NFS with other filesystem types are not supported, and may result in errors.

Jetson Users

  • When installing JetPack SDK using the SDK Manager Docker image, you should first install qemu-user-static and binfmt-support on your host machine, then run the following command on your host machine:

    sudo update-binfmts --enable
    

    Without these steps, you get the following error during installation from the File System and OS component:

    'dpkg': Exec format error
    
  • When flashing JetPack 4.x, ensure that no more than one target hardware is in recovery mode.

  • When installing Jetson SDK components on multiple Jetson boards at once, all active boards must be connected to the Internet using an Ethernet cable.

  • When flashing to a USB flash drive on Jetson Developer Kits for Orin and Xavier modules, a minimum of 256GB space is required on the flash drive.

  • When flashing to a Jetson device with automatic flashing in CLI mode, if a USB 3.x port is used, the first try may cause a connection issue. To continue, retry a few times.

Holopack SDK (Holoscan Product) Users

When flashing Jetson Orin Developer Kits, sometimes SDK Manager fails with the following error:

timeout in USB write

To resolve this issue, switch the USB cable, use a different USB port, or reboot the device.

RAPIDS Users

  • Review the RAPIDS known issues.

  • In some situations, if you use a response file to install RAPIDS, you can later inadvertently install a broken RAPIDS installation if you use a different installation method (e.g., PIP –> Conda) than the installation method you originally used (e.g., PIP –> PIP). Avoid using a response file and instead use the GUI or CLI methods if this is a possibility for you or your organization.