DGX A100 System Firmware Update Container Release Notes

This document describes the key features, software enhancements and improvements, and known issues for the NVIDIA DGX A100 System Firmware Update Container.

1. DGX A100 System FW Update Container Overview

The NVIDIA DGXTM A100 System Firmware Update container is the preferred method for updating firmware on DGX A100 system. It provides an easy method for updating the firmware to the latest released versions, and uses the standard method for running Docker containers.

This document describes firmware components that can be updated, any known issues, and how to run this container.

Features

  • Automates firmware (FW) update for DGX A100 system firmware, such as the system BIOS and BMC.
  • Provides flexibility to update individual or all FW components
  • Embeds the following

    • Qualified FW binaries for supported components

    • Flash update utilities and supporting dependencies

    • Manifest file which lists

      • Target platform and firmware version numbers

      • Sequence in which FW update should be applied

      • “On-Error” policy for every FW component

  • Supports interactive and non-interactive firmware update

2. Using the DGX A100 FW Update Utility

The NVIDIA DGXTM A100 System Firmware Update utility is provided in a tar ball file and also as a .run file. Copy the files to the DGX A100 system, then update the firmware using one of the following three methods:
  • NVSM provides convenient commands to update the firmware using the firmware update container.
  • Using Docker to run the firmware update containere
  • Using the .run file

Using NVSM

The NVIDIA DGX A100 system software includes Docker software required to run the container.

  1. Copy the tar ball to a location on the DGX system.
  2. From the directory where you copied the tarball file, enter the following command to load the container image. 
    $ sudo docker load -i nvfw-dgxa100_20.05.12.3_200716.tar.gz
  3. To verify that the container image is loaded, enter the following. 
    $ sudo docker images 

REPOSITORY   TAG 
nvfw-dgxa100 20.05.12.3
  4. Using NVSM interactive mode, enter the firmware update module.
    $ sudo nvsm
nvsm-> cd systems/localhost/firmware/install
  5. Set the flags corresponding to the action you want to take. 
    $ nvsm(/system/localhost/firmware/install)-> set Flags=<option>

    See the Commands/Argument Summary section below for the list of common flags.

  6. Run the command. 
    $ nvsm(/system/localhost/firmware/install)-> start

Using the Tar Ball File

The NVIDIA DGX A100 system software includes Docker software required to run the container.

  1. Copy the tar ball to a location on the DGX system.
  2. From the directory where you copied the tarball file, enter the following command to load the container image. 
    $ sudo docker load -i nvfw-dgxa100_20.05.12.3_200716.tar.gz
  3. To verify that the container image is loaded, enter the following. 
    $ sudo docker images 

REPOSITORY   TAG 
nvfw-dgxa100 20.05.12.3
  4. Use the following syntax to run the container image.
    $ sudo docker run --rm --privileged -ti -v /:/hostfs nvfw-dgxa100:20.05.12.3 <command> <[arg1] [arg2] ... [argn]
See the Commands/Argument Summary section below for the list of common commands and argument.

Using the .run File

The update container is also available as a run file that does not require a Docker installation.

After obtaining the .run file, make the file executible.
$ chmod +x nvfw-dgxa100_20.05.12.3_200716.run

Use the following syntax to run the container image. 

$ sudo nvfw-dgxa100_20.05.12.3_200716.run <command> <[arg1] [arg2] ... [argn]
See the Commands section below for the list of common commands and arguments.

Command/Argument Summary

The following are the common commands and arguments to use.
  • Show the manufest
    show_fw_manifest
  • Show version information
    show_version
  • Check the onboard firmware against the manifest and update all down-level firmware.
    update_fw all
  • Check the specified onboard firmware against the manifest and update if down-level.
    update_fw [fw]
    Where [fw] corresponds to the specific firmware as listed in the manifest. Multiple components can be listed within the same command.
CAUTION:
Stop all unnecessary system activities before attempting to update firmware, and do not add additional processing loads while an update is in progress. A high workload can disrupt the firmware update process and result in an incapacitated component.

When initiating an update, the update software assists in determining the activity state of the DGX system and provides a warning if it detects that activity levels are above a predetermined threshold. If the warning is encountered, you are strongly advised to take action to reduce the workload before proceeding with the update.

Fan speeds may increase while updating the BMC firmware. This is a normal part of the BMC firmware update process.

3. DGX A100 System Firmware Update Container Version 20.05.12.3

