Release: SCO Unix ASC Universal Driver 2.9D
Last Updated: 04/26/00
Copyright (c) 2000
The AdvanSys SCO Unix Universal Driver supports AdvanSys SCSI
Adapters for the SCO Unix 4.2, OpenServer 5.0, and OpenServer
5.0.2, 5.0.4 , 5.0.5 Releases.
The SCO directory includes the following files. The latest versions
of these files are contained on the AdvanSys FTP site. If the date
listed in the SCO.TXT file is more than a few months old, please
check the FTP site for a newer version of the driver.
SCO.TXT Installation Instructions
SCOBTLD.EXE DOS Self-extracting Boot Diskette Image
SCOBTLD.Z UNIX Compressed Boot Diskette Image
To install the SCO Universal Driver you will need to create a
Boot Diskette containing the driver. You may create the diskette
using either a DOS or Unix system. Decide which system to use and
follow the directions below. After the diskette is created it can
be used to add the driver during an SCO Unix installation or used
to add the driver to an existing SCO Unix system. Directions for
both of these installation options are listed below.
Supported Adapters
==================
The CDB counts below indicate the number of SCSI CDB (Command
Descriptor Block) requests that can be stored in the RISC chip
cache and board LRAM. A CDB is a single SCSI command. This value
can be lowered in the BIOS by changing the 'Host Queue Size' adapter
setting.
Connectivity Products:
ABP510/5150 - Bus-Master ISA (240 CDB) (Footnote 1)
ABP5140 - Bus-Master ISA PnP (16 CDB) (Footnote 1, 3)
ABP5142 - Bus-Master ISA PnP with floppy (16 CDB) (Footnote 4)
ABP920 - Bus-Master PCI (16 CDB)
ABP930 - Bus-Master PCI (16 CDB) (Footnote 5)
ABP930U - Bus-Master PCI Ultra (16 CDB)
ABP960 - Bus-Master PCI MAC/PC (16 CDB) (Footnote 2)
ABP960U - Bus-Master PCI MAC/PC Ultra (16 CDB)
Single Channel Products:
ABP542 - Bus-Master ISA with floppy (240 CDB)
ABP742 - Bus-Master EISA (240 CDB)
ABP842 - Bus-Master VL (240 CDB)
ABP940 - Bus-Master PCI (240 CDB)
ABP940U - Bus-Master PCI Ultra (240 CDB)
ABP970 - Bus-Master PCI MAC/PC (240 CDB)
ABP970U - Bus-Master PCI MAC/PC Ultra (240 CDB)
Dual Channel Products:
ABP752 - Dual Channel Bus-Master EISA (240 CDB Per Channel)
ABP852 - Dual Channel Bus-Master VL (240 CDB Per Channel)
ABP950 - Dual Channel Bus-Master PCI (240 CDB Per Channel)
Footnotes:
1. This board has been shipped by HP with the 4020i CD-R drive.
The board has no BIOS so it cannot control a boot device, but
it can control any secondary SCSI device.
2. This board has been sold by Iomega as the Jaz Jet PCI adapter.
3. This board has been sold by SIIG as the i540 SpeedMaster.
4. This board has been sold by SIIG as the i542 SpeedMaster.
5. This board has been sold by SIIG as the Fast SCSI Pro PCI.
Instructions for creating the ASC Universal Driver Diskette from DOS
====================================================================
The file scobtld.exe is a self-extracting archive which contains
an image of an SCO Unix EAFS file system. The image can be copied
to a 3.5" diskette to make an ASC Universal Driver BTLD diskette.
1. Copy the file scobtld.exe from the AdvanSys DOS diskette containing
the directory SCO to a DOS system.
> copy a:\sco\scobtld.exe
2. Type the command scobtld.exe. The following two files will be created:
btld.dat
unixfer.exe
3. Insert a blank formatted diskette in the 3.5" floppy disk drive and create
the diskette with the following command.
> unixfer btld.dat a:
4. To verify the contents of the diskette unixfer can also be run in
reverse. The file btld.dat should exactly match test.dat.
> unixfer a: test.dat
> fc btld.dat test.dat
Instructions for creating the ASC Universal Driver Diskette from SCO Unix
=========================================================================
The file scobtld.Z is a compressed image of an SCO Unix EAFS file system.
The image can be copied to a 3.5" diskette to make an ASC Universal
Driver Diskette.
1. Copy the DOS file SCOBTLD.Z from the AdvanSys DOS diskette containing
the directory SCO to an SCO Unix system.
$ doscp a:/sco/scobtld.z scobtld.Z
2. Uncompress the file scobtld.Z with the following command.
$ uncompress scobtld.Z
3. Insert a blank diskette in the 3.5" floppy disk drive and use
"dd" to create the diskette with the following command.
$ dd if=scobtld of=/dev/rfd0 bs=64k
4. To verify the contents of the diskette run dd in reverse.
The file scobtld should exactly match test.dat.
$ dd if=/dev/rfd0 of=test.dat bs=64k
$ cmp scobtld test.dat
Installing the ASC Driver during SCO Unix Installation
======================================================
1. Create an AdvanSys driver diskette as described above. Label
the diskette "AdvanSys SCO BTLD Diskette." Please also record
the version of the driver on the diskette. The driver version
number should be listed at the beginning of this file.
2. Set-up your devices to have the following SCSI Target IDs:
Hard Disk: 0, CD-ROM: 5, and Tape Drive: 2.
3. Boot the system with the SCO installation boot disk.
4. Type "link" at the boot prompt "Boot:". This will cause SCO
to dynamically link the AdvanSys driver into the install
kernel. The AdvanSys driver is a BTLD (Boot Time Loadable
Driver).
5. When the installation asks you what package to link, enter
"asc". This is the name of the AdvanSys BTLD driver package.
NOTE : When using both "asc" and "adv" drivers, type in
"asc" first. "adv" is the SCO-OpenServer driver for AdvanSys
UW/U2W/U3W SCSI adapters.
6. Insert the "AdvanSys SCO BTLD Diskette" into the floppy drive when
the system requests it. Note: The diskette should not be inserted after
entering "asc". The install procedure will ask for it later.
7. The install procedure may ask for the "AdvanSys SCO BTLD Diskette"
more than once.
8. At the end of the installation, you may be asked: "Do you want to
replace 'auto' with 'asc' Y or N." Answer yes to the question.
Installing the ASC Driver after SCO Unix has already been Installed
===================================================================
1. Create an AdvanSys driver diskette ask described above. Label
the diskette "AdvanSys SCO BTLD Diskette." Please also record
the version of the driver on the diskette. The driver version
number should be listed at the beginning of this file.
2. Type the command "installpkg" from the SCO Unix command line.
3. Insert the "AdvanSys SCO BTLD Diskette" into the floppy drive
when prompted.
4. After installation, type the following commands to rebuild a
new kernel that contains the asc driver. For more information
refer to the SCO documentation regarding compiling the kernel.
cd /etc/conf/cf.d
./link_unix
Installing SCSI Devices under SCO Unix
=======================================
To create device files to access SCSI devices use the SCO "mkdev"
command. "mkdev" is an interactive command that will ask you questions
about your SCSI configuration, make kernel configuration changes, and
re-build the kernel. Type "mkdev hd" for disks, "mkdev tape" for tape
drives, and "mkdev cdrom" for CD-ROM devices.
"mkdev" will ask the name of the AdvanSys driver and AdvanSys SCSI adapter
number. The driver name is "asc" and adapter numbering begins with 0. If
there is one AdvanSys adapter enter "0", a second adapter is number "1",
etc. For disk devices "mkdev hd" should be run twice. The second time it is
run after the kernel has been re-built and booted so that the disk can be
partitioned and file systems can be built.
The "mkdev" kernel configuration file is /etc/conf/cf.d/mscsi. It can be
viewed with an editor to verify "mkdev" has added the correct parameters
to the kernel configuration.
Here is a basic list of SCO SCSI device files:
Disk Device Files: /dev/[r]dsk/[0-9]s[0-9]
Tape Device Files: /dev/[nruh]Stp[0-9]
CD-ROM Device Files: /dev/[r]cd[0-9]
Installation Problems and Troubleshooting
=========================================
Problem 1:
----------
The AdvanSys SCSI Host Adapter controls the boot disk.
When the system boots the following warning message is printed
and, the SCSI disk is NOT recognized.
WARNING: hd: no root disk controller
Resolution 1: Make sure that the SCSI Disk is at ID 0.
Resolution 2: When there are multiple HBAs installed ( AdvanSys or
from other vendors ), the root hard disk is expected to be on the
first of these HBAs as detected by the OS.
To change this default, enter the following string after "link"
at the "Boot:" prompt. ( Step 4 of Installation procedure)
defbootstr Sdsk=asc(ha_num, SCSI ID, 0)
Example : link defbootstr Sdsk=asc(1,0,0)
Note :
The ha_num can be found from the line printed by the AdvanSys
Driver.
%asc 0x6000-0x6040 11 0 AdvanSys SCSI 2.9D ha_num=0
%asc 0x6000-0x6040 13 0 AdvanSys SCSI 2.9D ha_num=1
. .
. .
%asc 0x6000-0x6040 15 0 AdvanSys SCSI 2.9D ha_num=n
Problem 2:
----------
The CD-ROM drive is not being recognized by the OS and the
following error message is displayed :
NO RESPONSE : There is no response from the controller for the
device that you have selected.
Resolution 1 : Make sure that the SCSI ID correct.
Resolution 2 : Make sure that the SCSI Adapter type is asc.
Resolution 3 : Make sure that the SCSI Host Adapter is correct.
When there are multiple AdvanSys HBAs this will take values
0,1,2....
Resolution 4 : Restart the Installation procedure and change the
default CDROM settings as follows.
To change this default, enter the following string after "link"
at the "Boot:" prompt. ( Step 4 of Installation procedure)
defbootstr Srom=asc(ha_num, SCSI ID, 0)
Example : link defbootstr Srom=asc(1, 5 ,0)
Problem 1: The AdvanSys SCSI Host Adapter controls the boot disk.
When the system boots the following warning and panic messages
are printed:
WARNING: hd: no root disk controller
PANIC: srmountfun - Error 19 mounting rootdev (1/40)
Resolution 1: These error messages indicate that the AdvanSys driver is
not compiled into the SCO UNIX kernel being booted or on an initial
installation the SCSI hard disk is not set to target ID 0.
If you are performing a first time installation make sure that your
SCSI hard disk target ID is 0. This is an SCO Unix requirement.
To recover if you have rebuilt the SCO UNIX kernel and the previous
kernel worked with the AdvanSys adapter, then at the boot prompt "Boot:"
type "unix.old". This will cause the last kernel to be booted ("unix.old")
instead of the currently installed kernel ("unix"). After restarting
the system, rebuild the SCO kernel to include the AdvanSys driver.
If you have never booted a kernel with the AdvanSys driver or do
not have a kernel saved with the AdvanSys driver, then you may be
able to boot the system using the "AdvanSys SCO BTLD Diskette". Make
the diskette as described above. At the boot prompt "Boot:" type
"link unix btld=fd(64) hd=asc". This will cause SCO to ask for a
driver to be dynamically linked into the kernel being booted.
Enter the package name "asc" when prompted for a package to link.
This is the name of the AdvanSys BTLD driver package. This command
may only work for later releases of SCO UNIX.
If you are successful booting your system look at the file
/etc/conf/cf.d/mscsi. This file should indicate that the AdvanSys
driver (asc) is controlling your boot disk. Refer to the manual
page mscsi(F) for more information. If the mscsi file does not
indicate the AdvanSys driver is controlling the boot disk you need
to reconfigure your kernel with the mkdev(ADM) command. Type "mkdev hd"
specifying the AdvanSys driver ("asc") controls the SCSI boot disk,
and build and install a new kernel.
If you are unable to boot your system from its hard drive root disk,
you will need to boot from an emergency boot diskette (hopefully you've
already created one) otherwise you may have to re-install the system.
Problem 2: When the AdvanSys driver is loaded the error message
"Characteristic h not valid" is printed.
Resolution 2: This warning can be ignored. Some versions of SCO
UNIX do not support the driver characteristic 'h', which indicates
that a device is a SCSI host adapter. Refer to the mdevice(F)
manual page for more information.
Problem 3: What does the AdvanSys boot string mean?
Resolution 3: At boot time the AdvanSys driver prints a line for
each AdvanSys SCSI Host Adapter installed in the system. Here is
a sample line printed for an AdvanSys ISA SCSI Host Adapter:
%asc 0x0110-0x011F 11 7 AdvanSys SCSI 2.3.6 fts=sbtn ha_num=0
The message indicates that an AdvanSys SCSI Host Adapter was found
at I/O Ports 0x110-0x11F. The adapter uses IRQ 11 and DMA channel
7. Note: If no DMA channel is needed as for VL, EISA, and PCI
adapters this number will be 0. The "fts" string indicates
supported SCSI driver features (s - scatter-gather, b - command
buffering, t - tagged queuing, n - no mapping). "ha_num" is the
system host adapter number for the adapter. All boot messages
including the AdvanSys driver boot message are logged to the
file /usr/adm/messages.
Problem 4: During SCO OpenServer 5.0 installation the keyboard locks
up and does not accept any keyboard input.
Resolution 4: This is a known SCO OpenServer 5.0 problem on faster
systems with an AMI keyboard BIOS. SCO has a solution for the
problem available from their technical support. The problem
can be identified as OSS424A. Here is the FTP location of the
solution:
ftp://ftp.sco.com/SLS/oss424a.ltr.Z
ftp://ftp.sco.com/SLS/oss424a.Z
Contact Information
=====================
Mail: Initio Corporation
2205 Fortune Drive Suite A
San Jose, CA 95131
Operator: 1-408-577-1919
FAX: 1-408-577-0640
Tech Support: 1-800-965-5039
Tech Support E-Mail: support@initio.com
Web Site: http://www.initio.com
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.