AlphaServer 4100/4000 Firmware Release Notes For Compaq Tru64 UNIX, DIGITAL UNIX and OpenVMS Customers Revised September, 2001 SRM Console Version: V6.0-4 These release notes are for the V6.0-4 SRM console, and include documented restrictions in V6.0-4. Firmware update instructions and other useful information is also provided. Firmware release notes for Windows NT AlphaServer 4100/4000 customers are available separately.
January, 2001 The information in this publication is subject to change without notice. COMPAQ, the Compaq log, DEC, the DEC logo, AlphaServer and VMS registered in U.S. Patent and Trademark office. OpenVMS, Tru64, are trademarks of Compaq Information Technologies Group, L.P. in the United States and/or countries. Microsoft and Windows NT are trademarks of Microsoft Corporation in the United States and/or other countries. Unix is a trademark of The Open Group in the United States and/or other countries.
Contents PREFACE CHAPTER 1 FIRMWARE UPDATE INFORMATION v 1–1 1.1 FIRMWARE AND OPERATING SYSTEM REVISION MATRIX 1–2 1.2 CONSOLE FIRMWARE COMPONENTS AND REVISION INFORMATION 1–3 PCI I/O OPTION FIRMWARE COMPONENTS - REVISION INFORMATION 1–4 1.4 CONFIGURATION UTILITY KIT AND VERSION INFORMATION 1–4 1.5 ALPHA SYSTEMS FIRMWARE QUARTERLY UPDATE KIT 1–5 1.6 ACCESSING FIRMWARE OVER THE INTERNET 1.6.1 Proper Transfer Types For Use With FAT-Format Floppy Updates 1–5 1–6 1.
Contents 2.2.3 2.2.4 2.2.5 2.3 Updating Using a FAT-Formatted Floppy Diskette Updating Using an ODS2-Formatted Floppy Diskette Updating Off Network Via Your Local MOP Server 2.2.5.1 Updating Off Network via BOOT command • 2–5 2.2.5.2 Updating Off Network via LFU command • 2–5 PERFORMING THE UPDATE CHAPTER 3 THINGS YOU SHOULD KNOW THE FIRST TIME YOU POWER ON YOUR MACHINE 2–6 3–1 3.1 MEMORY TESTS CAN TAKE A VERY LONG TIME! 3–1 3.2 SELECTING WHICH CONSOLE IS LOADED AND YOUR DISPLAY DEVICE 3–1 3.
Contents 3.9.1 3.9.2 3.10 Set EW*0_Mode Auto-Negotiate Behavior Note on Systems with Multiple DE500’s NOTE ON UNIX INSTALLATIONS CHAPTER 4 RUNNING EISA, RAID, AND OTHER CONFIGURATION UTILITIES 3–8 3–8 3–9 4–1 4.1 SETTING UP YOUR SYSTEM TO RUN ARC-BASED UTILITIES 4–1 4.2 USING A SERIAL LINE INTERFACE TO RUN ARC-BASED UTILITIES 4–1 4.3 RESTRICTIONS WHEN RUNNING KZPSA UTILITIES 4–2 APPENDIX A RESTORE_NVRAM AND SAVE_NVRAM A–1 A.1 SAVE NVRAM DATA IN EEROM/TOY TO A FLOPPY FILE. A–1 A.
Preface Purpose of These Release Notes These release notes are intended for users of the AlphaServer 4100 and AlphaServer 4000 cabinet- and pedestal-style systems. Henceforth in these notes, "4100" will be used to refer to both the model 4100 and model 4000. These release notes also support the DIGITAL Server 7000 Models 7300, 7305 and 7310.
Preface Conventions Used in This Guide This document uses the following conventions: vi KEY Indicates a key on your keyboard. CTRL/key Indicates control characters. For example, Control C is shown as CTRL/C and indicates that both the CTRL and the C must be pressed simultaneously.
1 Firmware Update Information This chapter provides firmware and utility revision information, as well as information on where to find firmware update images and documentation for your AlphaServer 4100 system. Firmware updates are performed using the SRM console’s built-in LFU utility. Bootable LFU images are also supported, e.g. when booting the firmware update CD. LFU supports multiple update devices: local SCSI CD-ROM (CDA0), local floppy (DVA0), and local network (EWA0).
Firmware Update Information 1.1 Firmware and Operating System Revision Matrix Table 1–1 lists operating system versions supported by SRM console. The firmware from this release is on the Alpha Systems Firmware Update V6.0 CD. Table 1–1 AlphaServer 4100 Firmware/Software Revision Matrix Alpha Systems Firmware Update CD Release V6.0 V5.9 V5.8 V5.7 Date June-01 Jan.-01 Aug.-00 Apr.-00 SRM Firmware V6.0-4 V5.9-5 V5.8-2 V5.7-4 AlphaBIOS Firmware V5.70-0 V5.70-0 V5.70-0 V5.
Firmware Update Information 1.2 Console Firmware Components and Revision Information The AlphaServer 4100 is shipped with two console images - the SRM console for Compaq Tru64 UNIX, DIGITAL UNIX and OpenVMS Alpha customers and the AlphaBIOS console for Windows NT customers and for running ARC-based utilities. The SRM console update image (RHSRMROM.SYS) is a compressed file which contains the following individual firmware images: Table 1–2 V6.
Firmware Update Information user enters the SRM console ALPHABIOS command at the SRM console prompt. AlphaBIOS is a separate, compressed image and is separately updatable using LFU. In general, both the SRM and AlphaBIOS consoles should be updated at the same time since the two images which ship on the update CD-ROM are typically qualified against one another. 1.
Firmware Update Information Table 1–5 Configuration Utility Revisions Utility Kit No. Part No. Minimum Rev. ECU (VMS/UNIX) QA-01YAA-HC AK-Q2CRH-CA V1.9 RCU QB-2XHAH-SB – V3.2 KZPSA Utilities - FWUPDATE.EXE V1.4 1 - CNFGDIAG.EXE V1.5 1 1 Using earlier versions of the KZPSA utilities on your AlphaServer 4100 will corrupt your KZPSA adapter’s NVRAM and render your system unusable! 1.5 Alpha Systems Firmware Quarterly Update Kit The Alpha Systems Firmware Update Kit ships on a CD-ROM.
Firmware Update Information The above-mentioned readme.html file describes the overall firmware directory structure and how the files can be downloaded and used. Note: Make sure you copy all of the necessary files when downloading firmware images. If updating via network (MOP), you will need to modify the copied files’ attributes before they can be used in a MOP server environment. See Chapter 2 for details on downloading firmware and performing firmware updates. 1.6.
2 Firmware Update Instructions The following sections provide instructions for updating your system firmware. 2.1 Updating Your System Firmware The SRM console’s built-in loadable firmware update utility (LFU) is used to update your console firmware (SRM and AlphaBIOS consoles). LFU can also be booted as a monolithic image off an update CD (e.g. using the Alpha Firmware Systems Update CD-ROM). IMPORTANT NOTE: Beginning with SRM V5.
Firmware Update Instructions 2.2 Preparing For The Update If you don’t have access to the Alpha Systems Firmware Update CD, you’ll need to copy the appropriate firmware files to a local computer system. You will first need to locate the appropriate firmware update files. Look in http://ftp.digital.com/pub/Digital/Alpha/firmware/V6.0 for the /as4x00, /options, and /doc subdirectories for the files you’ll need. The list of files required is provided below.
Firmware Update Instructions 5 Update AlphaBIOS 6 Exit LFU If you update via the "BOOT" command from either the CD-ROM, (eg. "P00>>>boot dka500") or from your local MOP server’s MOM$LOAD directory (e.g. "P00>>>boot ewa0 -fi as4100_V6_0 -fl 0,0"), then it will not be necessary to run the update twice. NOTE:: A downgrade to any previous version of firmware will require performing the update procedure twice for all methods of update. 2.2.2 Updating Using the Alpha Systems Firmware Update V6.
Firmware Update Instructions • Copy the following files to diskette #2: rhsrmrom.sys • Copy the following files to diskette #3 if you’ll be updating I/O option firmware: as4x00io.sys rhreadme.sys cipca420.sys dfxaa320.sys kzpsaa12.sys Be sure to copy all of the aforementioned files for the diskette(s) you need. Once created your diskettes can then be used to update firmware by invoking the update utility via the LFU command. 2.2.4 Updating Using an ODS2-Formatted Floppy Diskette For V5.
Firmware Update Instructions If creating a diskette for updating your I/O option firmware only: $! $! make_rhods2io.com $! $ inquire ignore "Insert blank HD floppy in DVA0, then continue" $ set verify $ set proc/priv=all $ init /density=hd/index=begin dva0: rhods2io $ mount dva0: rhods2io $ create /directory dva0:[as4x00] $ create /directory dva0:[options] $ copy as4x00fw.sys dva0:[as4x00]as4x00fw.sys $ copy as4x00io.sys dva0:[as4x00]as4x00io.sys $ copy rhreadme.sys dva0:[as4x00]rhreadme.
Firmware Update Instructions Make sure the files will be accessible via your target AlphaServer 4100 system. Also, be sure not to change the names of any files if using the SRM console LFU command update method. Downloaded files require an additional step for MOP loads; the file attributes must be modified to a proper VMS fixed-record format. Use the following OpenVMS command on each downloaded file before using the files for MOP booting. $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) *.sys 2.
Firmware Update Instructions • If network, answer "AS4X00FW", "AS4X00CP", or "AS4X00IO" depending upon whether you want to update all firmware (console + I/O option), only console, or only I/O option, respectively. NOTE:: For firmware updates, via the LFU command update method, on a system running any version of firmware prior to V5.3, you must perform the update procedure twice. The first update for the SRM console firmware and the second update for the AlphaBIOS firmware.
Firmware Update Instructions AlphaBIOS DO NOT ABORT! Updating to V5.68-0... ........ Verifying V5.68-0... PASSED. UPD> up srm* WARNING: updates may take several minutes to complete for each device. Confirm update on: srmflash srmflash [Y/(N)] y DO NOT ABORT! Updating to V5.4-1... .......... Verifying V5.4-1... PASSED. UPD> exit Initializing... A sample session is provided below of an update of SRM console from V5.31 to V5.4-1 and AlphaBIOS V5.67-0 to AlphaBIOS V5.68-0.
Firmware Update Instructions Starting Firmware Update Utility Copying source: to 1243000 from 3110200 size 1a6e00(1732096) Unpacking firmware files as4x00_readme adr = 1000020 len = 1600(5632) readme adr = 1001840 len = 1600(5632) srmrom adr = 1003060 len = 10f800(1112064) arcrom adr = 1112a80 len = 80000(524288) ccmab_fw adr = 1192ca0 len = 80200(524800) cipca_fw adr = 12130c0 len = cf40(53056) dfxaa_fw adr = 13e9e20 len = 38a00(231936) kzpsa_fw adr = 1422a40 len = 74000(475136) ***** Loadable Firmware Up
3 Things You Should Know the First Time You Power On Your Machine It is recommended that you read this section in its entirety prior to using your AlphaServer 4100 machine. 3.1 Memory Tests Can Take a Very Long Time! Memory is tested by each CPU each time you power on or reset your machine. These tests can take upwards of several minutes on very large memory, single-CPU machines.
Things You Should Know the First Time You Power On Your Machine Note: you will not see any console display output on your VT or VGA display if CONSOLE is set to "GRAPHICS" until power-up testing and sizing has completed *and* VGA initialization has completed. This can take upwards of several minutes depending upon your system configuration.
Things You Should Know the First Time You Power On Your Machine Refer to the AlphaServer 4100 System Drawer User’s Guide for more details about configuring your machine prior to booting. Chapter 4 also provides a brief overview on running ARC-based utilities.
Things You Should Know the First Time You Power On Your Machine 3.4 SRM Console Firmware Supported Boot Devices The PCI I/O options/devices listed in Table 3–1 are supported as SRM console boot devices by the V4.8 or above SRM console: Table 3–1 Supported Boot Devices (SRM Console V4.
Things You Should Know the First Time You Power On Your Machine 3.6 4 Code changes have been implemented to correct a problem where crash dumps written to disks connected via a CIPCA adapter would fail to complete. Prior to V6.
Things You Should Know the First Time You Power On Your Machine 3.7.2 Effects of Window NT Serviceability support on the update process One of the most important changes, resulting from the implementation of Windows NT serviceability support, is the relocation of the AlphaBIOS to a different sector in flash ROM. This relocation was required to accomodate the space requirements for fatal error logging. All update methods, from a system running firmware prior to V5.
Things You Should Know the First Time You Power On Your Machine 3.8 Additional notes for KZPSA changes implemented with the V5.1 release The driver code used for KZPSA adapters was changed resulting in the controller being represented as "pks" and no longer represented as "kzpsa". Several changes to command usage change with use of this PKS driver. • LFU updates under the V5.1 SRM console or later will no longer use the UPD>UPDATE KZPSA* command but will use UPD>UPDATE PKS* command.
Things You Should Know the First Time You Power On Your Machine line speed of auto-negotiation supported devices on the other end of an ethernet wire. Important: Auto-negotiate mode is NOT RECOMMENDED if you know the speed of your ethernet because of possible considerable delay when booting or when restarting the operating system.
Things You Should Know the First Time You Power On Your Machine 3.10 Note on UNIX installations When installing DIGITAL UNIX from the graphics console, the screen may scroll past the following instructions to set console environmental variables and to boot the operating system.
4 Running EISA, RAID, and Other Configuration Utilities NOTE:Relocation of AlphaBIOS to a different sector in flash ROM was implemented in the 5.3 release. Please ensure you have read Chapter 2. Of particular importance is the change for updating the SRM and AlphaBIOS firmware. Failure to have followed the procedure properly will invalid the AlphaBIOS image. This invalid image problem is corrected by excuting the LFU a second time and updating the AlphaBIOS.
Running EISA, RAID, and Other Configuration Utilities 4.3 Restrictions When Running KZPSA Utilities You must use V1.4 of the KZPSA Firmware Update Utility (FWUPDATE.EXE) if you wish to use it rather than LFU to update your KZPSA firmware. Note: running earlier versions of the KZPSA FWUPDATE.EXE utility will corrupt the NVRAM on your KZPSA and disable the module and your system! Restrictions also exist if using the KZPSA CNFGDIAG.EXE utility. For one, you must use version V1.
A RESTORE_NVRAM and SAVE_NVRAM A.1 Save NVRAM data in EEROM/TOY to a floppy file. Save the system NVRAM data from 8KB EEROM and last 50 TOY RAM bytes onto a write-UN-locked FAT formatted floppy to a file. By default, if no script argument is specified, all NVRAM is saved to file ALLNVRAM.SAV. If the file already exists, then a copy of the original file is made to *.BAK. If that file exists, it is overwritten. Note, attempts to write to a write-locked floppy fail silently.
RESTORE_NVRAM and SAVE_NVRAM A.2 Restore NVRAM data to EEROM/TOY from a floppy file. Restore the system NVRAM data to 8KB EEROM and/or last 50 TOY RAM bytes from a floppy containing the NVRAM save file(s). By default, if no script argument is specified, all NVRAM is restored from file ALLNVRAM.SAV. Syntax restore_nvram {all,arc,srm,toy} Arguments group Specifies the group of NVRAM data to be restored.