The DGX Firmware Update container version 20.05.12.3 is available.

  • Package name:nvfw-dgxa100_20.05.12.3_200716.tar.gz
  • Run file name: nvfw-dgxa100_20.05.12.3_200716.run
  • Image name: nvfw-dgxa100:20.05.12.3

Highlights and Changes in this Release

  • This release is supported with the following DGX OS software -
    • DGX OS 4.99.9 or later
  • Fixed an issue where the DGX A100 fans would run at high speed when the optional dual-port network card was not installed.

Contents of the DGX A100 System Firmware Container

This container includes the firmware binaries and update utilities for the firmware listed in the following table.

Component Version Key Changes Update Time
BMC (via CEC) 00.12.06 Fixed high fan speed bug. 31 minutes
SBIOS 0.25 No change 7 minutes
Broadcom 88096 PCIe switch board 1.3 No change 8 minutes
BMC CEC SPI v3.05 No change 8 minutes
PEX88064 Retimer 0.1.13 No change 7 minutes
PEX88080 Retimer 0.1.13 No change 7 minutes
NvSwitch BIOS 92.10.12.00.01 No change 8 minutes
VBIOS 92.00.19.00.01 No change 7 minutes

Updating Components with Secondary Images

Some firmware components provide a secondary image as backup. The following is the policy when updating those components:
  • SBIOS: The two images are referred to as active and inactive, where the active is the currenly running image and the inactive is the backup image. The update container can only update the inactive image. After reboot, the updated image becomes the active image. You can perform the update again to update the current inactive image so that both images are updated.
  • BMC: The two images are referred to as active and inactive, where the active is the currenly running image and the inactive is the backup image. The update container can only update the inactive image. After the update is completed, the updated image becomes the active image. You can perform the update again to update the current inactive image so that both images are updated.

3.1. Instructions for Updating Firmware

This section provides a simple way to update the firmware on the system using the firmware update container. It includes instructions for performing a transitional update for systems that require it. The commands use the .run file, but you can also use the container image directly.
  1. Perform a transitional update if needed.

    Depending on the BMC and MB_CEC versions on the system, you may need to perform a transitional update before updating the BMC and SBIOS to the latest versions.

    1. Check if the transitional update is needed.
      $ sudo nvfw-dgxa100_20.05.12.3_200716.run run_script --command "fw_transition.py show_version"

      The following message appears if a transition update is needed.

      BMC/MB_CEC firmware needs update to Active/Inactive, secure boot mode 
This is a one-time update required for DGXA100. All future updates require BMC in this mode
      • If the one-time update is required, continue with the next step to perform the transitional update.
      • If the one-time update is not required, then skip to step 2.
    2. Perform the transitional update.
      $ sudo nvfw-dgxa100_20.05.12.3_200716.run run_script --command "fw_transition.py update_fw" 
$ sudo reboot
    3. Verify that BMC (both images) and the MB_CEC are up to date.
      $ sudo nvfw-dgxa100_20.05.12.3_200716.run run_script --command "fw_transition.py show_version"
  2. Check if other updates are needed.
    $ sudo nvfw-dgxa100_20.05.12.3_200716.run show_version
    • If there is "no" in any up-to-date column for updatable firmware, then continue with the next step.
    • If all up-to-date column entries are "yes", then no updates are needed and no further action is necessary.
  3. Perform the final update for all firmware supported by the container and reboot the system. 
    $ sudo nvfw-dgxa100_20.05.12.3_200716.run update_fw all

$ sudo reboot
    Note: The update_fw all command updates the inactive BMC and SBIOS images only. After rebooting the system, the updated images become "active". You can then update the inactive images using nvfw-dgxa100_20.05.12.3_200716.run update_fw [BMC] [SBIOS] --inactive as needed.
You can verify the update by issuing the following. 
$ sudo nvfw-dgxa100_20.05.12.3_200716.run show_version

Expected output.

 BMC DGX 
=========
Image Id             Status  Location  Onboard Version  Manifest   up_to_date
0:Active   Boot      Online   Local     00.12.06        00.12.06         yes
1:Inactive Updatable          Local     00.12.06        00.12.06         yes

  CEC
============
                                     Onboard Version   Manifest    up-to-date      
MB_CEC(enabled)                       3.05              3.05             yes         
 
 SBIOS
=======
Image Id                   Method    Onboard Version   Manifest    up_to_date   
0:Inactive Updatabl        afulnx     0.25              0.25             yes       
1:Active   Boot                       0.25              0.25             yes       
 
 Video BIOS
============
Bus            Model                 Onboard Version    Manifest    up-to-date
0000:07:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:0f:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:47:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:4e:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:87:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:90:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:b7:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:bd:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes

  Switches
