This release note and the software that accompanies it are copyright (c) 2005, Intel Corporation, and may only be installed and used in accordance with the license that accompanies the software. This Software is furnished under license and may only be used or copied in accordance with the terms of that license. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. The Software is subject to change without notice, and should not be construed as a commitment by Intel Corporation to market, license, sell or support any product or technology. Unless otherwise provided for in the license under which this Software is provided, the Software is provided AS IS, with no warranties of any kind, express or implied. Except as expressly permitted by the Software license, neither Intel Corporation nor its suppliers assumes any responsibility or liability for any errors or inaccuracies that may appear herein. Except as expressly permitted by the Software license, no part of the Software may be reproduced, stored in a retrieval system, transmitted in any form, or distributed by any means without the express written consent of Intel Corporation. This download supports Intel(R) RAID controllers using software stack 2 (SROMBU42E, SRCU42X, SRCU42E, SRCU41L, SRCS16, SRCS28X, & SRCZCRX), please verify that this driver has been tested with the RAID card you have chosen to use by checking the drivers web page for your controller at http://support.intel.com. ================ Package Information ================ mega4_xx.ham version = 7.01.09 OS supported = NW 5.1 SP8, NW6.0 SP5, NW6.5 SP3 ==================== Attention! ==================== N/A ================ Known Restrictions ================ These drivers are not compatible with the SRCU21, SRCU31, SRCU31L, SRCMR, SRCZCR, SRCU32, SRCU42L, SRCS14L, or SRCFC22C RAID controllers. 1) Usage of megamgr or megamon on systems with more than 2GB of memory is possible ONLY AFTER the support pack 2, (Nw51sp2) for Netware 5.1 is applied, and the Server is restarted. 2) As part of package, driver requires following component when it loaded - MegaMMIO.NLM 3) During unload (or replace driver via hot swap capability) the NetWare driver (Mega4_XX.HAM) the user needs to make sure there are no utilities which uses the driver is present. The sequences needs to follow: - Unload all utilities (MegaMGR and MegaMON) - Unload MegaMMIO.NLM - Unload Mega4_XX.HAM (driver) Failed to do the above sequence the system goes to hang and user has to restart the system. ==================== Contents on the package ==================== The following files are included in this package: Name Description mega4_xx.ham Driver megammio.nlm DRiver mega4_xx.ddi DDI file Web Licence.rtf License NW_DRV_readme.txt This file ================== Installation Instructions ================== Extract package contents to a user specified location such as = a:\ Install this driver during the installation process when prompted for storage device drivers by inserting the driver disk into the floppy drive and providing the floppy drive path when prompted. ================ Component Features ================ N/A ================ Known Issues ================ N/A ================ Fixes/Updates ================ Enhancement #1 Purpose: PCI Express PCI ID's added to applicable components Enhancement #2 Purpose: Add support for SATA 150-8x/4x in Drivers, Application, FW... Enhancement # 3 Purpose: NEW IOCTL command (0xF1) with BusInterruptLevel support. Enhancement details: Added one more member (BusInterruptLevel) to MegaPciInformation. Enhancement #4 Purpose: Support for SRCU41L controller added Enhancement #5 Purpose: For those contollers' PCI Device ID are unique to the industry so that driver doesn't need check them. By removing the check for those controllers, the driver for each of those controller support added. Fix #0 Symptom: loading of driver failed Fix:added PCI signature in the ddi file Fix #1 Symptom: marble service locks up NW6 server in some conditions/controllers Fix: For the MSRB command, second parameter of buildSGList() was not correct. Driver need to pass ‘dataptr as a second parameter, but it passed pointer to ‘dataptr which leads system lock up or crash Fix #2 Symptom: NW 5.1 installation failure on Boxter platform Fix: this is system specific, which means issue not related to the driver Fix #3 Symptom: memory corruption on device scanning Fix: For INQUIRY, driver passed wrong data type for NPA_Allocate_Memory API which is allcation of memory under 16 MB area. This caused memory corruption which leads to system hang/crash Fix #4 Symptom: CERC ATA100, driver can not be loading at NW 5.1 installation Fix: Fixed in FW #5 Symptom: general instability in NW 5.1 using with some adapters Fix: Fixes in driver Fix #6 Symptom: With some utilities the disk spin up or spin off from the physical disks menu is selected the server instantly abends and has to be rebooted manually. Fix: masked out extra ‘EnterDebugger() in the buildSGList() function that cause the system enter debugger mode during ‘spin up/off deivce which is one of dellmgr command via. IOCTL. Fix #7 Symptom: During a bus scan the driver displays FreeFreeFreeFree after the vendor ID. Fix: changed way to display LD information. Fix #8 Symptom: PCI information (subSysVID) for SATA controller was not correct and this leads that driver couldn’t load for the controller. Fix: changed subSysVID for the controller Fix #9 Symptom: PCI information (subSysID) for controller was not correct and this leads that driver couldn’t load for the controller. Fix: changed subSysVID for the controller Fix #10 Symptom: driver passed wrong data for one of IOCTL request which is ‘GET_ADAPTER_PCI_RESOURCES Fix: changed properly to send back right data. Fix #11 Symptom: when driver gets SCSI opcode ‘START STOP UNIT for the LD which is failed some how (by deleting or make that LD offline from megaMgr), there was memory move operation with invalid data pointer and this operation leads system go to Abend.. Fix: masked out the memory move operation on that SCSI opcode case in the processLDIORequest(). Fix #12 Symptom: Driver had problem with error handling that happen on drive failure in the middle of I/O. As part of error handling, driver had ‘mega_HAM_Abort_HACB() type 0 function 2, but functionality of this function was not correct and this problem leads system goes to hang or abend. Fix: updated ‘mega_HAM_Abort_HACB() function so that driver could handle HACB request abort properly. Fix #13 Symptom: Driver is not loading for the second controller. Fix: Driver has two entries for the same VID DID combination. Removed one entry. Fix #14 Symptom: When an S30 (FSC enclosure) is connected to a controller, the environment chip (Qlogic GEM3xx) on the backplane is not visible in the Netware device list. FSC Server management software "SERVER VIEW" needs to access this device (GEM3.. Fix: Made driver change so that it registers all device type defined in the SCSI specification. With this changes, driver will register initiator/back plane processor so that FSC Server Management S/W can see devices connected to back plane. Fix #15 Symptom: When multi controllers present, If the 'IRQ sharing option' enabled in the system BIOS, the system goes to hang during the heavy I/O. Fix: Command completion acknowledgement to the firmware only if the IRQhandle and the controller firmware signal is set. Fix #16 Symptom: Component name is SRCU42E, rather than SRCU42EX. Fix: The subsystem ID has been changed from 0x1000 to 0x8086 Fix #17 Symptom: mega4_xx.ham driver timeout error when heavy I/O's are executed overnight Fix: When a very first command timed out (time out amount 1 minutes for all commands except srb, format and erase) the driver stop issuing anymore command to the firmware and wait for 3 minutes to make sure the firmware completes all the pending commands. If the firmware completes all the pending commands within 3 minutes the operation resumes normally. If the firmware not responds within the 3 minutes interval the drive mark the controller malfunctioned. Fix #18 Symptom: When installing Netware 6.5 SP2, the driver loads but incorrectly names the controller, fails to autodetect the slot number, and will fail the install. Fix: mega4_xx.ddi file has the incorrect device ID 0x0408. *Third-party trademarks are the property of their respective owners.