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 firmware file supports Intel(R) SCSI RAID controllers using software stack 2 (SRCU42X & SRCZCRX), please verify that this firmware 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.

Attention!
===========
Application of this firmware file requires the use of the irflash utility.  
This firmware file is not compatible with the SRCU21, SRCU31, SRCU31L, SRCMR, SRCZCR, SRCU32, SRCU42L, or SRCS14L RAID controllers.

Contents
=========
The following files are included in this zip:
Name			Description
414B.rom		firmware binary
FW414B_readme.txt	This file
Web License		License Agreement


Installation instructions:
==========================
This update can be applied using the irflash utility available for EFI Shell(SRCU42X only), DOS, Windows, Linux, or Netware.
1. Download and extract the irflash utility for your Operating system to a local drive.
2. Download and extract the firmware file to a local drive.
3. Boot the target system to the target OS or EFI shell.  For the purposes of this instruction, DOS will be assumed.  Consult the readme file for the version of irflash you have chosen to use.
4. Change directory to the local drive and directory containing both the irflash utility and the firmware image file.
5. Type "irflash /p"
6. When prompted for the name of the firmware binary file enter the name of the file (414B.rom) and press enter.
7. When prompted, confirm the update.

Help can be obtained with the command "irflash /?"
Multiple controllers installed in the same system can be updated one after the other by following the prompts that are presented.


Fixes/Updates
==============
413D - Adds 64 bit EFI and OS support.
413E - Fixes 64 bit error resulting in a boot error when a Logical drive member is missing.
413Y - Adds PMM Memory & Int19 support.
413Z - Added the following fixes:
1: 4X fail PCI 2.1 and ACPI WHQL test on platforms supporting standby (s1). Passes on system supporting S4. Added ACPI-WHQL compliance on PCI-X controller: Implement power management changes in PCI-X FW to ensure ACPI-WHQL compliance. 
2: Flashing PCI-X in some third party platforms results in a PCI error, Fixed in firmware.
3: ACPI-WHQL compliance on PCI-X ZCR, Fixed in firmware.
4: In cluster mode PCI Express fw goes to mon task during cluster node POST. Fixed by 1. Invalidate the entire MPT Reply IOB at ISR time and 2. DBG_MPT_TMM_LOG(1) may access an invalid data object since ioIdx is not encapsulated in the replyContext.
5: Fix MPT BUSY handling for DCDBs.  The MPT recovery state machine did not retry DCDBs and did not return BUSY status to the issuer of the DCDB. This caused the drives to drop at init time because the disk initialization (DISM) inquiries were failing and not getting retried.
6: Fix MPT replies that arrive after a queued reset. 
7: W2K3 cluster server might hang during reboot test by eliminating any extra queued DISM commands.
8: A fix was previously added to reset the 1030 NVDATA in case the NVDATA was corrupted. This cleared out data that would normally be persistent across boot. One of those data objects is the SCSI initiator ID, so to prevent the FW from using the wrong (default) initiator ID it will reinitialize this object at boot time.
9: Fix MPT clusterInquiry struct to only allow asynch.
10: Fixed issue with cluster data abort in 2 channel spanned config with init id 15 and a pc+ scan is done from the peer.
11: CLUSTER: PCI X fw breaks into megamon after ws2003 phase 5 run, Fixed in firmware.
12: Modify FW to support change in BAR1 register, 
13: When cluster is disabled the scsi chip was not updated with the adapter scsi id. Fixed in FW.
414B - Added the following fixes:
1: Fix battery issue for customer with incorrect Write Back/Write Through
2: Fix ambiguous message when unresolved config mismatch occurs.
3: Fixed a system hang issue if BIOS POST encounters a bad data in controller memory. 
4: Fix the error message when disks are not in correct positions during POST
5: Added native EFI driver support
7: Implemented showing non-disk device details at POST
8: Update MCU default values
9: Increase default value of Inbound ATU Limit Register
10: Updated BIOS Console from 1.97 to 1.98
11: Fix cache flush issue on iBBU

*Third-party trademarks are the property of their respective owners.


