SCO UNIX Installation

The following explains how to install the Adaptec Ultra160 Family Manager Set driver ad160 for SCO OpenServer 5.0.5.

The ad160 driver drivers support the Adaptec ASC-29160, ASC-29160N, ASC-29160LP, and ASC-39160 host adapters.

If you are performing a first time SCO UNIX installation, see Installing the Driver When Installing SCO UNIX below to begin driver installation.

If SCO UNIX is already installed in your system, see the section Installing the Driver When SCO UNIX is Already
Installed.

Set the SCSI IDs of your devices as recommended by SCO:

If you are installing SCO UNIX products with a SCSI tape drive, set the tape drive to SCSI ID 2 (two)

If you are installing with a CD-ROM, set the CD-ROM drive to SCSI ID 5 (five)

Set the Boot SCSI hard drive to SCSI ID 0 (zero)

Note: SCO UNIX installation requires that the host adapter driver be installed from a diskette. Refer to the QuickStart Guide for SCO UNIX driver diskette creation.

Installing the Driver When Installing SCO UNIX
To install the ad160 driver at the same time you install SCO UNIX, follow the instructions below.

Installing SCO OpenServer 5.0.5
Follow these instructions only if you are installing SCO OpenServer 5.0.5 for the first time.

Note: Remember that UNIX commands are case sensitive.

Enter the commands exactly as shown in the instructions.

1) Insert the SCO OpenServer 5.0.5 boot disk into the primary

floppy disk drive and turn ON the computer. Alternatively, insert the SCO OpenServer 5.0.5 boot CD into the primary CD-ROM drive and turn ON the computer.

2) When you see these prompts:
SCO OpenServer (TM) Release 5
Boot :
Type ahslink and press Enter.

3) Type ad160 as the package you want to link to the system and press Enter.

4) Insert the requested volume (the Ultra160 Family Manager Set disk for SCO UNIX) in the floppy disk drive and press Enter.

5) If the driver is properly loaded, the following message appears:

ad160.ad160:Loading module fd(52)/ad160/driver/ad160/Driver.o text............

: ad160: Driver "ad160" successfully loaded.

6) Follow the procedures in your SCO UNIX documentation for completing the installation.

Installing the Driver When SCO UNIX is Already Installed

To update or install the ad160 driver if SCO UNIX is already installed, follow the instructions in this section. The procedures are similar for all versions of SCO UNIX. Procedures that are specific to a SCO version are noted when necessary.

Caution: Improper or corrupt driver updates might destroy your existing UNIX file system.

Back up all important files before proceeding.

Installing or updating the driver involves the following tasks, which must be completed in the order presented:

Back up the old UNIX kernel and any other important files.

Use installpkg to load the driver.

Change the primary host adapter to an Ultra160 Family host adapter, if necessary.

Rebuild the kernel to reflect the new changes.

Reboot the computer with the new kernel.

Note: To update or install the driver, you must first enter the Single User Mode (System Maintenance Mode). Refer to the  SCO UNIX documentation for instructions on how to use the init(m) or shutdown(m) command to put the system into System Maintenance Mode.

1) Perform a System Backup

If you have not already done so, back up all important files on the computer by following these steps:

Note: To back up the whole system, refer to your SCO UNIX documentation.

a) Log in as root.

b) To back up the current kernel configuration, type the following and press Enter after each line:

umount /stand
mount /dev/boot /stand
cp /stand/unix /stand/unix.orig

Note: If you ever need to boot up from the pre-update kernel, load the unix.orig backup kernel at the UNIX Boot:
prompt. To do this, type unix.orig and press Enter.

c) This step is optional. For extra security, you may back up the mdevice file and the sdevice.d directory.

To perform this backup, type the following and press Enter:

copy -rom /etc/conf /etc/conf.bak

2) To load the driver using installpkg, follow these steps:

a) At the UNIX system prompt, type installpkg and press Enter. The screen displays the following messages:

Confirm
Please insert the floppy disk
:
:

Strike ENTER when ready or ESC to stop.

b) Insert the Ultra160 Family Manager Set disk for SCO UNIX and press Enter. The screen displays the following messages:

Installation is in progress - do not remove the floppy disk. The following packages are on this disk:

NAME DESCRIPTION
ad160 Adaptec Ultra160 Family Driver for SCO OpenServer 5.0.5/dxx
Please enter the names of the packages you wish to install, or q to quit:

