Drivers › Hard Disk Controller. Hard Disk Controller. Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0. NVIDIA MCP61 Serial ATA. Hard Disk Drivers free download - Flobo Hard Disk Repair, Western Digital Disk Manager Drivers, Disk Drill, and many more programs.

If your RAID disks are not recognized by the Lazesoft WinPE boot disk, you need to load the proper RAID driver files for your RAID controller.

Here are the steps to load RAID controller driver files from Lazesoft WinPE boot disk:

1. Find RAID controller driver of your computer for Windows Server 2008 R2. (If you do not know how to or cannot find Windows Server 2008 R2 driver for your RAID controller, please feel free to contact us at support@lazesoft.com.
2. Download the driver files package or setup file. And then extract the driver files.
3. Install the new, downloaded version of the Lazesoft Recovery Suite.
4. Launch the Lazesoft Recovery Suite.
5. Click <Burn CD/USB Disk> on the home page of Lazesoft Recovery Suite
6. Click <Options> on the welcome page of the Lazesoft Media Builder.
7. Enable the option <Specify WinPE Version> and select <Windows 7 64 bit PE> (Windows 7 64 bit has same core with Windows 2008 R2).
8. Click <OK> to save the options.
9. Follow the Lazesoft Media Builder ‘wizard’ to create a WinPE boot disk.
10. Copy the extracted the RAID controller driver files folder to a USB disk.
11. Insert the USB Disk into your locked/target computer.
12. Reboot your locked/target computer from the new burned Lazesoft WinPE boot disk
13. On the home page of Lazesoft Recovery Suite boot disk, click <Load Drivers>, after boot disk is loaded.
14. Load the driver file, *.inf, from the the extracted the RAID controller driver files folder.

If you do not know how to find and load your RAID drivers, please contact our technical staff with your computer brand name/model number and RAID controller brand name/model number. We will help you find the proper driver files, then reply with detailed steps to download and load RAID drivers.

• SOLUTIONS
  • DRIVE AV

This page provides access to software for developers using NVIDIA DRIVE™ AGX, DRIVE Hyperion and DRIVE PX 2 Developer Kits.

Developers using DRIVE AGX Developer Kits may choose between:

• DRIVE OS 5.2.0 and DriveWorks 3.5 which includes more recent versions of CUDA and TensorRT. DRIVE OS and DriveWorks include the DRIVE OS and DriveWorks modules per diagram above.
• DRIVE Software 10.0 which is intended for Hyperion Developers. DRIVE Software includes the DRIVE OS, DriveWorks, DRIVE IX and DRIVE AV modules above.
Please carefully choose the release that best meets your development needs.

Developers using DRIVE PX 2 Developer Kits have access to the legacy DRIVE OS 5.0 software.

See Automotive Software for more details.

Requires membership to the NVIDIA DRIVE Developer Program for DRIVE AGX

Here’s what you need to know to update to DRIVE OS Linux 5.2.0:

• Software is supported on the DRIVE AGX hardware:
  • NVIDIA DRIVE AGX Pegasus™
  • NVIDIA DRIVE AGX Xavier™
• You must have DRIVE Software 10.0 or DRIVE OS 5.1.15 (from NVONLINE) flashed on your target DRIVE AGX System. Once updated to DRIVE OS 5.2.0, you may only downgrade to DRIVE OS 5.1.15 or DRIVE Software 10.0 with specified caveats, please see DRIVE OS Installation Guide for more info.
• Install the most up to date version of the NVIDIA SDK Manager
  

  PLEASE NOTE: The NVIDIA Developer latest login and authentication system has been updated. The steps to login to the DRIVE Developer Programs when using SDK Manager have changed. Please see the SDK Manager User Guide for more details.

• Documentation is publicly available at https://docs.nvidia.com/drive/, under NVIDIA DRIVE™ OS and DriveWorks for DRIVE AGX.


• After updating your software, be sure to review DRIVE OS 5.2.0 Installation Guide, Section 1.4 on how to Finalize your DRIVE AGX System Setup

Please Note: DriveWorks 3.5 is only compatible with DRIVE OS 5.2.0. Please install/flash DRIVE OS 5.2.0 (available above) before downloading and installing DriveWorks 3.5. To clarify, DriveWorks 3.5 will not work with DRIVE Software 9.0 or 10.0.

Here’s what you need to know to install DriveWorks 3.5 after you have updated to DRIVE OS 5.2.0:

• DriveWorks 3.5 must be installed on top of DRIVE OS 5.2.0.
• DriveWorks 3.5 SDK Reference Documentation is also available at https://docs.nvidia.com/drive/, under NVIDIA DRIVE™ OS and DriveWorks for DRIVE AGX.

• Download the DriveWorks 3.5 packages
  DriveWorks 3.5 for Host PC .tar DriveWorks 3.5 for DRIVE AGX .tar

Support:

For support, please post any queries or issues to the DRIVE Developer Forum.

Requires membership to the NVIDIA DRIVE Developer Program for DRIVE AGX

Please Note: DRIVE Software 10.0 includes DRIVE OS 5.1.6.1 and DriveWorks 2.2, DRIVE IX and DRIVE AV. We recommend you develop using the latest DRIVE OS and DriveWorks available above. DRIVE Hyperion developers should continue to use DRIVE Software.

Here’s what you need to know to update to DRIVE Software 10.0:

• Software is supported on the following hardware:
• You must have DRIVE Software 9.0 (available below) or DRIVE OS 5.1.6 (from NVONLINE) flashed on your target DRIVE AGX System. Please see DRIVE Software Installation Guide and DRIVE AGX Developer Kit Flashing Technical Bulletin for DRIVE Software 10.0 for more info.
• Install the most up to date version of the NVIDIA SDK Manager.
  NVIDIA SDK Manager
  

  PLEASE NOTE: The NVIDIA Developer latest login and authentication system has been updated. The steps to log in to the DRIVE Developer Programs when using SDK Manager have changed. Please see the SDK Manager User Guide for more details.

• Documentation is available at DRIVE Documentation and https://docs.nvidia.com/drive/, under NVIDIA DRIVE™ Software for DRIVE AGX.

Open Source:

DRIVE OS Open-Source Package installed by SDK Manager

Support:

For support, please post any queries or issues to the DRIVE Developer Forum.

Requires membership to the NVIDIA DRIVE Developer Program for DRIVE AGX

Supported Hardware:

• NVIDIA DRIVE AGX Pegasus™
• NVIDIA DRIVE AGX Xavier™

Includes:

• CUDA
• TensorRT
• cuDNN

Nvidia Hard Disk Controller Drivers

• Sensor Abstraction
• Recorder
• Image/Point Cloud Processing

• Driver Monitoring System
• DRIVE Hub

System requirements for the host machine

• Software:
  • Ubuntu Linux 16.04 LTS x86_64
  • X11 enabled on the host system
• Hardware:
  • Memory: 8GB of RAM
  • Hard disk: 120 GB of free disk space for the complete host and target deployed SDK version.
  • Graphics card: NVIDIA Pascal (or newer) GPU (required only for running the sample applications on the host machine).
  • A working Internet connection.

If you plan to run your sample applications on your development workstation, please ensure your system includes an NVIDIA Pascal based (or newer) GPU and that the latest NVIDIA GPU graphics driver is installed.

Setting up the development environment for DRIVE Software and DRIVE OS

1. REVIEW DOCUMENTATION

• DRIVE AGX Developer Kit Flashing Technical Bulletin for DRIVE software 9.0 (PDF) (05/23/19)

2. DOWNLOAD

3. UPDATE the PCIe SWITCH FIRMWARE

Before upgrading to a new release please verify and update the PCIe switch firmware on your DRIVE AGX System before proceeding. Refer to the documentation to identify your current firmware, if different from 0x40014001, download the restricted-pdk.run utility and follow the upgrade procedure.

4. INSTALL

From a terminal window, install the Debian package with the command: sudo apt install ./sdkmanager_0.9.12-4180_amd64.deb

5. LAUNCH

From a terminal window, launch SDK Manager with the command: sdkmanager

Nvidia Hard Disk Controller Driver

6. LOGIN & SETUP

• From the SDK Manager launch screen, select the login tab for DEVELOPER ZONE | developer.nvidia.com.
• Enter the same credentials used to access the DRIVE Platform Download Center, and click Login.
• Select the Software version you would like to install and follow the steps to complete the installation.

Requires membership to the NVIDIA DRIVE Developer Program for DRIVE PX 2

Includes:

• CUDA
• TensorRT
• cuDNN

• Sensor Abstraction
• Recorder
• Image/Point Cloud Processing

System requirements for the development workstation

• Software:
  • Ubuntu Linux 16.04 LTS x86_64
  • X11 enabled on the host system
• Hardware:
  • Memory: 8GB of RAM
  • Hard disk: 120 GB of free disk space for the complete host and target deployed SDK version.
  • Graphics card: NVIDIA Pascal (or newer) GPU (required only for running the sample applications on the host machine).
  • A working Internet connection.

If you plan to run your sample applications on your development workstation, please ensure your system includes an NVIDIA Pascal based (or newer) GPU and that the latest NVIDIA GPU graphics driver is installed.

Setting up the development environment for DRIVE Software and DRIVE OS

1. REVIEW DOCUMENTATION

NOTE: For the most up to date documentation please refer to the documentation page as these are more frequently updated than the ones installed through the SDK Manager.

2. DOWNLOAD

NVIDIA SDK Manager


3. INSTALL

From a terminal window, install the Debian package with the command: sudo apt install ./sdkmanager_0.9.12-4180_amd64.deb

4. LAUNCH

From a terminal window, launch SDK Manager with the command: sdkmanager

5. LOGIN & SETUP

• From the SDK Manager launch screen, select the login tab for DEVELOPER ZONE | developer.nvidia.com.
• Enter the same credentials used to access the DRIVE Platform Download Center, and click Login.
• Select the Software version you would like to install and follow the steps to complete the installation.

Additional Resources

• Automotive Software uses third-party software
• DriveWorks uses third-party software
• SDK Manager uses open-source software

NVIDIA’s platforms and application frameworks enable developers to build a wide array of AI applications. Consider potential algorithmic bias when choosing or creating the models being deployed. Work with the model’s developer to ensure that it meets the requirements for the relevant industry and use case; that the necessary instruction and documentation are provided to understand error rates, confidence intervals, and results; and that the model is being used under the conditions and in the manner intended.