|Document revision date: 19 July 1999|
This section contains release notes pertaining to AlphaServer 8200/8400
1.9.1 Problems and Restrictions
The following notes describe restrictions that apply to AlphaServer
188.8.131.52 Field Replaceable Units (FRU) Table Error
The error log buffer size is controlled by the SYSGEN parameter
ERLBUFFERPAGES, which has a maximum value of 32 pagelets. If the Field
Replaceable Unit (FRU) table exceeds this limit during a boot of the
OpenVMS Alpha operating system on an AlphaServer 8200/8400 or 4100
system, an entry will not be written to the error log file.
184.108.40.206 Environmental Data Restrictions
On AlphaServer 8200 systems, the power regulators do not contain sensors for environmental conditions. Therefore, data cannot be reported in the thermal and power supply MIB groups of the DSM System subagent.
On AlphaServer 8400 systems, the power regulators do contain
environmental sensors, but some configurations might not report
environmental information correctly to the DSM System subagent. This
problem affects the thermal and power supply MIB groups and will be
resolved in a future release of the software.
1.10 AlphaStation 255 (Alpha Only)
See Section 220.127.116.11 for a release note about using PowerStorm graphics
cards on an AlphaStation 255.
1.11 DEC 7000 (Alpha Only)
This section contains release notes pertaining to DEC 7000 systems.
1.11.1 Changes and Enhancements
The following note describes a change in the behavior of DEC 7000
18.104.22.168 Ctrl/P Behavior Change During Boot
Starting with OpenVMS Alpha Version 7.1, the remote halt command, issued by typing Ctrl/P at the system console, does not work during boot until the following copyright banner appears.
$! Copyright (c) 1996 Digital Equipment Corporation. All rights reserved.
In previous versions of OpenVMS, typing Ctrl/P at the system console
always returned the system to the console prompt at any time during the
1.12 DECwindows X11 Display Server (Alpha Only)
This section contains release notes pertaining to the DECwindows X11
display server for OpenVMS Alpha systems.
1.12.1 Changes and Enhancements
The following note describes a change in behavior on the DECwindows X11
22.214.171.124 Ctrl/F2 Behavior Change
Starting with OpenVMS Alpha Version 7.1, you can no longer press Ctrl/F2 to switch from windows mode to console mode if your workstation or server contains one of these Qvision graphics boards:
This behavior has always been true for the S3 Trio64 graphics board (PB2GA--JA/JB).
Directing any output directly to the operator console window (OPA0: device) might cause a system crash during a simultaneous graphics operation.
Support for the operator console is now provided using a Motif-based window option that is enabled during DECwindows startup. For details, refer to Section 126.96.36.199.
Note that you can still use Ctrl/F2 to switch from console mode to
1.12.2 Problems and Restrictions
The following notes describe restrictions for the DECwindows X11
188.8.131.52 Graphics Boards Support
You must install DIGITAL Open3D Version 4.7 or later for OpenVMS Alpha to support the following types of graphics boards on Version 7.2:
The DIGITAL Open3D product also provides the following 3D extensions:
OpenGL, PEX, and PCM.
184.108.40.206 PowerStorm Graphics Cards Can Hang System
On AlphaStation 255 systems using PowerStorm 3D30 and 4D20 (TGA2)
graphics cards, the system will hang if the user selects the InlayColor
or InlayPlain backdrop in the Style Manager's Backdrop dialog box. If
this happens, you must reboot the system to use it.
220.127.116.11 S3 Multihead Graphics
Alpha computers equipped with S3 Trio32 or Trio64 graphics cards
support single-screen display only. Multihead graphics are not
1.13 DIGITAL Modular Computing Components (DMCC) (Alpha Only)
This section contains release notes pertaining to DMCC.
1.13.1 Problems and Restrictions
The following notes describe restrictions for DMCC.
18.104.22.168 CPUSPINWAIT Crash and Recovery on DMCC 21164A Systems
DIGITAL Modular Computing Components 21164A systems may experience the following crash running OpenVMS Version 7.2:
CPUSPINWAIT, CPU spinwait timer expired
To avoid this problem, reboot the system with the SYSTEM_CHECK parameter disabled. Use the following commands when you reboot to disable the SYSTEM_CHECK parameter:
>>> boot -flags, 0,1 bootdevice SYSBOOT> SET SYSTEM_CHECK 0 SYSBOOT> CONTINUE
The KZPDA SCSI Controller and the PBXGA Graphics Card cannot be placed
in a slot behind the bridge on the DIGITAL Modular Computing Components
(DMCC) Alpha 5/366 and 5/433 PICMG SBCs.
22.214.171.124 Updating the SRM Console
To update the SRM console on the Alpha 4/233 (21064a), 4/266 (21164a), 5/366, and 5/433 DMCC systems, you must choose either the SRM console or the AlphaBIOS setup. You can store only one console.
If you accidentally update both the SRM and the AlphaBIOS consoles, you will enter the AlphaBIOS Setup menu, and you will not have the option to return to the SRM console. The only way to then exit the AlphaBIOS Setup menu and return to the SRM console is to use a Firmware Update Utility located at the following Internet site:
This section contains a release note for the Ohio State University
(OSU) HTTP server.
1.14.1 Problems and Restrictions
The following note describes a potential problem with the OSU HTTP
126.96.36.199 Running on OpenVMS Version 7.2
If you use the OSU HTTP server on OpenVMS Version 7.2, you should install Version 3.3A (or later) of the server. Earlier versions of the server can hang when you use the "privrequest shutdown" or "privrequest restart" commands.
You can download Version 3.3A from the following web site:
If you do not want to install a new version of the server, there is a small source patch for earlier versions available in the server mailing list archives at:
Release notes in this section pertain to the RF31T, RF31T+, RF35,
RF35+, RF73, and RF74 DSSI disk devices.
1.15.1 Problems and Restrictions
This section describes a problem found in certain RF31T, RF31T+, RF35,
RF35+, RF73, and RF74 DSSI disk devices.
188.8.131.52 RF73 and Other RFnn DSSI Disk Devices and Controller Memory Errors
A problem exists with the microcode for earlier versions of RF31T, RF31T+, RF35, RF35+, RF73, and RF74 DSSI disk devices that can cause data loss. The problem can occur when reading data from one of these devices if the device has had a controller memory error (also known as an error detection and correction (EDC) error). The error could have been induced by a virtual circuit closure or faulty hardware.
Compaq advises customers with any of these devices to check their microcode revision levels. If the microcode revision levels are lower than the numbers shown in Table 1-2, Compaq recommends that you update the microcode. The microcode for all models, except RF31T, RF31T+, and RF35+, is provided on the latest OpenVMS binary distribution CD-ROM.
The RF_VERS utility, a utility program that displays the microcode revision level of the DSSI disk devices, is also provided on the CD-ROM. Instructions for using the utility program and for updating the microcode are provided in this section.
If you have an RF31T, RF31T+, or RF35+ disk drive with a version of microcode that is not supported (see Table 1-2), and if you have a support contract, contact your Compaq support representative. Otherwise, contact your authorized reseller.
The earliest supportable revision levels of the DSSI disk microcode are shown in Table 1-2.
|Device Type||Minimum Level with Supported Microcode|
To display the microcode version level of your DSSI disk devices, perform the following steps:
$ SET PROCESS /PRIVILEGE=(DIAGNOSE,CMKRNL,SYSPRV) $ SHOW DEVICE FYA0:
$ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONN FYA0/NOADAP SYSGEN> ^Z
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> IO CONNECT FYA0: /NOADAP SYSGEN> ^Z
The following is an example of the display produced by the RF_VERS utility:
Program Name: RF_VERS Revision Level: V1.2s NOTICE: This program does not currently support the RF72 or any HSDxx controllers. See next version for support. DSSI disks currently on this system as seen by RF_VERS Device Node Status Hardware Firmware Name Name Type Version _$22$DIA7: R4JL2I mounted RF73 T387A _$22$DIA6: R4I0BG mounted RF73 T387A _$22$DIA8: R4XLWE mounted RF73 T387A _$22$DIA2: R4FCZK mounted RF73 T387A _$22$DIA3: R4CKCG mounted RF73 T387A _$22$DIA4: R4ZKUE mounted RF73 T387A _$22$DIA9: R4GYYI mounted RF73 T387A _$22$DIA1: R4XRYI mounted RF73 T387A
To update the microcode in your device, use the appropriate command for your device and platform from Table 1-3.
Back up the disk before updating the microcode.
Do not delete SCSI_INFO.EXE, RF_VERS.EXE, or any of the files listed in Table 1-3. If these files are deleted, VMSKITBLD.COM (on VAX) will not be able to find them. Similarly, on Alpha systems, the PRODUCT INSTALL commands in AXPVMS$PCSI_INSTALL and AXPVMS$PCSI_INSTALL_MIN will fail.
|privacy and legal statement|