c) At this point, type ad160 and press Enter. The screen then displays this message and various installation status prompts:

Installing ad160

When the driver is loaded, the following message appears, indicating that the ad160 driver has been loaded into the Link Kit for kernel addition:

Installed ad160 #

3) Modify the mscsi file, if necessary, to change your primary host adapter to an Ultra160 Family host adapter, using the
procedure below:

a) Enter the following command:
cd /etc/conf/cf.d

b) Use a text editor to edit this file. Enter the following command if using the vi editor:

vi mscsi

c) Search for all entries with the host adapter number 0 (zero).
The host adapter number is the third column in each entry.

For example:

* This field applies to SCO OpenServer 5 and later.

d) Modify the mscsi file according to your hardware setup:

If you are booting from an Ultra160 Family host adapter, make sure the host adapter prefix for the host adapter
number 0 is ad160.

If you are not booting from an Ultra160 Family host adapter, make sure the host adapter prefix for the host adapter number 0 is the appropriate prefix for each device on your primary Adaptec host adapter. See the table above.

e) Save the file and exit the text editor.

4) Rebuild the UNIX kernel by following these steps:

a) Type the following at the # prompt and press Enter after each line:

cd /etc/conf/cf.d ./link_unix
Status messages appear on-screen.

b) When the kernel has been built, shut down the system
by typing shutdown-g0 and pressing Enter.

c) Turn OFF the system power when you are prompted to do so.

If you need to reconfigure your system, you may do so now.

d) Add or remove host adapters or devices as needed.

5) Boot the new kernel by following these steps:

a) Follow the onscreen instructions to reboot your system, usually by pressing Enter.

b) Check the host adapter BIOS messages to verify that all your installed SCSI devices are listed. If some or all of your installed SCSI devices do not appear at this time, your SCSI cables may be loose, or the SCSI device setup may not be complete. If so, go back and correct any problem before proceeding.

c) Wait for UNIX to boot with the new kernel.
See the Troubleshooting section if the system crashes or if "panic" (UNIX error) messages are displayed at boot time. The ad160 driver for your Ultra160 Family host adapter should now be ready for use.

Using SCO UNIX and the Host Adapter

This section contains useful information on using SCO UNIX and your host adapter.

Using Multiple Host Adapters

If you are adding an additional Ultra160 Family host adapter to a system with an Ultra160 Family host adapter already installed, follow the instructions in the SCO UNIX documentation for adding devices using the mkdev command. When the system asks for the host adapter prefix, type ad160 and press Enter.

Changing the Boot Disk

If you are changing the boot device from a non-SCSI hard disk to a SCSI hard disk attached to an Adaptec Ultra 160 Family host adapter, you must reinstall SCO UNIX. If you are already booting from a SCSI hard disk attached to
an Adaptec PCI SCSI host adapter, and wish to boot from the same SCSI hard disk attached to an Adaptec Ultra160 Family host adapter, you may elect to either reinstall SCO UNIX with the new driver, or update SCO UNIX with the new driver.

See the sections Installing the Driver When Installing SCO UNIX, and Installing the Driver When SCO UNIX is Already Installed for instructions.

Using Wide SCSI Host Adapters and Devices SCO OpenServer 5.0.5 supports SCSI IDs 0 to 15. If your Ultra160 Family host adapter is a Wide SCSI adapter, up to 15 SCSI devices can be attached and supported. Using Tunable Parameters for the ad160 Driver

For SCO UNIX, some parameters are defined in the following file:

/etc/conf/pack.d/ad160/space.c

After modifying the space.c file, you must rebuild the kernel for the new parameters to take effect. The following section describes how to set the tunable parameters.

Setting Parameters
If the space.c file has not been modified, all the parameters are set according to the values specified by your SCSISelect utility for your Ultra160 Family host adapter. However, you can override the parameters by modifying the space.c file. The information you need to change the parameters is included in the space.c file. Examples are provided in the following sections.

If you want to change the configured values, the first number indicates whether the default should be changed. If it is set to 0 (zero), the parameter is set to the default.

If it is set to 1, the second number is used to override the default.

For example:

char variable = {1,22};

The first number is 1, which overrides the default variable with the value 22.

Examples

ad160_parity[SCSI_NAD160]

This specifies whether the host adapter checks parity on incoming SCSI data.

