IBM xSeries 360 POST/BIOS RSA PKT Update
Version 1.14
Installation README File
CONTENTS
________
1.0 Overview
2.0 Change History
3.0 Installation and Setup Instructions
4.0 Unattended Mode
5.0 Web Sites and Support Phone Number
6.0 Trademarks and Notices
7.0 Disclaimer
1.0 Overview
1.1 This README file contains the latest information about
installing the IBM xSeries 360 POST/BIOS. Before performing
the flash update you must follow the update procedure noted
in the Dependencies section.
1.2 Limitations - NA
1.3 Enhancements - This version of POST/BIOS supports IBM xSeries
360 system with or without the IBM RXE-100 Remote Expansion
Enclosure.
1.4 Dependencies
For flash update of POST/BIOS and Remote Supervisor Adapter
code:
1.4.1 If the current level of BIOS code on the xSeries 360 is
BIOS 1.01 or below, then BIOS 1.02 must be installed
before attaching the RXE-100 Remote Expansion Enclosure.
1.4.2 If the current level of BIOS code on the xSeries 360 is
BIOS 1.02 or later, attach the RXE-100 Remote Expansion
Enclosure.
1.4.3 If the current level of the IBM Remote Supervisor Adapter
code in the xSeries 360 is less than 1.01, then the
Supervisor Adapter code must be updated.
Note: Updating this code must be performed with the
RXE-100 Remote Expansion Enclosure attached.
2.0 Change History
V1.14 - June 01, 2004
-------------------------
- Updated the microcode for Gallatin processor B1 stepping
(CPUID:0F25h, PATCH ID:1D).
- Added support for wFlash and lFlash.
V1.13 - April 9, 2004
-------------------------
- Added fix to boot from alternate boot sequence for all subsequent
warm boots after WOL event occured.
- Updated latest microcode for Gallatin processor B1 stepping
(CPUID:0F25h, PATCH ID:19) and A0 stepping (CPUID:0F22h, PATCH ID:05).
V1.12 - September 4, 2003
-------------------------
- Added in fix to allow emm386.exe to be used when booting the system
with the remote boot feature of the Remote Supervisor Adapter.
- Fixed the Gigabit ethernet adapter issue for Model 1RX, 2RX and 3RX.
Other x360 models do not have this problem.
V1.11 - June 13, 2003
-------------------------
- Updated latest microcode for Gallatin processor B1 stepping
(CPUID:0F25h, PATCH ID:0E).
V1.10 - June 04, 2003
-------------------------
- Updated latest microcode for Gallatin processor B1 stepping
(CPUID:0F25h, PATCH ID:0B).
- Fixed SMBIOS Type 17 structure for 2GB DIMMs.
V1.09 - April 15, 2003
-------------------------
- Added support for Gallatin processor B1 stepping(CPUID:0F25h, PATCH ID:04).
V1.08 - March 14, 2003
-------------------------
- Fixed the target abort error during ROM scan of JNIFCX-6562 fiber
controller PCI-X adapter card.
- Fixed the failed processor number reporting due to MCA error.
- Fixed SMBIOS header information.
- Added code to support additional warning messages with 2GB DIMMs installed.
- Fixed the problem of unrecoverable error that was caused with Netware
hot-plug device driver.
- Fixed unreported Memory/IO test failure of HCT.
V1.07 - February 19, 2003
-------------------------
- Added code to handle Dialogic fax adapter (Model = D/41JCT-LS,
Vender ID = 12C7 and Device ID = 0676).
V1.06 - October 25, 2002
-------------------------
- Added the enhancement to the ECC logic verification test during POST.
- Changed the maximum CPU speed reported in SMBIOS for system with
Gallatin processor.
V1.05 - October 02, 2002
-------------------------
- Added Serial port support code.
- Fixed the problem of ALT-F1 not working with serial console redirection.
- Updated Foster Micro Code (patch = 08).
- Added Remote Floppy Ghost Disk support.
- Fixed the problem of Diagnostics flash update failure in unattended mode.
- Changed WOL default setup option to disabled for 8686-1RX/2RX/3RX models.
- Added NLS translations.
- Modified code to keep SP COM port enabled during serial console
redirection.
- Resolved the issue of configuration change caused by updating to
the latest version of BIOS using RDM.
- Changed the Product ID field in MPS table from "NF 6000R SMP" to
"CRUSADER SMP".
V1.04 - July 11, 2002
-------------------------
- Fixed the code to report "161 - Bad CMOS Battery Error" whenever
bad CMOS battery is detected.
- Added RXE-100 slots in "Boot Device Location" of Setup.
- Updated Intel ethernet PXE ROM to version 4.0.17.
- Added remote floppy boot support.
- Added in POST/BIOS serial console redirection. This feature
can be enabled in system setup and will provide remote console
redirection via the serial ports without the service processor.
- Modified BIOS defaults to support remote deployment.
- Reorganized some menus of IBM BIOS setup screen.
- Added support to enable/disable Hyper-Threading technology in SETUP.
- BIOS will not log onboard SCSI disabled messages when SCSI cable is
connected between the add-on SCSI adapter and connector on the system
planar.
- Patched the DAC problem of S3 video controller only when onboard SCSI
is enabled.
- Fixed the incorrect memory type reporting in Smbios.
V1.03 - April 2, 2002
-------------------------
- Fixed the problem of cache disabled after installation of Windows
operating system.
- Patched the DAC problem of S3 video controller which may cause system
hang if the system has 8GB memory installed.
- Fixed the problem of remote console which may cause system hang.
- Tuned the bus timeout of each HOST-PCI bridge to max. value.
- Added code to enhance the robustness of PCI-X bridge support.
V1.02 - March 29, 2002
-------------------------
- Integrated code to support the attachment of "IBM RXE-100 Remote
Expansion Enclosure".
- Fixed the problem of "IBM xSeries 360 diagnostics" unable to
obtain the status of RXE through service processor.
- Fixed ROM scan problem of QLogic SCSI adapter installed in RXE-100.
- Fixed the problem of adapter unable to be recognized in "Windows.NET
server" operating system when the adapter is hot-removed and
then hot-added.
- Fixed message displayed for changed field replaceable unit (FRU)
in RXE-100.
- Changed the 'year' field of copyright message to 2002.
- Changed the remote flash update utility to support the method
of virtual disk.
PLEASE NOTE:
(1) If system is installed with BIOS V1.02 (or above), must use
packet file(s) for BIOS V1.02 (or above).
(2) If system is installed with BIOS 1.01 (or below), must use
file(s) for BIOS V1.01 (or below).
It should be noted that this change has no impact on
"diskette flash update".
- Fixed Linux system hang during boot when remote video console is
used.
- Added PCI(x)-PCI(x) bridge support at boot time.
- Corrected some data for SMBIOS.
V1.01 - December 19, 2001
-------------------------
- Added code to fix occurrence of IERRs during reboot test
caused by an RXE expansion device timeout.
- Fixed SMBIOS structure to display correct processor cache size.
- OS will now display the same BIOS version as POST.
- Flash diskette attributes now being set correctly.
- Added a workaround to fix Intel Xeon processor errata which can
cause an invalid processor machine check.
- Fixed several setup help related problems.
- Added a BIOS check for installed adapters with onboard PCI-X.
- Added an enhancement to processor MCK initialization requirement
by Intel.
- Removed Checkpoint 50 and log error for SPINT clear failure.
V1.00 - December 13, 2001
-------------------------
- Initial release
3.0 Installation and Setup Instructions
The procedure to update the POST/BIOS is as follows:
3.1 Download the "IBM xSeries 360 POST/BIOS RSA PKT Update"
to your hard drive from the IBM support site.
3.2 Double-click on the icon or execute the update from the
command line. This will create two files, the .PKT file and
this readme file.
3.3 Using a web browser, log in to the Remote Supervisor
Adapter (RSA) of the server you want to update. You must
log in with a user ID that has read/write privileges.
3.4 In the Tasks section of the blue navigation frame, click
Transfer Files.
3.5 In the Update Firmware section of the page that opens,
click Browse.
3.6 Navigate to the .PKT file that you extracted in 3.2. Select
the file and then click Open.
3.7 Click Update.
A progress indicator will be displayed as the update
file is transferred to temporary storage on the RSA for
initial processing.
ATTENTION: To avoid permanent damage to your server, do
not manually power off or restart the server during an
update unless specifically asked to do so in these
instructions or by the web interface. If the server is
already powered on, it will automatically be restarted
by the RSA as part of the update process. If the server
currently is powered off, it will automatically be
powered on.
3.8 When the Confirm Firmware Update page is displayed,
verify that the update file type is "Diagnostics" and
then click Continue. If a different update type is
shown, click Cancel and make sure that you downloaded
the correct file in step 1 and selected the correct file
in step 5.
A progress indicator will be displayed as the firmware
is flashed.
3.9 Wait for the browser to display a completion message
after the update has finished.
4.0 Configuration Information
5.0 Unattended Mode - NA
6.0 Web Sites and Support Phone Number
6.1 IBM Support Web Site:
http://www.pc.ibm.com/support
6.2 IBM Marketing eserver Web Site:
http://www.pc.ibm.com/us/eserver/xseries
6.3 If you have any questions about this update, or problems
applying the update go to the following Worldwide Help Center
phone list index URL:
http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html
7.0 Trademarks and Notices
THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR
IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES
TO ANY PATENTS OR COPYRIGHTS.
8.0 Disclaimer
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.