home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 4 Drivers
/
04-Drivers.zip
/
dac960sw.zip
/
swkit.EXE
/
README.SCO
< prev
next >
Wrap
Text File
|
1998-03-24
|
6KB
|
172 lines
Mylex Corporation
NOTES ON SCO 5.x and UnixWare 2.x DRIVERS
Date: March 18, 1998
DAC960 Driver:
- MSCSI Compliant
- Multi Processor Safe, Multi-threaded
- Single driver for Uniprocessor and Multiprocessor Environments.
- Supports up to 4 DAC960 adapters
- Supports Non-Disk Devices on any Channel. SCSI Id's need to be unique
across channels.
- Adapters/Hard Disks can be configured using standard SCO utilities
- Supports EISA, PCI and MCA DAC960 models
- Supported under SCO Rel 5.0.x
Utilities:
- dac960sh - Front end DAC960 Shell Administrator Utility
- dac960tk - To perform low level DAC960 specific commands
- rbldsh - Utility to rebuild redundant system drives
- dacmon - Monitor utility to monitor all configured DAC960 Adapters
Packaging:
- The driver and utilities are packaged in SCO BTLD format
Naming convention:
- Driver package name: mdac
- Driver name : mdac
- Adapter Nodes name : /dev/rdaN00, where N is adapter number
- Hard Disk/Tape/Cd-ROM nodes: SCO standard naming.
****************************SCO OpenServer 5.0******************************
NOTES ON SCO OpenServer 5.0
NOTE 1
If you are installing the DAC960 on a system with a secondary or an imbedded
Host Bus Adapter, the BIOS information of that adapter may remain visible to
the SCO OpenServer Installation Program. This can happen on some motherboards
even though you think that you have disabled the BIOS. The result is that SCO
will detect the on-board controller and make it the default SCSI. During the
installation process, after you have typed "ahslink=mdac" as instructed, SCO
will report:
warning : no root disk controller
warning : no root disk device
To bypass this problem, the user needs to enter a bootstring instead of the
default "ahslink=mdac" for SCO 5 to specify the installation is on the DAC960.
Procedure :
At the boot prompt, enter :
defbootstr ahslink=mdac Sdsk=mdac(0,0,0,1)
Following is the meaning of the above bootstring ( refer to the SCO
Openserver handbook):
periph=adapter(hanum,bus,id,lun)
Periph Sdsk = SCSI hard disk
adapter mdac - Mylex host adapter drivers prefix
hanum host adapter number ( from 0-7), 0 for 1st Mylex controller
bus number of SCSI bus on adapter, usually 0 on DAC960
id logical drive number, usually 0 for the first System Drive
lun use LUN number 1 for hard disks on Mylex DAC960
NOTE 2
Errors during Installation:
During fresh installation of SCO Unix Rel 5.0.x using DAC960 driver BTLD
diskette "mdac", the following error message appears on the screen
Error Message: Extracting BTLD distribution for mdac ...
/etc/uadmin getdev b mdac: (No such device 19)
Status: This doesn't seem to have any effect on installation. The system
would work fine once the installation is complete. This issue is being
investigated.
NOTE 3
The Driver does not support shared interrupts in multiprocessor mode and
support for shared interrupts is automatically disabled even under
uniprocessor mode. To enable shared interrupts for uniprocessor mode change
the following in the /etc/conf/pack.d/mdac/space.c file:
int mdac_share_pci_irqs = 0; (default setting)
int mdac_share_pci_irqs = 1; (uniprocessor shared IRQ setting)
After changing this value relink and reboot for shared IRQs to take effect.
NOTE 4
If the 'Verify Software' program is run under 'scoadmin' and you Fix Discrepencies,
an old version of 'dac960sh', 'dac960mon', and 'dac960tk' will replace the current
utilities which will produce warnings and error messages. In order to fix this
the mdac driver must be reinstalled by using the 'installpkg' utility. Be sure to
be in single user mode when performing this operation. After reinstalling the
driver the kernel must be relinked and rebooted.
**********************************************
Driver Scanning:
- The driver scans for DAC960 adapters in the following order
1). DAC960 PCI adapters with FirmWare version < 3.x
2). DAC960 PCI adapters with FirmWare version >= 3.x
3). DAC960 EISA adapters
4). DAC960 MCA adapters
Note that it is very important to remember this order, while configuring
adapters (hardware, software), in order to ensure consistent mapping
across driver/utils/hardware.
****************************UnixWare 2.x******************************
NOTE 1
IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT
!!!!!!!!!!! THE DAC960PG, DAC960PJ, DAC960PR and DAC960PT REQUIRE SPECIAL FILES
IN ORDER TO INSTALL UNIXWARE 2.X !!!!!!!!!!!!
The DAC960PG/PJ family of controllers are multifunction devices and require
multifunction support in the system BIOS and the driver in order to boot. The current
embedded drivers in Unixware 2.x do not support multifunction devices. To install
Unixware on either of these controllers you need to get both the updated installation
diskette and the supplement diskette. These can be obtained from the SCO WEB site with
the names ptf3256 for the installation diskette and ptf3256.s for the supplement diskette.
They can also be obtained from Mylex's Web site at mylex.com with the names
ptf3256.boot.dd.exe for the updated installation diskette and prt3256.s.exe for the
supplement diskette.
NOTE 2
If UnixWare is installed onto an IDE and GAM server is to be installed, the
dak driver must be loaded prior to installing GAM using the pkgadd command
('pkgadd -d diskette1 dak'). Installation of GAM server can then be performed
using the command 'pkgadd -d diskette1 GAM'. The kernel must then be relinked
and rebooted.