ad160_parity[SCSI_NAD160] = {First number, second number} If the second number is set to 0, parity checking is enabled.
If it is set to 1, parity checking is disabled.

In this example you want the host adapter not to check parity on incoming SCSI data; define parameters as

ad160_parity[SCSI_NAD160] = {1,0};

Changing the Maximum Number of LUNs Supported
The default setting for maximum number of LUNs supported is Disable. To enable this setting, you may have to use
vi to edit the space.c file located at /etc/conf/pack.d/ad160. Modify the following line so that lun=1:

int ad160_scan_lun=0;
Enabling Scatter/Gather and Tagged Queuing The ad160 driver supports scatter/gather and tagged queuing; however, the Sdsk (SCSI disk module) driver controls whether these features are enabled or disabled. Look for the Sdsk driver
controls in the space.c file located at:

/etc/conf/pack.d/Sdsk/space.c

Troubleshooting

My computer does not recognize my SCSI devices.

At boot time, check to see if the BIOS messages for your primary Ultra160 Family host adapter lists all installed SCSI devices. If some or all devices do not appear, check your host adapter User's Guide for additional troubleshooting information, and check the following:

Are all SCSI devices powered on?

Are all SCSI bus cables and power cables properly connected?

Do the host adapter and all devices on the SCSI bus have unique SCSI IDs?

Are all devices on the SCSI bus terminated properly?

Do you have an older SCSI peripheral installed? Some older SCSI peripherals, especially CD-ROM drives, do not properly respond to synchronous negotiation. As a result, these peripherals may lock or reset the SCSI bus. To solve this
problem, turn off synchronous negotiation for this device ID through the SCSISelect utility for the host adapter. See the host adapter's User's Guide.

My computer does not recognize my host adapter.

At boot time, check to see if the BIOS message for your primary Ultra160 Family host adapter appears. If the messages do not appear, the host adapter may not be properly configured; check the following:

The Ultra160 Family host adapter supports level-triggered interrupts and can share the same interrupt with another

Ultra160 Family host adapter or PCI hardware that also supports level-triggered interrupts. Check your host adapter
User's Guide and the documentation supplied with your computer for information about configuring IRQs and other parameters in the system CMOS setup. The Boot host adapters should be installed into the lowest PCI Device number. The Device number is determined by the slot number on the PCI bus.

To find out the Device number of your Ultra160 Family host adapter(s):

a) Run the SCSISelect utility (by pressing a key combination displayed on-screen at boot time).

b) Look on the first screen of SCSISelect in the upper right hand corner for Bus:Device xx:xxh (shown in hexadecimal).

If the Device number is high, power OFF the computer, move the Ultra160 Family host adapter to a PCI slot at the other end of the motherboard, and run SCSISelect again to see if the number is lower.

The host adapter LED lights during activity. This light helps to determine which adapter SCSISelect displays information
for. Refer to your system documentation for further details on determining the PCI slot number and slot number order in the system.

Problems booting the computer from a SCSI drive.

Note: If both SCSI and non-SCSI disk drives (such as IDE) are installed, a non-SCSI disk drive must be the boot device, unless your system supports Bios Boot Specification (BBS).

Refer to the documentation supplied with your system for more information. Make sure your host adapter is installed and configured correctly, as described in the documentation that came with it. Check the following if the host adapter is correctly installed: Ensure the Drives setting (in your computer's CMOS setup program) that corresponds to the SCSI boot drive is set to None or No Drives Installed, as required for SCSI hard disk drives. See the documentation supplied with your computer for more information.

Ensure the Host Adapter BIOS setting in the SCSISelect utility is Enabled.

Ensure the Extended BIOS Translation feature in the SCSISelect utility is Disabled. The OS automatically selects the correct translation method as needed.

Examine the SCO UNIX mscsi file to make sure the correct host adapter and device are specified as the boot entry. The boot entry is the first Sdsk entry in the mscsi file (see step 3 in the section Installing the Driver When SCO UNIX is Already Installed for additional information). For SCO OpenServer 5.0.5, the boot entry looks like one of the
two examples below:

ad160 Sdsk 0 0 0 0

Note: Each field is separated by a tab. Do not use the spacebar to separate fields.

The meanings of the fields are as follows:

* This field applies to SCO OpenServer 5 and later.

Host Adapter Prefix: Identifies the name of the host adapter driver. If you are booting from an Ultra160 Family host adapter, the Host Adapter Prefix must be ad160.

SCSI Device Type: Identifies the type of SCSI device. For example, Sdsk indicates that the device is a hard disk; Srom indicates a CD-ROM drive; and Stp indicates a tape drive.

Host Adapter Number: Identifies the SCSI host adapter that the SCSI device is attached to. For example, the first Ultra160 Family host adapter is 0, the second Ultra160 Family host adapter is 1. Target ID: Identifies the SCSI ID of the SCSI device. Logical Unit Number: Identifies the Logical Unit Number (LUN) of the SCSI device. This field is usually 0. Bus: Identifies the SCSI bus that the SCSI device is attached to. For most Adaptec host adapters, the bus number is 0.

If you need to edit the mscsi file, use the vi editor. You must build a new kernel in order for any changes to take effect (see step 4 in the section Installing the Driver When SCO UNIX is Already Installed).

If you are booting from an Ultra160 Family host adapter and are using ISA/EISA-based host adapters as secondary devices, you must disable the BIOS on all ISA/EISA-based host adapters. If you are booting from ISA/EISA-based host adapters and are using an Ultra160 Family host adapter as a secondary device, see your ISA/EISA-based host adapter documentation to ensure the host adapter is at the lowest BIOS base address. ISA/EISA-based host adapters boot before the Ultra160 Family host adapters.

My computer crashes or displays panic messages at boot time.

You may have to boot from the backup kernel created earlier. To boot from the backup kernel, follow these steps:

1) Reboot the system.

2) At the Booting UNIX System... prompt, type unix.orig
and press Enter.

3) Your system should now boot from the backup kernel that you created prior to the driver update.

My computer hangs during heavy system load activity.

You may have to increase the maximum size available for configuration information. To change the maximum size available for configuration information, follow these steps:

1) At the prompt, type the following command and press Enter:

cd /etc/conf/cf.d

2) Type ./configure and press Enter.

3) Under the Configuration tunables, select the Miscellaneous System Parameters.

4) Enter the new value for the maximum size of configuration info.

5) After increasing the maximum size of configuration info, type q to quit.

6) Type Y to update the system configuration files.

7) Type ./link_unix and press Enter to relink the kernel.

8) Type Y to boot from the new kernel by default.

9) Type Y to rebuild the kernel environment.

10) Reboot the system.

Error Messages

The error messages listed below are the messages associated with the ad160 driver. Messages are listed sequentially according to the last three digits of the error code. For example, [xxxxx020], [xxxxx021], [xxxxx022], etc.

[xxxxx020] Adapter or target device not responding or not connected

The target device did not respond to the adapter. If the device is present, refer to your host adapter User's Guide for troubleshooting information. If the device is no longer connected to the system, ignore this error.

[xxxxx022] Adapter or target device protocol error

The adapter or target device has broken the communication protocol. A temporary problem could be the cause. Normally this is not a serious problem. If you get this message frequently over a short period of time, it could indicate that the device or system
is malfunctioning. Unplug or power down unused devices to see if the problem persists.

[xxxxx030] Target device busy [xxxxx032] Target device busy

The target device reports a busy status. Another program might already be using this device.

[xxxxx09D] Unexpected interrupt

The Adaptec driver received an interrupt from the system that does not correspond to any adapter supported by the driver. This could be caused by another host adapter from a different vendor, such as a video card or a network card. The problem can also be caused by

malfunctioning hardware.

[xxxxx0a3] Adapter diagnostic failure - possible resource conflict

The driver failed the internal software or hardware diagnostic. Refer to your host adapter User's Guide for troubleshooting information.

[xxxxx0ca] Cannot initialize device

The system, host adapter, or target device is busy or is not responding. The target device could not be initialized.

[xxxxx0cb] Unable to allocate memory. Decrease ad160_instr_buffersz in space.c

The driver has requested a larger buffer size than the available RAM. Either add RAM to the system, or decrease the user option ad160_inotr_buffersz in the /etc/conf/pack.d/ad160/space.c file.

[xxxxx0cc] CONFLICT: Disconnection must be enabled in order
for tagged queueing to work

Use the SCSISelect utility of your host adapter to enable Disconnection for each device reporting this message. Alternatively, disable tagged queuing in /etc/conf/pack.d/ad160/space.c file by setting ad160_do_tagged = 0. If tagged queuing is disabled, performance may be negatively affected.