============
PCI Bus#                  Model       Onboard Version   Manifest     up-to-date
DGX - 0000:91:00.0(U261)  88064_Retimer  0.13.0          0.13.0            yes
DGX - 0000:88:00.0(U260)  88064_Retimer  0.13.0          0.13.0            yes
DGX - 0000:4f:00.0(U262)  88064_Retimer  0.13.0          0.13.0            yes

DGX - 0000:48:00.0(U225)  88080_Retimer  0.13.0          0.13.0            yes

DGX - 0000:c4:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c5:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c2:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c6:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c3:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c7:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes

DGX - 0000:01:00.0(U1)    PEX88096        1.3               1.3            yes
DGX - 0000:81:00.0(U3)    PEX88096        1.3               1.3            yes
DGX - 0000:41:00.0(U2)    PEX88096        1.3               1.3            yes
DGX - 0000:b1:00.0(U4)    PEX88096        1.3               1.3            yes

4. DGX A100 System Firmware Update Container Version 20.05.12.2

The DGX Firmware Update container version 20.05.12.2 is available.

  • Package name:nvfw-dgxa100_20.05.12.2_200630.tar.gz
  • Run file name: nvfw-dgxa100_20.05.12.2_200630.run
  • Image name: nvfw-dgxa100:20.05.12.2

Highlights and Changes in this Release

  • This release is supported with the following DGX OS software -
    • DGX OS 4.99.9 or later
  • Restored ability to view hidden options in the SBIOS setup screens.

Contents of the DGX A100 System Firmware Container

This container includes the firmware binaries and update utilities for the firmware listed in the following table.

Component Version Key Changes Update Time
BMC (via CEC) 00.12.05 No change. 31 minutes
SBIOS 0.25
  • Restored Hidden Options
7 minutes
Broadcom 88096 PCIe switch board 1.3 No change 8 minutes
BMC CEC SPI v3.05 No change 8 minutes
PEX88064 Retimer 0.1.13 No change 7 minutes
PEX88080 Retimer 0.1.13 No change 7 minutes
NvSwitch BIOS 92.10.12.00.01 No change 8 minutes
VBIOS 92.00.19.00.01 No change 7 minutes

Updating Components with Secondary Images

Some firmware components provide a secondary image as backup. The following is the policy when updating those components:
  • SBIOS: The two images are referred to as active and inactive, where the active is the currenly running image and the inactive is the backup image. The update container can only update the inactive image. After reboot, the updated image becomes the active image. You can perform the update again to update the current inactive image so that both images are updated.
  • BMC: The two images are referred to as active and inactive, where the active is the currenly running image and the inactive is the backup image. The update container can only update the inactive image. After the update is completed, the updated image becomes the active image. You can perform the update again to update the current inactive image so that both images are updated.

Instructions for Updating Firmware

This section provides a simple way to update the firmware on the system using the firmware update container. It includes instructions for performing a transitional update for systems that require it. The commands use the .run file, but you can also use the container image directly.
  1. Perform a transitional update if needed.

    Depending on the BMC and MB_CEC versions on the system, you may need to perform a transitional update before updating the BMC and SBIOS to the latest versions.

    1. Check if the transitional update is needed.
      $ sudo nvfw-dgxa100_20.05.12.2_200630.run run_script --command "fw_transition.py show_version"

      The following message appears if a transition update is needed.

      BMC/MB_CEC firmware needs update to Active/Inactive, secure boot mode 
This is a one-time update required for DGXA100. All future updates require BMC in this mode
      • If the one-time update is required, continue with the next step to perform the transitional update.
      • If the one-time update is not required, then skip to step 2.
    2. Perform the transitional update.
      $ sudo nvfw-dgxa100_20.05.12.2_200630.run run_script --command "fw_transition.py update_fw" 
$ sudo reboot
    3. Verify that BMC (both images) and the MB_CEC are up to date.
      $ sudo nvfw-dgxa100_20.05.12.2_200630.run run_script --command "fw_transition.py show_version"
  2. Check if other updates are needed.
    $ sudo nvfw-dgxa100_20.05.12.2_200630.run show_version
    • If there is "no" in any up-to-date column for updatable firmware, then continue with the next step.
    • If all up-to-date column entries are "yes", then no updates are needed and no further action is necessary.
  3. Perform the final update for all firmware supported by the container and reboot the system. 
    $ sudo nvfw-dgxa100_20.05.12.2_200630.run update_fw all

