Help Center/ Bare Metal Server/ Private Image Creation Guide/ Linux/ Installing and Upgrading Drivers and Firmware for Ascend BMSs/ Installation and Maintenance/ Preparations for Installation/ Checking the OS and Kernel
Updated on 2022-07-12 GMT+08:00
View PDF
Share

Checking the OS and Kernel

Table 1 and Table 2 list the OSs and kernels required by different driver and firmware packages.

Table 1 OS and kernel versions required by binary driver packages

BMS

OS

Kernel

GCC Version

Atlas 800 9000 (AArch64)

Ubuntu 18.04

4.15.0-45-generic

Note:

If the kernel does not match the OS, install DKMS to compile the driver source code before you install the driver. For details about how to install DKMS, see Driver Source Code Compilation.

7.4.0

Atlas 800 9000 (AArch64)

EulerOS 2.8

4.19.36-vhulk1907.1.0.h475

7.3.0

Atlas 800 9000 (AArch64)

CentOS 7.6

4.14.0-115.el7a.0.1.aarch64

-

Atlas 800 9000 (AArch64)

BC_Linux 7.6

4.19

-
Table 2 OS and kernel versions required by general driver packages

BMS

OS

Kernel

GCC Version

Atlas 800 9000 (AArch64)

CentOS 8.2

4.18.X

Note:

The kernel can be upgraded to 5.6.14.

8.3.1

Atlas 800 9000 (AArch64)

BC_Linux 7.6

4.19

-

Atlas 800 9000 (AArch64)

Kylin OS V10SP1

Note:

Kylin OS V10SP1 is only supported by NPU driver 21.0.rc1 and later versions.

4.19.90-17.ky10.aarch64

8.3.1-4.5

Atlas 800 9000 (AArch64)

BC_Linux 7.7

Note:

BC_Linux 7.7 is only supported by NPU driver 21.0.rc1 and later versions.

4.19.25-203.e17.bclinux.aarch64

4.8.5
  1. Check the OS version.

Run the uname -m && cat /etc/*release command to query the OS version and architecture.

The OS version and architecture must comply with Table 1 or Table 2.

  1. Check general driver packages.
  • Check whether the make tool has been installed. Run the make -v command. If a make tool version is displayed, the make tool has been installed.
  • Ensure that at least either of the following conditions is met.
    • Dependent tools such as DKMS have been installed. For details about how to install DKMS, see Driver Source Code Compilation.
    • The default source code directory (/lib/modules/`uname -r`/build) of the kernel exists. Run the ls /lib/modules/`uname -r`/build command to check whether the directory exists.
      • If it does, the kernel is automatically used to compile the driver.
      • If it does not, you can provide it during driver installation. For details, see 5.
  1. Check the OS kernel version.

Run the uname -r command to query the kernel version.

  • For a binary driver package, the kernel version must comply with Table 1. If it does not, perform either of the following operations:
  • For a general driver package, the kernel version must comply with Table 2. Otherwise, the driver package may fail to be installed or driver functions may be affected.
  1. Check whether NPU driver and firmware packages have ever been installed in the OS.

If you need to upgrade the kernel, ensure that NPU driver and firmware packages have never been installed in the OS. Otherwise, the packages to be used will fail to be started after the kernel is upgraded. You can rectify this issue by referring to What Do I Do If the Software Package Is Unavailable Because It Is Not Uninstalled When Updating the OS Kernel? Run the lsmod|grep drv command to check whether the packages have been installed.

  • If no information is displayed, the packages have never been installed. You can upgrade the kernel without additional actions.
  • If driver information is displayed, the software packages have been installed. Uninstall them and then upgrade the kernel. For details, see Uninstalling the NPU Driver and Firmware.