README
Adaptec Ultra320 Device Driver
for
IBM OS/2 Warp Server for eBusiness
Revision 1.0.RC01a
September 3, 2003
Copyright:
©2003
Adaptec, Inc. All rights reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted in any form or by any
means, electronic, mechanical, photocopying, recording or otherwise, without
the prior written consent of Adaptec, Inc.,
Notice:
The
material in this document is for information only and is subject to change
without notice. While reasonable efforts have been made in the preparation of
this document to assure its accuracy, Adaptec, Inc. assumes no liability
resulting from errors or omissions in this document, or from the use of the
information contained herein.
Adaptec
reserves the right to make changes in the product design without reservation
and without notification to its users.
1..... Changes from
Prior Releases
3..... Supported Adaptec Host
Adapters
4..... Supported Operating System
7..... Installation Instructions
7.1 Installing
a New Driver or Updating an Existing Driver
7.1.1 Using
“OS/2 Device Driver Install” Program
7.2 First-Time
Installation from CD-ROM
1
Changes
from Prior Releases
|
Revision |
Description |
|
1.0.A00 |
Pre-Alpha release 1. Preliminary Readme file. |
|
1.0.A01 |
Alpha01 release 1. Added Table of Contents, Hyperlink,
Left Frame Table of Contents, document format. |
|
1.0.B01 |
Beta01 release 1. Added into Section 9 - Known Issues,
a description about PCI IRQs allocation conflicts on the IBM Granite & Opal
Servers with ServeRAID and U320 adapters. |
|
1.0.RC01 |
RC01 release 1. Added into Section 9 - Known Issues,
a description about BackAgain 2000, OS2ASPI and config.sys. 2. General cleanup. Reformat document. |
|
1.0.RC01a |
RC01a release 1. Updated Section 9 - Known Issues, a
description about BackAgain 2000, OS2ASPI.DMD and config.sys. 2. Updated Sections 5 & 6. 3. Added Copyright and Notice. 4. Added header and footer. |
2 Diskette Contents
The
following files are included in this diskette:
|
File |
Description |
|
\AICU320\AICU320.ADD |
Ultra320
SCSI driver for OS/2 Warp Server for e-business |
|
\AICU320\AICU320.DDP |
AICU320
device driver profile |
|
\AICU320\U320PRES.EXE |
Adaptec
Ultra320 Family Devices Detection Module |
|
\README\READOS2.HTM |
This
file |
3 Supported Adaptec Host Adapters
The
following Adaptec SCSI Host Adapters are supported by the Adaptec Ultra320 OS/2
Device Driver.
|
Host Adapter |
ASIC |
Vendor ID |
Device ID |
Subsystem Vendor ID |
Subsystem ID |
Description |
|
AIC-7901 |
H2A |
9005 |
800F |
9005 |
FFFF |
Single Channel PCI-to-Ultra320 SCSI ASIC |
|
AIC-7901 |
H1B |
9005 |
801E |
9005 |
FFFF |
Single Channel PCI-to-Ultra320 SCSI ASIC |
|
AIC-7902 |
H2B |
9005 |
801D |
9005 |
FFFF |
Dual Channel PCI-to-Ultra320 SCSI ASIC |
|
ASC29320LP |
H1A |
9005 |
8014 |
9005 |
0044 |
Single Channel 64-bit Low Profile PCI-to-Ultra320
SCSI Host Adapter |
|
ASC29320ALP |
H1B |
9005 |
8017 |
9005 |
0044 |
Single Channel 64-bit Low Profile PCI-to-Ultra320
SCSI Host Adapter |
|
ASC39320A |
H2B |
9005 |
8016 |
9005 |
0040 |
Dual Channel 64-bit Low Profile PCI-to-Ultra320 SCSI
Host Adapter |
4 Supported Operating System
|
Operating System |
Version |
Convenience Pack |
|
IBM OS/2 Warp Server for e-Business |
4.52 |
2 |
5 Supported Servers
|
Servers (List IBM Servers under the Server Proven Program that are supported
by this Ultra320 Device Driver) |
Model Number |
Description |
|
Opal |
8647-21Z |
|
|
Granite |
8671-4AX |
|
6 Supported SCSI Devices
There
is no requirement to support single-ended devices. The AICU320.ADD Ultra320
SCSI driver supports the following LVD devices:
|
SCSI Device Type |
Manufacturer |
Supported Model Numbers |
Firmware Revision |
|
Hard Drives |
Maxtor |
Atlas
10KIII 36GB |
B430 |
|
|
Seagate |
Cheetah
ST318432LW 15K.2 18GB |
0024 |
|
|
IBM |
UltraStar
IC35L146UCDY10-0 146GB |
S25F |
|
|
Fujitsu |
MAP3735NP
73GB |
0107 |
|
|
|
DK32EJ-72NC
68GB |
TPTP |
|
|
|
IC354L036vCDY10-0 |
|
|
Tape Devices |
Dell/Quantum |
TR-S13AA-AZ
SDLT |
|
|
|
Dell |
Powervault
110t VS80 |
|
|
|
Quantum |
00N8015
SDLT1 |
|
|
|
Quantum |
59P6736
SDLT320 |
|
|
|
EXABYTE |
59P6746
VXA-2 |
|
|
|
HP |
24P2396
HH LTO |
|
7 Installation Instructions
The AICU320.ADD Ultra320 SCSI driver only supports OS/2
Warp Server for e-business.
7.1 Installing a New Driver or Updating an Existing Driver
7.1.1 Using “OS/2 Device Driver Install” Program
(NOTE: When installing a new host
adapter, make sure it is inserted in the system before installing the driver.)
1. Insert the Adaptec’s OS/2 Ultra320
Device Driver Installation Floppy in the appropriate floppy drive.
2. Select the System Setup
Icon in the tools bar at the bottom of the OS/2 desktop, select Install/Remove and then select Device Driver
Install.
3. Alternatively, you can also
accomplish the same by opening on the OS/2 desktop, the OS/2 System
folder, the System Setup folder, the Install/Remove folder and then double-click on the Device Driver Install icon.
4. In the OS/2 Warp 4 Device Driver
Installation dialog box, if the Installation Floppy is not located in A:, change the default Source directory to point to the
appropriate drive. The Device Driver Install program makes use of the
destination directory information contained in the Device Driver profile file
(AICU320.DDP) on the floppy and installs the AICU320.ADD driver into the
\OS2\BOOT directory. You can, however, also change that by specifying a new
Destination directory.
5. Select Install… to
start the installation process.
6.
*** IMPORTANT *** After the installation has been completed, be sure to check
the C:\ directory and delete any previous versions of the AICU320.ADD drivers before
rebooting the system. If you do not remove those drivers, OS/2 will load them
instead of the new drivers that you have just installed. You can easily check
for the existence of multiple copies of the driver by typing at the C:\ prompt,
dir aicu320.add /s.
7. Select EXIT and reboot the
computer.
7.1.2 Installing Manually
You may also install the driver manually by
using the following steps.
1. Copy AICU320.ADD to C:\OS2\BOOT.
2. Add the following line to your
CONFIG.SYS file:
BASEDEV=AICU320.ADD /V.
7.2 First-Time Installation from CD-ROM
(NOTE: To install the driver, it is
necessary to copy the driver from the Adaptec’s OS/2
Ultra320 Device Driver Installation Floppy on to the OS/2 Diskette 1. However, before
you can copy the driver, you must first remove various files from the OS/2
Diskette 1, as explained in step 2 below.)
1.
Type
CDINST from CD-ROM drive and follow the instructions to create the boot
diskettes from the OS/2 Installation CD.
2. Delete some of the existing files
on the OS/2 Diskette 1 so that approximately 200 KB of disk space is available
on the diskette. Use the following information to help you decide which files
to delete:
·
If
the Ultra320 host adapter is the only Adaptec host adapter installed in your
system, delete all other Adaptec drivers (aha152x.add, aha154x.add,
aha164x.add, aha174x.add, aic7770.add, aic7870.add, aic78u2.add and
fd16-700.add).
·
For
each driver removed from the OS/2 Diskette 1, remove its corresponding line in the
config.sys file (also on OS/2 Diskette 1). For example, if you deleted all
Adaptec drivers as explained in the above, remove the following lines from the
config.sys file:
rem basedev=aha152x.add
rem basedev=aha154x.add
rem basedev=aha164x.add
rem basedev=aha174x.add
rem basedev=aic7770.add
rem basedev=aic7870.add
rem basedev=aic78u2.add
rem basedev=fd16-700.add
·
If
you have deleted the suggested Adaptec drivers and you still do not have
approximately 200 KB of disk space available on the diskette, delete the file:
CDINST.EXE.
*****************************************************************
Note: The following files MUST NOT BE
DELETED from Diskette 1:
CLOCK01.SYS,
CLOCK02.SYS, IBM1S506.ADD, IBM1FLPY.ADD, IBM2FLPY.ADD, IBM2ADSK.ADD,
IBM2SCSI.ADD, IBMINT13.I13, IBMKBD.SYS, KBDBASE.SYS, OS2LOGO, OS2DASD.DMD,
PNP.SYS, RESERVE.SYS, RESOURCE.SYS, SCREEN01.SYS, SCREEN02.SYS, XDFLOPPY.FLT,
and all *.SNP files.
*****************************************************************
3. Copy the driver from the Adaptec’s OS/2
Ultra320 Device Driver Installation Floppy onto
the OS/2 Diskette 1 (\AICU320\AICU320.ADD).
4. In the config.sys file on OS/2
Diskette 1, add the line
set copyfromfloppy=1
5. This line should be added so that the
install process copies the AICU320.ADD driver from the OS/2 Diskette 1, rather
than the driver included on the OS/2 CD-ROM.
6. Add the following line to the top
line of config.sys on OS/2 Diskette 1.
BASEDEV=AICU320.ADD /V
7. Run the OS/2 installation program;
follow the instructions in your OS/2 documentation, until you reach the System
Configuration window.
8. In the System Configuration
window, click the SCSI Adapter Support icon.
9. Deselect any highlighted adapters
(including the Adaptec 294x, 394x, AIC7870 PCI SCSI), and click OK.
(NOTE: If these adapters are not deselected, the driver
included on the CD-ROM will be copied over the driver being installed.)
10. Follow the instructions in your
OS/2 documentation to complete the installation.
8 Command Line Options
OS/2
adapter device drivers (.ADD files) are normally installed automatically and
require no further information from the user. However, in certain situations
the user may wish to modify the behavior of the driver to meet their specific
needs.
(IMPORTANT:
Please proceed cautiously with the following information.)
The
standard format for command line switches is:
BASEDEV=AICU320.ADD
[GlobalParam][AdapterID][UnitParam]{[ScsiTargetID]}
GlobalParam Global Parameters. These options apply to all adapters
controlled by the driver.
·
ET Allow embedded targets. This parameter
indicates that the ADD should assume that all targets have more than one
logical unit (LUN) defined.
·
/!ET Do not allow
embedded targets (DEFAULT). This parameter indicates that the ADD should assume
that all targets have only one logical unit (LUN) defined.
·
/V Load driver verbosely. This parameter
will display the driver name as well as the version number and Adaptec
copyright information. Information on
all targets found in the system will also be displayed.
AdapterID The adapter ID # is assigned
during the device driver initialization and is based on the order that the
adapters are discovered in the system. Each channel on a host adapter is
considered as an independent adapter, hence, a 2 channels host adapter is
assigned with 2 consecutive adapter IDs.
· /A:n where, n is the ID number (zero relative) of the host adapter installed in the system.
UnitParam Unit
Parameters.
General:
·
/I Ignore the
specified adapter. This allows another driver to share the adapters that the
ADD would normally use.
·
/DM: Enable DASD manager support (DEFAULT).
This parameter allows OS2DASD.DMD to control the specified target(s) if they
are identified as DASD (hard disk) devices.
·
/!DM: Disable DASD
manager support. This parameter prevents OS2DASD.DMD from controlling the
specified target(s).
·
/SM: Enable SCSI manager support (DEFAULT).
This parameter allows OS2SCSI.DMD to control the specified target(s) if they
are identified as NON-DASD SCSI devices. All SCSI hard drives will be
controlled by OS2DASD.DMD.
·
/!SM: Disable SCSI
manager support. This parameter prevents OS2SCSI.DMD from controlling the
specified target(s).
·
/
·
/!
Special
:
·
/TAG:n Specifies the
maximum number (n) of tagged commands for all target devices on the host
adapter. A value of 1 disables tagged queuing. The maximum number allowed is
16. The default is 8. U320 devices are required to support tag commands and the
disconnect features. The driver will negotiate with the U320 devices and adjust
its settings accordingly. The driver also maintains a maximum of 2 non-tagged
commands per target internally and sends only one non-tagged command at a time
per target to the host adapter.
ScsiTargetID SCSI
Target IDs. The targets to which the Unit Parameter will be applied.
This parameter may be a single ID (d) or list of IDs (d,d,d).
8.1 Configuration Examples:
Example 1:
Suppose
that you had a removable hard drive as target ID 3 and you wanted to control
the hard drive with an ASPI application and driver. Normally OS2DASD will
allocate this device, treat it as a large floppy and prevent you from sending
any SCSI commands via ASPI. The following command line will prevent OS2DASD.DMD
from accessing the target ID 3 and still allow OS2SCSI.DMD and OS2ASPI.DMD to
share access to it.
BASEDEV=AICU320.ADD /A:0 /!DM:3
Example
2:
Suppose
that you had a multi-disk CD-ROM as target 4 on host adapter 0 and two DASD
devices as targets 1 and 5 on host adapter 1. The following command line will
prevent OS2SCSI.DMD from accessing the CD-ROM and prevent OS2DASD.DMD from
controlling the DASD devices. The driver will also search for multiple LUNs on all
host adapters.
BASEDEV=AICU320.ADD /ET /A:0
/!SM:4 /A:1 /!DM:1,5
Example
3:
The
following command line will set the first host adapter (adapter ID #0) to
support a maximum of 8 tagged commands for all target devices.
BASEDEV=AICU320.ADD /A:0 /TAG:8
9 Known Issues
1.
When
using CDS BackAgain 2000 for tape backup, you may run into the error message “The media in the device appears to contain
data from another application and must be erased before it can be used”.
Try adding BASEDEV=OS2ASPI.DMD to
config.sys and reboot the system. Start the BackAgain 2000 application and
select “Erase Media” during the backup setup process.
2. On the IBM Granite and Opal
servers with ServeRAID controller, the system BIOS automatically assigns IRQs
and you may run into system hardware resources conflict issue when installing
the U320 adapters. You can correct the problem by going into the system BIOS
setup and manually reassign the PCI IRQs.
3. Intel Errata #8511 lists known
data integrity issues with the processor cache on the Saturn-1 chipset
(82424TX). For this reason, Adaptec recommends that processor cache be disabled
via the CMOS setup to avoid data corruption. For more information, see Intel
Errata #8511.
4. There are known installation
problems installing OS/2 Warp v4.0 on a Micron (LSI chipset) 64 bit PCI system.
5. There are known installation
problems installing OS/2 Warp with 8MB of RAM unless all the third-party
basedev statements are removed from config.sys.
6. There are known installation
problems installing OS/2 using two SCSI host adapters on a "
10 Additional Notes
1. This version of the Ultra320
Device Driver supports the AIC-7901/7902 ASIC Family of Host Adapters. Adapter
numbers are first assigned to boards with their BIOS enabled. The numbers are assigned
from lowest BIOS address to highest address. Any remaining boards are assigned
numbers by scanning slots. Each slot is a combination of a bus number and a
device number pair starting from the lowest to the highest numbers, and the
adapters are assigned a number in the order they are found.
Example
Bus 0, device 0
assigned as adapter 0; Bus 1, device 1 assigned as adapter 1, etc.
2. There are no switches for
controlling OS2ASPI.DMD directly. IBM did not define them in their
specification and Adaptec cannot be sure that other host adapters will have the
same switches.
3. OS2SCSI.DMD will only allocate
devices when a device driver requests it, but this will prevent OS2ASPI from
accessing it. There is nothing in the ASPI specification regarding device allocation
so OS2ASPI must rely on other managers to fairly share targets. This should
only be a problem if you have two drivers that use different managers and you
want them both to access the same target at the same time.
4. DO NOT disable DASD manager access
to target ID 0 if you are booting from your SCSI host adapter. This will
prevent the system from booting!
5. Fault Tolerance is supported in
the driver. However, ABORT and SCSI BUS RESET will only work for targets that
are properly behaved.
6. IBM does not support installing
the operating system onto magneto optical devices. Additionally, OPTICAL.SYS
(OS/2 3.0) or OPTICAL.DMD (OS/2 4.0) allows magneto optical devices to be
supported as though they were large floppy devices. LOCKDRV.FLT allows
removable media such as MO's to be supported as though they were fixed hard
drives.
7. It is not possible to install OS/2
3.0 on drives with capacity greater than 8 GB, nor in a partition greater than
4 GB. The following is the suggestion from IBM on this problem:
Problems
with large partitions and installation or booting: There is a BIOS restriction
that installable (startable) or bootable partitions must be contained within
the first 1024 physical cylinders of the disk. FDISK does not enforce this
limitation. If you have installation or boot failures this could be the reason.
Use FDISK to reduce the size of your startable or bootable partition by
sufficient MBs. One way to calculate the correct size partitions is to do the
following:
1)
Edit
your CONFIG.SYS and add the following parameter to the BASEDEV=IBM1S506.ADD
line as below:
BASEDEV=IBM1S506.ADD /V
2) Save this change.
3) Reboot your system.
4) At initialization, record the far
left hand column of number of the Geometry information under the ACT heading.
Example:
ACT
Cyl 1027 Head 63 Sec 128 (head x sec) /2 = bootable partition must be contained
within this boundary in MBytes (round down)
This
is the maximum size of a bootable partition in MBytes. Any bootable partition
must also be contained from the beginning of the drive to this number of
MBytes. A bootable partition may be smaller than the maximum size but still
must be contained within this boundary. In this example the bootable partition
must be contained in the first 4032 MBytes of the disk and cannot exceed a single
partition size of 4032 MBytes within this area. No bootable partition may
extend beyond the first 4032 MBytes. Use this information when configuring your
bootable partition with FDISK.
8. OS/2 will allocate the SCSI
devices as the order in CONFIG.SYS if two drivers (such as the AIC160.ADD and
AICU320.ADD) are loaded.
9. OS/2 will assign drive letters for
SCSI devices first then IDE devices.
11 Contacting Adaptec
Technical
information, including product literature, answers to commonly asked questions,
information on software upgrades, and other topics is available electronically
through the following:
·
Search
the Adaptec World Wide Web site at http://www.adaptec.com
·
Search
the Adaptec Support Knowledgebase (A.S.K.) at http://www.adaptec.com/support/ for
articles, troubleshooting tips, and frequently asked questions for your
product.
·
For
Internet support, send technical questions to Adaptec's Technical Support
Specialists via WebMail at http://www.adaptec.com/support/webmail.html
.
To speak with a Technical Support Specialist, call 408-934-7274, Monday-Friday,