
				File Name: README.TXT

IBM xSeries 450/455 Diagnostics 
System 8688/8855

Version 2.08, Build ID: MZYT28A
                     

CONTENTS

1.0  Overview
2.0  Change history
3.0  Installation and Setup Instructions
3.1  File placement for flashing
3.1.1  Mapping the EFI System Partition from Windows(TM)
3.1.2  Mapping the EFI System Partition from Linux(R)
3.2  Troubleshooting
4.0  Running the diagnostics
5.0  Unattended Mode
6.0  Web sites and support phone number
7.0  Trademarks and Notices
8.0  Disclaimer 

1.0 Overview

This README file contains the latest information about installing
the IBM xSeries 450/455 Diagnostics.  The contents of this file are
intended for system installers, administrators, and servicers.


2.0 CHANGE HISTORY

2.1  Version 2.08 - MZYT28A:
     o Restore RXE-100 tests in the scalability ports diagnostic.
2.2  Version 2.07 - MZYT27A:
     o Remove RXE-100 tests in the Scalability ports diagnostic. 
2.3  Version 2.06 - MZYT26A: 
     o correct Scalability port diagnostic error on known good port. 
2.4  Version 2.05 - MZYT25A: 
     o Correct memory mirroring problem with mixed technology memory dimms.
2.5  Version 2.04 - MZYT24A: 
     o In the memory test the diagnostic will analyze each port status individually,
       eliminating incorrect fru callouts.  
     o Corrected message during memory test.   
2.6  Version 2.03 - MZYT23A: 
     o Correct message during ATAPI R/W test. 
2.7  Version 2.02 - MZYT22A: 
     o Increase buffer space for GetMemoryMap function.
       Used in releases mem_64test and memmir_64test. 
2.8  Version 2.01 - MZYT21A: 
     o Update Copyrights
     o DVD diagnostic searches for correct media after cancel selected
2.9  Version 2.0 - MZYT20A: 
     o Added multinode support
2.10 Version 1.0: 
     o Initial release


3.0 INSTALLATION and SETUP INSTRUCTIONS

1. Place the diagnostic image file, whose name will start with
   MZYT, onto the root of any EFI-visible filesystem.  See 
   "3.1 File placement for flashing" for further details.
2. Boot or reboot your system to the EFI Boot Selection menu
   and choose the "Flash Update" option.  
3. From within the Flash Update Utility, select the option 
   entitled "Update Diagnostic".          
4. The Flash Update Utility should detect the presence of the
   file and update the flash.  Ensure that the filename in
   the Flash Update Utility is the same as the file you are
   attempting to flash.
5. When prompted, press Enter to restart your system.  If the
   system does not restart, manually restart the system.

3.1 File placement for flashing

In order for the Flash Update Utility to recognize the diagnostic
image file to be flashed, the image must be placed in the root of
an EFI-visible filesystem.  This can be achieved by placing the 
file on a CD-ROM, LS-120/240 diskette, or onto a FAT filesystem on
an installed SCSI hard file in the system.  Every system with an 
operating system (OS) installed is required to have a FAT-
formatted EFI System Partition.  
For details on how to transfer files from an OS environment into 
this partition, see "3.1.1 Mapping the EFI System Partition from
Windows" or "3.1.2 Mapping the EFI System Partition from Linux".
Whichever method you choose for making the flash file visible in 
EFI, make certain that the file is placed in the root of the 
device you are transferring it to.  Placing the file in a 
sub-directory will cause it to not be recognized by the Flash
Update Utility.

3.1.1 Mapping the EFI System Partition from Windows

In Windows, the EFI System Partition is normally hidden from user
view.  To make it visible for file transfer purposes, boot the 
system, login with Administrator privilege and do the following:

1. Launch a Command Shell window.
2. At the shell prompt, type

     mountvol <drive letter>: /S

   where <drive letter> is an available drive letter of your 
   choosing.  For example, mountvol z: /S will mount the EFI 
   System Partition to drive letter z.
3. Copy the diagnostic image file into this drive.  It will then 
   be visible from the Flash Update Utility upon system reboot.

3.1.2 Mapping the EFI System Partition from Linux

For Linux installations, the EFI System Partition is normally 
mapped.  To identify the filesystem and its mount point, boot the
system to multiuser, login with root privilege, and do the 
following:

1. Start a shell.
2. At the shell prompt, type

     cat /etc/fstab

   The EFI System Partition will generally be the 0 partition of 
   the disk containing the root filesystem.  For example, if / is
   mounted on /dev/sda1, then /dev/sda0 will likely be the EFI 
   System Partition.
3. At the shell prompt, type

     mount /dev/sda0

   to mount this filesystem.  You will have to substitute the 
   /dev/sd identifier you discovered in the previous step in this
   command.
4. Copy the diagnostic image file into this filesystem at its 
   mount point.  It will be available to the Flash Update Utility
   at the next reboot of the system.

3.2 Troubleshooting
                
If the Flash Update Utility exits immediately upon selecting
"Update Diagnostic", the most likely problem is that the file
is not visible to the EFI filesystem driver.  Please verify
that the file is visible within EFI and is in the root of the 
device that you are flashing from.

If there is any other error in updating the IBM ROM Diagnostics 
software, repeat the installation steps (see "3.0 INSTALLATION").
If problems persist, contact IBM Service (see "5.0 WEB SITES AND
SUPPORT PHONE NUMBER").

4.0 RUNNING THE DIAGNOSTICS

Upon system restart, after flashing of the ROM, the ROM 
Diagnostics package may be invoked from the EFI Boot Manager using
the menu selection entitled "Diagnostic".

Alternatively, if the system can be booted to an EFI shell 
environment, the ROM Diagnostics will be located in a 
memory-mapped filesystem, which will be mounted in the shell 
environment.  To launch the ROM Diagnostics from a command-line, 
type 

     amidiag

at the EFI shell prompt.

5.0 UNATTENDED MODE

Refer to the "SAL/EFI Flash Update Utility release notes" for 
details on unattended installation of the ROM Diagnostics. 


6.0 WEB SITES AND SUPPORT PHONE NUMBER

If you have any questions about this update, or problems applying
the update, consult the following URLs:

o  IBM Support Web Site: http://www.pc.ibm.com/support
o  IBM xSeries Web Site: 
   http://www.ibm.com/eserver/xseries 
o  Help Center World Telephone Numbers and URL:
   http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html.

7.0 TRADEMARKS and NOTICES

7.1 The following terms are trademarks of the IBM Corporation in
      the United States or other countries or both:
o IBM
o xSeries    

7.2 Microsoft, Windows, and Windows NT are trademarks of Microsoft
    Corporation in the United States, other countries, or both.

7.3 Linux is a registered trademark of Linus Torvalds.

7.4 EFI is a registered trademark of Intel Corporation.

7.5 Other company, product, and service names may be trademarks
    or service marks of others. 

8.0 DISCLAIMER

8.1 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.2 Note to Government Users

    Note to U.S. Government Users -- Documentation related to
    restricted rights -- Use, duplication or disclosure is
    subject to restrictions set forth in GSA ADP Schedule
    Contract with IBM Corporation.


