**********************************
Linux Driver Package Release Notes
**********************************
OEM Name :LSI Logic Corporation.
Relase Date :Thu Oct 11 10:48:45 EDT 2001
Product Name :Linux x86/IA64 package v1.18
Comonent Name(s) and Version #:
------------------------------------------------
Components: For Redhat Linux 5.x / 6.x / 7.x
Kernels Tested: 2.0.36 , 2.2.X , 2.4.x
----------------------------------
Driver Package version : v118
Driver Version : v118
Megamgr : v5.07
Previous Release: Driver Version 1.17c/1.17d
Megamgr Version 5.04
Driver Standard Features:
-------------------------
:Multithreaded
:Multiple Processor Support
:Non-Disk Support
:Forty Logical Drive Support
Megamgr Standard Features:
--------------------------
:4-chnl,8-logdrv,8-arrays, span4/span8
:Supports Span4 and span8
:Displays span type in adapter parms
:Up to 12-adapters
:Display Controller type, if possible.
:Supports reconstruct on relevant firmwares.
Megaraid Driver Changes -- Since previous release
-------------------------------------------------
<> 1.17d branded as a LSI Logic driver instead on AMI driver
BUGS:
Some older 2.1 kernels (eg. 2.1.90) have a bug in pci.c that
fails to detect the controller as a pci device on the system.
Timeout period for upper scsi layer, i.e. SD_TIMEOUT in /drivers/scsi/sd.c,
is too short for this controller. SD_TIMEOUT value must be increased to
(30 * HZ) otherwise false timeout will occur in the upper layer.
Never set skip_id. The existing PCI code the megaraid uses fails
to properly check the vendor subid in some cases. Setting this then
makes it steal other i960's and crashes some boxes
Linux Megamgr Changes -- Since previous release
-------------------------------------------------
Known Driver and Megamgr Limitations/Restrictions:
--------------------------------------
Driver Installation:
-------------
There are two types of driver installations that one might choose
to adopt
1. Source compilation method
2. Driver Update Disk (DUD) method
The second option is quite easy, and it doesn't require knowledge of
kernel intricacies.
Source Compilation Method:
--------------------------
The linux driver package contains the megaraid.c and megaraid.h file.
You will need to copy these files to /usr/src/linux/drivers/scsi/ and
choose to replace the existing source files.
The file /usr/src/linux/drivers/scsi/sd.c needs to be edited,
and the following line changed from:
#define SD_TIMEOUT (15 * HZ)
to:
#define SD_TIMEOUT (30 * HZ)
Next step is to run "make menuconfig" from /usr/src/linux and configure
your kernel as desired. Make sure that under the <scsi>sub-menu the
option for "probe all LUN's" is selected, and under the low-level
driver section there is an asterisk next to MegaRAID
(or an M to build as a module). After making the necessary
changes, exit and save. Then recompile the kernel with the following
command:
# make dep clean zImage modules modules_install
(or bzImage for larger kernels)
After the kernel has finished compiling, copy the image from
arch/i386/boot/ to /boot and name it according to the naming
convention that you are using. Make the appropriate changes to
/etc/lilo.conf.
An example
For systems containing a single processor on the motherboard alone
# cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.2.15-20
and if the system has more multiple processors on the motherboard
the general convention is
# cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.2.12-20smp
# mkinitrd /boot/initrd-{linux kernel version}.img {version of the kernel}
An example is given below
(for linux kernel 2.2.12-20)
For systems containing single processor on the motherboard alone
# mkinitrd /boot/initrd-2.2.12-20.img 2.2.12-20
and if the system has multiple processors on the motherboard
the general convention is
# mkinitrd /boot/initrd-2.2.12-20smp.img 2.2.12-20smp
Make sure that the new entries created in the /etc/lilo.conf for the new
kernel is updated with the latest kernel and initrd parameter
An example entry for the lilo.conf that contains new entries
For systems containing one processor provision in the motherboard alone
image=/boot/vmlinuz-2.2.12-20
label=linux-ami
initrd=/boot/initrd-2.2.12-20.img
read-only
root=/dev/sda1
and if the system has more than one processor provision in the motherboard
the general convention is
image=/boot/vmlinuz-2.2.12-20smp
label=linux-amismp
initrd=/boot/initrd-2.2.15-20smp.img
read-only
root=/dev/sda1
Note: if you are using a built-in RAID extension slot on an Intel
Madrona motherboard, figure out which scsi id the SAF_TE processor
is using (can be found in Ctlr-M utitlity) and add the line
append="megaraid=skipXX" to the section for the current image in
lilo.conf (replace XX with the scsi id of the SAF_TE processor).
The driver will crash if it tries to scan this id, so this lets
it know to skip it.
When finished editing lilo.conf, run lilo and reboot. When it comes
up again, the RAID controller and all disks attached should be
detected.
Driver Update Disk ( DUD ) Method
---------------------------------
The latest driver can be installed during the installation of the OS itself.
First extract the contents of the file mraid[driver version]
Although the DUD disk contains a few very small files, the image
is in 1,440k image format. This requires that you use the provided
"rwfloppy" utility to convert the image to floppy.
Rwfloppy utility:
Note:
rwfloppy expects the standard 7+3 format for file names. Therefore
the maximum file name length can not exceed seven characters and
must include a three character extention. Thus if a file is named
dud7.0-1.15.img, then it should be renamed to 115.img or
redhat.img, etc.
rwfloppy -r <filename> converts floppy in a: to 1440k image format.
rwfloppy -w <filename> writes 1440k image to a dos format floppy.
You will need to use the second method to convert the DUD image
so that it is usable during the Linux install.
When installing the OS, type 'linux dd' when the cd boots. This will
prompt you to insert the driver update disk ( DUD ). At this time
insert the driver update disk ( DUD )and press OK to continue.
The driver should load immediately. You can use <ctrl><alt><F2>
to verify that the latest driver is being loaded.
After this step continue with install as normal.
Note: Redhat 6.2 requires that you type 'expert' at the beginning
of the CD install. Then follow the prompts and choose "Add Device"
and then select the MegaRAID driver.
In some instances the kernel images and ramdisk image may not be created
properly. This will keep the system from rebooting and resulting in a
panic. In order to verfiy that the images were created, you will use the
following steps. If the vmlinuz image and initrd image are present you can
skip the rest of this section
At the very end of installation, BEFORE you select "Exit" switch
(Ctrl+Alt+F2) screens then do the following
1. 'chroot /mnt/sysimage'
2. edit /etc/conf.modules and delete the 'unknown adapter' line
3. cd /boot
4.'/sbin/mkinitrd initrd-2.2.14-50smp.img 2.2.14-50smp' (for smp kernel's)
-- .'/sbin/mkinitrd initrd-2.2.14-50.img 2.2.14-50' (for UP kernels)
5. edit /etc/lilo.conf to add both of the above lines to the appropriate
place...for example
image=/boot/vmlinuz-2.2.14-50smp
label=linux
initrd=/boot/initrd-2.2.14-50smp.img
read-only
root=/dev/sda1
image=/boot/vmlinuz-2.2.14-50
label=linux-up
initrd=/boot/initrd-2.2.14-50.img
read-only
root=/dev/sda1
6. type '/sbin/lilo'
7. type 'exit' to leave the chroot shell.
8. Change back to F1 for text installs or F7 for Gnome installs and select
the reboot option.
Special Instructions for RH 6.2
-------------------------------
Redhat 6.2 ships with driver 1.07. Although this driver supports older
megaraid controllers, it does not support the latest 40 logical drive
controllers. In order to install the OS to one of these newer controllers,
you will have to use the DUD update disk provided on our ftp site. If you
are installing OS to non MegaRAID device you can recompile with latest
driver after the install.
If you are installing the latest driver with the DUD diskette you will
need to follow these steps:
Boot from Linux CD and enter 'expert' at the boot prompt. Select "Add
Device" and scroll and select the MegaRAID driver. Continue with
install as normal.
Note: In using a DUD disk in expert mode there will be two drivers in
the database. The one that came with the distribution and the one that
you have just loaded. You will want to select the one that is
generically titled "MegaRAID RAID Controllers".
Special Instructions for RH 7.0
-------------------------------
The Redhat 7.0 distribution ships with driver 1.09. This driver supports
all currently shipping MegaRAID controllers.
If you want to update a previously installed system, you can recompile with
the new source code following the "Source Compilation Method" outlined
earlier in this document.
If you are installing fresh and would like to use the latest Linux DUD, you
can follow the instructions for "Driver Update Disk" outlined earlier in
this document.
Megamgr Installation
--------------------
This version of Megamgr comes in a script version. There are two files:
(a) megamgr (script)
(b) megamgr.bin (binary)
Both of these should be in the same directory prior to invocation.
Change the permissions of both the script and the binary by typing
chmod +x ./megamgr
chmod +x ./megamgr.bin
Then inovoke the utility with
./megamgr
-------------------------------------------------------------------------
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.