********************************************* LSI Logic Driver MegaSR Release ********************************************* Release Date: 10/02/07 =================== Supported Controllers ================== MegaRAID SAS 8208ELP MegaRAID SAS 8208XLP MegaRAID SAS 8204ELP MegaRAID SAS 8204XLP Component: ========= MegaSR Driver Red Hat 5 Release Date: 03/11/2008 Changes / Defects resolved: LSID100073127 (CO) CR_Ref# LSID100064693: Add the ability to pull OpROM version to StorLIB LSID100073129 (CO) CR_Ref# LSID100068807: Need to create a R5 from OS without prior config LSID100080339 (CO) CR_Ref# LSID100079663: Adding new customer IDs into MegaSR LSID100071310 (CO) CR_Ref# LSID100070143: Need support for ICH9 fault LED for OEM’s backplane LSID100091495 (CO) Add HW, PnP ID, and MFC (ini) file LSID100093095 (CO) CR_Ref# LSID100092259: SWR megasr.inf modification LSID100079178 (DFCT) INFTEST fails in Vista 64 bit LSID100080001 (DFCT) Self signed cat file requirement for Vista x86 LSID100078716 (DFCT) Specific DVD fails Linux stress test LSID100081655 (DFCT) Alpharetta SWR driver cannot make the SATA drive dead when that drive returned the CRC Error. LSID100090609 (DFCT) OS slow down symptom occurred during the RAID1 medium error handling by SWR Alpharetta driver. LSID100090689 (DFCT) MegaSR driver not loading on OEM system LSID100090791 (DFCT) SWR5 Alpharetta - several kernel panics during reboot tests LSID100092331 (DFCT) Data integrity issue may occur when SWR driver tried to fix Media Error in R5 subsystem LSID100092963 (DFCT) Possible data integrity issue in R5 error recovery path if MPT controllers are used LSID100091258 (DFCT) Write on IO Buffer after Media error status results MPT FW to fail LSID100093874 (DFCT) Write on IO Buffer after Media error status results MPT FW to fail LSID100092451 (DFCT) Message “megasr[cfg]: ddf, flush controller cache failed on target=3, 4, 6, 7” on RAID activity LSID100092972 (DFCT) Unable to install SLES 9 [due to IRQ disabled] LSID100081025 (DFCT) Windows MegaCLI changes the value of PDList and GetNum when DVD-ROM is on Port 0. LSID100081663 (DFCT) Possible data integrity issue for medium error handling for RAID1 SATA drives. LSID100091576 (DFCT) Possible data integrity issue when SWR driver tried to fix the ECC error in particular environments. Version Numbers: =============== Includes Current Version: megasr-09.32.0207.2008-1-rhel50-ga-all.img megasr-09.32.0207.2008-1-rhel50-u1-all.img Heading: Known Restrictions Contents: • Type "brokenmodules=ahci" line at kernel parameter line during SLES 9 & 10 installations • RHEL 3.0 64-bit versions are not supported on AMD systems. Only Intel systems are supported. • In SWR5 driver, RAID 5 feature is enabled only if iButton is present in the system. BIOS communicates the presence/absence of iButton using configuration data on disk (DDF). If driver does not read a valid DDF, it will disable R5 creation. Driver may not see valid DDF if (A) user does not configure using BIOS Ctrl+M; or (B) if no drives were present at the boot time and all the drives were hot-inserted after OS is booted. In both cases, user must create initial configuration using BIOS Ctrl+M utility. • A RAID 5 logical drive withstands single drive failure by reconstructing missing data from the data and parity from the remaining drives. The assumption underlying this ability is that the data in the remaining drives is consistent. This assumption becomes invalid if there is a power loss during write operation(s). If there is a loss of power during a write operation, data inconsistencies may occur because data and parity writes may have completed only partially. After subsequent reboot the logical drive has inconsistent data on that particular stripe. If a drive were to fail at this point, missing data (for the inconsistent stripe alone) cannot be reconstructed from remaining drives. To correct inconsistency, drivers starts back ground initialization (BGI) at reboot. While BGI is in progress, the inconsistent stripe(s) are vulnerable to drive failure. One way to avoid this window of vulnerability is to run check consistency on the logical drive using BIOS utility. Another way is to prevent an unplanned shutdown (e.g. using UPS). • The LITE-ON SH S752K model CD/DVD ROM device does not respond to 0x55 & 0x51 MMC commands properly. The device hangs when these commands are issued multiple times. The driver resets the device when it hangs; but reset adversely affects DVD burning. This behavior can be consistently observed using K3B DVD burning software. K3B aborts DVD writes when 0x55 is failed and device is reset. • RHEL5 installation does not automatically prefer the driver in DUD to native driver. Run replace_ahci script inside the DUD before rebooting during the last stage of installation. Refer to readme.txt under in the DUD for more detailsDownload 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.