$ sudo reboot
    Note: The update_fw all command updates the inactive BMC and SBIOS images only. After rebooting the system, the updated images become "active". You can then update the inactive images using nvfw-dgxa100_20.05.12.2_200630.run update_fw [BMC] [SBIOS] --inactive as needed.
You can verify the update by issuing the following. 
$ sudo nvfw-dgxa100_20.05.12.2_200630.run show_version

Expected output.

 BMC DGX 
=========
Image Id             Status  Location  Onboard Version  Manifest   up_to_date
0:Active   Boot      Online   Local     00.12.05        00.12.05         yes
1:Inactive Updatable          Local     00.12.05        00.12.05         yes

  CEC
============
                                     Onboard Version   Manifest    up-to-date      
MB_CEC(enabled)                       3.05              3.05             yes         
 
 SBIOS
=======
Image Id                   Method    Onboard Version   Manifest    up_to_date   
0:Inactive Updatabl        afulnx     0.25              0.25             yes       
1:Active   Boot                       0.25              0.25             yes       
 
 Video BIOS
============
Bus            Model                 Onboard Version    Manifest    up-to-date
0000:07:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:0f:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:47:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:4e:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:87:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:90:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:b7:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:bd:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes

  Switches
============
PCI Bus#                  Model       Onboard Version   Manifest     up-to-date
DGX - 0000:91:00.0(U261)  88064_Retimer  0.13.0          0.13.0            yes
DGX - 0000:88:00.0(U260)  88064_Retimer  0.13.0          0.13.0            yes
DGX - 0000:4f:00.0(U262)  88064_Retimer  0.13.0          0.13.0            yes

DGX - 0000:48:00.0(U225)  88080_Retimer  0.13.0          0.13.0            yes

DGX - 0000:c4:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c5:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c2:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c6:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c3:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c7:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes

DGX - 0000:01:00.0(U1)    PEX88096        1.3               1.3            yes
DGX - 0000:81:00.0(U3)    PEX88096        1.3               1.3            yes
DGX - 0000:41:00.0(U2)    PEX88096        1.3               1.3            yes
DGX - 0000:b1:00.0(U4)    PEX88096        1.3               1.3            yes

5. DGX A100 System Firmware Update Container Version 20.05.12

The DGX Firmware Update container version 20.05.12 is available.

  • Package name:nvfw-dgxa100_20.05.12_200603.tar.gz
  • Run file name: nvfw-dgxa100_20.05.12_200603.run
  • Image name: nvfw-dgxa100:20.05.12

Highlights and Changes in this Release

  • This release is supported with the following DGX OS software -
    • DGX OS 4.99.8 or later
  • Enabled BMC Secure Flash
  • Enabled PCI-Compliant DPC and AER error propagation
  • Implemented critical VBIOS fixes

Contents of the DGX A100 System Firmware Container

This container includes the firmware binaries and update utilities for the firmware listed in the following table.

Component Version Key Changes Update Time
BMC (via CEC) 00.12.05 Added to container.
  • BMC now recognizes the level of CEC installed, and enforces Secure Flash if the CEC supports it.
  • Removed the ability to update the BMC via the UI.
  • Added micro-controller assist (MCA) SEL, downloadable from the UI.
  • Added Logs & Reports > Debug Log > Download Debug log control to BMC UI.
31 minutes
SBIOS 0.23 Added to container
  • Removed Hidden Options and made TPM Configuration options visible
  • Fixed NVSM Show Health Errors related to DIMMs and DIMM population
  • Fixed system getting stuck at POST after enabling and then disabling drive encryption
7 minutes
Broadcom 88096 PCIe switch board 1.3 Added to container
  • Disabled hot-plug and hot-plug surprise capability
8 minutes
BMC CEC SPI v3.05 Added to container 8 minutes
PEX88064 Retimer 0.1.13 Updated 7 minutes
PEX88080 Retimer 0.1.13 Updated 7 minutes
NvSwitch BIOS 92.10.12.00.01 No change 8 minutes
VBIOS 92.00.19.00.01 Updated
  • Fixed Xid 64 (Row Remapper Error)
7 minutes

Updating Components with Secondary Images

Some firmware components provide a secondary image as backup. The following is the policy when updating those components:
  • SBIOS: The two images are referred to as active and inactive, where the active is the currenly running image and the inactive is the backup image. The update container can only update the inactive image. After reboot, the updated image becomes the active image. You can perform the update again to update the current inactive image so that both images are updated.
  • BMC: The two images are referred to as active and inactive, where the active is the currenly running image and the inactive is the backup image. The update container can only update the inactive image. After the update is completed, the updated image becomes the active image. You can perform the update again to update the current inactive image so that both images are updated.

