IBM xSeries 345 POST/BIOS Flash Disk Version 1.13 Installation README File CONTENTS ________ 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Unattended Mode 6.0 Web Sites and Support Phone Number 7.0 Trademarks and Notices 8.0 Disclaimer 1.0 Overview 1.1 This README file contains the latest information about installing the IBM xSeries 345 POST/BIOS. 1.2 Limitations: N/A 1.3 Enhancements: - This updated Flash disk contains support for both 400 MHz- based and 533 MHz-based systems. In order to prevent the Flash update of 400 MHz POST/BIOS to new 533 MHz-based systems, the Flash image file name on the diskette has been changed. This will allow the newer POST/BIOS to be updated to older systems, but it will not allow older POST/BIOS to be updated to new systems. Additionally, the POST/BIOS image file size has increased from 256 KB to 384 KB because of new support for RSA II, as well as booting from USB CDROM and diskette drives. These are the guidelines for using Flash Disks with various types of systems: 1. Older 533 MHz-based systems shipped with 256 KB POST/ BIOS images (Version 1.05 or 1.06) will accept either 256 KB or 384 KB POST/BIOS images, but they should not be updated with 256 KB/400 MHz-based images (Version 1.04 or earlier). 2. New 533 MHz-based systems shipped with 384 KB POST/BIOS (Version 1.07 or later) will accept only 384 KB images using a new Flash Disk. 3. New 384 KB/533 MHz-based POST/BIOS images may be loaded on all systems (including 400 MHz-based systems) using a new Flash Disk. 4. After any system has been updated with a 384 KB/533 MHz- based image, an older 256 KB/400 MHz-based Flash Disk may not be used to load an older POST/BIOS image. This is how to back down to an older POST/BIOS image: - Copy the old POST/BIOS image file (named $0042000.FLS) to the new Flash Disk. - Rename the $0052000.FLS file on the new Flash Disk to something different. - Rename the $0042000.FLS file on the new Flash Disk to $0052000.FLS. - Run the Flash update as usual with the new Flash Disk. WARNING: Do not load any 400 MHz-based POST/BIOS image (Version 1.04 or earlier) on a 533 MHz-based system. 5. It is not recommended to keep a mixture of 256 KB and 384 KB POST/BIOS images in the Flash ROM; therefore, you should update the ROM backup image to match the primary image after making a change to the primary image size (and then verifying the new primary image is booting properly). The new Flash utility contains warning messages to inform you when a size mismatch will occur, and also when a size mismatch exists. 1.4 Recommendations and Prerequisites for the Update: - Ensure you have Integrated System Management Processor firmware version 1.05 (or later) prior to installing this POST/BIOS update. - Refer to the list of changes below to determine whether you are affected by the enhancements and fixes. 1.5 Dependencies - Version 1.08 (or later) is required for systems using RSA II. 2.0 Change History V1.13 - September 4, 2003 ------------------------- - Fixed INT 13h, Function 4B01h, for USB CD-ROM drives. - Fixed Red Hat 2.1 Advanced Server install. - Fixed writes to Remote Floppy with RSA II installed. - Removed 162 error when mouse added with Keyboardless Operation enabled. - Updated firmware for CPU IDs F27 and F29. V1.12 - July 14, 2003 --------------------- - Fixed chipset erratum for integrated ServeRAID support. V1.11 - June 27, 2003 --------------------- - Added support for CPU ID F25 (with 1 MB L3 cache). - Fixed false I9990301 error when USB Legacy disabled. - Fixed minor SMBIOS structure issues. V1.10 - May 29, 2003 -------------------- - Fixed various chipset errata. - Removed 301/8603 POST errors when USB keyboard attached with Keyboardless Operation enabled. - Removed 3 MB reserved memory regions when no RSA installed. - Updated SCSI BIOS to fix intermittent checkpoint 1E hangs. - Updated SMBIOS Type 20 structure memory addresses. V1.09 - April 22, 2003 ---------------------- - Added firmware for CPU ID F29. - Added Enhanced Memory support for 533 MHz-based systems. - Added video VPD support for RSA II. - Disable USB and ECC Diagnostics tests from RSA II remote session. - Identify single DIMM in error isolation. - Preserve PCI LED status until AC power is removed. - Read current RSA II setting for OS USB Selection. V1.08 - March 24, 2003 ---------------------- - Added support for Diagnostics VPD display from Director and RSA II utility. - Changed RSA II Settings menu layout in Setup. - Fixed 32-bit Power Management Timer flag for ACPI support. - Fixed saving RSA II IP address settings from Setup. - Updated firmware for CPU ID F24. V1.07 - March 10, 2003 ---------------------- - Added boot support for USB CDROM and diskette drives. - Added Front-side Bus speed display in Setup. - Added hardware flow control option for Remote Console Redirection. - Added RSA II support. - Added Setup option for PXE option ROM priority. - Added VT100 keyboard emulation for Remote Console Redirection. - Changed the default Flash image file name to "$0052000.FLS". - Changed Setup to plain grey background. - Disabled power switch in early POST to prevent improper shutdown. - Fixed 1602 POST error code (RSA cable not present). - Fixed ACPI BIOS warnings in Windows Event Viewer. - Fixed BIOS VPD structure checksum. - Fixed improper detection of changes in Setup. - Fixed more chipset errata. - Fixed lighting of PCI Bus LEDs for PCI errors. - Fixed remote diskette boot issues. - Fixed Wake-up Type in SMBIOS Type 1 structure. - Improved Wake on LAN after improper shutdown. - Increased FLS file size to 384 KB. - Removed LS-120 boot support. - Updated CPU mismatch POST error (199) handling. - Updated firmware for CPU ID F27. - Updated Flash Utility to handle 384 KB images. - Updated help text for System MAC Addresses menu. - Updated LSI (on-board SCSI) ROM image for INT 13h bug fix. V1.06 - January 20, 2003 ------------------------ - Added workaround for system hang using RDM with RSA installed. V1.05 - January 3, 2003 ----------------------- - Added EMM386 support for remote diskette boot. - Added support for 533 MHz-based chipset and CPUs. - Fixed INT 1Ah function to set Real-Time Clock alarm. - Fixed PCI interrupt routing to assign values from Setup menu. - Fixed various chipset errata. - Removed non-US language files. - Updated firmware for Xeon C-1 stepping (CPU ID F27). - Updated PCI error handling. - Updated PXE BIOS to latest version. - Updated reserved resources for ACPI-based operating systems. V1.04 - December 10, 2002 ------------------------- - Added 164 event logging for memory size changes. - Added CPU Prefetch Queue option in Setup. - Added MAC address display in Setup. - Added remote diskette boot support. - Added Front-side-bus parity error handling. - Improved reporting of single-bit memory errors. - Fixed ASF Stop Watchdog command. - Fixed BIOS revision display in RSA utility. - Fixed event logging for PERRs. - Fixed Flash Update Utility bugs. - Fixed Remote Console Redirection bugs. - Fixed RSA remote POST keyboard issues. - Fixed SMBIOS planar device reporting. - Updated SCSI BIOS for tape drive support. V1.03 - September 11, 2002 -------------------------- - Enabled CPU(s) Prefetch Queue to improve performance. - Updated firmware for Xeon C-1 stepping (CPU ID F27). V1.02 - August 15, 2002 ----------------------- - Updated LSI (on-board SCSI) firmware. V1.01 - August 14, 2002 ---------------------- - Added Setup option to disable hyperthreading. - Added support for Xeon C-1 stepping level processors. - Added support for 1301 POST error. - Added local disk support under remote floppy boot. - Updated PXE BIOS. - Updated SCSI BIOS. - Fixed keyboard use during remote boot. - Fixed VPD display in Setup. - Fixed SMBIOS structures. - Fixed ISMP communication after 3-boot fail. - Fixed potential reset problems. - Fixed warm-boot immediately after enabling on-board SCSI. - Fixed other miscellaneous errors. V1.00 - June 28, 2002 --------------------- - Initial release. 3.0 Installation and Setup Instructions *Note: If installing from an update package, see additional instructions, in Appendix A. The procedure to update the POST/BIOS is as follows: 3.1 Insert the "IBM xSeries 345 POST/BIOS Flash Disk" into drive A. 3.2 Start up or restart your IBM xSeries 345 server. 3.3 The system will boot from the disk and present a menu which allows you to choose from various update options. Choose "1 - Update POST/BIOS". 3.4 You will be asked if you would like to move the current POST/BIOS image to the backup ROM location. If you select 'Y', the current code will be flashed in to the backup bank immediately. 3.5 If the current system POST/BIOS supports the Asset Tag feature, you will be asked if you would like to change it. If you select 'Y', you will be able to enter a new number. 3.6 You will then be asked if you would like to save the current code to a disk. If you select 'Y', you need to have a formatted disk already available, or specify a fully qualified path and file name. 3.7 You will then have a final opportunity to proceed with the Flash update or exit the utility. If you proceed, the utility will update the Flash ROM with the new code. When this is complete you will be prompted to remove the diskette and press Enter to reboot the system. 4.0 Configuration Information 5.0 Unattended Mode 5.1 Steps for unattended mode. 5.1.1 Clear the read-only attribute of CONFIG.SYS on the Flash Diskette. 5.1.2 Modify CONFIG.SYS on the Flash Diskette to read: "SHELL=FLASH2.EXE /u /r *" 5.1.3 Reboot the system with the Flash Diskette in Drive A: * Note: An optional parameter of "/a:" can be added to allow for storing a system Asset Tag number where "" is replaced with up to a 32-character string. 6.0 Web Sites and Support Phone Number 6.1 IBM Support Web Site: http://www.pc.ibm.com/support 6.2 IBM Marketing Web Site: http://www.pc.ibm.com/ww/eserver/xseries/ 6.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html. 7.0 Trademarks and Notices 7.1 IBM and the e(logo) are registered trademarks of International Business Machines Corporation. 7.2 U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Contract with IBM Corporation. IBM web site pages may contain other proprietary notices and copyright information which should be observed. 8.0 Disclaimer 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 PANTENTS OR COPYRIGHTS. Appendix A: Package Specific Installation Instruction This update is packaged as a self-extracting PackageForTheWeb (PFTW) executable file. To unpack, this update requires that your TEMP environment variable be set to a path with read/write access. You must be logged in as an administrator. The package update log, ux.log, is created on the system drive. To locate the log file go to: %SystemDrive%\uxlog\ux.log The command-line syntax for PackageForTheWeb firmware update package is: Package.exe [-s] [-a [-s] | [-r] | [-c] | [-x directory] | [-xd] | [-w] | [-?] ] [-s] This command installs the Package-For-The-Web software silently and does not prompt if files are to be over-written in the %temp% directory. [-a] This command passes all subsequent commands to the PFTW software to install the update package. [-s] This command runs a silent and unattended update. For firmware updates, the update is scheduled to run on the next reboot. An immediate reboot can be forced with the -r option. [-r] This command schedules the update and reboot immediately. It can be used with or without the -s command. [-c] This command cancels any scheduled firmware update and records results of this operation in the log file. Only one firmware package can be scheduled at a time, if a firmware update needs to be applied instead of the currently scheduled firmware update package, cancel the current (run with the -c option on any firmware package) package. Then, run the applicable firmware package. [-x directory] This command is used with firmware updates to extract the update to the directory named directory. The PackageForTheWeb executable extracts itself to a subdirectory in the %TEMP% directory, a relative directory will be relative to that location. You must specify an absolute directory if you do not want to use the default directory. [-xd] This command is used with firmware updates to extract to a floppy diskette. The floppy diskette can then be used to boot from and apply the update. This option is not available for all firmware updates, such as tape drive and hard-disk drive updates. [-w] PowerQuest Virtual Boot Environment requires that there are 2 free sectors on the first track before it can schedule a firmware update. Use this option only if scheduling an update failed because 2 free sectors were not available on the first track. This option clears the non-boot and the non-partition information sectors on the first track. Typically, these sectors are not used. Before clearing the sectors a copy of the complete first track is saved in the %temp% directory from which the update runs. [-?] This command displays information about the command line switches. The command line switches -s, -r -c and -e are unnattended. Other command line options such as display help (-?) might require that you hit any key to continue. If Windows packages are run without any command line options, a GUI is displayed. This GUI offers all of the options that are available using the command line.