AlphaServer DS20 V5.9 Console Firmware Release Notes Copyright 2000 Compaq Computer Corporation. COMPAQ, the Compaq logo, DEC, the DEC logo, DECPC, ALPHAbook, AlphaPC, AlphaStation, 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 other countries. Microsoft and Windows NT are trademarks of Microsoft Corporation in the Unites States and/or other countries. UNIX is a trademark of The Open Group in the United States and/or other countries. All other product names mentioned herein may be trademarks or registered trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is subject to change without notice. The limited warranties for Compaq products are exclusively set forth in the documentation accompanying such products. Nothing herein should be construed as constituting a further or additional warranty. 1 SCOPE 4 1.1 AUDIENCE 4 1.2 GOLDEN RULES ON UPDATING FIRMWARE 4 1.3 INTERNET ACCESS TO FIRMWARE 4 2 READ ME FIRST 5 2.1 CONSOLE CHANGES THIS RELEASE 5 2.1.1 Show Bios/Run Bios Console Commands 5 2.2 OPERATING SYSTEM/CONSOLE FIRMWARE REVISION MATRIX 5 2.3 KNOWN ANOMALIES 6 2.3.1 AlphaBIOS V5.70 requires HAL Revision G 6 2.3.2 When the Console KGPSA Driver starts. 7 3 FIRMWARE UPDATE PROCEDURE 7 3.1 UPDATE FIRMWARE FROM THE SRM CONSOLE 7 3.2 UPDATE FIRMWARE FROM THE ALPHABIOS CONSOLE 8 3.3 LOADABLE FIRMWARE UTILITY [LFU] COMMANDS 9 3.3.1 Update Command 9 3.3.2 List Command 9 4 USING THE FFAUTO AND FFNEXT ENVIRONMENT VARIABLES 10 4.1 BACKGROUND ON DEVICE STATES 10 4.1.1 Behavior of "Not Connected" Devices 10 4.1.2 Determining a "Not Connected" Device from an HSZ80 or HSG80 11 4.1.3 Determining a "Not Connected" Device from the SRM Console 12 4.2 FORCING THE CONSOLE TO USE A "NOT CONNECTED" DEVICE 12 4.2.1 Using FFAUTO to Autoboot a "Not Connected" Devices 12 4.2.2 Using FFNEXT on "Not Connected" Devices 14 1 Scope The document lists significant changes in this firmware release and describes methods to update console firmware and console-supported I/O options firmware. This document does not describe console firmware internals or console architecture. 1.1 Audience The audience for this document is intended for individuals responsible for operating system installations and upgrades, for console firmware updates and for (console-supported) I/O options firmware updates. 1.2 Golden Rules on Updating Firmware Update console firmware before installing or updating an operating system. Update both consoles (SRM and AlphaBIOS) to ensure compatibility with the associated operating system. SRM console firmware is used for Tru64 Unix and OpenVMS systems. AlphaBIOS console firmware is used for WindowsNT. After an operating system shutdown, always re-initialize the system before running the update utility. 1.3 Internet Access to Firmware Internet access to console firmware and to AlphaBIOS/HAL and NT Drivers. www.compaq.com/support/ (click on Alpha Systems under the "Downloadable Drivers & Utilities" menu). http://www.compaq.com/support/files/alphant/index.html (Current version of BIOS, HAL and NT Drivers) 2 Read Me First 2.1 Console Changes This Release The release notes and firmware are on the V5.9 Alpha Systems Firmware Update CD. This release contains the following: * OpenVMS V1.90 and Unix PALCode 1.86- improved memory scrubbing, ensure a double bit error detected during a crd flow for any kind of error will be turned into a machine check * Console recognition of the FCA-2354 Fibre Channel Host Bus Adapter * New AlphaBIOS V5.70b * Loadable Firmware Utility [LFU] no longer supports updating CCMAB memory channel firmware. * Console Environment Variables * pci_parity - previously only checked at console initialization, now checked during system shutdown so that the appropriate action is taken during an automatic reboot(this was affecting certain 3rd party graphic cards) * new - exx0_tftp_blocksize (e.g. ewa0_tftp_blocksize) - enables a client to negotiate tftp blocksize to allow downloading files between 32MB and 90MB. Blocksize is limited to 512, 1024 and 1450 bytes. Default value is 1024 and switches to 512 bytes when negotiating with servers that do not support rfc.1782 and 1783. * Bug fixes * DE6xx driver - fix auto-negotiate by negotiating the proper setting during a power up * DE60xx/DE5xx driver - fix "slow MOP booting" with KZPCM by setting receive process to one CPU 2.1.1 Show Bios/Run Bios Console Commands * show bios command lists the location of controllers with a BIOS expansion ROM. Not all controllers have a BIOS expansion ROM. show bios command will reset the I/O buses after execution. P00>>> show bios (use 0 or 1 for , default is 0) * run bios invokes the BIOS expansion ROM on a supported PCI controller (e.g. KZPCC-CE). This command is commonly used to invoke functions or utilities in the expansion ROM. For example, the KZPCC-CE uses the expansion ROM for its configuration utility. P00>>> show config (to get controller name) P00>>> run bios [controller name] e.g. P00>>> run bios pka0 When you enter the run bios command, the system first does a bus reset. You are then prompted to type a control sequence (e.g. Ctrl^D) to enter the PCI options' BIOS utility. The control sequence depends on the PCI option. Refer to the documentation supplied with the PCI option for information on running the utility. 2.2 Operating System/Console Firmware Revision Matrix The following matrix shows the minimum operating system version required with this console firmware release. Table 2-1 AlphaServer DS20 Operating System and Firmware Revision Matrix Firmware CD V5.8 January 2001 Operating System OpenVMS V7.1-2 + required patches Tru64 Unix V4.0F Windows NT V4.0 Console Firmware SRM Version V5.9-4 AlphaBIOS Version V5.70b 2.3 Known Anomalies 2.3.1 AlphaBIOS V5.70 requires HAL Revision G READ THIS BEFORE INSTALLING THE FIRMWARE AlphaBIOS 5.70 supports changes introduced in HAL Revision G for systems based on the Alpha 21264 CPU. You must install HAL Revision G on your system before attempting to install AlphaBIOS 5.70. Otherwise, the system will hang at boot time. See the AlphaBIOS 5.70 Section of the AlphaBIOS release notes for additional details. 2.3.2 When the Console KGPSA Driver starts. When the console KGPSA driver starts, you may see the error message "pga0.0.0.2.4 - Nvram read failed". See the WWIDMGR USERS MANUAL for information about formatting the NVRAM. 3 Firmware Update Procedure This chapter explains how to invoke the Loadable Firmware utility [LFU] to update AlphaServer firmware from the SRM or AlphaBIOS console. Firmware update information is also described in the Owners Guide. AlphaServer systems recently shipped may have a higher firmware revision than the firmware revision listed in this release. Do not load firmware that is older than what is presently installed. A higher firmware revision usually indicates support for the currently shipping operating system. The revision number of the console firmware and the Alpha Firmware CD are mutually exclusive. A system reset or re-initialization should be done after the operating system is shut down and before the update utility is run. 3.1 Update Firmware from the SRM Console The following procedure shows how to update console and I/O option firmware. To update only I/O option firmware, select the option name after the update command e.g. UPD> update pka0. Type LIST to display available option names. Insert Firmware CD into drive Re-initialize the system Boot the Alpha Firmware CD Press the Enter key after Bootfile: Type update Exit the LFU >>> show device >>>init >>> Boot dka500 Bootfile: UPD> update UPD>exit Find the CD-ROM device ID e.g. dka500 Boot code determines the AlphaServer type Press enter to use default firmware Update console and i/o option firmware Exiting will initialize the system Example updating firmware from the SRM console: >>> show device dka500.5.0.2000.1 DKA500 RRD47 1206 >>> boot dka500 (Firmware CD is inserted in CD Drive) block 0 of dka500.5.0.2000.1 is a valid boot block reading 989 blocks from dka500.5.0.2000.1 bootstrap code read in base = 156000, image_start = 0, image_bytes = 7ba00 initializing HWRPB at 2000 initializing page table at 148000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code [Release notes are displayed] Bootfile: [press Enter-key] eb.....ea.e9.e8.e7.e6. Checking dka500.5.0.1000.0 for the option firmware files... ***** Loadable Firmware Update Utility ***** ------------------------------------------------------------------ Function Description ------------------------------------------------------------------ Display Displays the system's configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name,update rev Update Replaces current firmware with loadable data image. Verify Compares loadable and hardware images. ? or Help Scrolls this function table. ------------------------------------------------------------------ UPD> update answer Yes to all questions then exit UPD> exit End of Example The firmware is now loaded into ROM. Typing exit will reset the AlphaServer system which invokes the new firmware. 3.2 Update Firmware from the AlphaBIOS Console The following procedures show how to update console and I/O option firmware. To get to the AlphaBIOS console menu from Windows NT, shutdown the operating system then reset the system. To get to the AlphaBIOS console from the SRM console prompt >>> , type "set os_type NT" then reset the system or type >>> alp from the SRM console. Insert Alpha Firmware CD into CD-ROM drive Select "Supplementary Menu" Select "Install New Firmware" Type "update" after the UPD> prompt Type "exit" after the firmware has updated to get to the "Install New Firmware" menu item to invoke the LFU from the Alpha Firmware CD. to update console and i/o option firmware to reset the system 3.3 Loadable Firmware Utility [LFU] Commands The Loadable Firmware Utility is the mechanism to update console and I/O option firmware. This section describes the most commonly used LFU commands. Type HELP at the LFU prompt (UPD>) to list all LFU commands. 3.3.1 Update Command Use the update command to update console and/or I/O option firmware. UPD> update [update will updates both console(s) and I/O option firmware] UPD> update e.g. >>> update ccmab02 3.3.2 List Command Use the list command to show a list of memory-loaded images and currently supported flash ROMs. In the following example three devices are installed in a system that can be firmware-updated. UPD> list Device Current Revision Filename Update Revision Abios 5.68 abios_fw 5.70 Srm_fw 5.5 SRM 5.4 UPD> 4 Using the FFAUTO and FFNEXT Environment Variables This section describes how to use console environment variables FFAUTO and FFNEXT to force devices (e.g. disks) from a "not connected" state to a "connected" state to make them bootable. The console does not allow booting devices that are in the "not connected" state. FFAUTO and FFNEXT are used for situations and configurations where an operator needs to force the console to boot a "not connected" device. These console environment variables were introduced in console firmware V5.5 (August 1999). 4.1 Background On Device States 4.1.1 Behavior of "Not Connected" Devices HSZ8x disk array controllers or HSG8x array controllers may have their disks in a "connected" or "not connected" state. In MULTIBUS mode, a disk state of "not connected" is normal and correct. Because the console does not allow booting devices in the "not connected" state, attempted to boot a "not connected" disk produces the console error message below: P00>>>b dga40.1003 resetting all I/O buses VGA Bios failed, status = 1 (boot dga40.1003.0.6.0 -flags 0) dga40.1003.0.6.0 is not connected failed to open dga40.1003.0.6.0 Therefore, to successfully boot a disk, select either a "connected" disk or use the FFAUTO or FFNEXT command. 4.1.2 Determining a "Not Connected" Device from an HSZ80 or HSG80 The HSZ8x or HSG8x console can help the operator determine where a disk device is connected. In this HSG80 console example below, the state of disk device d40 is 'ONLINE to this controller' therefore connected. HSG80> show d40 LUN Uses Used by ----------------------------------------------------------------------------- D40 DISK50000 LUN ID: 6000-1FE1-0000-04A0-FFFF-FFFE-0005-0000 IDENTIFIER = 40 Switches: RUN NOWRITE_PROTECT READ_CACHE READAHEAD_CACHE MAXIMUM_CACHED_TRANSFER_SIZE = 32 Access: ALL State: ONLINE to this controller Not reserved NOPREFERRED_PATH Size: 4110480 blocks Geometry (C/H/S): ( 3045 / 16 / 85 ) 4.1.3 Determining a "Not Connected" Device from the SRM Console There are a couple of methods: 1. The console error message at boot time, as previously shown, is one way to determine a "Not Connected"device. This console error message is also displayed when a console disk exerciser attempts to exercise a "Not Connected" device. 2. Using the WWIDMGR command, the console can also display the status of fibre channel devices controlled by an HSG8x. P00>>>wwidmgr -show wwid -udid 40 -full [0] UDID:40 WWID:01000010:6000-1fe1-0000-04a0-ffff-fffe-0005-0000 (ev:wwid0) - current_unit:40 current_col: 1 default_unit: 5901 via adapter via fc_nport Con DID Lun - pga0.0.0.6.0 5000-1fe1-0000-04a2 Yes 210313 40 - pga0.0.0.6.0 5000-1fe1-0000-04a1 Yes 210513 40 - pga0.0.0.6.0 5000-1fe1-0000-04a4 No 210713 40 4.2 Forcing the Console to Use a "Not Connected" Device 4.2.1 Using FFAUTO to Autoboot a "Not Connected" Devices FFAUTO determines console behavior when the system is trying to autoboot. An autoboot is any boot other than a manual >>>boot command issued at the SRM console by a user. FFAUTO can be set to ON or OFF. The default state is OFF where console behavior is not affected. FFAUTO is stored in non-volatile memory therefore its state persists across system resets and power cycles. >>> set FFAUTO ON In the ON state, console behavior is affected during an autoboot. When the console is trying to autoboot, the console attempts to boot from each "connected" device listed in bootdef_dev. If the console reaches the end of the bootdef_dev list without successfully booting, the console goes to the beginning of the bootdef_dev list and attempts booting again. Disks that are found in the "not connected" state are changed to the "connected state", thereby enabling the console to access that device. 4.2.1.1 Example Using the FFAUTO Environment Variable P00>>>set FFAUTO ON P00>>>set bootdef_dev dga40.1003 P00>>>b (boot dga40.1003.0.6.0 -flags 0) dga40.1003.0.6.0 is not connected failed to open dga40.1003.0.6.0 P00>>>init VMS PALcode V5.56-7, OSF PALcode V1.45-12 starting console on CPU 0 CPU 0 booting (boot dga40.1003.0.6.0 -flags 0) dga40.1003.0.6.0 is not connected failed to open dga40.1003.0.6.0 Retrying, type ^C to abort... (boot dga40.1003.0.6.0 -flags 0) block 0 of dga40.1003.0.6.0 is a valid boot block reading 896 blocks from dga40.1003.0.6.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = 70000 initializing HWRPB at 2000 initializing page table at 1ff0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code 4.2.2 Using FFNEXT on "Not Connected" Devices FFNEXT determines the console behavior of the next command issued to a "not connected" device. FFNEXT can be set to either OFF or ON. The default-state is OFF where console behavior is not affected. FFNEXT is a volatile environment variable and its value is temporary therefore does not propagate across a system reset or reboot. >>> set FFNEXT ON In the ON-state, the console will change the next "not connected" device to a "connected" state for booting. The FFNEXT state is automatically reset to OFF after the console changes device state from "not connected" to "connected". Resetting FFNEXT to OFF protects the user from accidentally changing the state of disks. Stated in another way, FFNEXT is a one shot. It stays in effect until a "Not Connected" device is accessed. 4.2.2.1 EXAMPLE: FFNEXT P00>>>b dga40.1001 (boot dga40.1001.0.6.0 -flags 0) dga40.1001.0.6.0 is not connected failed to open dga40.1001.0.6.0 P00>>>set ffnext on P00>>>b dga40.1001 (boot dga40.1001.0.6.0 -flags 0) block 0 of dga40.1001.0.6.0 is a valid boot block reading 896 blocks from dga40.1001.0.6.0 bootstrap code read in base = 200000, image_start = 0, image_bytes = 70000 initializing HWRPB at 2000 initializing page table at 1ff0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OpenVMS (TM) Alpha Operating System, Version X6PC-SSB halted CPU 0 halt code = 5 HALT instruction executed PC = ffffffff8b4e2ba4 P00>>>show ffnext ffnext OFF End of Examples AlphaServer DS20 13 Console Firmware V5.9 Page 5 August 1999