This chapter contains notes that apply to the following computers:
The following sections apply to more than one processor type.
You can follow the instructions in the Installation Guide and those provided by your hardware and firmware documentation when you add new options or change your system hardware. However, if the new option is supported only in the newest version of Tru64 UNIX, you must perform the upgrade in the following sequence:
On PCI machines that include ATI Mach64 graphics controllers in the
configuration, you must set the console environment
pci_parity
variable to
off.
Due to a hardware limitation, hardware machine checks will occur if
this variable is not turned off. Use the following commands:
>>>
set pci_parity off
>>>
init
In Version 3.2D and subsequent releases of the operating system, the PCI-based system and I/O support code is capable of shared interrupts. The only exception is the 53C810 (onboard or option) SCSI controller.
You can use the following console firmware command to determine if your system has a 53C810 SCSI controller:
>>>
show config
To set up your PCI-based system to share interrupts, you must ensure the following:
Refer to your layered product documentation (for example, for MME or Open3D) for information about the shared interrupt capabilities of the software.
On AlphaServer 1000A and 2100A class systems, updating the firmware on a KZPSA SCSI adapter is not supported when the adapter is behind the PCI-to-PCI bridge. See your hardware installation guide for further information. A later version of the console firmware will support this feature.
On systems with a Qlogic ISP1040B option, CAM errors like the following may occur during bootup:
pci2000 at pci0 slot 8 isp0 at pci2000 slot 0 isp0: QLOGIC ISP1020A cam_logger: CAM_ERROR packet cam_logger: bus 0 isp_probe NVRAM parameters invalid, using driver Fast10 defaults
To alleviate the error, you must use the
eeromcfg
utility to program the NVRAM with the proper
set of parameters. The
eeromcfg
utility is provided in the
/mnt-pnt/utility directory of the
Alpha Systems Firmware Update
CD-ROM. Consult the
readme.txt
file in that same directory for information about how to use the
utility.
The revision of the ML200-xx 2/4/8MB PCI NVRAM adapter must be revision E01.
To start a RIS installation on an AlphaServer 1200, 4000, 4100, 8200,
or 8400, you must no longer specify the
n
option with the
boot
console firmware command, as in the following example:
>>>
boot -fl n ewa0
If you specify the
n
option, the RIS installation kernel will panic. You can safely
initiate a RIS installation by omitting the
n
option:
>>>
boot ewa0
The following notes are specific to Compaq Personal Workstation class systems.
The Compaq Personal Workstation class systems contain two EIDE (ATAPI) ports.
Version 4.0F supports the use of ATAPI CD-ROM devices attached to the internal EIDE adapter of the Compaq Personal Workstation class systems. The CD-ROM devices appear as SCSI rz devices. The device names for devices attached to the first EIDE port are rz0 and rz1. The device names for the devices attached to the second EIDE port are rz8 and rz9. The EIDE master devices are rz0 and rz8. The EIDE slave devices are rz1 and rz9.
The device names are reserved even if no devices are connected to those ports at the present time. Disks connected to the SCSI buses on the system are numbered rz16 and above.
Any Tru64 UNIX application designed to use a SCSI CD-ROM drive can use a supported EIDE CD-ROM drive through this software interface.
The 64-bit PCI slots, slots 4 and 5, are intended only for those cards listed in the Systems and Options Catalog as supported for slots 4 and 5. The console prevents system operation and displays the following error if an unsupported card is present in these slots (n):
Illegal device detected on primary bus in physical slot
n
Power down the system and remove the unsupported device from slot
n
If you use a PCXLA-NA keyboard on a Compaq Personal Workstation 433au, 500au, or 600au class system, the keys will not map properly unless you reconfigure the keyboard driver to use the correct keymaps.
You can do this by executing the following command:
#
sysconfig -r gpc_input kbd_scancode=2
If you prefer, you can use the
sysconfigdb
command to add the following entry to the
/etc/sysconfigtab
file:
gpc_input: kbd_scancode = 2
Note that if you execute the
sysconfig
command to reconfigure the driver, you must do this every time
you reboot the system. Using the
sysconfigdb
utility to make the change preserves the information across reboots,
and no other user intervention is required.
The following notes are specific to AlphaServer 1000 and 1000A systems.
This note applies to users who utilize the onboard Cirrus VGA graphics controller.
The default setting for the VGA graphic controller when running the
EISA Configuration Utility (ECU) Version 1.10 diskette is
Disabled.
For previous versions the default is
Enabled.
When you run the ECU Version 1.10 for the first time on a system that was
previously configured with an earlier version of the ECU diskette,
the setting for the onboard VGA graphic controller is automatically set to
Disabled.
While running the ECU, select Step 3: View and edit details
and set the VGA graphic controller to
Enabled
before exiting. If you do not set the VGA graphic controller to
Enabled
prior to booting
Tru64 UNIX, your X server will not start and you will use generic
console support when you boot Tru64 UNIX.
The default graphics resolution for Compaq AlphaServer 1000A systems containing built-in Cirrus video with 1 MB of video ram is 1024x768. If the optional 512 KB of video ram is not present, Tru64 UNIX supports resolutions of 640x480 (by default) or 800x600 only.
The default resolution for Compaq AlphaServer 1000 systems that contain built-in Cirrus video with 512 KB of video ram is 640x480. This configuration also supports 800x600 resolution.
To use 800x600
resolution, edit the following line in the
/usr/lib/X11/xdm/Xservers
file:
:0 local /usr/bin/X11/X
Change the line to:
:0 local /usr/bin/X11/X -screen0 800
To use 800x600 resolution for the CDE session
manager, edit the following line in the
/usr/dt/config/Xservers
and
Xservers.conf
files:
:0 Local local@console /usr/bin/X11/X :0
Change the line to:
:0 Local local@console /usr/bin/X11/X :0 -screen0 800
Before editing these files for XDM or CDE, be sure that your system's monitor supports 800x600 resolution.
The following note applies to the AlphaServer 8200, 8400, GS60, and GS140 systems.
Before installing the Tru64 UNIX software kit, ensure that your system has the correct firmware version. The minimum firmware version required Compaq AlphaServer 8200, 8400, GS60, and GS140 systems is Version 5.4. If you have an earlier firmware version, update your firmware before installing the Version 4.0F software. For information on how to update your firmware, refer to the AlphaServer hardware documentation.
To determine the version of firmware on your system, enter the
show version
console firmware command at the prompt:
P##>>>
show version
Note that ## is the primary processor number (usually 00).
The Compaq Alpha VME 4/nnn and 5/nnn series are Compaq's latest VME-based single board computers (SBCs).
Support for the VME VIP/VIC64 VME adapter on the Compaq Alpha VME 4/nnn and 5/nnn series SBCs is the same as the support for this adapter on Compaq AXPvme SBCs and Compaq Alpha VME 2100 systems. The following notes are specific to Compaq Alpha VME 4/nnn and 5/nnn SBCs.
The
sizer
utility identifies Compaq Alpha VME 4/nnn and
5/nnn SBCs as Compaq Alpha 4/nnn or 5/nnn family
members.
The
sizer -c
command displays the
following output for Compaq Alpha VME 4/224 and 4/288 SBCs:
sysname> sizer -c cpu "DECALPHAVME_224"
The
sizer -c
command displays the
following output for Compaq Alpha VME 5/nnn SBCs:
sysname> sizer -c cpu "DECALPHAVME_320"
Before installing the Tru64 UNIX software kit, make sure that your system has the correct firmware version. The minimum firmware versions required are Version 1.2 or higher for a Compaq Alpha VME 4/224 or 4/288 SBC, and Version 1.0 or higher for a Compaq Alpha VME 5/nnn SBC. If you have an earlier firmware version, update your firmware before installing the Version 4.0F software. For information on how to update your firmware, refer to the firmware documentation.
To determine the version of firmware on your system, enter the following command at the console firmware prompt:
>>> show version
The following restrictions apply to Compaq Alpha VME 4/nnn and 5/nnn SBCs.
In addition to sparse and dense addressing modes, the Compaq Alpha VME 5/nnn SBC hardware supports byte addressability. This includes the ability to perform simple math on a byte address to derive and access other byte addresses.
Currently, byte addressability is not supported by the Tru64 UNIX
mmap
interface.
VMEbus device drivers running on Compaq Alpha VME 5/nnn SBCs can continue to use the same sparse and dense space macros as in previous Tru64 UNIX releases and in existing VMEbus device drivers. Note that using the macros to access memory can help maintain the driver's binary compatibility (portability) across VMEbus platforms.
Byte addressability for Compaq Alpha VME 5/nnn SBCs will be supported in a future release of Tru64 UNIX.
The Compaq Alpha VME 4/nnn and 5/nnn SBCs do not support VME autovectors.
A Compaq Alpha VME 4/nnn or 5/nnn SBC that has the network configured in an UP state must have its external network connection properly terminated. If the network connection is unplugged or not properly terminated, then the network software will periodically time out and perform a network reset. This is normal for an unterminated Compaq Alpha VME system. However, it will cause high system latencies during the reset period, resulting in delays of about 10 milliseconds that can affect the realtime performance of the system.
Note that a loopback connector is not sufficient to terminate the network connection.
For information about writing VMEbus device drivers and configuring the
VMEbus on Compaq Alpha VME systems, refer to the
vme_manual_setup(7)
reference page.
If you are not currently running Version 4.0E, and are upgrading CPU boards, then you must install Version 4.0F before you upgrade your machine with the new AlphaServer 8200/8400 (Compaq AlphaServer GS60,GS140) 6/525 CPU boards.
The Futurebus backplane is not supported when an AlphaServer 8200/8400 is upgraded to the Compaq AlphaServer GS60 and GS140 6/525. This hardware must be removed from the system.
The Modular Computing Components (DMCC) EBM2n-xx and EBM4n-xx are Compaq's latest PCI/ISA-based single board computers (SBCs).
The EBM2n-xx is a PICMG-compliant processor card based on the Compaq Alpha 21164 CPU. The EBM4n-xx is a PICMG-compliant processor card based on the Compaq Alpha 21064A CPU.
The following notes are specific to DMCC EBM2n class and EBM4n class single board computers.
The
sizer
utility identifies Compaq DMCC EBM2n class and
EBM4n class SBCs as DMCC EBM2n or EBM4n family members.
The
sizer -c
command displays the following
output for Compaq DMCC EBM2n class SBCs:
sysname> sizer -c cpu "DECEV56_PBP"
The
sizer -c
command displays the following output for
Compaq DMCC EBM4n class SBCs:
sysname> sizer -c cpu "DECEV45_PBP"
Before installing the Tru64 UNIX software kit, make sure that your system has the correct firmware version. The minimum firmware versions required for Compaq DMCC EBM2n and EBM4n class SBCs is Version 4.7 or higher. If you have an earlier firmware version, update your firmware before installing the Version 4.0F software. For information on how to update your firmware, refer to the firmware documentation.
To determine the version of firmware on your system, enter the following console firmware command at the prompt:
>>> show version
The following restrictions and known problems apply to Compaq DMCC EBM2n class and EBM4n class SBCs.
You can use the DMCC EBM2n class and EBM4n SBCs on DMCC backplanes in the ETMXB-xx and ETMAB-xx family. The list of supported DMCC backplanes currently includes the following:
| Part Number | Description of Backplane |
| ETMXB-BA | 5-slot PICMG (2 PCI, 1 PCI/ISA, 1 ISA, 1 CPU) |
| ETMXB-AA | 7-slot PICMG (2 PCI, 1 PCI/ISA, 3 ISA, 1 CPU) |
| with onboard SCSI controller | |
| ETMXB-DA | 7-slot PICMG (3 PCI, 1 PCI/ISA, 1 ISA, 2 CPU) |
| ETMXB-CA | 9-slot PICMG (5 PCI, 1 PCI/ISA, 1 ISA, 2 CPU) |
| ETMXB-AB/ETMAB-AB | 14-slot PICMG (7 PCI, 6 ISA, 1 CPU) |
| ETMXB-BB/ETMAB-BB | 14-slot PICMG (10 PCI, 3 ISA, 1 CPU) |
| ETMXB-AC/ETMAB-AC | 19-slot PICMG (10 PCI, 7 ISA, 2 CPU) |
| ETMXB-BC/ETMAB-BC | 19-slot PICMG (13 PCI, 4 ISA, 2 CPU) |
All ETMXB-xx/ETMAB-xx backplanes, except the 5-slot ETMXB-BA and the 7-slot ETMXB-AA and ETMXB-DA, use PCI-to-PCI bridge (PPB) technology to provide both primary (in front of the bridge) and secondary (behind the PPB) slots.
All ETMAB-xx backplanes are PCI Version 2.1 compliant.
Only the ETMXB-AA contains an onboard SCSI controller. The other ETMXB-xx/ETMAB-xx backplanes require a SCSI option card.
The option cards shown in Table 3-1 work behind (as well as in front of) the bridge. You can plug these cards in to any available slot.
| Option Type | Part Number | Description |
| Graphics | SN-PBXGB-AA[Table Note 1] | TGA2 2MB PowerStorm 3D30 |
| SCSI | KZPAA-AA | PCI-SCSI host bus adapter |
| SCSI | SN-KZPBA-CA | PCI-SCSI Ultra Wide adapter |
| Network | DE450-CA | PCI NIC (TP, TW, AUI) |
| Network | DE500-BA | PCI NIC (TP) |
Table note:
When used with DMCC EBM2n SBCs (only), the SN-KZPBA-CA (PCI-SCSI Ultra Wide adapter) requires the following console parameter to be set:
>>>
set pci_prefetch SMS
The following restrictions apply to the PBXGB-AA (TGA2 PowerStorm 3D30) video card that is listed in Table 3-1:
For EBM2n SBCs only, you must set the EV5 Alias jumper on the PowerStorm 3D30 card to On.
Only one PowerStorm 3D30 card can have its VGAEN jumper set to On. This card must be positioned in a primary PCI slot for the SRM Console to be displayed. All other PowerStorm 3D30 cards must have their VGAEN jumpers set to Off but may be positioned in any PCI slot.
For more information about the jumpers, see the PBXGB-AA/CA PCI Graphics Option Owner's Guide provided with the card.
Some configurations of PowerStorm 3D30 cards on Compaq EBM2n and EBM4n SBCs require that you disable X Server direct memory access (DMA) write operations. Specifically, you must disable these operations if there are multiple PowerStorm 3D30 cards in the system, or if any PowerStorm 3D30 graphics card is installed behind the PCI-PCI bridge (PPB).
The Tru64 UNIX operating system does not support the operator control panel or watchdog timer. These server management features are supported only in the hardware and firmware.
This section describes how to configure a Modular Computing Components (DMCC) system to run eight-headed graphics under the Tru64 UNIX operating system.
You can configure DMCC platforms that contain a EBM2n-AZ Alpha PICMG single-board computer (SBC) and multiple PowerStorm 3D30 graphics cards to run multiheaded graphics, controlling up to eight monitors at a time.
Running eight-headed graphics on a DMCC system requires the following:
http://www.digital.com/oem/
The following DMCC configuration has been qualified by Compaq for running eight-headed graphics under Tru64 UNIX Version 4.0E:
When you configure the DMCC 15-slot platform for eight-headed graphics, placement of the graphics cards is critical.
The configuration described in the Hardware and Software Requirements section, and qualified by Compaq, uses an ETM33-BD desktop enclosure with 14-slot backplane. Within that enclosure, the PCI option cards must be placed into PCI slots in top to bottom order as follows:
For reference, the power connector is situated above the PCI slots, and the CPU and ISA connectors below.
All PowerStorm cards must have the ALIAS jumper in and VGA EN jumper out, except the SCREEN 0 card, which must be VGA enabled.
After you complete the hardware configuration for the eight-headed system, you can set up the Tru64 UNIX software to operate the eight screens as one row of eight screens (8x1) or two rows of four screens (4x2).
By default in a multiheaded configuration, the screens are operated as
8x1. To set up the screens in a 4x2 combination, you must edit your
system's X Window System server configuration file,
/usr/var/X11/Xserver.conf.
Instructions for editing this file in order to customize the X server
configuration are provided in the
Xserver(1X)
reference page.
To set up 4x2 operation, you need to specify
-edge_top,
-edge_bottom,
-edge_right,
and
-edge_left
command-line arguments that arrange and attach the screens as you want
them. Each argument takes
scr1
and
scr2
values, which are the numbers of the screens you are attaching.
For example, you could arrange the eight screens as follows:
/---------------\ | 4 | 5 | 6 | 7 | |---------------| | 0 | 1 | 2 | 3 | \---------------/
To achieve this combination, add the following information to the command-line
arguments section of
Xserver.conf:
! you specify command line arguments here args < -pn -edge_top0 4 -edge_top1 5 -edge_top2 6 -edge_top3 7 -edge_bottom4 0 -edge_bottom5 1 -edge_bottom6 2 -edge_bottom7 3 -edge_right0 1 -edge_right1 2 -edge_right2 3 -edge_right4 5 -edge_right5 6 -edge_right6 7 -edge_left1 0 -edge_left2 1 -edge_left3 2 -edge_left5 4 -edge_left6 5 -edge_left7 6 >
For information on how to configure AXPvme single board computers, see the Writing VMEbus Device Drivers manual.
The following notes are specific to the AXPvme SBCs.
Compaq AXPvme SBCs must upgrade to Version 17.0 or higher of the AXPvme firmware to run Tru64 UNIX Version 4.0F.
The following restriction applies to the VIP/VIC adapter used on Compaq AXPvme SBCs and Compaq Alpha VME 2100 systems.
Performing master block transfers with a data width of D64 can produce unpredictable results in the following cases:
vba_post_irq
function.
Memory must be mapped to the VMEbus prior to D64 slave access.
Access to memory must coincide with the appropriate access mode. If supervisory mode access is specified when memory is mapped, memory accesses must use supervisory mode. If user mode access is specified, both supervisory and user access are allowed.
See the Writing VMEbus Device Drivers manual for more information on slave and master block transfers.
The following note is specific to the DEC 7000 system.
During installation of Tru64 UNIX Version 4.0F software on a DEC 7000 system, the following message might appear on the console screen:
prom_saveenv: console returned illegal value
You should ignore this message and follow the instructions displayed on the screen by the installation process.
During an initial installation of Tru64 UNIX Version 4.0F software on some AlphaPC 164 family systems, the installation procedure might hang while setting the console environment variables prior to rebooting the system with the new software. The problem does not occur during an update installation because console environment variables are not reset.
This problem is due to a limitation in the console firmware for the systems on
which it is observed. The use of the
consvar
command, or attempts to modify parameters in the
bparm
subsystem through use of the
sysconfig -r
command also cause these systems to hang. To avoid this problem, change
console environment variables directly at the SRM console prompt instead of
through the privileged kernel interfaces.
If your AlphaPC 164 family system hangs during initial installation, you should power cycle the system and then set the console environment variables to reflect the correct boot device and boot mode. When you reboot the system, the installation procedure will continue with system configuration.
For example, if the system software is installed on the disk connected
as unit 0 on SCSI bus 0 (that is, on rz0), then enter the following commands
when the system powers up to
the SRM console prompt (
>>>):
>>>
set bootdef_dev dka0
>>>
set boot_osflags A
>>>
set auto_action boot
The next time the system powers up, it will automatically boot from
the freshly-installed disk and prepare to come up in multiuser mode. You can
boot immediately from the console prompt by entering the
boot
command, or you can power cycle the system.