IBM eserver xSeries 366 Linux BIOS Update Version 1.05 (Build ID ZUJT39A) 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 x366/x460/x260 POST/BIOS. 1.2 Limitations - NA 1.3 Enhancements - NA 1.4 Level of Recommendations and Prerequisites for the Update: - See the list of changes for information to determine whether or not you are affected by the enhancements and fixes. 1.5 Dependencies - BMC Firmware Version 1.5 (ZUBT22A) or higher is REQUIRED to be used with BIOS version 1.03 (ZUJT30A) and higher. Using a BMC version of 1.4 or lower and/or in combination of BIOS 1.03 or higher will result in a loss of RSA II related menus/information items in the F1 POST/BIOS Setup Utility and/or a loss of communication between POST/BIOS and the RSA II. 2.0 Change History V1.05 - August 2, 2005 (Build ID ZUJT39A) -------------------------- - BIOS changed to force symetric routing between nodes. This supports missing cables or nodes. V1.04 - July 15, 2005 (Build ID ZUJT37A) -------------------------- - Initial support for the IBM xSeries x260. - Added support for IBM xSeries x460 4 and 8 node configurations. V1.03 - May 13, 2005 (Build ID ZUJT30A) -------------------------- - Initial support for the IBM xSeries x460. V1.02 - March 31, 2005 (Build ID ZUJT26A) -------------------------- - Changed default setting for "RSA II Disable Periodic SMI Generation" to Enabled to prevent from RSA II from generating a 15 minute SMI. This periodic SMI is not currently used on the x366/x460 and should be defaulted to disabled. - Fix to prevent system from generating a NMI if a PCIX Correctable Threshold has been reached. The system will now properly generate a PFA alert if this condition occurs. - Fix to allow the Automatic BIOS Recovery feature to properly recover from a catastrophic POST/BIOS flash update failure. - Fix to modify the POST/BIOS USB CHS translation to be compatible with that used by most laptops. This will require specific USB keys which were bootable before on the x366/x460/x260 to be re-created. - Change to increase performance when running Windows Server 2003 and using the performance monitor application. This fix will also resolve a timer skew issue when running SAP. - Fix to properly send the BMC the correct system time during POST/BIOS operation between the hours of 19:00:00 and 00:00:00. - Fix to prevent a possible system hang when booting from a locally attached USB floppy device. V1.01 - March 7, 2005 (Build ID ZUJT23A) -------------------------- - Fix required to prevent system hang during Broadcom PXE ROM execution when Serial Over Lan session is active with the BMC. - Fix required to prevent intermittent "1602 System Management Adapter Communication" error when the RSA II adatper is installed and AC power has been applied. - Fix required to allow the RSA II "Vital Product Data" section of the web interface to properly show the system serial number and machine type. - Fix to prevent POST/BIOS from intermittently reporting and disabling memory DIMMs during memory configuration during repeated warm boot or AC cycles. V1.00 - March 1, 2005 (Build ID ZUJT21A) -------------------------- - Initial release 3.0 Installation and Setup Instructions 3.1 Step by step instructions for this code update - Run the "IBM eserver xSeries 366 Linux BIOS Update" with the following command line: "./.sh -s" where .sh is the downloaded update. NOTE: The following message is shown on RedHat Enterprise Linux 3.0 and other distributions that do not install the compatibility libstdc++ library. ./lflash: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory. If the above message is shown, install the compat-libstdc++*.rpm that was included on the distribution media. 3.2 Step by step instructions for extracting the Linux update files. - Run the "IBM eserver xSeries 366 Linux BIOS Update" with the following command line: "./.sh -x " where .sh is the downloaded update and is the path to which the Windows update files will be extracted. NOTE: The following message is shown on RedHat Enterprise Linux 3.0 and other distributions that do not install the compatibility libstdc++ library. ./lflash: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory. If the above message is shown, install the compat-libstdc++*.rpm that was included on the distribution media. - The files extracted are all the files that are necessary to perform a BIOS update under Linux. Run "./lflash" from a command line to update BIOS in 32-bit Linux or run "./lflash64" from a command line to update BIOS in 64-bit Linux. - To flash the backup BIOS, run "./lflash -2". NOTE: On 366, the OSA IPMI Device Driver and the IBM Mapping Layer for OSA IPMI Device Driver are required to flash the BIOS. 3.3 Step by step instructions for extracting the DOS update files to diskette. - Run the "IBM eserver xSeries 366 Linux BIOS Update" with the following command line: "./.sh -xd " where .sh is the downloaded update and is the path to which the Windows update files will be extracted. If is omitted, /dev/fd0 is assumed. NOTE: The following message is shown on RedHat Enterprise Linux 3.0 and other distributions that do not install the compatibility libstdc++ library. ./lflash: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory. If the above message is shown, install the compat-libstdc++*.rpm that was included on the distribution media. - The diskette created is the DOS BIOS update diskette. 4.0 Configuration Information 5.0 Unattended Mode 5.1 Performing the update in unattended mode - Run the "IBM eserver xSeries 366 Linux BIOS Update" with the following command line: "./.sh -s" where .sh is the downloaded update. NOTE: The following message is shown on RedHat Enterprise Linux 3.0 and other distributions that do not install the compatibility libstdc++ library. ./lflash: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory. If the above message is shown, install the compat-libstdc++*.rpm that was included on the distribution media. 5.2 Extracting the Linux update files in unattended mode - Run the "IBM eserver xSeries 366 Linux BIOS Update" with the following command line: "./.sh -x " where .sh is the downloaded update and is the path to which the Linux update files will be extracted. NOTE: The following message is shown on RedHat Enterprise Linux 3.0 and other distributions that do not install the compatibility libstdc++ library. ./lflash: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory. If the above message is shown, install the compat-libstdc++*.rpm that was included on the distribution media. - The files extracted are all the files that are necessary to perform a BIOS update under Linux. Run "./lflash" from a command line to update BIOS on 32-bit Linux or run "./lflash64" from a command line to update BIOS on 64-bit Linux. 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/ 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 Schedule 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 PATENTS OR COPYRIGHTS.