• Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Intelligent Storage
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
  • Technical Blogs
All Support
  • Become A Partner
  • Partner Policy & Program
  • Global Learning
  • Partner Sales Resources
  • Partner Business Management
  • Service Business
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
Home Support Resource Center Software Download Servers

HBA-LSI-9500-LP-16i(2023/11/15)

Category-Component Type:

Driver-Storage

Version:

45.00.00.00

OS:

linux-Ubuntu Server 20.04.5 (HWE-Kernel) (64 bit) – LTS

    Description

  • Description
  • Installation steps
  • Publish Description
  • Problems Solved
  • New Functions
  • Historical Versions
  • Description

    The software is the driver of broadcom IT-IR storage controller card in the Linux operating system (OS).

  • Installation steps

    Rpm drive package

    1.Log in to the server system with administrator privileges and upload the driver files to the xxx directory of the system (using the home directory as an example below).

    2.Open the command line terminal and enter the following command (using RHEL9.0 as an example);

    Driver installation command: rpm -ivh /home/<name>.rpm (where<name>is the file name of the rpm installation package)

    Driver update command: rpm -Uvh /home/<name>.rpm (where<name>is the rpm installation package file name)

    3.After the command execution is completed, the system needs to be restarted to make the driver package effective.

    4.After restarting and entering the system, open the command line terminal and execute the cat/sys/module/<name>/version (Here<name>see Driver submodule information table - Module name) command to confirm that the driver version of the array card is already the target driver version. If the version is the target version, it means that the new driver installation is successful.

    (Note: Before installing the driver in Suse OS, check whether the third-party module support option is enabled: check the /etc/modprobe.d/unsupported-modules configuration file to ensure that allow_unsupported_modules option is set to 1.)

    Deb drive package

    1.Log in to the server system with administrator privileges and upload the driver files to the xxx directory of the system (using the home directory as an example below).

    2.Ensure that the target server operating system has installed build essential and dkms software packages. You can query the installed software packages of the current operating system through dpkg -l. If there are no results from the query, you can try installing as follows (using Ubuntu 20.04 as an example):

    a)Configure local or network apt sources;

    b)Enter the following command to install:

    # sudo apt-get update

    # sudo apt-get install build-essential

    # sudo apt-get install dkms

    3.Execute the driver package installation command:

    #sudo dpkg -i /root/<name>.deb (where<name>is the file name of the deb installation package).

    4.After the command execution is completed, the system needs to be restarted to make the driver package effective.

    5.After restarting and entering the system, open the command line terminal and execute the cat/sys/module/<name>/version (Here<name>see Driver submodule information table - Module name) command to confirm the driver version of the array card. If the version is the target version, it means that the new driver has been successfully installed.

    Src driver source code package

    1.Log in to the server system with administrator privileges and upload the driver files to the xxx directory of the system (using the home directory as an example below).

    2.Open the command line terminal and upload the src.zip compressed package to the system;

    3.Use the command to unzip: unzip src.zip.

    4.Unzip and enter the kmod_srpm directory.

    5.Grant executable permissions to the kmod xxx.src.rpm package, using the command:rpmbuild --rebuild kmod-xxx.src.rpm.

    6.Enter /root/rpmbuild/RPMS/x86_64 directory.

    7.Place the compiled kmod-mpt3sas-xxx.x86_64.rpm package in the system root directory.

    (Note: Remember to drag the compiled driver package locally in a timely manner for saving and archiving)

    8.Enter the root directory and use the following command to install the driver package: rpm -ivh kmod-mpt3sas-xxx.x86_64.rpm.

    9.After the command execution is completed, the system needs to be restarted to make the driver package effective.

    10.After restarting and entering the system, open the command line terminal and execute the cat/sys/module/<name>/version (Here<name>see Driver submodule information table - Module name) command to confirm the driver version of the array card. If the version is the target version, it means that the new driver has been successfully installed.

    Dd driver package

    1.The above update method is for regular OS, and if the array card cannot be recognized during installation, the driver shall be installed first following the steps below.

    2.Provide the dd.iso corresponding to the OS in the current driver folder and mount it in KVM.

    3.Start OS boot and when entering the selection menu, press e to enter grub.

    Redhat, CenOS, ORCL Linux series systems: Add "Linux dd" at the end of the linuxefi... line and press Ctrl+x to start booting.

    Suse series systems: Add "dud=1" at the end of the linuxefi... line, and press Ctrl+x to start booting.

    4.After entering, you will first select the path where the driver is located, select the mount media menu option, press the space to select, press c to continue, and follow the prompts to continue the operation. After entering, you can install the OS.

    5.After the OS installation is completed, there is no need to reinstall the driver. If you need to update the driver, follow the update method under the OS mentioned above.

  • Publish Description

    Supported products

    H3C UniServer B5700 G3

    H3C UniServer B5700 G5

    H3C UniServer B5800 G3

    H3C UniServer B7800 G3

    H3C UniServer E3200 G3

    H3C UniServer R2700 G3

    H3C UniServer R2900 G3

    H3C UniServer R4300 G3

    H3C UniServer R4300 G5

    H3C UniServer R4330 G5

    H3C UniServer R4330 G5 H3

    H3C UniServer R4500 G3

    H3C UniServer R4700 G3

    H3C UniServer R4700 G5

    H3C UniServer R4700 G6

    H3C UniServer R4900 G3

    H3C UniServer R4900 G5

    H3C UniServer R4900 G6

    H3C UniServer R4900 G6 Ultra

    H3C UniServer R4930 G5

    H3C UniServer R4930 G5 H3

    H3C UniServer R4950 G5

    H3C UniServer R4950 G5 Milan

    H3C UniServer R4950 G5 Rome

    H3C UniServer R4950 G6

    H3C UniServer R5300 G3

    H3C UniServer R5300 G5

    H3C UniServer R5500 G5 AMD

    H3C UniServer R5500 G5 Intel

    H3C UniServer R6700 G3

    H3C UniServer R6900 G3

    H3C UniServer R8900 G3

    H3C UniServer R5350 G6

    H3C UniServer R6900 G5

    H3C UniServer R5500 G6 AMD

    H3C UniServer R5500 G6 Intel

    H3C UniServer R5300 G6

    H3C UniServer R5500LC G5 Intel

    H3C UniServer R5500 G5 HYGON

    H3C UniServer B5700 G6

    H3C UniServer R4900LE G6 Ultra

    H3C UniServer R4700LE G6

    H3C UniServer R4900LC G5

    H3C UniServer R4700LC G5

    H3C UniServer R4930LC G5 H3

    H3C UniServer R4300 G6

    H3C UniServer R4500 G6

    H3C UniServer R6700 G6

    H3C UniServer R6900 G6

    H3C UniServer R5330 G7

    H3C UniServer R5500 G7 Hygon

    H3C UniServer R4930 G7

    H3C UniServer E3300 G6

    H3C UniServer R3950 G6

    H3C UniServer R4330 G7

    H3C UniServer R4950 G7

    H3C UniServer R3950 G7

    H3C UniServer R3350 G7

    H3C UniServer R4900 G7

    H3C UniServer R4700 G7

    H3C UniServer R3900 G7

    H3C UniServer R4300 G7

    Restrictions and guidelines

    1.Before updating the software, as a best practice, understand the changes on the software between versions, assess the impacts of the changes on the services and read supporting materials.

  • Problems Solved

    1.Increased the device scanning scsi commands timeout to 30s.

    2.Fixed the compilation errors observed on kernel versions from 5.12 to 5.15.

    3.Fixed an issue where executing rmmod and related operations triggered use after free, which caused system crashes. The relevant log information is referenced as follows:

    图片 1

    4.Fix system crash observed on doing firmware upgrade/downgrade on IT controller.

  • New Functions

    1.Added SLES15 SP4 OS and Ubuntu 22.04 LTS OS support.

  • Version:52.00.00.00(2025/9/9)

    Upgrade recommendations

    Upgrade the driver,as a best practice.

    Problems Solved

    1.None.

    New Functions

    1.Issue a Diag-reset when the "Doorbell-In-Use" bit is set during the driver load/initialization. 

    Version:49.00.00.00(2024/4/11)

    Upgrade recommendations

    Upgrade the driver,as a best practice.

    Problems Solved

    1.During heavy IO test doorbell is not giving correct value.

    New Functions

    1.Drivers: Handle IOMMU restore at exit boot services. 

    Version:45.00.00.00(2023/11/15)

    Upgrade recommendations

    Upgrade the driver,as a best practice.

    Problems Solved

    1.Increased the device scanning scsi commands timeout to 30s.

    2.Fixed the compilation errors observed on kernel versions from 5.12 to 5.15.

    3.Fixed an issue where executing rmmod and related operations triggered use after free, which caused system crashes. The relevant log information is referenced as follows:

    图片 1

    4.Fix system crash observed on doing firmware upgrade/downgrade on IT controller.

    New Functions

    1.Added SLES15 SP4 OS and Ubuntu 22.04 LTS OS support.

新华三官网