Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Installing the NPU Driver and Firmware

Updated on 2022-07-12 GMT+08:00

Prerequisites

Preparations for the installation have been made by referring to Preparations for Installation.

Procedure

Install a driver and then the firmware. The procedures for installing a driver and firmware are the same. Replace the asterisk (*) with an actual package name in commands.

  1. Log in to the OS as the root user and upload the *.run package to any directory, for example, /opt.
  2. Grant the execute permission on the package to the installation user.

    You can run the ls -l command in the directory where the package is stored to check whether the installation user has the permission to execute the file. If it does not, run the following command to grant the permission:

    chmod +x *.run

  1. Run the following command to check the consistency and integrity of the package:

    ./*.run --check

  1. Install the software package.

If you want to install the software package in a specified directory, for example, /test/HiAI/, run the ./*.run --full --install-path=/test/HiAI/ command.

If you want to install the software package in the default directory, run the ./*.run –full command.

The following uses EulerOS 2.8 as an example to describe how to install a driver. (The method for installing firmware package is the same.) Go to the directory where the software package is stored and run the ./A800-9000-npu-driver_xxx_euleros2.8-aarch64.run --full --install-for-all command. (If the command does not contain --install-for-all, a certificate error may be reported when a non-root user uses the driver.)

NOTE:
  • Drivers can be installed on VMs. Firmware can only be installed on BMSs.
  • If the root user is specified as an execution user, --install-for-all must be contained in the command.
  • Default installation directory: /usr/local/Ascend
  • Installation log directory: /var/log/ascend_seclog/ascend_install.log
  • The installation directory, installation command, and user information are stored in /etc/ascend_install.info after the installation complete.
  1. For a general driver package, if the following information is displayed, DKMS is not installed and the default kernel source code directory /lib/modules/`uname -r`/build does not exist.
[WARNING]rebuild ko has something wrong, detail in /var/log/ascend_seclog/ascend_rebuild.log Do you want to try build driver after input kernel absolute path? [y/n]:

If you want to continue the installation, enter y.

When the following information is displayed, enter the path of the kernel source code, for example, /lib/modules/`uname -r`/build-bak.

Please input your kernel absolute path:

Press Enter to continue with the installation.

NOTE:
  • If DKMS and related components such as kernel-header and kernel-devel have been installed, the system will automatically compile driver source code and install the driver.
  • If DKMS is not installed but the default kernel source code directory /lib/modules/`uname -r`/build exists, the kernel will be automatically used for driver compilation.
  1. If information similar to the following is displayed, the installation is successful:
    • Driver: Driver package install success! Reboot needed for installation/upgrade to take effect!
    • Firmware: Firmware package install success! Reboot needed for installation/upgrade to take effect!
  2. Restart the OS.
  3. Check the driver version.

In the software package installation directory, for example, the default directory of the root user /usr/local/Ascend/${package_name}, run the following command to check the driver version:

cat version.info

Version=1.73.T105.0.B050
  1. Check the firmware version.

/usr/local/Ascend/driver/tools/upgrade-tool --device_index -1 --component -1 --version

Get component version(1.73.5.0.b050) succeed for deviceId(0), componentType(0).          {"device_id":0, "component":nve, "version":1.73.5.0.b050}  Get component version(1.73.5.0.b050) succeed for deviceId(0), componentType(3).          {"device_id":0, "component":uefi, "version":1.73.5.0.b050}  Get component version(1.73.5.0.b050) succeed for deviceId(0), componentType(8).          {"device_id":0, "component":imu, "version":1.73.5.0.b050}  Get component version(1.73.105.0.b050) succeed for deviceId(0), componentType(9).          {"device_id":0, "component":imp, "version":1.73.105.0.b050}
  1. Run the npu-smi info command to check whether the npu-smi tool is successfully installed.

The tool is installed successfully if the following information is displayed. Otherwise, the installation fails. Contact technical support.

NOTE:

Important Notes

  • Logs are recorded based on the system time. NPU synchronizes the system time. To change the system time, run the date command.

    For example, to set the system time to 17:55:55, run the date -s 17:55:55 command.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback