____________________ (c) 1998 The Santa Cruz Operation, Inc. All rights reserved. SCO OpenServer Release 5.0.5 Driver Supplement This document covers the following topics: + ``Highlights of this supplement'' + ``Who should install the supplement?'' + ``Creating a BTLD disk'' + ``Installing BTLDs at boot-time'' + ``Installing BTLDs after boot-time'' + ``Modified man pages'' Highlights of this supplement This supplement provides the following modified Host Bus Adapter Boot- Time Loadable Drivers (BTLDs) for SCO OpenServer(TM) Release 5.0.5 systems: Adaptec alad bug fixes Adaptec blad updated hardware support Mylex mdac updated hardware support ncr bug fix that prevents panic during install Symbios slha updated hardware support and bug fixes wd bug fixes Modified man pages for blad(HW), mdac(HW), slha(HW), and wd(HW) are provided at the end of this document. If you have questions regarding this supplement, or the product on which it is installed, please contact your software supplier. Who should install the supplement? This supplement can be installed on any SCO OpenServer Release 5.0.5 system where support for the aforementioned BTLDs is required. The Link Kit must be installed on your system to use BTLDs. For more information, see ``Using boot-time loadable drivers'' in the SCO OpenServer Handbook. Creating a BTLD disk Drivers included in this supplement are installed from a floppy disk image. You can create a floppy disk containing this images with the ezcp command provided on the CD-ROM. For information about other installation options, please consult the SCO OpenServer Release 5.0.5 Release Notes. The ezcp command is available for use with UNIX or Windows/DOS and is located in the /images directory on the SCO OpenServer Installation CD- ROM. ezcp.bat is an MS-DOS batch file that uses floppycp to copy floppy images to drive A: (the first 3.5-inch floppy drive). ezcp is a UNIX shell script that copies images to /dev/rfd0135ds18 (also known as drive A:). The /images/README file contains a description and instructions. ezcp copies images to the first 3.5-inch floppy drive; use the dd(C) or floppycp command if you need to specify another drive. 1. Insert a formatted disk into the floppy drive. 2. Move to the images directory on the CD-ROM. (For UNIX users, this is usually mounted on /mnt. DOS/Windows users should use the appropriate drive letter.) 3. To run ezcp from the images directory, enter: ezcp image where image is the name of the image file. For example, under a UNIX system, to copy the image from btld.img, enter: ./ezcp boot/btld.img Under MS-DOS or Windows, enter: ezcp boot\btld.img 4. To run ezcp from the directory containing the images (for example, the boot directory), move to that directory. Then, run ../ezcp under a UNIX system or ..\ezcp under MS-DOS or Windows. For example, under a UNIX system, to copy the image from btld.img, enter: ../ezcp boot/btld.img Under MS-DOS or Windows, enter: ..\ezcp boot\btld.img Note that the image file may be in a different directory than the ezcp script, as in the above example. 5. Be sure to label the finished diskette appropriately. Installing BTLDs at boot-time This section describes how to install a new or updated BTLD required at boot-time or required for the installation of the SCO OpenServer system. If you need to use your BTLD disk at installation time, you should have already inserted your boot disk. After inserting the boot disk, the boot prompt is displayed; this is the point at which you begin the installation procedure for this BTLD disk. At this stage the boot floppy disk should be in the drive, and the system should be displaying: SCO OpenServer(tm) Release 5 Boot : 1. Enter link at the ``:'' prompt. 2. The screen displays the following prompt: What packages do you need linked in the system, or `q' to quit? : Available packages in this BTLD release are: + alad + blad + mdac + ncr + slha + wd Enter only the packages which are required by the installation. If you want to install the other packages on the distribution media, you should use the post-installation procedure as described in the SCO OpenServer Release 5.0.5 Release Notes. 3. Next, you will see a boot line similar to the following example: fd(64)unix ramdisk=f(64) rootfs root=ram(7) ram.preload=7 swap=none dump=none nbuf=100 link=pkg btld=fd(x) Memory found: 0k - 640k, 1m - 9600k pkg in the line above is replaced by the actual name of the driver package for boot-time loading and x is replaced by the minor number for your floppy device. After a moment, a series of prompts are displayed with trailing dots; these messages progress as software is loaded. 4. Next you see: Please insert the fd(x)pkg volume and press : Insert the requested volume (the BTLD disk). The system prompts for and extracts the contents of the package. If the wrong volume is inserted or the drive is empty, the system displays the following: Sorry, that volume does not contain the pkg package followed by the insertion request again: Please insert the fd(x)pkg volume and press : 5. link(HW) performs the linking of the extracted drivers into the kernel in core and may require more information for the extracted drivers. If the system prompts you for more information about configuring in these drivers, refer to the link(HW) manual page. _________________________________________________________________________ NOTE If there are any errors during this extraction (linking) process, the process is aborted and you are forced to reboot. _________________________________________________________________________ 6. After a series of messages culminating in a message such as: pkg: Driver "pkg" successfully loaded you will see a message prompting you to re-insert the boot disk. The new BTLD driver has been installed and you can continue with your SCO OpenServer installation procedure. Installing BTLDs after boot-time BTLD drivers installed at Initial System Load (ISL) are not visible to the Software Manager even though they are installed in the Link Kit. To install a BTLD when the SCO OpenServer system is already installed: 1. Login as root, put the system into system maintenance mode. 2. Insert the BTLD disk into the floppy drive and mount it, for example: mount -r /dev/fd0135ds18 /mnt 3. Run the btldinstall() command: /etc/btldinstall /mnt 4. When prompted, select a package to install from this list: + alad + blad + mdac + ncr + slha + wd 5. If a driver with the same name already exists in the Link Kit, you will be prompted to resolve the conflict, either by replacing the driver in the Link Kit or by choosing not to install the BTLD. 6. Relink the kernel when prompted. The new BTLD will be available after you reboot your system. Modified man pages This section contains modified driver manual pages: + blad(HW) + mdac(HW) + slha(HW) + wd(HW) A complete set of updated online manual pages will be available in the next SCO OpenServer release. ____________________ blad(HW) 16 Nov 1998 Name blad - Adaptec Ultra II SCSI host adapter driver Description The blad driver directly supports the following host adapters: AHA-2940U2W AHA-2950U2W AHA-3940U2W AHA-3950U2 AHA-3950U2B These Adaptec Ultra II host adapters support 80MB/sec burst throughput. To determine the support status of your host adapter, contact your system supplier or refer to the SCO Compatible Hardware Web Pages: http://wdb1.sco.com/chwp/owa/hch_search_form Configuring the blad driver You can configure the blad driver using entries in /etc/conf/cf.d/mdevice and /etc/conf/sdevice.d/blad. See mdevice(F) and sdevice(F). Changes to these files take effect once you relink the kernel using link_unix(ADM) and reboot the system. Configure blad driver-specific characteristics by editing the /etc/conf/pack.d/blad/space.c file, which controls parameters such as the SCSI ID, I/O port address, scatter/gather, tag queuing and connect/disconnect. See also boot(HW), link_unix(ADM), mdevice(F), mkdev(ADM), sconf(ADM), scsi(HW), sdevice(F) Chapter 16, ``Adding SCSI host adapters and peripherals'' in the SCO OpenServer Handbook SCO OpenServer System Administration Guide ____________________ mdac(HW) 16 Nov 1998 Name mdac - Mylex Disk Array driver Description mdac is the device driver for Mylex Disk Array controllers. It directly supports these PCI host adapters: DAC960P DAC960PD DAC960PDU DAC960PG DAC960PJ DAC960PL DAC960PTL0 (AcceleRAID 200) DAC960PTL1 (AcceleRAID 250) DAC1164P (eXtremeRAID) To determine the support status of your host adapter, contact your system supplier or refer to the SCO Compatible Hardware Web Pages: http://wdb1.sco.com/chwp/owa/hch_search_form Configuring the mdac driver You can configure the mdac driver using entries in /etc/conf/cf.d/mdevice and /etc/conf/sdevice.d/mdac. See mdevice(F) and sdevice(F). Changes to these files will only take effect if the kernel is relinked using link_unix(ADM) and the machine rebooted. Configure mdac driver-specific characteristics by editing the /etc/conf/pack.d/mdac/space.c file. Boot-time configuration of SCSI Use the bootstring(HW) parameters to override the default hardware configuration information. Of special interest are the adapter= parameter that specifies information for the host adapter card that plugs into or is part of the motherboard, and the periph= parameter that specifies information about the host adapter being used by one of the generic peripheral interfaces (Sdsk, Srom, or Stp). ioctl commands The mdac driver supports all standard SCSI ioctls that are defined in the header file and documented on the scsi(HW) manual page. Diagnostics See messages(M) for general information about kernel error messages, including a list of generic device driver errors. Files /usr/include/sys/scsicmd.h SCSI interface header files See also boot(HW), link_unix(ADM), mdevice(F), mkdev(ADM), sconf(ADM), scsi(HW), sdevice(F) Chapter 16, ``Adding SCSI host adapters and peripherals'' in the SCO OpenServer Handbook SCO OpenServer System Administration Guide ____________________ slha(HW) 16 Nov 1998 Name slha - Symbios Logic/LSI Logic host adapter driver Description slha is the boot-time loadable driver (BTLD) for the 8xx family of Symbios Logic SCSI controllers. It directly supports: Symbios 53C53C810 (all 53c8xx SCSI I/O processors) Symbios 53C810A Symbios 53C815 Symbios 53C825 Symbios 53C825A Symbios 53C860 Symbios 53C875 Symbios 53C8751 Symbios 53C875J Symbios 53C876 Symbios 53C895 Symbios 53C896 This driver dynamically maps interrupts, supports Fast and Wide SCSI, scatter/gather, and multiple host bus adapters (HBAs). In addition, this driver fully supports either single or multiple processor systems (multiple processor systems must also have the SCO Symmetrical Multiprocessing Support package installed). slha works with all Symbios Logic 53c8xx SCSI I/O Processors. The 53C896, 875, and 895 are fully supported. The 53C810A and 825A are supported in legacy mode of 53C810 and 825, respectively. The Fast20 negotiation feature of the 53C860 and 875 is also supported. The SCRIPTs RAM operation of the 53C825A and 875 is not currently supported. After installation, if you add additional Symbios Logic SCSI host bus adapters to the system, use the appropriate mkdev command for each device attached to the new host bus adapter. Then, rebuild the kernel, and reboot the system for the change to take effect. To determine the support status of your host adapter, contact your system supplier or refer to the SCO Compatible Hardware Web Pages: http://wdb1.sco.com/chwp/owa/hch_search_form Configuring the slha driver You can configure the slha driver using entries in /etc/conf/cf.d/mdevice and /etc/conf/sdevice.d/slha. See mdevice(F) and sdevice(F). Changes to these files will only take effect if the kernel is relinked using link_unix(ADM) and the machine rebooted. Configure slha driver-specific characteristics by editing the /etc/conf/pack.d/slha/space.c file. Boot-time configuration of SCSI Use the bootstring(HW) parameters to override the default hardware configuration information. Of special interest are the adapter= parameter that specifies information for the host adapter card that plugs into or is part of the motherboard, and the periph= parameter that specifies information about the host adapter being used by one of the generic peripheral interfaces (Sdsk, Srom, or Stp). ioctl commands The slha driver supports all standard SCSI ioctls that are defined in the header file and documented on the scsi(HW) manual page. Diagnostics See messages(M) for general information about kernel error messages, including a list of generic device driver errors. Files /usr/include/sys/scsicmd.h SCSI interface header files See also boot(HW), link_unix(ADM), mdevice(F), mkdev(ADM), sconf(ADM), scsi(HW), sdevice(F) Chapter 16, ``Adding SCSI host adapters and peripherals'' in the SCO OpenServer Handbook SCO OpenServer System Administration Guide ____________________ wd(HW) 16 Nov 1998 Name wd - EIDE disk and ATAPI host adapter driver Description wd is the driver for EIDE hard drives and ATAPI peripherals. It provides support for MP and MicroChannel systems, and for ATAPI CD-ROM and Seagate ATAPI TAPE devices. To determine the support status of your host adapter, contact your system supplier or refer to the SCO Compatible Hardware Web Pages: http://wdb1.sco.com/chwp/owa/hch_search_form Configuring the wd driver You can configure the wd driver using entries in /etc/conf/cf.d/mdevice and /etc/conf/sdevice.d/wd. See mdevice(F) and sdevice(F). Changes to these files will only take effect if the kernel is relinked using link_unix(ADM) and the machine rebooted. Configure wd driver-specific characteristics by editing the /etc/conf/pack.d/wd/space.c file. Boot-time configuration of SCSI Use the bootstring(HW) parameters to override the default hardware configuration information. Of special interest are the adapter= parameter that specifies information for the host adapter card that plugs into or is part of the motherboard, and the periph= parameter that specifies information about the host adapter being used by one of the generic peripheral interfaces (Sdsk, Srom, or Stp). The wd driver supports the wd.noscan bootstring(HW), which disables hardware checking by the driver. This prevents conflicts on systems that have both SCSI and ATAPI hardware enabled. This bootstring is only required during installation. Systems that include single types of mass storage devices (that is, EIDE/ATAPI or SCSI only) do not need this bootstring. ioctl commands The wd driver supports all standard SCSI ioctls that are defined in the header file and documented on the scsi(HW) manual page. Diagnostics See messages(M) for general information about kernel error messages, including a list of generic device driver errors. Files /usr/include/sys/scsicmd.h SCSI interface header files See also boot(HW), link_unix(ADM), mdevice(F), mkdev(ADM), sconf(ADM), scsi(HW), sdevice(F) Chapter 16, ``Adding SCSI host adapters and peripherals'' in the SCO OpenServer Handbook SCO OpenServer System Administration Guide ____________________ SCO, The Santa Cruz Operation, the SCO logo, SCO Doctor, SCO Doctor Lite, SCO Doctor for Networks, SCO OpenServer, SCO TermLite, SCO TermVision, SCO Vision97, SCO VisionFS, Skunkware, and UnixWare are trademarks or registered trademarks of The Santa Cruz Operation, Inc. in the US and other countries. SQL-Retriever, SuperVision, TermVision and XVision are trademarks or registered trademarks of Visionware Limited, a subsidiary of The Santa Cruz Operation, Inc. UNIX is a registered trademark of The Open Group in the US and other countries. Sun, Sun Microsystems, Java, Java Studio, and Java Workshop are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries, and are used under license. Netscape, Netscape Communicator, Netscape Enterprise Server, Netscape FastTrack Server, Netscape Mail Server, Netscape Navigator, Netscape Navigator Gold, and LiveWire are trademarks or registered trademarks of Netscape Communications Corporation in the US and other countries. Basic Server Plus, RealNetworks, and RealSystem are trademarks of RealNetworks, Inc. in the US and other countries. ARCserve and Cheyenne are registered trademarks of Cheyenne Software, Inc. The Santa Cruz Operation, Inc. and SCO Skunkware are not related to, affiliated with or licensed by the famous Lockheed Martin Skunk Works(R), the creator of the F-117 Stealth Fighter, SR-71, U-2, Venturestar(TM), Darkstar(TM), and other pioneering air and spacecraft. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners. The Santa Cruz Operation, Inc. reserves the right to change or modify any of the product or service specifications or features described herein without notice. This document is for information only. The Santa Cruz Operation, Inc. makes no express or implied representations or warranties in this document. Copyright (C) 1998 The Santa Cruz Operation, Inc. All Rights Reserved.