Professional Documents
Culture Documents
QLogic Corporation
All rights reserved
Table of Contents
1. Package Contents
2. OS Support
3. Supported Features
4. Deploying the Driver
4.1 Building the Driver for RHEL 5.x Linux
4.2 Building the Driver for SLES 10 SP2 Linux
4.3 Building the Driver for SLES 11 Linux
5. Driver System Parameters
6. Additional Notes
6.1 Booting from SAN
6.2 Firmware Installation
6.3 Dynamically Modifying SCSI Blacklist Entries
7. Contacting Support
1. Package Contents
The Fibre Channel Adapter and Converged Network Adapter Inbox Driver for Linux Kernel 2.6.x
package contains the following files:
2. OS Support
The Fibre Channel Adapter and Converged Network Adapter Inbox Driver for Linux is compatible with
the following OS platforms:
Red Hat RHEL AS 5.x (32-bit, 64-bit) on Intel x86, Intel 64, AMD64
Novell SLES 10 SP2 (32-bit, 64-bit) on Intel x86, Intel 64, AMD64
MSI-X interrupts
Device mapper
This section provides procedures for deploying the driver on various Linux versions, including the
following:
# cd qla2xxx-src-x.xx.xx.xx.xx.xx-k
2. Build and install the driver modules from the source code by executing the build.sh script as
follows:
# ./extras/build.sh install
To directly load the driver from the local build directory, issue the following insmod
commands in order:
# insmod qla2xxx.ko
# modprobe -v qla2xxx
# modprobe -r qla2xxx
4. Automatically load the driver by rebuilding the RAM disk to include the driver as follows:
a. Edit the /etc/modprobe.conf file and add the following entry (if they are not present):
b. Create a backup copy of the RAMDISK image by issuing the following commands:
# cd /boot
NOTE: Depending on the server hardware, the RAMDISK file name may be different.
# cd qla2xxx-x.xx.xx.xx.xx.x-k4
2. Build and install the driver modules from the source code by executing the build.sh script as
follows:
# ./extras/build.sh install
To directly load the driver from the local build directories, issue the following insmod
commands in order:
# insmod /lib/modules/2.6.../updates/qla2xxx.ko
# modprobe -v qla2xxx
# modprobe -r qla2xxx
4. Automatically load the driver by rebuilding the RAM disk to include the driver as follows:
a. Edit the /etc/sysconfig/kernel file to modify the INITRD_MODULES directive and append
qla2xxx to the string.
For example:
INITRD_MODULES=".... qla2xxx"
b. Create a backup copy of the RAMDISK image by issuing the following commands:
# cd /boot
# mkinitrd
NOTE: Depending on the server hardware, the RAMDISK file name may be different.
# cd qla2xxx-x.xx.xx.xx.xx.xx-k4
2. Build and install the driver modules from the source code by executing the build.sh script as
follows:
# ./extras/build.sh install
allow_unsupported_modules 1 (replace 0 by 1)
To directly load the driver from the local build directories, issue the following insmod
commands in order:
# insmod /lib/modules/2.6.../updates/qla2xxx.ko
# modprobe -v qla2xxx
# modprobe -r qla2xxx
4. Automatically load the driver by rebuilding the RAM disk to include the driver.
allow_unsupported_modules 1 (replace 0 by 1)
# cd /boot
# mkinitrd
NOTE: Depending on the server hardware, the RAMDISK file name may be different.
This section describes the driver parameters. (Where appropriate, format parameters into a table to
identify parameter names, descriptions, value ranges, and default values.)
The driver gets its parameters when specified with the insmod command.
If using the modprobe command, you must specify the parameters in the /etc/modprobe.conf file
for RHEL and /etc/modprobe.conf.local for SLES.
For example:
ql2xlogintimeout – Defines the login timeout value in seconds during the initial login. Default:
20 seconds.
qlport_down_retry – Defines how long to wait for a port that returns a PORT-DOWN status
before returning I/O back to the OS. Default: 30 seconds.
ql2xplogiabsentdevice – Enables PLOGI to devices that are not present after a Fabric scan.
This is needed for several broken switches. Default is 0 – no PLOGI. 1 – perfom PLOGI.
ql2xloginretrycount – Specifies an alternate value for the NVRAM login retry count. Default is
8.
ql2xmaxqdepth – Defines the maximum queue depth reported to SCSI mid-level per device. The
Queue depth specifies the number of outstanding requests per LUN. Default is 32.
ql2xqfullrampup – Number of seconds to wait to begin to ramp-up of the queue depth for a
device after a queue-full condition has been detected. Default is 120 seconds.
ql2xqfulltracking – Controls whether the driver tracks queue full status returns and
dynamically adjusts a SCSI device's queue depth. Default is 1 to perform tracking. Set to 0 to
disable tracking and adjustment of queue.
ql2xfwloadbin – Specifies location from which to load ISP firmware. 2 – load firmware via the
request_firmware() interface. 1 – load firmware from Flash. 0 – use default semantics.
# /sbin/modinfo qla2xxx
6. Additional Notes
Booting from SAN means booting to the OS from a Fibre Channel target device. We recommend
using the QLogic inbox driver to install the OS to a Fibre Channel target device that is attached to a
QLogic adapter. If there is no QLogic inbox driver that supports the adapter, you should use a DD-kit
to boot from SAN.
When installing to a LUN other than LUN 0 and LUN 0 is present, follow these steps to successfully
boot from the LUN:
1. On the Boot Loader Configuration screen, select the Configure Advance Boot Loader Option,
and then click Next.
2. On the Advanced Boot Loader Configuration screen, select Change Drive Order.
3. On the Edit Drive Order window, move the entry for the boot LUN.
$ cd /
$ cp /lib/firmware/ql2400_fw.bin /lib/firmware/ql2400_fw.bin.orig
$ cp /lib/firmware/ql2500_fw.bin /lib/firmware/ql2500_fw.bin.orig
2. Extract firmware:
$ cd /
$ tar xvfz /tmp/qla2xxx-fw-apex-v5.03.02.tar.gz
The SLES10/11 drivers should report 4Gb and 8Gb firmware versions 5.03.02.
On 2.6.x kernels, you can dynamically change the SCSI blacklist, either by writing to a /proc entry
or using the scsi_mod module parameter, which allows persistence across reboot.
This requires the SCSI Vendor/Model information for the SCSI device, available at /proc/scsi/scsi.
vendor:model:flags[v:m:f]
For example:
7. Contacting Support
Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of
integration for assistance. QLogic Technical Support can be reached by the following methods:
Web: http://support.qlogic.com
E-mail: support@qlogic.com
Go to Top
© Copyright 2010. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic
Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners.