Beruflich Dokumente
Kultur Dokumente
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 update for Linux
Kernel 2.6.x package contains the following files:
The Fibre Channel Adapter and Converged Network Adapter Inbox Driver update for Linux is
compatible with the following OS platforms:
Operating Systems
3. Supported Features
The Fibre Channel Adapter and Converged Network Adapter Inbox Driver for Linux Kernel 2.6.x
supports the following:
This section provides procedures for deploying the driver on various Linux versions, including
the following:
# ./extras/build.sh install
3. Manually load the driver for Linux by issuing the following command:
# 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):
alias scsi_hostadapterX qla2xxx
where, X is based on the order of the SCSI modules being loaded.
b. Create a backup copy of the RAMDISK image by issuing the following commands:
# cd /boot
# cp initrd-[kernel version].img initrd-[kernel version].img.bak
# mkinitrd -f initrd-[kernel version].img `uname -r`
NOTE: Depending on the server hardware, the RAMDISK file name may be different.
2. Build and install the driver modules from the source code by executing the build.sh script
as follows:
# ./extras/build.sh install
3. Manually load the driver for Linux by issuing the following command:
# modprobe -v qla2xxx
# modprobe -r qla2xxx
4. Automatically load the driver by rebuilding the RAM disk to include the driver as follows:
Create a backup copy of the RAMDISK image by issuing the following commands:
# cd /boot
# cp initramfs-[kernel version].img initramfs-[kernel version].img.bak
# mkinitrd -f /boot/initramfs-[kernel version].img `uname -r`
NOTE: Depending on the server hardware, the RAMDISK file name may be
different.
2. Build and install the driver modules from the source code by executing the build.sh script
as follows:
# ./extras/build.sh install
# modprobe -v qla2xxx
# modprobe -r qla2xxx
4. Automatically load the driver by rebuilding the RAM disk to include the driver as follows:
INITRD_MODULES=".... qla2xxx"
b. Create a backup copy of the RAMDISK image by issuing the following commands:
# cd /boot
# cp initrd-[kernel version] initrd-[kernel version].bak
# mkinitrd
NOTE: Depending on the server hardware, the RAMDISK file name may be different.
4.4 Building the Driver for SLES 11 and SLES11 SP1 Linux
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)
# 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
# cp initrd-[kernel version].img initrd-[kernel version].img.bak
# mkinitrd
NOTE: Depending on the server hardware, the RAMDISK file name may be different.
The driver gets its parameters when specified with the insmod command. For example:
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:
# /sbin/modinfo qla2xxx
6. Additional Notes
Booting from SAN means booting the OS from a Fibre Channel target device. We recommend
using the QLogic inbox driver to install the OS to the 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.
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.
4. To continue, click OK.
5. Continue with the OS installation as usual.
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.