![[Contents]](TOC.GIF)
![[Prev Chap]](REW.GIF)
![[*]](BLANK.GIF){kind=spacer}
![[Next Sect]](NEXT.GIF)
![[Next Chap]](FF.GIF)
![[Index]](INDEX.GIF)
![[(i)]](HELP.GIF)
This chapter contains notes that apply to the following computers:
The following sections apply to more than one processor type.
![[Prev Sect]](PREV.GIF)
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 DIGITAL 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 DIGITAL UNIX Version 3.2D and subsequent releases, the PCI-based system and I/O support code is shared interrupt capable. 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 DIGITAL UNIX 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, the following CAM errors 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.
Monitors that do not support the Display Power Management Signaling (DPMS) feature available on DIGITAL Personal Workstation 433AU, 500AU, 600AU, AlphaStation 255, and other systems can be damaged by the activation of monitor power management. Check your monitor specifications before using this feature.
The time it takes a DPMS-compatible monitor to come out of a power-saving state depends on the monitor. Users will observe that the longer the monitor is in the power-off state, the longer it takes for the display to return as a result of mouse or keyboard activity. This is the result of the monitor phosphor cooling down and the time required to heat it back up, and is not under the control of DIGITAL UNIX.
In addition, there are some monitors (for example, the VRC21-HX) that turn off the Power On/Off LED when they enter the DPMS_OFF state. Moving the mouse or typing at the keyboard will not bring the display back. Only by pressing the power switch off, then on again, will mouse and keyboard activity cause the display to return. Because of the varying behavior of monitors when in certain DPMS states, you should read your monitor specification to find out about the expected behavior and other visual features while in each power-savings state.
For more information about enabling power management, see the
dxpower(8)
reference page and the
System Administration
guide.
The following notes are specific to DIGITAL Personal Workstation class systems.
The DIGITAL Personal Workstation class systems contain two EIDE (ATAPI) ports.
Version 4.0D supports the use of ATAPI CD-ROM devices attached to
the internal EIDE adapter of the DIGITAL 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. The SCSI buses on the system are
numbered
rz16
and above.
Any DIGITAL 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 DIGITAL 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 from the command line:
#
sysconfig -r gpc_input kbd_scancode=2
If you prefer, you can use
sysconfigdb
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 DIGITAL 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
DIGITAL UNIX, your Xserver will not start and you will use generic
console support when you boot DIGITAL UNIX
The default graphics resolution for DIGITAL 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, DIGITAL UNIX supports resolutions of 640x480 (by default) or 800x600 only.
The default resolution for DIGITAL 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 -nice 2
Change the line to:
:0 local /usr/bin/X11/X -nice 2 -screen0 800
To use 800x600 resolution for the CDE session
manager, edit the following line in the
/usr/dt/config/Xservers
and
Xservers.con
files:
:0 Local local@console /usr/bin/X11/X :0 -nice 2
Change the line to:
:0 Local local@console /usr/bin/X11/X :0 -nice 2 -screen0 800
Before editing these files for XDM or CDE, be sure that your system's monitor supports 800x600 resolution.
The DIGITAL Alpha VME 4/nnn and 5/nnn series are DIGITAL's latest VME-based single board computers (SBCs).
Support for the VME VIP/VIC64 VME adapter on the DIGITAL Alpha VME 4/nnn and 5/nnn series SBCs is the same as the support for this adapter on DIGITAL AXPvme SBCs and DIGITAL Alpha VME 2100 systems. The following notes are specific to DIGITAL Alpha VME 4/nnn and 5/nnn SBCs.
The
sizer
utility identifies DIGITAL Alpha VME 4/nnn and
5/nnn SBCs as DIGITAL Alpha 4/nnn or 5/nnn family
members.
The
sizer -c
command displays the
following output for DIGITAL Alpha VME 4/224 and 4/288 SBCs:
sysname> sizer -c cpu "DECALPHAVME_224"
The
sizer -c
command displays the
following output for DIGITAL Alpha VME 5/nnn SBCs:
sysname> sizer -c cpu "DECALPHAVME_320"
Before installing the DIGITAL 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 DIGITAL Alpha VME 4/224 or 4/288 SBC, and Version 1.0 or higher for a DIGITAL Alpha VME 5/nnn SBC. If you have an earlier firmware version, update your firmware before installing the Version 4.0D 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 DIGITAL Alpha VME 4/nnn and 5/nnn SBCs.
To use the EBVXG (TGA) video card on DIGITAL Alpha 4/nnn and 5/nnn SBCs, you must disable X Server direct memory access (DMA) write operations. Section 6.1.1.1. describes the procedure for disabling these operations. Note that the EBVXG (TGA) video card is always installed behind the PCI-PCI bridge (PPB).
In addition to sparse and dense addressing modes, the DIGITAL 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 DIGITAL UNIX
mmap
interface.
VMEbus device drivers running on DIGITAL Alpha VME 5/nnn SBCs can continue to use the same sparse and dense space macros as in previous DIGITAL 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 DIGITAL Alpha VME 5/nnn SBCs will be supported in a future release of DIGITAL UNIX.
The DIGITAL Alpha VME 4/nnn and 5/nnn SBCs do not support VME autovectors.
A DIGITAL 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 DIGITAL 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 DIGITAL Alpha VME systems, refer to the DIGITAL UNIX manual Writing VMEbus Device Drivers. This manual is included in the DIGITAL UNIX Device Driver Kit. See Section 1.24 for ordering information.
The DIGITAL Modular Computing Components (DMCC) EBM2n-xx and EBM4n-xx are DIGITAL's latest PCI/ISA-based single board computers (SBCs).
The EBM2n-xx is a PICMG-compliant processor card based on the DIGITAL Alpha 21164 CPU. The EBM4n-xx is a PICMG-compliant processor card based on the DIGITAL Alpha 21064A CPU.
The following notes are specific to DIGITAL DMCC EBM2n class and EBM4n class single board computers.
The
sizer
utility identifies DIGITAL DMCC EBM2n class and
EBM4n class SBCs as DMCC EBM2n or EBM4n family members.
The
sizer -c
command displays the following
output for DIGITAL DMCC EBM2n class SBCs:
sysname> sizer -c cpu "DECEV56_PBP"
The
sizer -c
command displays the following output for
DIGITAL DMCC EBM4n class SBCs:
sysname> sizer -c cpu "DECEV45_PBP"
Before installing the DIGITAL UNIX software kit, make sure that your system has the correct firmware version. The minimum firmware versions required for DIGITAL 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.0D 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 DIGITAL DMCC EBM2n class and EBM4n class SBCs.
You can use the DMCC EBM2n class and EBM4n SBCs on DMCC backplanes in the ETMXB-xx family. The list of supported DMCC backplanes currently includes the following:
| Part Number | Description of Backplane |
| ETMXB-AA | 7-slot PICMG (2 PCI, 1 PCI/ISA, 3 ISA, 1 CPU) |
| with onboard SCSI controller | |
| ETMXB-AB | 14-slot PICMG (7 PCI, 6 ISA, 1 CPU) |
| ETMXB-BB | 14-slot PICMG (10 PCI, 3 ISA, 1 CPU) |
| ETMXB-AC | 19-slot PICMG (10 PCI, 8 ISA, 1 CPU) |
| ETMXB-BC | 19-slot PICMG (13 PCI, 5 ISA, 1 CPU) |
All ETMXB-xx backplanes, except ETMXB-AA, use PCI-to-PCI bridge (PPB) technology to provide both primary (in front of the bridge) and secondary (behind the PPB) slots.
Only the ETMXB-AA contains an onboard SCSI controller. The other ETMXB-xx backplanes require a SCSI option card such as KZPAA-AA.
The option cards shown in Table 3-1 have been found to work behind (as well as in front of) the bridge. You can plug these cards into any available slot.
| Option Type | Part Number | Description |
| Graphics | PBXGA-AA | ZLXp-E1 8 Plane Adapter |
| Graphics | PBXGB-AA[Table Note 1] | TGA2 2MB PowerStorm 3D30 |
| Graphics | PB2GA-JA | Trio64 2MB PowerStorm 3D10 |
| Disk | KZPAA-AA | PCI-SCSI Host Bus Adapter, FNS |
| Network | DE435-AA | PCI Bus, 32 Bit, PC NIC |
| Network | DE450-CA | PCI NIC (TP, TW, AUI) |
Table note:
The PB2GA-FA graphics option card (ATI Mach64 CX 2D GFX) does not function behind the bridge. You must plug this card into primary slots only.
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 may 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 DIGITAL 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 (or ZLXp-E1 [PBXGA-AA]) graphics card is installed behind the PCI-PCI bridge (PPB).
The procedure for disabling X Server DMA write operations is described in Section 6.1.1.1.
The DIGITAL 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.
For information on how to configure AXPvme single board computers, see the Writing VMEbus Device Drivers manual.
The following notes are specific to the DIGITAL AXPvme SBCs.
DIGITAL AXPvme SBCs must upgrade to Version 17.0 or higher of the AXPvme firmware to run DIGITAL UNIX Version 4.0D.
The following restriction applies to the VIP/VIC adapter used on DIGITAL AXPvme SBCs and DIGITAL 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.