2 Processor-Specific Notes

This chapter contains notes that apply to processors supported by Digital UNIX Version 4.0:

2.1 General Notes on Processors

The notes in this section apply to more than one processor type.

2.1.1 PCI-based Systems with ATI Mach64 Graphics Controllers

On PCI machines that include ATI Mach64 graphics controllers in the configuration, the console environment variable pci_parity must be set 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

2.1.2 PCI Shared Interrupt Support

In Digital UNIX Version 3.2D and subsequent releases, 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

In order to setup your PCI-based system to share interrupts, you must ensure the following:

The firmware revision for your system supports shared interrupts
You have placed the option cards in PCI slots that allow sharing

Refer to your Digital UNIX Layered Product documentation (for example, for MME or Open3D) for information as to the shared interrupt capabilities of the software.

2.1.3 Support for RTS/CTS (Hardware) Flow Control

Digital UNIX Version 4.0, supports RTS/CTS (hardware) flow control in the serial drivers that are used on the DEC3000 series, DEC2000 series, AlphaStation, and AlphaServer systems. This support can be enabled or disabled using the -crtscts argument to the stty command. It can also be enabled on logins by specifying the Fflag option CRTSCTS on the appropriate /etc/gettydefs entry. By default, RTS/CTS flow control is disabled.

2.2 Digital AlphaStation 200 and Digital AlphaStation 400 Processors

The following notes apply to the Digital AlphaStation 200 and Digital AlphaStation 400 series processors.

2.2.1 Power Management Support for the Digital AlphaStation 255

This release supports power management for the Digital AlphaStation 255 system. The power management capability allows you to control:

Disk spindown
CPU slowdown
Monitor powerdown (DPMS).

The user may control power management settings using a graphical user interface /usr/bin/X11/dxpower A command line interface sysconfigdb is also available. Specific monitor settings can also be modified using the xset command.

See the System Administration manual and the xset(1X) and sysconfigdb(8) reference pages for more information.

Note that a system (root) disk cannot spin down due to normal system activity. User disks will spin down unless applications are running and the applications require constant access to the user disks.

2.2.2 Monitor Power Management for the Digital AlphaStation 255

Monitors that do not support DPMS (Display Power Management Signaling) can be damaged by the activation of the DPMS feature. Check your monitor specifications.

Monitors that support DPMS and are put in a power savings state will vary in the time it takes to come out of power savings. Users will observe that the longer the monitor is in 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 not a function of the operating system.

2.3 Digital AlphaServer 1000 4/200 Processors

The following notes apply to the Digital AlphaServer Model 1000 4/200

2.3.1 EISA Configuration Utilty and RIS Installation

When upgrading a AlphaServer 1000 series processor from the firmware CD-ROM, you should boot the firmware file AS1000_V5_1.EXE, (version 5.1) and not AS1000_V5_2.EXE (version 5.2) as indicated in the Alpha Systems Firmware Update FT1 Release Notes Overview

If you use version 5.1 instead of version 5.2 you will not be able to perform an installation using RIS.

2.4 Digital AlphaServer 2000, AlphaServer 2100 Processors and Digital Alpha VME 2100 Processors

The notes in this section apply to the AlphaServer 2000, AlphaServer 2100 Server and Digital Alpha VME 2100 series processors.

2.4.1 SWXCR Raid Configuration Updates

Do not perform SWXCR RAID configuration updates with ARC Version 4.2-1 on the AlphaServer 2000 or AlphaServer 2100.

2.4.2 Digital Alpha VME 2100

The notes in this section apply to the Digital UNIX software running on the Digital Alpha VME 2100.

For information on how to configure the VME subsystem, see the Writing VMEbus Device Drivers manual.

2.4.2.1 Unpredictable Results When Performing Master Block Transfers

Performing master block transfers with a data width of D64 can produce unpredictable results. For more information, see Section 2.6.2.

2.5 KDM70 Disk Controller on DEC 7000 Processors

The KDM70 disk controller is not supported when more than one gigabyte of memory is installed. After running the ECU over a serial line, the cursor will not display. You must change the terminal setup to redisplay the cursor.

2.6 Digital AXPvme Single Board Computers

The following notes apply to the Digital UNIX software running on the following single board computers (SBCs):

Digital AXPvme 64 Single Board Computer
Digital AXPvme 100 Single Board Computer
Digital AXPvme 160 Single Board Computer
Digital AXPvme 230 Single Board Computer

For information on how to configure AXPvme single board computers, see the Writing VMEbus Device Drivers manual.

2.6.1 Hardware Restriction

To install Digital UNIX Version 4.0 on a Digital AXPvme SBC you must have a local disk. To attach to a local disk, a 50-pin IDC SCSI cable is required and must be properly terminated. The exact cable requirements depend on your enclosure, disk mounting, and other factors. This cable is not supplied with the Digital AXPvme 64 SBC.

The following cables, specified by Digital part numbers, are examples of cables that may be used for this purpose:

Part number 17-01244-01, 17-01244-02, or 17-01244-03
These are, respectively, an 8-, 12-, or 21-inch cable with a 50-pin IDC connector for connection to the AXPvme breakout module, and a female IEEE (Champ) connector for connecting to external drives.
Part number 17-03459-02
This cable is 40.5 inches long and contains six 50-pin female IDC connectors. A-50 pin IDC SCSI terminator is included. This cable connects the AXPvme breakout module to up to four internal drives with the terminator on the last connector.
Part number 17-03036-01
This cable is about 87 inches long and contains six 50-pin IDC connectors. This cable connects the AXPvme breakout module to up to four internal drives. It also contains an IEEE (Champ) connector for connection with external drives. A Champ SCSI terminator (part number H8574-A) may be required.

2.6.2 Unpredictable Results When Performing Master Block Transfers

Performing master block transfers with a data width of D64 can produce unpredictable results in the following cases:

If D64 slave access is performed before memory has been mapped to the VMEbus.
If memory access does not coincide with the appropriate access mode, such as attempting user access to memory specified as supervisory mode access.
If the AXPvme SBC is a VME interrupter and is targeted for D64 slave access, the interrupt vector presented by the VME interrupter may not be the vector specified in the 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 notes apply to the Digital AXPpci 33 series processors.

2.6.3 IRQs for PCI Options on Digital AXPpci 33 Systems

PCI options are assigned IRQs after ISA options are configured. Available IRQs are {5, 9, 10, 15}. The firmware automatically assigns PCI IRQs from this list. IRQ 11 is assigned to the internal SCSI controller.