Compaq Smart-2/E Array Controller
Updated July 10, 2001
Created Jan 12, 2001

Spare# 194752-001 Assembly# 194771-001 Option# 194751-001

If you have any comments, questions, or improvements then please drop me a line. Click here to find out how to contact me: contact.html.
If you have the Compaq Original Eisa Smart Array Controller then please refer to these instructions located at smart.html.
If you wish to learn more about the differences between static drivers and modular drivers then go to lindrivers.html. This lindrivers.html document discusses when to use smart2=0x6000 and when to use eisa=0x6000.
If you have the Smart-2/E controller then it is not very difficult at all in order to get it working with Linux. Here's a summary of a normal install:

Hardware Setup:

  • System Erase [warning, system erase erases all data in the system, be sure to backup any data needed before running system erase]
  • Reconfigure system using SmartStart or SCU
  • Choose Linux as the installed OS
  • Configure the array controller using ACU
  • Software Install:

  • Begin the RedHat Linux Install
  • Begin the "expert" mode of install by typing "linux expert" at the boot: prompt
  • When prompted for a driver disk, select cancel driver disk
  • When asked if you need to specify any drivers, then choose the Compaq Smart2 (cpqarray) driver
  • Specify module options of eisa=0x6000
  • Note that the value of eisa= is the slot number, so if you have the Smart-2/E in slot 5, then you put eisa=0x5000.
  • Continue on with the normal install.

  • Module Options

    The parameters you keyed in (eisa=...) should get put in /etc/conf.modules for you. Here's what part of your /etc/conf.modules would look like when it's done:
    alias scsi_hostadapter cpqarray
    options cpqarray eisa=0x6000
    Remember that for the Smart-2/E you do not have to build a new kernel. It seems that only the original smart (smart.html) has a problem with cpqarray loaded as a module. The Smart-2/E does not have a problem with cpqarray loaded as a module.

    Building a new Initrd

    Note: After updating /etc/conf.modules or /etc/modules.conf with new information regarding your boot controller (with driver loaded as a module and not statically) you must build a new initrd. This is accomplished in Red Hat by using the mkinitrd command:
    mkinitrd -v /boot/initrd-2.4.2-20010518-1630smp.img 2.4.2-20010518-1630smp

    Updating /etc/lilo.conf and running /sbin/lilo

    Then don't forget to make sure that /etc/lilo.conf points to your new initrd and then run /sbin/lilo to make the changes take effect.
    vi /etc/lilo.conf
    See kernel.html for more information on building a new initrd and notes concerning LILO.