Instructions for Updating Firmware

This section provides a simple way to update the firmware on the system using the firmware update container. It includes instructions for performing a transitional update for systems that require it. The commands use the .run file, but you can also use the container image directly.
  1. Perform a transitional update if needed.

    Depending on the BMC and MB_CEC versions on the system, you may need to perform a transitional update before updating the BMC and SBIOS to the latest versions.

    1. Check if the transitional update is needed.
      $ sudo nvfw-dgxa100_20.05.12_2006003.run run_script --command "fw_transition.py show_version"

      The following message appears if a transition update is needed.

      BMC/MB_CEC firmware needs update to Active/Inactive, secure boot mode 
This is a one-time update required for DGXA100. All future updates require BMC in this mode
      • If the one-time update is required, continue with the next step to perform the transitional update.
      • If the one-time update is not required, then skip to step 2.
    2. Perform the transitional update.
      $ sudo nvfw-dgxa100_20.05.12_2006003.run run_script --command "fw_transition.py update_fw" 
$ sudo reboot
    3. Verify that BMC (both images) and the MB_CEC are up to date.
      $ sudo nvfw-dgxa100_20.05.12_2006003.run run_script --command "fw_transition.py show_version"
  2. Check if other updates are needed.
    $ sudo nvfw-dgxa100_20.05.12_2006003.run show_version
    • If there is "no" in any up-to-date column for updatable firmware, then continue with the next step.
    • If all up-to-date column entries are "yes", then no updates are needed and no further action is necessary.
  3. Perform the final update for all firmware supported by the container and reboot the system. 
    $ sudo nvfw-dgxa100_20.05.12_2006003.run update_fw all

$ sudo reboot
    Note: The update_fw all command updates the inactive BMC and SBIOS images only. After rebooting the system, the updated images become "active". You can then update the inactive images using nvfw-dgxa100_20.05.12_2006003.run update_fw [BMC] [SBIOS] --inactive as needed.
You can verify the update by issuing the following. 
$ sudo nvfw-dgxa100_20.05.12_2006003.run show_version

Expected output.

 BMC DGX 
=========
Image Id             Status  Location  Onboard Version  Manifest   up_to_date
0:Active   Boot      Online   Local     00.12.05        00.12.05         yes
1:Inactive Updatable          Local     00.12.05        00.12.05         yes

  CEC
============
                                     Onboard Version   Manifest    up-to-date      
MB_CEC(enabled)                       3.05              3.05             yes         
 
 SBIOS
=======
Image Id                   Method    Onboard Version   Manifest    up_to_date   
0:Inactive Updatabl        afulnx     0.24              0.24             yes       
1:Active   Boot                       0.24              0.24             yes       
 
 Video BIOS
============
Bus            Model                 Onboard Version    Manifest    up-to-date
0000:07:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:0f:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:47:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:4e:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:87:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:90:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:b7:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes
0000:bd:00.0   A100-SXM4-40GB        92.00.19.00.01     92.00.19.00.01    yes

  Switches
============
PCI Bus#                  Model       Onboard Version   Manifest     up-to-date
DGX - 0000:91:00.0(U261)  88064_Retimer  0.13.0          0.13.0            yes
DGX - 0000:88:00.0(U260)  88064_Retimer  0.13.0          0.13.0            yes
DGX - 0000:4f:00.0(U262)  88064_Retimer  0.13.0          0.13.0            yes

DGX - 0000:48:00.0(U225)  88080_Retimer  0.13.0          0.13.0            yes

DGX - 0000:c4:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c5:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c2:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c6:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c3:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes
DGX - 0000:c7:00.0        LR10        92.10.12.00.01    92.10.12.00.01     yes

DGX - 0000:01:00.0(U1)    PEX88096        1.3               1.3            yes
DGX - 0000:81:00.0(U3)    PEX88096        1.3               1.3            yes
DGX - 0000:41:00.0(U2)    PEX88096        1.3               1.3            yes
DGX - 0000:b1:00.0(U4)    PEX88096        1.3               1.3            yes

Notices

Notice

This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.

NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice.

Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.

NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.

NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk.

NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.

No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.

Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.

THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.

Trademarks

NVIDIA, the NVIDIA logo, DGX, DGX-1, DGX-2, and DGX Station are trademarks and/or registered trademarks of NVIDIA Corporation in the Unites States and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.