HP ProLiant BL660c HP ProLiant and Integrity Firmware Management Best Practice - Page 38

continued, Emulex, QLogic, and Brocade Fiber Channel HBA firmware

Get HP ProLiant BL660c PDF manuals and user guides View all HP ProLiant BL660c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 38 highlights

Table 5 Driver dependency considerations (continued) Firmware types Smart Array controller firmware Known driver dependencies Windows • hpcisss2.sys driver 5.8.0.0 or later • hpsa2.sys (any version) • HpAHCIsr.sys (any version) Linux • cpq_cciss RPM 2.4.48-12 or later • hpahcisr RPM (any version) • hpsa (any version) NOTE: Later driver versions might be required to support newer Smart Array controllers. The version listed is the minimum needed to support firmware updates. The driver listed will need to be matched to the type of Smart Array controller in the server. SAS and SATA hard drive Windows • hpcisss2.sys driver 5.8.0.0 or later • bchtsw32.sys (any version) • lsi_sas.sys (any version) • lsi_sas2.sys(any version) • hpcisss2.sys (any version) • HpAHCIsr.sys (any version) • hpsa2.sys (any version) Linux • cpq_cciss RPM 2.4.48-12 or later • hpahcisr RPM (any version) • hpvsa RPM (any version) • mpt2sas RPM (any version) • hpsa RPM (any version) • cciss RPM (any version) NOTE: Later driver versions might be required to support newer Smart Array controllers. The version listed is the minimum needed to support firmware updates. The driver listed will need to be matched to the type of Smart Array or SATA controller in the server. The drivers provided by the Linux distributions can also be used in place of the RPM if desired. Emulex, QLogic, and Brocade Fiber Channel HBA firmware Windows • All dependencies are included in the SPP. Linux The requirement is for a kernel driver for the appropriate adapter that has been compiled to work with the boot kernel. Because all three of these adapter's drivers are shipped as source RPMs, the source must be compiled through installation of the RPM and then the resulting driver used in the boot environment. Tape firmware For SCSI attached tape drives, the following drivers must be loaded. For USB-attached tape drives, the support is already in the operating system. 38 FAQs

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
Table 5 Driver dependency considerations
(continued)
Known driver dependencies
Firmware types
Windows
Smart Array controller firmware
•
hpcisss2.sys
driver 5.8.0.0 or later
•
hpsa2.sys
(any version)
•
HpAHCIsr.sys
(any version)
Linux
•
cpq_cciss
RPM 2.4.48-12 or later
•
hpahcisr
RPM (any version)
•
hpsa
(any version)
NOTE:
Later driver versions might be required to support
newer Smart Array controllers. The version listed is the
minimum needed to support firmware updates. The driver
listed will need to be matched to the type of Smart Array
controller in the server.
Windows
SAS and SATA hard drive
•
hpcisss2.sys
driver 5.8.0.0 or later
•
bchtsw32.sys
(any version)
•
lsi_sas.sys
(any version)
•
lsi_sas2.sys
(any version)
•
hpcisss2.sys
(any version)
•
HpAHCIsr.sys
(any version)
•
hpsa2.sys
(any version)
Linux
•
cpq_cciss
RPM 2.4.48-12 or later
•
hpahcisr
RPM (any version)
•
hpvsa
RPM (any version)
•
mpt2sas
RPM (any version)
•
hpsa
RPM (any version)
•
cciss
RPM (any version)
NOTE:
Later driver versions might be required to support
newer Smart Array controllers. The version listed is the
minimum needed to support firmware updates. The driver
listed will need to be matched to the type of Smart Array
or SATA controller in the server. The drivers provided by
the Linux distributions can also be used in place of the RPM
if desired.
Windows
•
All dependencies are included in the SPP.
Linux
Emulex, QLogic, and Brocade Fiber Channel HBA firmware
The requirement is for a kernel driver for the appropriate
adapter that has been compiled to work with the boot
kernel. Because all three of these adapter’s drivers are
shipped as source RPMs, the source must be compiled
through installation of the RPM and then the resulting driver
used in the boot environment.
For SCSI attached tape drives, the following drivers must
be loaded. For USB-attached tape drives, the support is
already in the operating system.
Tape firmware
38
FAQs