This chapter contains general notes that apply to all processors and specific notes that apply to the following systems:
AlphaServer 1000 and 1000A systems (Section 4.2)
AlphaServer GS systems (Section 4.3)
Personal Workstation 433au, 500au, and 600au systems (Section 4.4)
Alpha VME and PCI/ISA (DMCC) Modular Single-Board Computers (Section 4.5)
Do not attempt to install Tru64 UNIX Version 5.1 without
first reading the notes appropriate to your processor.
Failure to read these
notes can result in installation problems.
Also, before you start your installation,
be sure to review the hardware documentation that came with your system.
4.1 General Notes on Processors
The following sections apply to more than one processor type.
4.1.1 Upgrading Your Hardware
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:
Update your operating system software to Tru64 UNIX Version 5.1.
Upgrade your firmware.
Upgrade your hardware or install the new option.
Follow the instructions in Chapter 2 of the Tru64 UNIX Installation Guide to rebuild your system kernel.
Some of the software documentation states to use the floppy disk drive
for certain procedures.
However, some systems do not include floppy disk drives.
If your system does not include a floppy disk drive, you will have to find
an alternative to the documented procedure.
4.1.3 KZPSA Behind the PCI-to-PCI Bridge
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.
4.1.4 Qlogic ISP1040B CAM Errors
On systems with a Qlogic ISP1040B option, CAM errors like the following might occur when you boot the system:
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 correct 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
directory for information about how to use the utility.
4.1.5 DJ-ML200-xx PCI NVRAM Hardware Revision
The revision of the ML200-xx 2/4/8MB PCI NVRAM adapter must be revision E01.
4.1.6 Managing HSZ and HSG Hardware
You must use the StorageWorks
Command Console (SWCC) Version 2.3 or higher to manage HSZ or
HSG controllers.
Versions prior to Version 2.3 are not supported for use on Tru64 UNIX
Version 5.0, or later.
4.1.7 No Console-Level Multipath Support for Some Older Systems
The console firmware on the AlphaServer 1000, AlphaServer 1000A, and AlphaServer 2x00 systems does not support selecting multiple boot or dump devices for storage units located behind HSZ70, HSZ80, or HSG80 Raid Array controllers that are enabled for multiple-bus failover mode.
The console must have a visible path to the storage unit that it is
booting from or to which it is dumping.
If a controller, in multiple-bus
failover mode, fails over to the other controller, all devices served by the
failed controller are now visible on alternate paths.
Therefore, before booting
the system, reset the
bootdef_dev
console environment
variable to a path that is visible to the boot device.
After the operating system has been booted, multipath support is fully
functional.
4.2 AlphaServer 1000 and 1000A Systems
The following notes are specific to AlphaServer 1000 and 1000A systems.
4.2.1 EISA Configuration Utility Version 1.10
This note applies to users who utilize the onboard Cirrus VGA graphics controller.
The default setting for the VGA graphics controller when running the
EISA Configuration Utility (ECU) Version 1.10 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, the setting
for the onboard VGA graphics controller is automatically set to
Disabled.
To change the default value, run 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 your system will have generic console support when you
boot Tru64 UNIX.
4.2.2 Graphics Resolution
The default graphics resolution for AlphaServer 1000A systems that contain 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 graphics resolution for 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.
4.3 AlphaServer GS Systems
The following notes are specific to AlphaServer GS systems.
For additional
information on configuring an AlphaServer GS system in a cluster, see the
TruCluster Server
Hardware Configuration
guide.
4.3.1 Offlining Certain CPUs Is Not Supported
Each quad building block (QBB)
on an AlphaServer GS system has a processor that takes the interrupts for
that QBB.
At present, there is no mechanism to move interrupts to other processors,
which means that you cannot take the processor off line.
(See the
psradm(8)
and the
offline(8)
reference pages for more information).
If you attempt to take a processor off line, the following error occurs:
#offline xxoffline: processor xx: Invalid argument
The affected processor numbers are typically
evenly divisible by 4.
For example 0, 4, 8, 12, 16, and so on.
4.4 Personal Workstation 433au, 500au, and 600au Systems
The following notes are specific to Personal Workstation class systems.
4.4.1 64-Bit PCI Option Cards
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 one of these slots (n):
Illegal device detected on primary bus in physical slotnPower down the system and remove the unsupported device from slotn
4.4.2 Incorrect Default Keyboard Mappings
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 use the
sysconfig
command to reconfigure the driver, you must execute the command each 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.
4.5 Alpha VME and PCI/ISA (DMCC) Modular Single-Board Computers
For information about configuring the operating system on Alpha VME single-board computers (SBCs) and PCI/ISA EBMnn modular SBCs, see the System Configuration Supplement: OEM Platforms manual. (The PCI/ISA modular systems and components product family was formerly known as DIGITAL Modular Computing Components, or DMCC.)