




















                        Solaris(TM) 2.5/2.5.1

                        x86 Driver Update 5 Guide





























SunSoft, Inc.
A Sun Microsystems, Inc. Business
2550 Garcia Avenue
Mountain View, CA 94043
U.S.A.

Part No: 802-6397-13
Revision A, November 1996

Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View,
California 94043-1100 U.S.A. All rights reserved.

This product or document is protected by copyright and distributed under
licenses restricting its use, copying, distribution, and decompilation. No part
of this product or document may be reproduced in any form by any means without
prior written authorization of Sun and its licensors, if any.

Portions of this product may be derived from the UNIX(R) system, licensed from
Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the
University of California. UNIX is a registered trademark in the United States
and other countries and is exclusively licensed by X/Open Company
Ltd. Third-party software, including font technology in this product, is
protected by copyright and licensed from Sun's suppliers.

RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is
subject to restrictions of FAR 52.227-14(g)(2)(6/87) and FAR 52.227-19(6/87),
or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-3(a).

Sun, Sun Microsystems, the Sun logo, SunSoft, SunDocs, SunExpress, Solaris,
Solstice DiskSuite, and NFS are trademarks, registered trademarks, or service
marks of Sun Microsystems, Inc. in the United States and other countries. All
SPARC trademarks are used under license and are trademarks or registered
trademarks of SPARC International, Inc. in the United States and other
countries. Products bearing SPARC trademarks are based upon an architecture
developed by Sun Microsystems, Inc. Dell is a registered trademark of Dell
Computer Corporation.

The OPEN LOOK(R) and Sun(TM) Graphical User Interfaces were developed by Sun
Microsystems, Inc. for its users and licensees. Sun acknowledges the
pioneering efforts of Xerox in researching and developing the concept of visual
or graphical user interfaces for the computer industry. Sun holds a
non-exclusive license from Xerox to the Xerox Graphical User Interface, which
license also covers Sun's licensees who implement OPEN LOOK GUIs and otherwise
comply with Sun's written license agreements.

X Window System is a product of the X Consortium, Inc.

THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

Contents

About This Book

1.  Solaris 2.5/2.5.1 x86 Driver Update 5

    New Device Functionality

       Device Drivers

    Driver Update Contents

       Driver Update Boot Diskettes

       Driver Update Distribution Diskettes

    Driver Update 5 Release Notes

       Boot Programs Modified to Support Compressed Files

       Boot Programs Fixed to Handle IDE Disks Greater Than 
       2 Gigabytes

       Make Sure You Install on the Correct Boot Drive

       Known Problems

       Modifying the Solaris Driver Update Boot Diskettes

    Installing Solaris Using the Driver Update Diskettes

    Adding New Drivers to an Existing Solaris System

    Disabling Drivers After Installing the Driver Update

A.  Device Reference Pages

    Disk Interface

       IDE Disk Drive and Enhanced IDE Controller
       (Including IDE CD-ROM ATAPI)

    SCSI Host Bus Adapters

       Adaptec AHA-154x ISA HBAs

       Adaptec AIC-7770/AHA-274x/AHA-284x HBAs

       Adaptec AIC-7850/AIC-7870/AIC-7871/AIC-7872/AIC-7880
       (AHA-2940/AHA-2940W/AHA-2940U/AHA-2940UW/AHA-
       3940/AHA-3940W PCI  HBAs)

       AdvanSys SCSI Adapters

       BusLogic FlashPoint LT Ultra SCSI, FlashPoint LW Ultra and Wide
       SCSI, FlashPoint DL Dual Channel Ultra SCSI, FlashPoint DW
       Dual Channel Ultra and Wide SCSI PCI HBAs

       Compaq 53C710, 53C810, 53C825 PCI and EISA SCSI-2 HBAs

       IBM Micro Channel SCSI-2 Fast/Wide Adapter/A

    SCSI Disk Arrays/RAID Controllers

       Compaq SMART-2 EISA/PCI Array Controller

       DPT PM-2024/PM-2124/PM-2124W/PM-3224/PM-3224W PCI
       HBAs

       IBM PC ServeRAID HBA

       IBM SCSI-2 RAID Controller and IBM SCSI-2 Fast/Wide
       Streaming-RAID Adapter/A, Mylex DAC960 EISA and Mylex
       DAC960P PCI Controllers

    Ethernet Network Adapters

       3Com EtherLink 16 (3C507)

       3Com EtherLink II (3C503) and EtherLink II/16 (3C503-16)

       3Com EtherLink III (3C5x9, 3C509B, 3C59x), EtherLink XL
       (3C900 TPO), Fast EtherLink XL (3C905)

       AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI)

       Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR EISA
       Controllers

       Compaq NetFlex-3 EISA and PCI Controllers

       DEC 21040, 21041, 21140 Ethernet

       Fujitsu FMV183 Ethernet

       Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP

       Intel EtherExpress Flash32 (82596)

       Intel EtherExpress PRO/100 (82556)

       Novell NE2000, NE2000plus Ethernet and Clones

       SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS Elite16,
       EtherCard PLUS (8416, 8216, 8013, 8003)

       SMC Ether 10/100 (9232)

    FDDI Network Adapters

       Rockwell Network Systems (RNS) 2200 Series FDDI PCI
       Adapters

    Token Ring Network Adapters

       IBM 16/4, Auto16/4 Token Ring and Compatible Adapters

       Madge Smart 16/4 Token Ring

    Audio Cards

       Analog Devices AD1848 and Compatible Devices

       Creative Labs Sound Blaster Pro

       Creative Labs Sound Blaster 16/Sound Blaster AWE32

    PC Card Hardware

       Modem and Serial PC Card Devices

About This Book

This document provides information about x86 hardware devices that are now
supported in the Solaris(TM) 2.5 and 2.5.1 computing environments. Typically,
as new drivers become available, they will be bundled with releases on separate
Driver Update diskettes. The drivers may support the following types of
devices: SCSI host bus adapters, disk interface, network adapters, PC Card
devices, and others, such as audio, SCSI tape devices, and serial ports. You
can use the Driver Update diskettes to install a new system for the first time,
or you can use them to update your installed Solaris 2.5/2.5.1 system with new
drivers.

Note - Driver Updates are cumulative distributions. Although the "New Device
Functionality" section in Chapter 1 describes what's been added since the last
Driver Update, the "Driver Update Contents" section in Chapter 1 provides a
complete list of what will be installed. It is only necessary to install the
current Driver Update to get the support described in this document.

Before You Read This Book

The importance of configuring your hardware before Solaris installation is
discussed in x86 Device Configuration Guide. This document assumes you have
fully read and understood that guide; Appendix A, "Device Reference Pages,"
in this document is an addendum to that guide and contains device
configuration information for newly supported hardware. Likewise, the
installation instructions in this Driver Update supplement the instructions in
x86: Installing Solaris Software.

How This Book Is Organized

This book contains a brief description of the contents of the Driver Update
diskettes, installation instructions for the new drivers, and detailed
configuration instructions for the hardware devices that are supported by the
new drivers.

Note - Even though the instructions for installing the new drivers are
presented first, read and follow the appropriate hardware configuration
instructions in Appendix A, "Device Reference Pages," before installing the
new drivers. The hardware must be configured properly for the Solaris
software to install and run correctly.

Chapter 1, "Solaris 2.5/2.5.1 x86 Driver Update 5," provides information about
what is new in this release and how to install it.

Appendix A, "Device Reference Pages," provides device configuration
information for the hardware supported by the drivers in this Driver Update.
This appendix should be read and the hardware configured prior to installing
the Driver Update software.

Related Books

You may need to refer to the following books when installing the Driver
Update:

o x86 Device Configuration Guide
  Describes how to configure x86 devices before installing Solaris software.

o x86: Installing Solaris Software
  Describes how to install the Solaris software on x86 systems.

o x86: Solaris 2.5 Installation Notes
  Describes late-breaking news about running Solaris 2.5/2.5.1 x86 software,
  including known problems with supported hardware or device drivers.

o Solaris 2.5x x86 Hardware Compatibility List
  Contains a list of supported hardware on Solaris 2.5/2.5.1 x86 systems.

How to Obtain Updated Hardware Compatibility Lists and Device Driver
Information

Hardware Compatibility Lists and Driver Update releases (including related
documentation) are produced periodically as support for new hardware
becomes available. They are available from these sources:

o World Wide Web--Open URL http://access1.Sun.COM, select "x86"
  (from the bookshelf), and choose "Solaris Intel (x86)."

o FTP--Use anonymous FTP to access ftp.uu.net, then go to
  /vendor/sun/solaris/x86/2.5/

o CompuServe--Type go sunsoft and go to the Solaris x86 library.

Note that the World Wide Web, CompuServe, and ASK-IT (below) also point to
Support-provided installation and configuration information as well as
answers to frequently asked questions.

Related Documentation Only

o Email Autoresponder--To obtain a Hardware Compatibility List or a Driver
  Update Announcement via email, write to hcl-index@Sun.COM for a list
  of autoresponse aliases that return hardware support information.

o ASK-IT--SunSoft's Automated Support Fax-on-Demand Service.
  Includes the current Hardware Compatibility List and document
  No. 51225, which summarizes the current Driver Update.

  o In North America, call one of these numbers:

       1-800-SUNSOFT and choose options 4, 1, 1, 1
       (310) 348-6219 and choose option 1

  o Outside North America, call one of these numbers and choose option 1:

       Australia        61-2-844-5374
       Japan            03-5717-2560
       Taiwan           886-2-719-8069
       United Kingdom   44-1494-510981

Ordering Sun Documents

The SunDocs(SM) program provides more than 250 manuals from Sun
Microsystems, Inc. If you live in the United States, Canada, Europe, or Japan,
you can purchase documentation sets or individual manuals using this
program.

For a list of documents and how to order them, see the catalog section of the
SunExpress(TM) Internet site at http://www.sun.com/sunexpress.

How to Obtain Technical Support

To obtain technical support:

o In North America, call 1-800-SUNSOFT and choose option 4.
o Outside North America, contact your technical support provider.

Chapter 1 - Solaris 2.5/2.5.1 x86 Driver Update 5

Driver Update 5 provides additional driver support for Solaris 2.5/2.5.1 x86
and must be used with this release.

New Device Functionality

Device Drivers

Table 1-1 lists device drivers in Solaris 2.5/2.5.1 x86 Driver Update 5 that
contain new functionality not included in previous Driver Updates. For a
complete list of drivers included in this release, see Table 1-2.

Table 1-1       New and Updated Drivers in This Driver Update
===============================================================================
Disk Interface Driver

ata            Added support for booting from CD-ROM in Compaq LTE
               5000 series machines                               

SCSI HBA Drivers

adp             Bug fixes

asc             New AdvanSys SCSI adapters, in three categories:
                1) Connectivity Products, 2) Single Channel Products,
                3) Dual Channel Products

                See the "AdvanSys SCSI Adapters" Device Reference Page
                for the SCSI adapters in each category.

ncrs            Fixed a bug which sometimes prevented Solaris from
                booting if the Solaris partition extended past 1 Gbyte

Ethernet Network Drivers

dnet            Fixed a number of bugs: stress tests caused dnet to fall off
                the net; potential TX descriptor corruption and false busy
                loops; did not allow 10 Mb on Cogent EM110TX;
                performance of 100 Mb/sec cards was slow; automatic
                detection of AUI and BNC failed; only first port worked on
                multiport cards; non-portable code; problems with multiple
                cards and/or shared interrupts; Solaris 2.4 environment
                xpci support not implemented correctly; couldn't have
                both BNC/AUI and 10Base-T DNET cards in Solaris 2.5
                environment; interrupts set up incorrectly under Solaris 2.4
                environment; couldn't netboot off SMC9332BDT and
                Cogent EM440 cards with subvendor IDs; IRQs did not get
                assigned properly on multiport cards; driver paniced under
                Solaris 2.5 environment

                Support has been added for a number of new cards; see the
                Hardware Compatibility List for details.

el              Fixed a number of probe conflicts that caused this driver to
                interfere with an elx or an smc card or with ata on a
                Compaq docking station; automatic port configuration
                should now work correctly

elink           Fixed a problem in which the realmode driver would not
                work in turbo mode

elx             Added support for 3Com EtherLink XL (3C900 TPO) and
                Fast EtherLink XL (3C905)

fmvel           Updated Device Reference Page to describe how to work
                around conflict with nei driver

iee             Fixed a problem in which the driver failed to come up on
                the network on a P60, and one in which the driver hung the
                network after attempting to copy a large file; MCA support
                is now implemented correctly; the driver also supports
                automedia detection

ieef            Implemented automedia/autospeed detection and fixed a
                number of other bugs: driver incorrectly handled RPL
                request packets; driver used old-style PCI support; driver
                generated CRC errors under stress; driver checked all
                4 bytes of EISA ID

iprb            Fixed a number of bugs: network connection drops on the
                way up; board structures should be declared volatile; zero
                message block fix; this driver also contains several
                performance enhancements

nei             Updated Device Reference Page to describe how to work
                around conflict with fmvel driver

pcn             Updated to prevent Compaq XL 560/590 systems from
                hanging after a soft reboot; fixed a bug in which
                netinstall would not work at IRQs above 7

FDDI Network Driver

sxp             Netboot now works

PC Card (PCMCIA) Hardware

pcser           Fixed a problem in which some PC card modems dropped a
                connection immediately after establishing it, or would not
                echo characters or dial
===============================================================================

Corrections to Known Problems

See "Driver Update 5 Release Notes" later in this chapter for information about
known problems that are fixed in this Driver Update.

Driver Update Contents

Solaris 2.5/2.5.1 x86 Driver Update 5 contains the following diskettes:

o "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette"
o "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette"
o "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette"
o "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 1 Diskette"
o "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 2 Diskette"
o "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 3 Diskette"

The boot and distribution diskettes are to be used with a Solaris 2.5/2.5.1 CD
or net install image.

Driver Update Boot Diskettes

Solaris 2.5/2.5.1 x86 can be installed with the new boot diskettes labeled
"Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette," "Solaris 2.5/2.5.1 x86
Driver Update 5 BOOT 2 Diskette," and "Solaris 2.5/2.5.1 x86 Driver Update 5
SOLARIS DRIVER Diskette." These diskettes contain scripts and configuration
files that enable you to boot and install your system using one of the newly
supported devices.

Driver Update Distribution Diskettes

The diskettes labeled "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 1
Diskette," "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 2 Diskette,"
and "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 3 Diskette" are
read when the Driver Update boot diskettes are used to install Solaris.
Alternatively, the Driver Update distribution diskettes can be used without the
boot diskettes to add new drivers to an existing x86 system running the Solaris
2.5 or 2.5.1 release.

The Driver Update distribution diskettes contain the drivers listed in Table
1-2.  A new or updated Section 7D man page for each of the drivers that added
new device support will also be installed in the appropriate man page directory
during installation.

Table 1-2       Device Drivers in This Driver Update
===============================================================================
Disk Interface Driver

ata             IDE device DDI compliance and other bug fixes, and
                support for NEC CDR-260R and CDR-273 CD-ROMs; added
                configurable flag to support suspend/resume on Compaq
                LTE Elite 4/40 notebooks; fixed conflict between this driver
                and dpt which caused systems with certain DPT SCSI
                HBAs to panic; added support for booting from CD-ROM in
                Compaq LTE 5000 series machines

SCSI HBA Drivers

adp             Updated driver to include support for the Adaptec
                AHA-2940U and AHA-2940UW and to fix a SCSI bus hang
                problem; updated to improve error detection and recovery
                in order to support Solstice DiskSuite; bug fixes

aha             Updated Device Reference Page for enabling AHA-154xCP;
                updated driver for the Adaptec AHA-154x SCSI adapter
                family to fix bugs and to provide support for hard disks
                with a capacity of 1 Gbyte or greater

asc             New AdvanSys SCSI adapters, in three categories:
                1) Connectivity Products, 2) Single Channel Products,
                3) Dual Channel Products

                See the "AdvanSys SCSI Adapters" Device Reference Page
                for the SCSI adapters in each category.

blogic          Bug fixes

cmdk, scdk,     Now supports Solstice DiskSuite (fixes bugs that could
snlb            cause stale VTOC or FDISK Partition Table information to
                be read or written)

corvette        Updated IBM Micro Channel SCSI-2 Fast/Wide Adapter/A
                Device Reference Page to supply additional configuration
                information

esa             Probe conflict fixed

flashpt         New BusLogic FlashPoint LT Ultra SCSI, FlashPoint LW
                Ultra and Wide SCSI, FlashPoint DL Dual Channel Ultra
                SCSI, FlashPoint DW Dual Channel Ultra and Wide SCSI
                PCI HBAs

ncrs            Fixed synchronous negotiation problems; updated support
                for Compaq 32-Bit Fast-SCSI-2, Compaq Integrated 32-Bit
                Fast-SCSI-2; new support for Compaq Integrated 32-Bit
                Fast-SCSI-2, Compaq Integrated 32-Bit Fast-Wide SCSI-2,
                Compaq 32-Bit Fast-Wide SCSI-2/E, Compaq 32-Bit Fast-
                Wide SCSI-2/P; fixed a bug which sometimes prevented
                Solaris from booting if the Solaris partition extended past
                1 Gbyte

SCSI Disk Arrays/RAID Controllers

chs             New IBM PC ServeRAID SCSI Array controller

dpt             Device Reference Page for the DPT PM-2024 and PM-2124
                PCI controllers, and the PM-3224 RAID controller for the
                PCI bus; updated Device Reference Page to include
                PM-2124W and PM-3224W; updated to improve error
                detection and recovery in order to support Solstice
                DiskSuite

mlx             Updated driver to add support for the Mylex DAC960P PCI
                controller

smartii         New Compaq SMART-2 EISA/PCI SCSI Array controller

Ethernet Network Drivers

cnft            New Compaq NetFlex-3/E and NetFlex-3/P, including
                support for Compaq 10T UTP, 100VG-AnyLAN UTP, and
                10/100BASE TX UTP modules

dnet            Bug fixes, and updated to include support for AsanteFAST
                10/100; SMC EtherPower 8432BT, 8432BTA, and 10/100
                9332DST; Cogent EM100TX and EM110TX; Znyx EtherXtend
                ZX342; fixed a number of bugs: stress tests caused dnet to
                fall off the net; potential TX descriptor corruption and false
                busy loops; did not allow 10 Mb on Cogent EM110TX;
                performance of 100 Mb/sec cards was slow; automatic
                detection of AUI and BNC failed; only first port worked on
                multiport cards; non-portable code; problems with multiple
                cards and/or shared interrupts; Solaris 2.4 environment
                xpci support not implemented correctly; couldn't have
                both BNC/AUI and 10Base-T DNET cards in Solaris 2.5
                environment; interrupts set up incorrectly under Solaris 2.4
                environment; couldn't netboot off SMC9332BDT and
                Cogent EM440 cards with subvendor IDs; IRQs did not get
                assigned properly on multiport cards; driver paniced under
                Solaris 2.5 environment

                Support has been added for a number of new cards; see the
                Hardware Compatibility List for details.

el              Fixed a number of probe conflicts that caused this driver to
                interfere with an elx or an smc card or with ata on a
                Compaq docking station; automatic port configuration
                should now work correctly

elink           Updated 3Com EtherLink 16 (3C507) Device Reference Page
                to supply additional configuration information; fixed a
                problem in which the realmode driver would not work in
                turbo mode

elx             Added support for 3Com EtherLink III 3C59x; updated to
                fix conflict with sbpro driver that prevented 3C509 ISA
                cards from working; added support for 3Com EtherLink XL
                (3C900 TPO) and Fast EtherLink XL (3C905)

fmvel           New Fujitsu FMV183; updated Device Reference Page to
                describe how to work around conflict with nei driver

iee             Fixed a problem in which the driver failed to come up on
                the network on a P60, and one in which the driver hung the
                network after attempting to copy a large file; MCA support
                is now implemented correctly; the driver also supports
                automedia detection

ieef            Updated Intel EtherExpress PRO/100 (82556) Device
                Reference Page to explain how to set 100-Mbps mode;
                implemented automedia/autospeed detection and fixed a
                number of other bugs: driver incorrectly handled RPL
                request packets; driver used old-style PCI support; driver
                generated CRC errors under stress; driver checked all
                4 bytes of EISA ID

iprb            New Intel EtherExpress PRO/100B TX, Intel EtherExpress
                PRO/100B/T4, and Intel EtherExpress PRO/10+; fixed a
                number of bugs: network connection drops on the way up;
                board structures should be declared volatile; zero message
                block fix; this driver also contains several performance
                enhancements

                No Device Reference Page is supplied for this driver as no
                special configuration procedures are required,

nei             Change in enabling batch file; updated Device Reference
                Page to describe how to work around conflict with fmvel
                driver

nfe             Bug fixes and DB-15 connector now works with NetFlex-2
                DualPort ENET

pcn             Corrected batch file name in Device Reference Page;
                updated to support HP PC LAN NC/16 TP J2405A Ethernet
                controller; updated to prevent Compaq XL 560/590 systems
                from hanging after a soft reboot; fixed a bug in which
                netinstall would not work at IRQs above 7

smc             Updated SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard
                PLUS Elite16, EtherCard PLUS (8416, 8216, 8013, 8003)
                Device Reference Page to supply additional configuration
                information

smcf            Updated SMC Ether 10/100 (9232) Device Reference Page to
                reflect correct product name

FDDI Network Driver

sxp             New Rockwell RNS 2200 Series; netboot now works

Token Ring Network Drivers

mtok            New Madge Smart 16/4 family, including
                AT Ringnode/Bridgenode, AT Plus Ringnode,
                ISA Client Ringnode, ISA Client Plus Ringnode,
                EISA Ringnode/Bridgenode, MC Ringnode/Bridgenode,
                MC32 Ringnode/Bridgenode, PCI Ringnode/Bridgenode

tr              Added support for IBM Auto 16/4 Token Ring

Keyboard Driver

kd              Updated to prevent the screen from going into unreadable
                white-on-white mode and to prevent a system panic during
                boot on systems that don't have a video card

Parallel Ports Driver

lp              Bug fix

Serial Ports Driver

asy             Serial driver bug fixes; updated to fix problems and to
                enhance the hardware flow control functionality, which
                works regardless of the CLOCAL flag bit; added support
                for 57.6 Kbps and 115.2 Kbps

Audio Driver

sbpro           New Analog Devices AD1848, which also supports
                compatible devices; Creative Labs Sound Blaster Pro Device
                Reference Page updated; Creative Labs Sound
                Blaster 16/Sound Blaster AWE/32 Device Reference Page
                included for convenience

PC Card (PCMCIA) Hardware

pcic            Fixed bug that caused modem cards to be recognized as
                memory on many systems; modems should now be usable
                on all supported systems

pcser           Fixed a problem in which some PC card modems dropped a
                connection immediately after establishing it, or would not
                echo characters or dial

Configuration Drivers

inetboot        Modified to provide support for diskette file compression;
                now allows use of full capacity of IDE disks greater than
                2 Gbytes

ufsboot         Updated to enable more machines to boot Solaris properly;
                modified to provide support for diskette file compression;
                now allows use of full capacity of IDE disks greater than
                2 Gbytes
===============================================================================

Note - The updated kd driver ensures that the screen display does not go into
a unreadable white-on-white mode during installation on some notebooks and
other machines. Although the kd driver supports video cards, it resides on the
boot diskettes rather than on the video distribution diskette.

Table 1-3 lists the MP kernel modules included in this Driver Update.

Table 1-3       MP Kernel Modules in This Driver Update
===============================================================================
compaq          An updated MP module for Compaq ProLiant that
                enhances performance

pcplusmp        An updated MP module that fixes some problems on Intel
                MultiProcessor Specification Version 1.1 (Intel MP Spec. 1.1)
                compliant systems; fixed a problem that caused a Micron
                Magnum Pro 200 with an Adaptec AHA-2940U PCI SCSI
                controller to panic during installation; fixed a bug on some
                Pentium Pro systems with the Intel PCIset 440FX (Natoma)
                chipset, such as IBM PC 300 Pentium Pro and Dell Optiplex
                GXPro 200

syspro          An updated MP module for Compaq Systempro that fixes
                some probe conflicts on Compaq ProLiant systems
===============================================================================


Driver Update 5 Release Notes

Note - The Adaptec AHA-3940 has been certified by Adaptec to run on specific
system platforms. Our testing has shown that the Solaris software works
properly on some of those systems and not on others. If you encounter
problems running Solaris x86 on an Adaptec-approved platform with the
AHA-3940, contact your technical support provider.

For a complete list of the known problems that are fixed in this Driver Update,
see the README files that get installed in the patch directories
/var/sadm/patch/<patch number>.

o (1226577) The mlx driver has been updated to provide PCI support in Solaris
  2.5/2.5.1. If you're using any one of the controllers supported by mlx,
  whether it is PCI or not, upgrading from 2.4 to 2.5 may fail, especially if
  mlx is the boot driver.

  Workaround: Don't upgrade, but rather reinstall if your system uses the mlx
  driver.

o If you are installing Solaris 2.5/2.5.1 x86 on one the following Intergraph
  systems, you will need to modify the Driver Update 5 boot diskettes to
  workaround a known PCI/EISA I/O space overlap problem on systems that contain
  an NCR chip:

  ISMP22 Server
  TD-5 Personal Workstation
  TD-4 Personal Workstation
  100 MHz TD-3 Personal Workstation

  This must be done prior to installing the Solaris 2.5/2.5.1 x86 operating
  environment. See "Modifying the Solaris Driver Update Boot Diskettes"
  later in this chapter.

o The Novell NE2000 and NE2000plus are sensitive to autoprobing by other
  drivers and require autoprobe reset sequences that may disturb other cards.
  For this reason, the Solaris nei driver is disabled by default, and special
  steps must be taken to enable it. See "Modifying the Driver Update Boot
  Diskettes" and "Enabling Support for Controllers After Installing Solaris
  x86" on the "Novell NE2000, NE2000plus Ethernet and Clones" Device Reference
  Page in Appendix A.

o Due to conflicts, the IBM SCSI-2 Fast/Wide Adapter/A should not be installed
  until the Solaris Micro Channel mcis driver is disabled. See "Modifying the
  Driver Update Boot Diskettes" and "Disabling the mcis Driver After Installing
  Solaris x86" on the "IBM Micro Channel SCSI-2 Fast/Wide Adapter/A" Device
  Reference Page in Appendix A.

o Due to conflicts, probing for the AHA-284x VLB has been disabled. See "Adding
  Support for AHA-284x Devices" and "Modifying the Driver Update Boot
  Diskettes" on the "Adaptec AIC-7770/AHA-274x/AHA-284x HBAs" Device Reference
  Page in Appendix A.

o To prevent conflicts with the tr driver, the mtok driver is disabled by
  default, and special steps must be taken to enable it. See "Modifying the
  Driver Update Boot Diskettes" and "Enabling Support for Controllers After
  Installing Solaris x86" on the "Madge Smart 16/4 Token Ring" Device Reference
  Page in Appendix A.

o Due to conflicts, the Fujitsu FMV183 should not be installed until the
  Solaris el and nei drivers are disabled. See the "Fujitsu FMV183 Ethernet"
  Device Reference Page in Appendix A.

o Early during Solaris 2.5.1 installation using the Driver Update diskettes,
  after the drivers have been loaded and the message "Configuring /devices
  directory" is displayed, the message "Segmentation Fault (coredump)" may
  appear. This message can be ignored.

o (1263053) When installing Driver Update 5, the following message may
  appear repeatedly:

  dpt_intr(7304): null ptr

  This message can be ignored.

Boot Programs Modified to Support Compressed Files

A new compression feature is being used on files included on the Solaris
2.5/2.5.1 x86 Driver Update 4 (and later) diskettes. Solaris x86 boot programs
(ufsboot and inetboot) have been modified to support this feature.

If a server has or will have Solaris 2.5 or 2.5.1 x86 netinstall or diskless
clients, the appropriate copies of inetboot in the server's /rplboot directory
and boot images must be updated to enable net booting from the compressed-
format Driver Update diskettes. If the system is not updated, you'll see the
following message when attempting to install this Driver Update during network
boot:

SunOS Release 5.5 Version Generic [UNIX(R) System V Release 4.0]
Copyright (c) 1983-1995, Sun Microsystems, Inc.
Can't load KD
Type any key to continue

Caution! - If a server has 2.5 or 2.5.1 x86 boot images that are mounted
directly from CD-ROM (that is, neither setup_install_server or
setup_install_server -b was run), then the version of inetboot in the boot
image cannot be updated. This means that the inetcp.sh script (in inetfix.dir
on the Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette) must be re-run
any time new x86 install clients are added for this boot image via
add_install_client. Due to a problem in add_install_client, this will result in
multiple physical copies of the inetboot program in the server's /rplboot
directory.

Use the procedure below to update the inetboot images on your netinstall or
netboot server.

1.  Become root on the server.

2.  Insert the "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette" into
    drive 0.

3.  Mount the diskette.

    o If Volume Management is running, type:

      # volcheck

    o If Volume Management is not running, manually mount the diskette:

      # mount -F pcfs /dev/diskette /mnt

4.  Run inetcp.sh (included in inetfix.dir on the "Solaris 2.5/2.5.1 x86
    Driver Update 5 BOOT 1 Diskette").

    o If Volume Management is running, type:

      # cd /floppy/floppy0/inetfix.dir
      # ./inetcp.sh inetboot

    o If Volume Management is not running, type:

      # cd /mnt/inetfix.dir
      # ./inetcp.sh inetboot

Boot Programs Fixed to Handle IDE Disks Greater Than 2 Gigabytes

On systems installed with Driver Update 3, the Solaris x86 boot programs
(ufsboot and inetboot) artificially limited the usable capacity of IDE disks
that are greater than 2 Gbytes. The usable capacity would appear to be half or
less than the capacity of the disk (for example, a 2.5-Gbyte disk would look
like a 1.2-Gbyte disk). Driver Update 5 fixes this problem. Releases prior to
Driver Update 3 did not exhibit the problem.

If you have a system that has this problem, you can reinstall your system,
using Driver Update 5 to reclaim the lost capacity. If you do not want to
reinstall, you should be able to use your system as is, but the extra disk
capacity will be unavailable to the Solaris environment. It is best to
reinstall your system to avoid any future problems with upgrading your system.

If you aren't sure if your system has this problem, on the system in question,
install the Driver Update 5 driver patches and reboot the system. Type the
following lines into a file named disktest:

#!/bin/sh
if [ ! -f /dev/rdsk/${1}p0 ] ; then
        echo "$1: invalid disk name";
        exit 1;
fi

fdisk -W /tmp/fdisk.$$ /dev/rdsk/${1}p0
prtvtoc /dev/rdsk/${1}s2 >/tmp/prtvtoc.$$
grep tracks/cyl /tmp/fdisk.$$ /tmp/prtvtoc.$$
rm /tmp/fdisk.$$ /tmp/prtvtoc.$$

As root, use the chmod command to make the script executable:

# chmod +x ./disktest

and run the script with the name of the disk you'd like to check. If you have
one IDE disk, the name will be c0d0; for different names, examine the
directory /dev/dsk to determine the names of the disks installed. The
following is sample output from the program:

# ./disktest c0d0
/tmp/fdisk:*                            128 tracks/cylinder
/tmp/prtvtoc:*                          64 tracks/cylinder

The script prints out two interpretations of how many tracks per cylinder the
system thinks there are for the given disk. If the values differ, then your
disk has the problem. Reinstall your system with Driver Update 5. If the values
are the same, then you don't need to reinstall your system, and installing
Driver Update 5 will have no effect on your disk capacity.

Make Sure You Install on the Correct Boot Drive

On machines with more than one disk controller, the Solaris installation
program may identify the wrong disk as the boot drive. Before installing, you
must identify the boot drive; consult your system documentation to determine
what it is. (The Solaris boot drive will be the same as the DOS boot drive.)
During the installation, put the root file system on what you know to be the
boot drive--even if it differs from what the installation program says is the
boot drive.

If you do not choose the correct boot drive during installation, your machine
will fail to boot. If this happens, you can access the Solaris environment by
booting with the Solaris boot diskettes and selecting the drive that contains
the root file system. Otherwise, to permanently set the correct boot drive, you
will have to reinstall the Solaris environment.

Known Problems

Caution! - (1233584) The Solaris installation program's default size for the
root file system may not be large enough to produce a working system with new
or updated drivers. If your root file system is too small, cpio will complain
of a lack of space when installing the Driver Update distribution diskettes. If
this problem is encountered, the Solaris environment will have to be
reinstalled in order to add the Driver Update.

Workaround: When installing the Solaris environment, press F4 to Customize the
file system partitions, and increase the size of the root file system.

o (1192152, 1184097) The vold program may fail when it tries to access a non-
  audio CD-ROM with certain CD-ROM players. The symptoms may be a failure to
  mount the CD-ROM, or a system panic if the Solaris dpt driver is being used.

  Workaround: Disable the Solaris Volume Management software when one of
  the following CD-ROM drives is installed:

  o Chinon CDS 535
  o NEC MultiSpin 4X
  o Pioneer DRM-604X

o (1203834) Installing over a network using a 3Com EtherLink 16/16 TP
  adapter will not work if the card is set to TURBO mode.

  Workaround: Set the card to non-TURBO mode before the initial network
  install. Once installed, set it back to TURBO mode to take advantage of
  maximum performance during normal operation.

Modifying the Solaris Driver Update Boot Diskettes

Before you install the Solaris operating environment on your system, it may be
necessary to modify the Driver Update boot diskettes to remove or enable
certain drivers that conflict with each other. See the beginning of this
section, "Driver Update 5 Release Notes," for examples.

There are scripts on the Driver Update boot diskettes for driver modification.
The diskettes must be modified using DOS. As a precaution, you should make
a backup of the original Driver Update boot diskettes prior to invoking the
special script.

1.  Boot DOS on your system.

2.  Insert a blank 3.5-inch diskette into drive A: and format it:

    format a:

3.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

4.  Label the copy of the Driver Update boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette for
    Intergraph Systems."

5.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

6.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

7.  Label the copy of the Driver Update boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette for
    Intergraph Systems."

8.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

9.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette" into
    drive A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

10. Label the copy of the Driver Update boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette
    for Intergraph Systems."

11. Store your original Driver Update boot diskettes in a safe place.

12. Insert the copy of "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER
    Diskette" (the third diskette) into drive A:.

    Make sure the diskette is writable because the contents will be modified.

13. Change to drive A: (remember DOS is still running):

    a:

14. Run the batch command file.

    The batch files are run from the SOLARIS DRIVER diskette, but some of
    these files will ask you to reinsert the other boot diskettes.

o To support the Intergraph ISMP22, TD-5, TD-4, or 100 MHz TD-3, run the
  intrgrph.bat command file:

  intrgrph

o See Appendix A, "Device Reference Pages," for information on:
  o AHA-284x probing
  o NE2000/NE2000plus
  o IBM Micro Channel SCSI-2 Fast/Wide Adapter/A
  o Madge Smart 16/4 controller

Installing Solaris Using the Driver Update Diskettes

To install Solaris 2.5/2.5.1 on an x86 system, follow the instructions in x86:
Installing Solaris Software using the diskettes labeled "Solaris 2.5/2.5.1 x86
Driver Update 5 BOOT 1 Diskette," "Solaris 2.5/2.5.1 x86 Driver Update 5
BOOT 2 Diskette," and "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS
DRIVER Diskette."

The procedure for installing the Solaris environment using the Driver Update
boot diskettes is almost the same as that described in x86: Installing Solaris
Software. Boot using "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette"
instead of the boot diskette that came with your Solaris 2.5 or 2.5.1 product.
During the installation process, you'll be prompted to insert "Solaris
2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette" and "Solaris 2.5/2.5.1 x86
Driver Update 5 SOLARIS DRIVER Diskette." There will be many times during the
early booting process when the system will read data from the diskettes, but
the sequence of interaction with the user remains the same. Early in the boot
process there will also be warning messages for each new driver whose device is
not on the system being installed. The warning messages will look like the
following:

Warning: forceload of drv/xxx failed.

Such warning messages are expected and can be ignored.

Before the installation program begins to install the Solaris software, you
will be able to choose whether you want the system to reboot after installing
the software.

Late in the install process, after all the standard packages have been
installed, new driver packages will be installed from the Driver Update
distribution diskettes. At the start of that phase of the installation, one of
the install scripts will ask you to insert "Solaris 2.5/2.5.1 x86 Driver Update
5 DISTRIBUTION 1 Diskette" into the drive. During the installation, you'll be
prompted to insert the other distribution diskettes. After the new driver
packages have all been added, the script will ask you to remove the diskette
from the drive. In each case, it will wait for you to perform the requested
action and press Enter.

After this is accomplished, the system will reboot as usual (unless you chose
the option not to reboot after installing the software). When it comes up, the
new device drivers should be completely installed and functional.

Note - If you have a Sound Blaster card or AD1848 device or compatible, there
may be additional steps you need to take after the Solaris software is
installed on your system. See the three Device Reference Pages for the sbpro
driver in Appendix A.

Adding New Drivers to an Existing Solaris System

Note - Before adding new drivers, the newly supported hardware devices
should be installed and configured according to the instructions in
Appendix A, "Device Reference Pages."

When the Solaris 2.5 or 2.5.1 x86 software is already installed, the simplest
way to add new drivers is to install the Driver Update distribution diskettes
as a patch on your system.

Follow these procedures to install the new drivers.

1.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 1 Diskette" into
    drive 0.

2.  Become root.

Note - To see if Volume Management software is running, type:
ps -e | fgrep vold
For more information about managing diskettes and drives, see System
Administration Guide, Volume I.

3.  Stop Volume Management if it is running.

    Typing this command is safe if Volume Management isn't running.

    # /etc/init.d/volmgt stop

4.  Use cpio to copy files off the diskette and run the installation script.

    # mkdir /tmp/Drivers
    # cd /tmp/Drivers
    # cpio -iduBI /dev/rdiskette0

    After some time, the following message is printed:

    End of medium on "input".
    Change to part 2 and press RETURN key. [q]

5.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 2 Diskette" and
    press Enter.

    After some time, the following message is printed:

    End of medium on "input".
    Change to part 3 and press RETURN key. [q]

6.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 DISTRIBUTION 3 Diskette" and
    press Enter.

    After some time, a message with the number of blocks read is printed.

7.  Remove the diskette from drive 0. If you want to restart Volume Management,
    type:

    # /etc/init.d/volmgt start

8.  Type the following:

    # ./installdu.sh

9.  Follow the instructions on the screen to shut down the system.

    The instructions include how to restart the system.

10. A second reboot may be required if you have installed a new network card
    that uses a new network driver.

    See x86 Device Configuration Guide for information about what to do when
    replacing a network card.

When the system comes up, the new device drivers should be completely
installed and functional. However, additional steps may be necessary. See the
beginning of "Driver Update 5 Release Notes" earlier in this chapter.

Note - If you have a Sound Blaster card or AD1848 device or compatible, there
may be additional steps you need to take after the Solaris software is
installed on your system. See the three Device Reference Pages for the sbpro
driver in Appendix A.

Disabling Drivers After Installing the Driver Update

It is sometimes necessary to disable certain Solaris drivers so they won't
interfere with the proper operation of other hardware. See the beginning of
"Driver Update 5 Release Notes" for information on disabling the mcis driver.

Appendix A - Device Reference Pages

This appendix supplements Appendix B, "Device Reference Pages," in x86
Device Configuration Guide. It includes necessary device configuration
information for hardware supported by the new or updated drivers.

Use the following table to locate information about your hardware and
proceed directly to those pages.

===============================================================================
Disk Interface                                          Solaris Driver

IDE Disk Drive and Enhanced IDE Controller              ata
(Including IDE CD-ROM ATAPI)
-------------------------------------------------------------------------------
SCSI Host Bus Adapters                                  Solaris Driver

Adaptec AHA-154x ISA HBAs                               aha

Adaptec AIC-7770/AHA-274x/AHA-284x HBAs                 esa

Adaptec AIC-7850/AIC-7870/AIC-7871/AIC-7872/            adp
AIC-7880 (AHA-2940/AHA-2940W/AHA-2940U/
AHA-2940UW/AHA-3940/AHA-3940W PCI HBAs)

AdvanSys SCSI Adapters                                  asc

BusLogic FlashPoint LT Ultra SCSI, FlashPoint LW Ultra  flashpt
and Wide SCSI, FlashPoint DL Dual Channel Ultra SCSI,
FlashPoint DW Dual Channel Ultra and Wide SCSI PCI
HBAs

Compaq 53C710, 53C810, 53C825 PCI and EISA SCSI-2       ncrs
HBAs

IBM Micro Channel SCSI-2 Fast/Wide Adapter/A            corvette
-------------------------------------------------------------------------------
SCSI Disk Arrays/RAID Controllers                       Solaris Driver

Compaq SMART-2 EISA/PCI Array Controller                smartii

DPT PM-2024/PM-2124/PM-2124W/PM-3224/PM-3224W           dpt
PCI HBAs

IBM PC ServeRAID HBA                                    chs

IBM SCSI-2 RAID Controller and IBM SCSI-2 Fast/Wide     mlx
Streaming-RAID Adapter/A, Mylex DAC960 EISA and
Mylex DAC960P PCI Controllers
-------------------------------------------------------------------------------
Ethernet Network Adapters                               Solaris Driver

3Com EtherLink 16 (3C507)                               elink

3Com EtherLink II (3C503) and                           el
EtherLink II/16 (3C503-16)

3Com EtherLink III (3C5x9, 3C509B, 3C59x), EtherLink    elx
XL (3C900 TPO), Fast EtherLink XL (3C905)

AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI)               pcn

Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR       nfe
EISA Controllers

Compaq NetFlex-3 EISA and PCI Controllers               cnft

DEC 21040, 21041, 21140 Ethernet                        dnet

Fujitsu FMV183 Ethernet                                 fmvel

Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP           iee

Intel EtherExpress Flash32 (82596)                      ieef

Intel EtherExpress PRO/100 (82556)                      ieef

Novell NE2000, NE2000plus Ethernet and Clones           nei

SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS    smc
Elite16, EtherCard PLUS (8416, 8216, 8013, 8003)

SMC Ether 10/100 (9232)                                 smcf
-------------------------------------------------------------------------------
FDDI Network Adapters                                   Solaris Driver

Rockwell Network Systems (RNS) 2200 Series FDDI PCI     sxp
Adapters
-------------------------------------------------------------------------------
Token Ring Network Adapters                             Solaris Driver

IBM 16/4, Auto16/4 Token Ring and Compatible Adapters   tr

Madge Smart 16/4 Token Ring                             mtok
-------------------------------------------------------------------------------
Audio Cards                                             Solaris Driver

Analog Devices AD1848 and Compatible Devices            sbpro

Creative Labs Sound Blaster Pro                         sbpro

Creative Labs Sound Blaster 16/Sound Blaster AWE32      sbpro
-------------------------------------------------------------------------------
PC Card (PCMCIA) Hardware                               Solaris Driver

Modem and Serial PC Card Devices                        pcser
===============================================================================

Disk Interface

IDE Disk Drive and Enhanced IDE Controller
(Including IDE CD-ROM ATAPI)

Description

An IDE disk drive contains a disk controller and drive electronics. An IDE
controller supports two devices per controller up to a maximum of four IDE
drives when both primary and secondary interfaces are available. This includes
hard disk drives and CD-ROM drives.

Device Configuration

Preparing for Configuration

If you have two IDE drives on the same adapter, one must be set to "master" and
the other to "slave." Typically, if you have both an IDE hard disk drive and an
IDE CD-ROM drive, the hard disk drive is the master, and the CD-ROM drive the
slave, but this isn't mandatory. If you only have one drive on an adapter, it
must be set to master.

Configuring the Device

1.  If you have an IDE CD-ROM drive installed, the system BIOS "Drive Type"
    parameters should be set to "not installed" for that device, since they
    only apply to IDE hard disks.

2.  Enable BIOS support for enhanced IDE drives, if your system supports it.

    Typically, this capability is referred to as logical block addressing
    (LBA).

Note - If the BIOS supports autoconfiguration, use this facility to set the
number of heads, cylinders, and sectors for the IDE hard disk drive. If this
capability is not supported by the BIOS, use the settings provided by the disk
manufacturer.

3.  Verify that the configuration recorded on your Device Configuration
    Worksheet for your IDE adapter is set within the parameters listed under
    "Valid Configurations."

Valid Configurations

Primary controller:

o IRQ           14
o I/O Address   0x1F0

Secondary controller:

o IRQ           15
o I/O Address   0x170

Known Problems and Limitations

o Several vendors ship PCI-equipped machines with IDE interfaces on the
  motherboard. A number of these machines use the CMD-604 PCI-IDE
  controller. This chip provides two IDE interfaces. The primary IDE interface
  is at I/O address 0x1F0 and the secondary interface at 0x170. However, this
  chip cannot handle simultanous I/O on both IDE interfaces. This defect causes
  Solaris to hang if both interfaces are used.

  Workaround: Use only the primary IDE interface at address 0x1F0. Machines
  known to use this chip include DELL(R) XPS/90, HP XU/590C, and American
  Megatrends Atlas boards.

o In this release, it is not possible to boot from the third or fourth IDE disk
  drives, although you can install Solaris software on them.

o The Solaris Volume Management software does not work with the Sony CDU-55E
  CD-ROM drive regardless of how it is configured (as the master or the
  slave). If you have a Sony CDU-55E, you must comment out the following line
  in the file /etc/vold.conf to prevent vold from hanging the controller:

  # use cdrom drive /dev/rdsk/c*s2 dev_cdrom.so cdrom%d

o The Panasonic LK_MC579B IDE CD-ROM drive cannot be used to install the
  Solaris operating environment and is not supported.

o The following ATAPI CD-ROM drives may fail during installation on some
  configurations:

  o NEC CDR-260
  o AZT CDR 268-031SE
  o Media Vision 6X
  o Sony CDU-55E

o Some systems may have problems booting from IDE drives that are larger than
  512 Mbytes, even though the install to the drive succeeds.

  Workaround: Disable logical block addressing and reduce the CMOS geometry
  information for the drive to be less than 1024 cylinders.

o If you have a Compaq LTE Elite 4/40 notebook, you may experience system hangs
  when changing from suspend mode to resume. To keep the ata driver from
  hanging after being resumed, use any text editor to change the default value
  of the timing_flags property (in the ata.conf file) from 0x0 to 0x1 (that is,
  timing_flags=0x1). Then save the file and reboot the system. The
  /platform/i386pc/kernel/drv/ata.conf file is shown below:

# Copyright (c) 1992 Sun Microsystems, Inc.  All Rights Reserved.
#

#ident "@(#)ata.conf    1.10    96/08/05 SMI"

#
# primary controller
#
# for performance upgrade - set block factor to 0x10
name="ata" class="sysbus" interrupts=5,14 reg=0x1f0,0,0
        ioaddr1=0x1f0 ioaddr2=0x3f0 timing_flags=0x0
        drive0_block_factor=0x1 drive1_block_factor=0x1
max_transfer=0x100
        flow_control="dmult" queue="qsort" disk="dadk" ;
#
# secondary controller
#
name="ata" class="sysbus" interrupts=5,15 reg=0x170,0,0
        ioaddr1=0x170 ioaddr2=0x370 timing_flags=0x0
        drive0_block_factor=0x1 drive1_block_factor=0x1
max_transfer=0x100
        flow_control="dmult" queue="qsort" disk="dadk" ;

Note that the file contains an entry for the timing_flags property for both
the primary controller and the secondary controller. For the Compaq LTE
Elite 4/40, you only have to change the property for the primary controller.

SCSI Host Bus Adapters

Adaptec AHA-154x ISA HBAs

Description

The Adaptec AHA-154x family of 16-bit SCSI host bus adapters is used with
ISA or EISA buses.

Device Configuration

Preparing for Configuration

o Use default configuration parameters in both basic and advanced modes for the
  Adaptec AHA-154xC and AHA-154xCP.

o To access the AHA-154x C/CF/CP BIOS setup utility Configuration screen, press
  ctrl+A.

o Select SCSI Device Configuration and disable Synchronous Negotiation for each
  CD-ROM drive target.

o If one or more disks connected to this controller are greater than 1 Gbyte,
  return to the Configuration screen, select Advanced Configuration Options,
  and enable Extended BIOS Translation for DOS Drives > 1 Gbyte. In some cases,
  this may require a low-level format of such disks.

o The DMA transfer rate for the AHA-154xCF should be left at the default unless
  your motherboard supports higher rates.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if the Adaptec AHA-154x
    settings need to be changed.

2.  Refer to the Adaptec manual for how to set the jumpers or DIP switches to
    the parameters that appear on your worksheet.

Note that the AHA-154xC, AHA-154xCF, and AHA-154xCP contain a
built-in, menu-driven program for configuring HBA options. (A DIP switch
replaces many of the jumpers found on the B version.) Use of the built-in
configuration program and DIP switch assignments are documented in the
installation guide that comes with the Adaptec AHA-154xC or
AHA-154xCP board.

3.  If necessary, modify the parameter values.

Valid Configurations

Following are the parameters for Adaptec AHA-154x host bus adapters:

o IRQ           Any legal value between 9 and 15

o DMA Channel   6

o I/O Address   0x330

Alternative Custom Configuration

The DMA speed, bus on time, and bus off time may be set for optimum
performance with each ISA motherboard. Refer to Adaptec AHA-1540/1542
User's Manual for instructions.

Adaptec AIC-7770/AHA-274x/AHA-284x HBAs

Description

These configuration notes apply to the Adaptec AHA-2740/2742, AHA-
2740A/2742A, AHA-2740T/2742T, AHA-2740W, and AHA-2740AT/2742AT
EISA host bus adapters, AHA-2840VL and AHA-2842VL VESA local host bus
adapters, and motherboards that integrate the Adaptec AIC-7770 chip, such as
the Intel Xpress and the Unisys U6000 server systems.

Caution! - Probing for AHA-284x VLB cards has been disabled to avoid
conflicts with some PCI devices. To enable your AHA-284x adapter, see
"Adding Support for AHA-284x Devices" later in this Device Reference Page.

Device Configuration

Preparing for Configuration

o Ensure that the SCSI bus is properly terminated.

o Make sure that the CD-ROM drive with the Solaris CD is on channel A of the
  boot controller and that the boot disk is target 0 on channel A of the same
  controller.

o Configure AHA-2740 boards with up-to-date configuration files to make sure
  they are properly recognized. Use Version 2.1 or later of the AHA-2740 series
  configuration utilities.

o On a motherboard with an AMI BIOS, use Version 2.01 or later of the AMI EISA
  configuration utility when configuring the AHA-2740 EISA.

o For disks larger than 1 Gbyte, enable BIOS support for large disks. The HBA
  geometry for large disks is 255 heads and 63 sectors per track; for smaller
  disks it is 64 heads, 32 sectors per track.

o For a slow CD-ROM device, such as the Sun(TM) Sony CD-ROM or the Unisys
  system CD-ROM, disable the Bus Reset option on channel A of the boot
  controller. Use the EISA configuration utility on the AHA-274x, or use the
  configuration utility for the AHA-284x by pressing Ctrl-A at boot time. After
  installation, enable the Bus Reset option again.

Avoiding Possible Device Conflicts

o Probing for AHA-284x VLB cards has been disabled to avoid conficts with some
  PCI cards at certain I/O addresses.

o Motherboards that support level-triggered interrupts, such as an EISA
  motherboard, will support multiple AHA-2740 adapters sharing the same IRQ
  (although there may be minor performance degradation).

o The AHA-2840VL adapter cannot share IRQ vectors because it supports only
  Edge-triggered interrupts.

Note - The AHA-2740 is not compatible with Wyse MP systems.

Adding Support for AHA-284x Devices

o If you are using a Driver Update to install Solaris on a system with an
  AHA-284x controller, you need to modify the Driver Update boot diskettes
  before installation. See the next section, "Modifying the Driver Update Boot
  Diskettes."

o If you are adding an AHA-284x controller to a system that has Solaris and a
  Driver Update installed, you must do the following as root before installing
  the controller:

  a.  Add the following line to the /etc/system file:

      set esa:esa_vlb_probe = 0xffff

  b.  Type:

      # touch /reconfigure
      # halt

  c.  Power down the system, install the controller, and power up the
      system.

Modifying the Driver Update Boot Diskettes

Since probing for AHA-284x VLB cards has been disabled by default, special
command files on the Driver Update boot diskettes are used to enable probing.
The diskettes must be modified using DOS. As a precaution, you should make a
copy of the original Driver Update boot diskettes prior to running the special
command files.

1.  Boot DOS on your system.

2.  Insert a blank 3.5-inch diskette into drive A: and format it:

    format a:

3.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

4.  Label the copy of the first Driver Update boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette for AHA-
    284x SCSI controller."

5.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

6.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

7.  Label the copy of the second Driver Update boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette for
    AHA-284x SCSI controller."

8.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

9.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette" into
    drive A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

10. Label the copy of the second Driver Update boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette
    for AHA-284x SCSI controller."

11. Store your original Driver Update boot diskettes in a safe place.

12. Insert the copy of "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER
    Diskette" into drive A:.

    Make sure the diskette is writable because the contents will be modified.

13. Change to drive A: (remember DOS is still running):

    a:

14. To enable AHA-284x probing, run the esavlb.bat command:

    esavlb

Configuring the Device

1.  Run the configuration utility supplied by the vendor, and load the
    configuration file for the Adaptec controller.

2.  Choose any valid IRQ that does not conflict with other devices in the
    system.

3.  Select channel A as the Primary Channel.

4.  Run the BIOS configuration and verify that BIOS support for more than two
    drives is disabled.

5.  If there are multiple AIC-7770 controllers on one system, the order of the
    I/O base addresses must match the order of the BIOS base addresses.

    On an EISA motherboard, the I/O base address corresponds to the EISA slot
    number times 0x1000 plus 0xc00 for controller boards. For example, if the
    first slot has an AHA-2740 controller, the address is 0x1c00, and if the
    adjacent slot also has an AHA-2740 controller, the address is 0x2c00.
    Motherboard vendors usually map the controller chip on the motherboard at
    the highest EISA slot plus 1. Thus in an EISA motherboard with three EISA
    slots, the motherboard AIC-7770 address is 0x4c00.

    The BIOS base address is selected from a range of possible choices on the
    vendor-supplied configuration utility. Common addresses for the AHA-2740
    controller are: 0xcc00, 0xd400, 0xd800, and 0xdc00. The controller with the
    lowest BIOS base address will become the boot or primary controller.

    Solaris numbers controllers using the I/O base address. To ensure that the
    boot controller for the BIOS is identified as the boot controller by
    Solaris, order the BIOS base addresses in the same manner as I/O base
    addresses.

Known Problems and Limitations

o A large disk used with Solaris on an AIC-7770 controller cannot be mounted on
  a controller with a different geometry, such as the DPT PM-2022 controller.

o Some VESA local bus motherboards do not support more than one bus master
  controller like the AHA-2840 VESA local host bus adapter.

o Disks larger than 1 Gbyte are supported with two different geometries
  depending on whether the disk is on a controller with the BIOS enabled or
  disabled at runtime.

  The boot controller must always have the BIOS enabled. After two disks have
  been located on one or two controllers, the BIOS is automatically disabled on
  all subsequent AHA-2740 controllers.

  The geometry for a disk with BIOS enabled in the EISA configuration utility
  at runtime where the system has not disabled the BIOS is 255 heads and 63
  sectors per track.

  For all other disks, the geometry is 64 heads and 32 sectors per track.

  A disk on an AHA-2740 controller configured with the BIOS enabled cannot be
  moved to a controller with the BIOS disabled and still have 255 heads and 63
  sectors per track.

o On the Unisys U6000/DT2, run the UNISYS.BAT file in a DOS environment before
  installation. Refer to x86: Solaris 2.5 Installation Notes for more
  information.

o When using AHA-2742T and AHA-2842VL adapters with slow tape devices, under
  heavy loads, error messages like the following are displayed:

  Warning: /eisa/esa@2c00/cmtp@4,0 (Tape4):
  0.25 inch cartridge
  Tape 11: Fixed record length (512 byte blocks) I/O

  Set the SCSI ID of the tape drive higher than the host bus adapter.

  For example, set the tape SCSI ID to 6 and the host bus adapter SCSI ID to 5
  or less by completing the following:

  o Log in as root and shut down the Solaris system.

  o Boot DOS and change the target ID of the host bus adapter to 5 using the
    EISA configuration utility supplied by the motherboard manufacturer.

  o Turn off the computer and power down the tape.

  o Jumper the tape device to SCSI ID 6.

  o Boot Solaris and run the drvconfig and tapes utilities.

Adaptec AIC-7850/AIC-7870/AIC-7871/AIC-7872/AIC-7880
(AHA-2940/AHA-2940W/AHA-2940U/AHA-2940UW/AHA-3940/AHA-
3940W PCI HBAs)

Description

The Adaptec AHA-2940, AHA-2940W, AHA-2940U, AHA-2940UW, AHA-3940,
and AHA-3940W cards are PCI-to-Fast SCSI controllers based on the Adaptec
AIC-7850, AIC-7870, AIC-7871, AIC-7872, or AIC-7880 chips.

Device Configuration

Preparing for Configuration

To use the AHA-3940 or AHA-3940W adapters, the motherboard must have a
BIOS that supports the DEC PCI bridge chips on the host bus adapter.

Configuring the Device

1.  Ensure that the SCSI bus is properly terminated.

2.  Set up the IRQ for the controller by using the CMOS setup utility supplied
    with the motherboard (if this feature is available for your computer).

    If you have more than one controller (or an embedded controller), use one
    IRQ per controller. Enable bus mastering for the slot(s) with your host bus
    adapter(s), when the choice is given.

3.  Run the Adaptec configuration utility by pressing Ctrl-A at boot time.

4.  Ensure that support for more than two DOS drives is disabled.

5.  For older disk drives, tape drives, and most CD-ROM devices, make sure the
    maximum SCSI data transfer speed is set to 5.0 Mbytes per second.

6.  Enable support for disks larger than 1 Gbyte if applicable.

7.  Make sure there are no IRQ conflicts between ISA cards on your system and
    PCI controllers.

Known Problems and Limitations

o The Adaptec AHA-3940 has been certified by Adaptec to run in specific system
  platforms. Our testing has shown that Solaris works properly in some of
  those systems and not in others. If you encounter problems running Solaris
  on an Adaptec-approved platform with the AHA-3940, contact your technical
  support provider.

o On some PCI systems with an Adaptec 294x card installed, problems with
  user-level programs have been observed on a number of PCI motherboards,
  including the following models:

  o PCI motherboards with a 60-MHz Pentium chip, with PCI chipset numbers
    S82433LX Z852 and S82434LX Z850. The part numbers of the Intel motherboards
    are AA616393-007 and AA615988-009.

  o PCI motherboards with a 90-MHz Pentium chip, with PCI chipset numbers
    S82433NX Z895, S82434NX Z895, and S82434NX Z896. The part number of the
    Intel motherboard is 541286-005. (Gateway 2000 uses this motherboard.)

  o The AA-619772-002 motherboard with 433LX Z852 and 434LX Z882 chips causes
    random memory inconsistencies. Return the motherboard to the vendor for a
    replacement.

  If you experience problems with user-level programs, turn off write-back
  CPU caching (or all caching if there is no control over the caching
  algorithm) using the BIOS setup facility.

o The Adaptec 2940 SCSI adapter does not recognize the Quantum Empire 1080S
  SCSI disk drive or the HP 3323 SE SCSI disk drive.

  Workaround: Reduce the Synchronous Transfer rate on the Adaptec controller to
  8 Mbytes per second.

AdvanSys SCSI Adapters

Description

The AdvanSys Solaris Universal Driver, asc, supports all AdvanSys SCSI
Adapters listed below.

Device Configuration

The Command Descriptor Block (CDB) counts below indicate the number of
SCSI CDB requests that can be stored in the RISC chip cache and board LRAM.
A CDB is a single SCSI command. The CDB value can be lowered in the BIOS
by changing the Host Queue Size adapter setting.

Connectivity Products                           CDB

ABP510/5150-Bus-Master ISA(1)                   240
ABP5140-Bus-Master ISA PnP1(1)                  16
ABP5142-Bus-Master ISA PnP with floppy          16
ABP920-Bus-Master PCI                           16
ABP930-Bus-Master PCI                           16
ABP930U-Bus-Master PCI Ultra                    16
ABP960-Bus-Master PCI MAC/PC(2)                 16
ABP960U-Bus-Master PCI MAC/PC Ultra             16

Single Channel Products                         CDB

ABP542-Bus-Master ISA with floppy               240
ABP742-Bus-Master EISA                          240
ABP842-Bus-Master VL                            240
ABP940-Bus-Master PCI                           240
ABP940U--Bus-Master PCI Ultra                   240
ABP970-Bus-Master PCI MAC/PC                    240
ABP970U-Bus-Master PCI MAC/PC Ultra             240

Dual Channel Products                           CDB

ABP752-Dual Channel Bus-Master EISA             240 per channel
ABP852-Dual Channel Bus-Master VL               240 per channel
ABP950-Dual Channel Bus-Master PCI              240 per channel

(1) These boards have been shipped by HP with the 4020i CD-ROM drive. Since
    they have no BIOS, they cannot control a boot device, but they can control
    secondary devices.

(2) This board has been shipped by Iomega with the Jaz Jet drive.


AdvanSys Contact Information

Updates to the AdvanSys Solaris driver and technical support for the
AdvanSys Solaris driver and AdvanSys adapters can be obtained by contacting
AdvanSys.

Mail                    Advanced System Products, Inc.
                        1150 Ringwood Court
                        San Jose, CA 95131

Operator                1-408-383-9400

FAX                     1-408-383-9612

Tech Support            1-800-525-7440

BBS                     1-408-383-9540 (14400,N,8,1)

Interactive FAX         1-408-383-9753

Customer Direct Sales   1-800-883-1099/1-408-383-5777

Tech Support Email      support@advansys.com

FTP Site                ftp.advansys.com (login: anonymous)

Web Site                http://www.advansys.com

BusLogic FlashPoint LT Ultra SCSI, FlashPoint LW Ultra and Wide SCSI,
FlashPoint DL Dual Channel Ultra SCSI, FlashPoint DW Dual Channel
Ultra and Wide SCSI PCI HBAs

Description

The FlashPoint family of cards are Ultra SCSI host adapters for the PCI bus.

Direct Support Provided by Mylex Corporation

Mylex Corporation provides direct support for the flashpt device driver.
Refer to the product menu and related documents for detailed information.
Technical support is available through telephone and email:

o (408) 654-0760
o techsup@buslogic.com

Device Configuration

Configuring the Device

Since the FlashPoint family is PCI compliant, no special hardware setup is
required. To display information and set up the adapters, use the on-board
AutoSCSI utility.

To run AutoSCSI, boot the system and press Control-b when "FlashPoint"
appears on the screen.

Compaq 53C710, 53C810, 53C825 PCI and EISA SCSI-2 HBAs

Description

The Compaq family of PCI and EISA controllers based on the 53C710, 53C810,
and 53C825 chips includes the following:

Compaq Controller                           Chip     Available On
-------------------------------------------------------------------------------
Compaq 32-Bit Fast-SCSI-2                   53C710   Optional EISA add-in card
Compaq Integrated 32-Bit Fast-SCSI-2        53C710   ProLiant 2000, 4000
Compaq Integrated 32-Bit Fast-SCSI-2        53C810   ProSignia 300, 500
Compaq Integrated 32-Bit Fast-Wide SCSI-2   53C825   ProLiant 1500, 4500
Compaq 32-Bit Fast-Wide SCSI-2/E            53C825   Optional EISA add-in card
Compaq 32-Bit Fast-Wide SCSI-2/P            53C825   Optional PCI add-in card

Optional PCI add-in card

Note - The Wide SCSI option is not supported under the Solaris operating
environment. Some cards include connectors for both narrow cables (8-bit SCSI A
cables) and wide cables (16-bit SCSI P cables). You can connect devices to the
SCSI Wide connectors using SCSI P cables, but the Solaris ncrs driver will not
initiate or accept the Wide Data Transfer option. The attached devices will
function in 8-bit narrow mode.

Device Configuration

Preparing for Configuration

See the hardware manufacturer's documentation for installation and cabling
requirements.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if the controller's
    settings need to be changed.

2.  Use the Compaq EISA configuration utility Version 2.20 Revision B or later.

    This can be run from the hard disk or from the diskettes that come with
    your system.

3.  At the MAIN MENU, press ctrl-A to see the Advanced Mode options.

    A pop-up box shows that Advanced Mode is enabled.

4.  Press Enter.

5.  Select System Configuration.

6.  Select Configure Hardware.

    The program will then ask you to insert the second diskette into the drive.

7.  Press Enter after you have inserted the second diskette.

8.  Select Configuration Set Up.

9.  Select Step 2 Add/Remove Board.

    Follow the instructions on the screen to add your board.

10. Select Step 3 View or Edit Details.

    Find the description of the slot with the controller. Use the Page-Down key
    as needed.

11. Select BIOS Hard Drive Geometry under the slot description that lists the
    controller.

12. Set this option to <=1 GB: 64 Heads, 32 Sectors > 1GB: 255 Heads, 63
    sectors.

    This will work for disks with sizes greater and smaller than 1 Gbyte.

13. Press F10 to leave that menu.

14. Select Step 5 Save and Exit.

    Save your changes and exit.

Known Problems and Limitations

The SCSI Tagged Queuing option is not supported.

IBM Micro Channel SCSI-2 Fast/Wide Adapter/A

Description

The IBM SCSI-2 Fast/Wide Adapter/A is a SCSI controller used with a Micro
Channel bus.

Caution! - The Solaris mcis driver, which supports the IBM Micro Channel
SCSI adapter, conflicts with the IBM SCSI-2 Fast/Wide Adapter/A. If your
system has an IBM SCSI-2 Fast/Wide Adapter/A installed, you must disable
the mcis driver before installing Solaris x86. This is done by modifying the
Driver Update boot diskettes using the corvette.bat file under DOS; see
"Modifying the Driver Update Boot Diskettes" below.

If you already have the Solaris operating environment running on your system
and you want to add support for the IBM SCSI-2 Fast/Wide Adapter/A, you
should not install the adapter until steps have been taken to disable the mcis
driver; see "Disabling the mcis Driver After Installing Solaris x86" below.

Device Configuration

Preparing for Configuration

Ensure that the controller board is properly installed in any slot between 1
and 8. Slots 9 and above are not supported in this release.

Avoiding Possible Device Conflicts

The IBM SCSI-2 Fast/Wide Adapter/A cannot be installed on a system with
the IBM Micro Channel SCSI adapter.

Configuring the Device

The Solaris mcis device driver interferes with the proper operation of the IBM
SCSI-2 Fast/Wide Adapter/A. To avoid conflicts, the Solaris mcis driver must
be disabled before the IBM SCSI-2 Fast/Wide Adapter/A and the Solaris
software can be installed. You must first modify the Driver Update boot
diskettes and then disable the mcis device driver.

Modifying the Driver Update Boot Diskettes

The diskettes must be modified using DOS. As a precaution, you should make
a copy of the original boot diskettes prior to running the special command
files.

1.  Boot DOS on your system.

2.  Insert a blank 3.5-inch diskette into drive A: and format it:

    format a:

3.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

4.  Label the copy of the boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette for IBM
    SCSI-2 Fast/Wide Adapter/A."

5.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

6.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

7.  Label the copy of the second boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette for IBM
    SCSI-2 Fast/Wide Adapter/A."

8.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

9.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette" into
    drive A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

10. Label the copy of the second boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette
    for IBM SCSI-2 Fast/Wide Adapter/A."

11. Store your original boot diskettes in a safe place.

12. Insert the copy of "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER
    Diskette" into diskette into drive A:.

    Make sure the diskette is writable because the contents will be modified.

13. Change to drive A: (remember DOS is still running):

    a:

14. Run the corvette.bat command:

    corvette.bat

Disabling the mcis Driver After Installing Solaris x86

Before you can add and configure IBM SCSI-2 Fast/Wide Adapter/A after
installing Solaris x86 and before adding Driver Update 5, you must disable the
mcis driver by modifying a system file and rebooting.

1.  Become root.

2.  Use a text editor (such as vi) to edit the /etc/system file and add the
    following line:

    exclude: mcis

Note - To comment out a line in the /etc/system file, place an asterisk * at
the beginning of the line.

3.  Remove or comment out the following line, if present:

    forceload: drv/mcis

4.  Save your changes and exit the editor.

5.  Shut down the system and power it off.

6.  Now perform a reconfiguration boot to make your changes take effect:

    # touch /reconfigure
    # halt

7.  Install your hardware.

    Use the configuration information in "Valid Configurations" below.

8.  Reboot the system.

Note - Upon reboot, the IBM Micro Channel SCSI adapter will no longer be
recognized by the Solaris software, and it cannot be used in a system with the
IBM Micro Channel SCSI-2 Fast/Wide Adapter/A.

Valid Configurations

The following parameters are supported for the IBM SCSI-2 Fast/Wide
Adapter/A:

o IRQ   14

o I/O Address   0x3540, 0x3548, 0x3550, 0x3558, 0x3560, 0x3568,
                0x3570, 0x3578

Known Problems and Limitations

o The microcode version of the SCSI-2 Fast/Wide Adapter/A board should be 0x71
  or later. Boards with older versions, such as version 0x58, may cause the
  Solaris system to hang when using certain tape drives. The Solaris corvette
  driver displays a warning message if it detects an older, unsupported version
  of the adapter.

o The IBM SCSI-2 Fast/Wide Adapter/A is currently only supported on systems
  with at least 32 Mbytes of memory installed.

SCSI Disk Arrays/RAID Controllers

Compaq SMART-2 EISA/PCI Array Controller

Description

The Compaq SMART-2 EISA/PCI Array controller supports internal and
external SCSI drives on Compaq servers.

Device Configuration

Preparing for Configuration

Be sure to read the documentation that comes with your hardware. Note the
following:

o The SMART-2 controller only supports SCSI disk drives. SCSI tape drives and
  CD-ROM drives are not supported.

o The boot device *must* be logical drive 0 on the *primary* controller. Even
  though the BIOS lets you configure any controller as your primary controller,
  it will only let you boot from logical drive 0 on that controller.

Configuring the Device

1.  EISA systems *only*: Configure the system using the Compaq EISA
    configuration utility (ECU Version 2.30 or higher) so the system recognizes
    the SMART-2 controller.

2.  Use the Compaq Array Configuration Utility to configure drives on the
    SMART-2 controller.

Known Problems and Limitations

o If disks on a *failed* drive are replaced by hotplugging during I/O, the
  system panics.

o Firmware version 1.26 of the SMART-2 PCI controller is slow on Solaris 2.5.
  Firmware version 1.36 and later versions don't exhibit this problem.

DPT PM-2024/PM-2124/PM-2124W/PM-3224/PM-3224W PCI HBAs

Description

The DPT PM-2024, PM-2124, PM-2124W, PM-3224, and PM-3224W are SCSI 
controllers for a PCI bus. The PM-3224 and PM-3224W are SCSI RAID 
adapters.

Device Configuration

Preparing for Configuration

o Check the EPROM revisions on the board. 

  o The DPT PM-3224 should have EPROM version 7A or later. 

  o The DPT PM-2024 and PM-2124 adapters should have EPROM version 
    6D4 or later. 

  o All the PCI boards should have SmartROM version 3.B or later.

o Ensure that the controller board is properly installed in any PCI slot
  capable of bus-mastering.

Configuring the Device

1.  Use the CMOS configuration utility supplied by the computer vendor to
    enable the DPT PCI controller.

    a.  Enable the DPT PCI controller.
    b.  Enable the PCI slot.
    c.  Enable bus mastering.
    d.  Choose an unused IRQ between 9 and 15.

Note - If IRQ 12 does not respond, try another unused IRQ.

2.  Enter the DPT Configuration Utility by typing Ctrl-D at controller boot
    time.

    a.  Set I/O address to "Auto."

    b.  If the firmware version of the controller is less than 7A, or if your
        computer memory is ECC or does not check parity, disable PCI parity
        checking.

Known Problems and Limitations

If the boot diskette reports a DPT controller driver cannot be installed, the 
motherboard installed in your system probably has ECC memory or does not 
check parity; disable PCI parity checking.

IBM PC ServeRAID HBA

Description

The IBM PC ServeRAID is a SCSI RAID controller for the PCI bus.

Device Configuration

Configuring the Device

Follow the configuration instructions in the vendor's manual.

Known Problems and Limitations

o In order to prevent any data loss, if a SCSI disk drive is not defined to be
  part of any physical pack within a logical drive, it won't be accessible
  through Solaris.

o If you are using the boot diskette to boot or install Solaris on a system
  that has a physical disk drive configured in Ready ("RDY") or Hot-Spare
  ("HSP") state, the system may hang.

  Workaround: Use the manufacturer's configuration utility to set Ready to
  Standby ("SBY") or Hot-Spare to Standby Hot-Spare ("SHS").

o If the boot logical drive is equal to or less than 2 Gbytes, before
  installing Solaris, use the IBM PC ServerRAID utility to set the BIOS
  compatibility to Limited BIOS Mapping. If this isn't done, you won't be able
  to boot from the IBM PC ServeRAID controller, and will need to reinstall
  Solaris.

IBM SCSI-2 RAID Controller and IBM SCSI-2 Fast/Wide Streaming-RAID
Adapter/A, Mylex DAC960 EISA and Mylex DAC960P PCI Controllers

Description

The IBM SCSI-2 RAID controller and IBM SCSI-2 Fast/Wide Streaming-RAID
Adapter/A (IBM DMC960) are devices for the MicroChannel bus. The Mylex
DAC960 SCSI controller is used with an EISA bus. The Mylex DAC960P SCSI
controller is used with a PCI bus. Various models within each family support
varying numbers of SCSI channels.

Device Configuration

Preparing for Configuration

o The choice of SCSI target ID numbers is limited. Assuming the maximum number
  of targets per channel on the particular model controller is MAX_TGT, the
  SCSI target IDs on a given channel should range from 0 to (MAX_TGT - 1). See
  the vendor documentation for more information.

o SCSI target IDs on one channel can be repeated on other channels.

    Example 1:
    The Mylex DxC960 5-channel models support a maximum of four targets
    per channel, that is, MAX_TGT = 4. Therefore, the SCSI target IDs on a
    given channel should range from 0 to 3.

    Example 2:
    The Mylex DxC960 3-channel models support a maximum of seven targets
    per channel, that is, MAX_TGT = 7. Therefore, the SCSI target IDs on a
    given channel should range from 0 to 6.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if the controller's
    settings need to be changed.

2.  Follow the configuration instructions in the vendor's manual.

Known Problems and Limitations

o If a SCSI disk drive is not defined to be part of any physical pack within a
  system drive, it is automatically labeled as a *standby* drive. If any SCSI
  disk drive within a system drive fails, data on a standby drive *may be lost*
  due to the standby replacement procedure. This procedure will overwrite the
  standby drive if the failed disk drive is configured with any level of
  redundancy (RAID levels 1, 5, and 6) *and* its size is identical to the size
  of the available standby drive. Therefore, despite the fact that the standby
  drives are physically connected, the system denies any kind of access to them
  so there is no chance of accidental loss of valuable data.

o Other than the standby rebuild of disk drives, which is described in the
  manufacturer's user's guide, these controllers do not currently support
  "hot-plugging" (adding or removing devices while the system is running). To
  add or remove devices you must shut down the system, add or remove devices,
  reconfigure the host bus adapter using the configuration utility provided by
  the vendor, and then reboot your system.

o The driver does not currently support variable-length tape drives. At this
  time, multivolume backup or restore is not supported for tape drives
  connected to the controller.

o Due to controller firmware limitations, a tape block size greater than
  32 Kbytes cannot be used. Also, tape drives will not work reliably on
  channels that also have SCSI hard drives attached to them. Therefore, to be
  certain of correct tape operation, use SCSI tape drives only on an otherwise
  unused channel, and with a fixed block size of 32 Kbytes or less. Long tape
  commands (such as the erasing of a large tape) may fail for this reason.

o Enable tag queuing only for the SCSI disk drives that are officially tested
  and approved by Mylex Corporation for the DAC960/DAC960P and by IBM for the
  DMC960. Otherwise, it is best to disable tag queuing to avoid serious
  problems.

o An interaction between certain CD-ROM players and the vold Volume Management
  daemon may cause a panic to occur in scsi_exam_arq().

  Workaround: Disable Volume Management of CD-ROM players by editing the
  /etc/vold.conf file and disabling lines that refer to CD-ROM players (see
  the vold and vold.conf manual pages for details).

o The mlx driver has been updated to provide PCI support in Solaris
  2.5/2.5.1. If you're using any one of the controllers supported by mlx,
  whether it is PCI or not, upgrading from 2.4 to 2.5 may fail, especially if
  mlx is the boot driver.

  Workaround: Don't upgrade; install Solaris 2.5/2.5.1 x86 if your system uses
  the mlx driver.

o The command mt erase works but reports the following error message when it
  gets to the end of the tape:

  /dev/rmt/0 erase failed: I/O error


Ethernet Network Adapters

3Com EtherLink 16 (3C507)

Description

The 3Com EtherLink 16 card is an Ethernet network adapter.

Device Configuration

Preparing for Configuration

o The manual for the 3Com EtherLink 16 card specifies that the base address of
  the card's shared RAM can be configured to several different addresses;
  however, the Solaris software does not support the F0000, F4000, F8000, and
  FC000 addresses.

o The 3Com EtherLink 16 Ethernet adapter has an on-board buffer of 64
  Kbytes. Using the configuration utility supplied by 3Com, you can configure
  the card to use the full 64 Kbytes, or a smaller amount.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if your 3Com EtherLink
    16 controller needs to be reconfigured.

2.  Follow the 3Com documentation and use the 3Com setup software to configure
    the card.

    Be sure you set the Data Mode from standard to Turbo.

Known Problems and Limitations

If the EtherLink 16 adapter is configured for less than 64 Kbytes of memory,
the adapter may fail. Using the manufacturer's configuration utility, configure
the adapter to use 64 Kbytes of memory even when the full 64-Kbyte memory range
is unavailable. After reconfiguring it to the desired memory size, the system
can usually access the network.

3Com EtherLink II (3C503) and EtherLink II/16 (3C503-16)

Description

The 3Com EtherLink II and EtherLink II/16 cards are Ethernet network
adapters.

Device Configuration

Preparing for Configuration

3Com 3C503 Ethernet adapters have two ports. One has RJ-45 and an AUI
connector, and the other has BNC (twisted-pair) and an AUI connector. The
3C503 adapter uses the BNC or RJ-45 port (the non-AUI connector) as the
default if it cannot detect a device connected to the AUI.

Avoiding Possible Device Conflicts

o These boards require that an I/O address and a shared memory address be set
  using jumpers on the board, as described in the 3Com documentation.

o Do not configure your 3C503 or 3C503-16 card at I/O address 0x2a0. This
  address has been removed as a valid I/O address for these cards because of a
  probe conflict with ata on Compaq docking stations.

o Due to probe conflicts, do not configure your 3C503 or 3C503-16 card at I/O
  address 0x280.

o The IRQ used by the 3C503 or 3C503-16 board depends on the I/O address set
  using the jumpers. If you configure your 3C503 or 3C503-16 at I/O address
  0x250, no other devices in your system should use IRQ 3. Refer to the
  manufacturer documentation for each device to see what IRQ is used.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if your 3Com EtherLink
    II card needs to be reconfigured.

2.  If you must set jumpers, refer to the 3Com documentation for the procedure.

Valid Configurations

This table shows which IRQ will be used by the 3C503 or 3C503-16 board
depending on the I/O address you select with the jumpers.

I/O Address  IRQ

0x250,0x2e0  3
0x300-0x350  2

Known Problems and Limitations

o The 3C503 board has a limited amount of on-board memory, which causes very
  poor NFS(TM) software performance. Because of this limitation, this card
  should not be used to netinstall Solaris.

o Do not configure the 3C503 or 3C503-16 card at I/O address 0x2a0 or
  0x280. These configurations could potentially cause conflicts and should not
  be used.

3Com EtherLink III (3C5x9, 3C509B, 3C59x), EtherLink XL (3C900 TPO),
Fast EtherLink XL (3C905)

Description

The 3Com EtherLink III 3C5x9, 3C509B, 3C59x, EtherLink XL 3C900 TPO, and
Fast EtherLink XL 3C905 controllers are Ethernet network adapters.

Device Configuration

Preparing for Configuration

o Configure the 3C509 (ISA bus) adapter for EISA addressing when installed in
  an EISA bus system.

o The 3C509B model is configured differently than the other models. Check the
  packaging material that comes with your adapter to verify that the "3C509B"
  designation is on the outside of the box.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if your 3Com EtherLink
    controller needs to be reconfigured.

2.  Follow the 3Com documentation and use the 3Com setup software to configure
    the card.

    If you have a 3C509B or 3C59x adapter, you can set the media type to "Auto
    Select."

3.  EtherLink III 3C509B *only*: Disable the Plug and Play option.

    This is particularly important on Plug and Play-capable systems.

Known Problems and Limitations

3C509B cards with the following information printed on the card won't work
with Solaris:

o ASSY 03-0021-000, REV A

AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI)

Description

The PCnet family of Ethernet controllers are based on the AMD PCnet-ISA and
PCnet-PCI controller chips. These include PCnet controllers embedded on
motherboards found in systems from Intergraph and Hewlett-Packard, and a
variety of add-in NICs.

Device Configuration

Configuring the Device

PCnet-ISA

Be sure that your PCnet-ISA adapter does not conflict with other adapters
configured in the system. See "Valid Configurations."

PCnet-PCI

PCI devices are autoconfigured by the system BIOS; no configuration is
required.

Valid Configurations

The following parameters are supported for PCnet-ISA adapters:

o IRQ           3, 5, 9, 10, 11, 15
o I/O Address   0x300, 0x320, 0x340, 0x360

Known Problems and Limitations

o In some cases, IRQ 4 may be offered as a configuration option for PCnet-ISA
  adapters; the Solaris pcn driver does not support IRQ 4.

o On some systems, particularly those with PCI controllers, IRQ 9 may not be
  usable by a PCnet-ISA adapter; configure the PCnet-ISA adapter to use another
  interrupt.

o Some versions of the PCnet-PCI chip have known problems that result in
  unreliable network operation or cause the system to "freeze." There are no
  known software workarounds, but if this happens while using an adapter based
  on a PCnet-PCI chip, contact the adapter vendor to see if the adapter
  contains the version of the chip known to exhibit these problems.

Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR EISA Controllers

Description

The Compaq NetFlex-2 DualPort ENET controller provides two Ethernet
interfaces under the Solaris operating environment. The Compaq NetFlex-2
ENET-TR controller can be configured for either Ethernet or token ring, but
only the Ethernet functionality is supported under the Solaris operating
environment.

Both the NetFlex-2 DualPort ENET and the NetFlex-2 ENET-TR are EISA bus
controllers.

Device Configuration

Preparing for Configuration

Compaq NetFlex-2 DualPort ENET *only*: If the dual-ported Ethernet card will
be used to install Solaris over a network, the connector for the network must
be connected to the *first* network port (Port 1). See the documentation that
comes with the dual-ported card to locate Port 1.

Avoiding Possible Device Conflicts

o Check for IRQ conflicts with ISA devices not defined in the EISA
configuration software.

o The default IRQ is 10, which can be a usable IRQ for many ISA cards,
including SMC Ethernet cards, for example.

Note - The Compaq NetFlex-2 DualPort ENET card shares the same IRQ for
both ports.

Configuring the Device

Use the EISA configuration utility to tell the system about the card.

1.  Set the connector type; use DB-15 or 10BaseT RJ-45.

    o For the NetFlex-2 DualPort ENET, using DB-15 connectors requires a
      special splitter cable that ships with the board.

    o The default setting (DB-9) on the NetFlex-2 ENET-TR needs to be changed.

2.  Compaq Netflex-2 ENET-TR card *only*: Configure this card to use a 10 Mbps
    data rate, not the default (16 Mbps).

Valid Configurations

The following IRQs are valid for this card:

o IRQ   3, 5, 9, 10, 11

Known Problems and Limitations

Promiscuous mode is not supported by the current release of the firmware for
this card.

Compaq NetFlex-3 EISA and PCI Controllers

Description

The Solaris cnft driver supports the NetFlex-3 family of Ethernet controllers
in a Compaq server. The NetFlex-3 products supported by the driver are:

o Compaq NetFlex-3/E
o Compaq NetFlex-3/P
o Compaq 10T UTP Module (included with NetFlex-3/E and NetFlex-3/P)
o Compaq 100VG-AnyLAN UTP Module (optional)
o Compaq 10/100BASE TX UTP Module (optional)

Device Configuration

Preparing for Configuration

o Insert a 10T UTP, 10/100BASE TX UTP, or 100VG-AnyLAN UTP module into the
  NetFlex-3 PCI or EISA controller base unit.

o Make sure the EISA NetFlex-3 controller is properly installed in one of the
  EISA slots and the PCI NetFlex-3 controller in one of the PCI slots in the
  server.

Configuring the Device

EISA Configuration

1.  Use the Compaq EISA configuration utility (ECU Version 2.30 or higher) so
    the system recognizes the NetFlex-3 controller(s).

2.  Modify IRQ settings for the NetFlex-3 controller, if required, using the
    Review or Modify Settings option in the EISA configuration utility.

3.  Save the configuration settings using the EISA configuration utility, and
    restart the system.

Software Configuration

Follow these steps to configure the behavior of your NetFlex-3 controller:

1.  Change the device configuration by modifying the driver configuration file
    /kernel/drv/cnft.conf.

    This file specifies the configurable parameters for the driver. The
    following are the valid configurable parameters:

    o duplex_mode: This property is used to force the duplex mode for the
      controller. It can be set to:

      o 0--autoconfigure (default)
      o 1--half duplex
      o 2--full duplex

    o media_speed: This property is used to set the media speed for the
      controller. This option can be used to force the 10/100BASE TX to 10- or
      100-Mbps operation. The valid values are:

      o 10--force 10-Mbps media speed
      o 100--force 100-Mbps media speed

      The media speed is auto-configured by default.

    o max_tx_lsts, max_rx_lsts, tx_threshold: These properties can be
      used to tune driver performance. The valid values are:

      Property        Valid Values    Default Value

      max_tx_lsts     4 to 32         16
      max_rx_lsts     4 to 32         16
      tx_threshold    2 to 32         2

    o debug_flag: This property is set to 1 or 0 to enable or disable debug
      messages from the driver. The debug messages are disabled by default.

2.  To activate the configuration changes, as root type:

    # touch /reconfigure
    # reboot

Valid Configurations

The following are the valid configurations for the NetFlex-3 controllers:

o NetFlex-3/E controllers:

  o IRQ         5, 9, 10, 11

o NetFlex-3/P controllers:

  o IRQ         2(9), 3, 4, 5, 6, 7, 10, 11

Known Problems and Limitations

o Trying to remove NetFlex-3 controllers configured at the same IRQ gives an
  error message:

  Couldn't remove function  ..... from ipl, irq

o Extreme load conditions on a ProSignia VS could result in a hardware lockup,
  affecting the functionality of the network driver.

o Configuring a NetFlex-3 controller and a NetFlex-2 controller on the same IRQ
  line on the same server could result in one of the controllers not being
  available.

  Workaround: Configure the two cards to different IRQ lines using the EISA
  configuration utility.

DEC 21040, 21041, 21140 Ethernet

Description

The Solaris dnet driver supports a large family of Ethernet and Fast Ethernet
controllers based on the DEC 21040, 21041, and 21140 controller chips. Refer to
the tables under "Valid Configurations" for a list of tested controllers.

Caution! - Stress tests have caused this driver to disconnect from the network.
Refer to "Known Problems and Limitations" below for more information.

Device Configuration

Avoiding Possible Device Conflicts

The following paragraphs describe how to set properties in the dnet.conf
file. In each case, just add a line with the property you want to change, and
end the line with a semicolon. For example, if you want BNC, add the following
line to the dnet.conf file:

bncaui=1;

If you want to change more than one property, put all properties on one line
separated by spaces with one semicolon at the end.

o The Solaris dnet driver is configured for optimal performance on today's
  10-Mbps networks, running in half-duplex mode. When used with a modern
  100-Mbps Fast Ethernet switch, running the driver in full-duplex mode will
  increase performance. To configure a controller to run in full-duplex mode,
  set the fulldup=1 property in the dnet.conf driver configuration file.

o This driver does not support autoconfiguration of the network media. The
  RJ-45 connector is used by default. If you use another network media
  (BNC/AUI), you will not be able to install from the network. After
  installation you can force configuration of the BNC/AUI connector by setting
  the bncaui=1 property in the dnet.conf driver configuration file.

o Some versions of controllers based on the DEC 21140 chip offer a choice
  between 100-Mbps Fast Ethernet and 10-Mbps Ethernet operation. By default,
  the dnet driver will operate the controller at 100-Mbps Fast Ethernet. To
  force 10-Mbps Ethernet operation on one of these controllers, set the mode=10
  property in the dnet.conf driver configuration file. Dual- speed controllers
  cannot be forced to 10-Mbps Ethernet operation during installation.

Note - It is not necessary to change the configuration file for the AsanteFAST
10/100 device. It automatically selects the correct speed both during and after
installation.

Valid Configurations

The PCI configuration process varies from system to system. Follow the
instructions provided by the vendor.

Successfully tested 21040/21041/21140-based adapters:
                                        Chip    10MB    100MB
Name/Model              Part/Vers       21xxx   Media   Media   Notes
----------              ---------       -----   -----   -----   -----
Asante Fast             09-00087-11 D   140AA   T       X       N
CNET PowerNIC CN935E    A               041AA   T B
Compex ReadyLINK ENET32 B2              040AA   T B A
Cogent EM100            100001-01 02    140             X
Cogent EM100TX          110001-02 02    140AB           X
Cogent EM110TX          110001-02 06    140AB   T       X
Cogent EM110TX          110001-03 01    140AB   T       X
Cogent EM110TX          110001-03 14    140AC   T       X
Cogent EM400       QUAD 400001-00 01    140             X
Cogent EM400       QUAD 400001-00 01    140AB           X
Cogent EM440       QUAD 440001-01 01    140AC   T       X       N
Cogent EM960C           960001-03 06    040AA   T B A
Cogent EM960C           960001-04 02    040AA   T B A           1
Cogent EM960TP          960001-03 07    040AA   T
Cogent EM960TP          960001-04 01    040AA   T
Cogent EM964       QUAD 964001-00 01    040AA   T
D-Link DE530CT          A2              040AA   T B
D-Link DE530CT          D2              041AA   T B
D-Link DE530CT+         A1              040AA   T B
DEC Evaluation          EB140A-TX 1.1   140A    T       X       N
Diversified Tech        651205025 1.2   140AC   T       X       5,I
Kingston KNE100TX       2001837-000.A00 140AC   T       X       N
Kingston KNE100TX       9920219-001.B00 140AB   T       X       N
Kingston KNE40BT        2001585 A00     041AA   T B
Rockwell RNS2300        320109-02       140AB   T       X
Rockwell RNS2340   QUAD 320112-00       140AB   T       X       2
SMC 8432 BT             60-600510-003 A 040AA   T B
SMC 8432 BT             60-600528-001 A 041AA   T B
SMC 8432 BT             61-600510-010 B 040AA   T B
SMC 8432 BTA            60-600510-003 A 040AA   T B A
SMC 8432 BTA            60-600528-001X1 041     T B A           6
SMC 8432 BTA            61-600510-000   040AA   T B A
SMC 8432 T              60-600528-001 A 041AA   T
SMC 9332BDT             60-600542-000 A 140AC   T       X       N
SMC 9332DST             60-600518-002 A 140     T       X       3
SMC 9332DST             61-600518-000 B 140     T       X       3
Znyx ZX311              SA0027 01       041AA   T B A
Znyx ZX312              SA0011 04       040AA   T B A           1
Znyx ZX314         QUAD PC0009-05       040AA   T
Znyx ZX314         QUAD SA0014-05       040AA   T
Znyx ZX315         DUAL SA0015 X2       040AA   T B
Znyx ZX342              PC0012 X2       140     T       X       4
Znyx ZX344         QUAD SA0019 X2       140AA           X
Znyx ZX345              SA0025 X1       140AB   T       X       N
Znyx ZX346         QUAD SA0026 X1       140AC   T       X       5,I
Znyx ZX348         DUAL SA0028 X2       140AC   T       X       N

10MB Media Codes:

o T-Twisted Pair (10BASE-T)
o B-BNC (10BASE-2)
o A-AUI (10BASE-5)

100MB Media Codes:

o X-100BASE-TX (Category 5 Unshielded Twisted Pair)

Notes:

o 1-BNC/AUI jumper on board must be set to select between those two media.
o 2-First port is the bottom one (closest to board edge connector).
o 3-STP (Shielded Twisted Pair) medium is not supported.
o 4-Board has separate jacks for 10 Mbytes and 100 Mbytes.
o 5-Cable must be plugged in at power-up time for proper speed selection.
o 6-The DEC chip on this card is a prototype 21041 chip, labeled "proto."
o I-ICS 1890Y PHY chip.
o N-National Semiconductor DP 83840 PHY chip.

Known Problems and Limitations

o The adapters and configurations listed above have been successfully tested
  with the dnet driver. Other adapters may work with the dnet driver, and
  additional boards will be tested in the future.

o The current release of this driver provides 100-Mbps Fast Ethernet support;
  however, the driver will not be able to transfer the data at rates expected
  of a 100-Mbps Fast Ethernet interface. The performance of the driver is under
  study, and a future release of this driver will enhance and address the
  performance characteristics of this driver.

Fujitsu FMV183 Ethernet

Description

The Fujitsu FMV183 is a software-configurable Ethernet controller for the ISA
bus.

Caution! - The FMV183 card is sensitive to autoprobing by other drivers, and
requires autoprobe reset sequences that may disturb other cards. Refer to
"Avoiding Possible Device Conflicts" for more information.

Device Configuration

Preparing for Configuration

Refer to the documentation included with the card.

Avoiding Possible Device Conflicts

o Because the default IRQ, 10, is used by many ISA cards (SMC cards, for
  example), make sure it doesn't conflict with other ISA devices on your
  system.

o FMV183 cards cannot be installed on a system with the Solaris el driver,
  which supports the 3Com EtherLink II (3C503) and EtherLink II/16 (3C503-16),
  or the nei driver, which supports the Novell NE2000, NE2000plus, and clones.

  If you already have the Solaris operating environment running on your system
  and you want to add support for the FMV183 card, do not install the adapter
  until you disable incompatible drivers as described in the next section.

Enabling Support for Controllers After Installing Solaris x86

If you already have the Solaris x86 operating environment running on your
system and you want to add an FMV183 Ethernet card, disable any conflicting
drivers that are already installed on your system *prior* to installing the
FMV183 card but *after* installing the Solaris software.

1.  Become root.

2.  Use a text editor (such as vi) to edit the /etc/system file, and add the
    following line:

    exclude: el
    exclude: nei

3.  In the /etc/system file, remove or use an asterisk (*) to comment out the
    following lines:

    exclude: fmvel
    forceload: drv/el
    forceload: drv/nei

4.  Save your changes and exit the editor.

5.  Perform a reconfiguration boot to make your changes take effect:

    # touch /reconfigure
    # init 0

6.  Shut down the system and turn it off.

7.  Install the FMV183 card and configure it according to "Configuring the
    Device."

8.  Turn the system on and allow it to reboot.

Note - Upon reboot, the incompatible Ethernet cards listed in this device page
will no longer be recognized by the Solaris software and cannot be used in the
system with the FMV183.

9.  Perform a normal reboot to bring your network into operation:

    # reboot

Configuring the Device

Refer to "Valid Configurations" below and then use the vendor's
FJN0ISET.EXE DOS utility to set the card configuration.

1.  DISABLE plug and play.
2.  Set the IRQ.
3.  Set the I/O address.

Valid Configurations

The following are the valid configurations for the FMV183:

o IRQ           3, 7, 10, 15

o I/O Address   0x220, 0x240, 0x260, 0x280, 0x2a0, 0x2c0, 0x300,
                0x340

Known Problems and Limitations

The fmvel driver does not support netbooting. Instead, use a CD to install
Solaris, as described in "Installing Solaris Using the Driver Update Diskettes"
in Chapter 1.

Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP

Description

The Intel EtherExpress 16, 16C, 16TP, MCA, and MCA TP cards are Ethernet
network adapters.

Device Configuration

Preparing for Configuration

Use Intel's DOS configuration utility, Softset (supplied on a diskette with
EtherExpress 16 adapters), to configure the connector manually.

Avoiding Possible Device Conflicts

Each type of Intel EtherExpress 16 conflicts with the SMC 8013 card. If the SMC
8013 card and an Intel EtherExpress 16 are both installed in your system, data
to and from the IEE 16 card will be randomly corrupted.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if your Intel
    EtherExpress 16 controller needs to be reconfigured.

2.  Follow the Intel documentation and use the Softset setup software to
    configure the card.

Alternative Custom Configuration

The Micro Channel versions of this adapter (Intel EtherExpress MCA and Intel
EtherExpress MCA TP) can be configured to use IRQs 12 and 15, but these
IRQs are not supported by the Solaris iee driver. Run the Softset configuration
utility in manual mode to make certain a valid IRQ is selected.

Known Problems and Limitations

Interrupt sharing is not supported.

Intel EtherExpress Flash32 (82596)

Description

The Intel EtherExpress Flash32 is an Ethernet network controller that supports
the Unisys family of on-motherboard and add-on Ethernet implementations.

Device Configuration

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if your Intel
    EtherExpress Flash32 controller needs to be reconfigured.

2.  If necessary, reconfigure using the software setup program provided by
    Intel.

3.  Using the EISA configuration utility, set this parameter:

Disable Flash Memory

Known Problems and Limitations

The ieef card may "hard-hang" under heavy load. This has been observed on
EISA cards at 10 Mbps and 100 Mbps and on PCI cards at 100 Mbps. This is a
hardware problem and cannot be fixed in software. The only way to recover
from this is to reboot the machine.

Intel EtherExpress PRO/100 (82556)

Description

The Intel EtherExpress PRO/100 is an Ethernet controller. Both the EISA and
PCI bus controllers are supported.

Device Configuration

Preparing for Configuration (PCI Only)

On some PCI systems, the user has control over assignments of IRQs to ISA
and PCI devices. In the chipset configuration of your particular system, verify
that an IRQ is enabled for use by the PCI bus. For example, your PCI CMOS
setup screen may show the following:

IRQ 9     Enabled for ISA card
IRQ 10    Enabled for ISA card
IRQ 14    Enabled for PCI card
IRQ 15    Enabled for PCI card

Use this opportunity to toggle your choices from ISA to PCI, or from PCI to
ISA, depending on your hardware configuration. It is preferable to assign as
many IRQs to PCI devices as possible. By configuring more available IRQs for
PCI devices, you give the PCI bus additional choices to resolve conflicts.

Avoiding Possible Device Conflicts

Avoid using IRQ 9 because it is often used for the video card in some systems.

Configuring the Device

Intel EtherExpress PRO/100 EISA

1.  Consult your Device Configuration Worksheet to see if your Intel
    EtherExpress PRO/100 controller needs to be reconfigured.

2.  Using the EISA configuration utility, set the following parameters:

    a.  Disable Flash Memory.

    b.  If necessary, reconfigure using the software setup program or the
        diagnostic tools provided by Intel.

Intel EtherExpress PRO/100 PCI

1.  Consult your Device Configuration Worksheet to see if your Intel
    EtherExpress PRO/100 controller needs to be reconfigured.

2.  If necessary, reconfigure using the software setup program or the
    diagnostic tools provided by Intel.

Valid Configurations

Intel EtherExpress PRO/100 (EISA only):

o IRQ   3, 5, 7, 9, 10, 11, 12, 14, 15

Known Problems and Limitations

o Under heavy load, on EISA cards (both 10 and 100 Mbps) and PCI cards (10
  Mbps), the board can get into a "hard-hang" state. This is believed to be a
  hardware problem. The only way to recover is to reboot the machine.

o The Intel EtherExpress PRO/100 card cannot net install at 100 Mbps.

o Some revisions of ieef-supported PCI network cards may exhibit an
  intermittent error under heavy stress, where the interface suddenly drops off
  the network (and carrier sense-lights go off on the card). The bug, under
  investigation, appears to be a PCI bus starvation problem. Use ifconfig to
  reinitialize the card. For example, as root, type:

  # ifconfig ieef0 down
  # ifconfig ieef0 unplumb
  # modunload -i 0
  # ifconfig ieef0 plumb
  # ifconfig ieef0 <IP_Address> netmask + broadcast + -trailers up

o The current release of this driver provides 100-Mbps Fast Ethernet support;
  however the driver will not be able to transfer the data at rates expected of
  a 100-Mbps Fast Ethernet interface. The performance of the driver is under
  study and a future release of this driver will enhance and address the
  performance characteristics of this driver.

o The current ieef driver does not support auto-detection of the Ethernet
  speed, so the board's speed has to be explicitly configured. To choose 100
  Mbps, add speed=100 to the appropriate line in /kernel/drv/ieef.conf. Use 10
  instead of 100 for 10 Mbps. The default speed is 10 Mbps.

Novell NE2000, NE2000plus Ethernet and Clones

Description

The Novell NE2000 and NE2000plus are ISA bus Ethernet controllers. The
NE2000plus card is software configurable; the NE2000 card must be manually
configured with dip switches and jumpers.

Caution! - The NE2000/NE2000plus adapters are sensitive to autoprobing by
other drivers, and require autoprobe reset sequences that may disturb other
cards. To avoid conflicts, the NE2000/NE2000plus cards cannot be installed on
a system with the Solaris drivers listed below.
In addition, the Solaris nei driver is disabled by default. You enable it using
a script (nov2000.bat) on the boot diskettes that will disable the other
drivers and enable the nei driver; see "Modifying the Driver Update Boot
Diskettes" below.
If you already have the Solaris operating environment running on your system
and you want to add support for the NE2000 or NE2000plus adapter, do *not*
install the adapter until you disable other drivers; see "Enabling Support for
Controllers After Installing Solaris x86" below.

The following supported hardware cannot be used with NE2000 and
NE2000plus cards.

===============================================================================
Solaris
Driver          Supported Hardware
-------------------------------------------------------------------------------

eepro           Intel EtherExpress PRO

el              3Com EtherLink II (3C503), EtherLink II/16 (3C503-16)

elink           3Com EtherLink 16 (3C507)

fmvel           Fujitsu FMV183

iee             Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP

pcn             AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI)

smc             SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS Elite16,
                EtherCard PLUS (8416, 8216, 8013, 8003)

tiqmouse        Texas Instruments TravelMate 4000E QuickPort Ball Point Mouse
===============================================================================

Device Configuration

Preparing for Configuration

The NE2000/NE2000plus Ethernet cards present special problems for
configuration. Various early versions and some clones of these models may hang
the system when probed. The large I/O space used by the card (0x20 bytes) also
increases the chance of conflicts with other devices. To avoid these problems,
read and follow the advice on the next few pages.

o The Solaris nei driver expects the NE2000/NE2000plus card to be in a 16-bit
  ISA slot. Ensure that the card is in a 16-bit slot and is jumpered for 16-bit
  operations.

o Some NE2000/NE2000plus clones allow you to configure the bus speed; the bus
  speed on the card should match that of the system.

o Certain I/O base addresses (0x320, 0x340, and 0x360) are not supported under
  the Solaris operating environment. These are described in the next section.

Avoiding Possible Device Conflicts

o Due to the large I/O space (0x20 bytes) used by the NE2000/NE2000plus cards,
  the I/O base addresses of 0x320, 0x340, and 0x360 are not supported by
  default because of conflicts with other drivers. This leaves only 0x300 for
  the NE2000, and 0x240, 0x280, 0x2C0, and 0x300 for the NE2000plus.

o Unfortunately, some NE2000 clones will not operate at all combinations of I/O
  base address and IRQ settings, so configuration may be further restricted to
  the default values of IRQ 3 and I/O base address 0x300. Be sure to read the
  configuration information in the manual provided by the manufacturer of the
  card.

Caution! -  *Never* use an IRQ or I/O base address other than the ones listed
under "Valid Configurations," even if they are supported by the
NE2000/NE2000plus card. Due to conflicts with other Solaris drivers, for
example, the I/O base addresses of 0x320, 0x340 and 0x360 are specifically
disallowed in the Solaris nei.conf file.

o For NE2000plus cards *only*: If the card has been configured to run in SHARED
  MEMORY mode, it will use 0x4000 bytes of shared memory in the range
  0xD0000-0xDFFFF. Be sure to check that the BIOS setup allocates this range of
  memory to the adapter and that other cards in the system do not conflict. If
  a conflict is unavoidable, configure the NE2000plus in I/O mode so that it
  will not use shared memory. (To configure the NE2000plus card, a
  vendor-supplied DOS program PLUSDIAG must be used.)

Modifying the Driver Update Boot Diskettes

Because the Novell NE2000/NE2000plus Ethernet adapters are disabled by default,
there are command files on the boot diskettes to enable the nei device
driver. The boot diskettes must be modified using DOS. As a precaution, make a
copy of the original boot diskettes prior to running the special command file.

1.  Boot DOS on your system.

2.  Insert a blank 3.5-inch diskette into drive A: and format it:

    format a:

3.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

4.  Label the copy of the boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette for
    NE2000/NE2000plus adapter."

5.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

6.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

7.  Label the copy of the second boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette for
    NE2000/NE2000plus adapter."

8.  Insert another blank 3.5-inch diskette into drive A: and format it:

    format a:

9.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette" into
    drive A:, make a copy of it, and remove the diskette:

    diskcopy a: a:

10. Label the copy of the second boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette
    for NE2000/NE2000plus adapter."

11. Store your original boot diskettes in a safe place.

12. Insert the copy of "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER
    Diskette" into drive A:.

    Make sure the diskette is writable because the contents will be modified.

13. Change to drive A: (remember DOS is still running):

    a:

14. Run the nov2000.bat command file:

    nov2000

Now the Driver Update boot diskettes are prepared to install the Solaris
software on your system.

Enabling Support for Controllers After Installing Solaris x86

If you already have the Solaris x86 operating environment running on your
system and you want to add an NE2000 or NE2000plus Ethernet card, disable the
conflicting drivers that are already installed on your system *prior* to
installing the NE2000/NE2000plus card but *after* installing the Solaris
software.

1.  Become root.

2.  Use a text editor (such as vi) to edit the /etc/system file, and add the
    following lines:

    exclude: eepro
    exclude: el
    exclude: elink
    exclude: fmvel
    exclude: iee
    exclude: pcn
    exclude: smc
    exclude: tiqmouse
    forceload: drv/nei

3.  In the /etc/system file, remove or use an asterisk (*) to comment out the
    following lines:

    exclude: nei
    forceload: drv/eepro
    forceload: drv/el
    forceload: drv/elink
    forceload: drv/fmvel
    forceload: drv/iee
    forceload: drv/pcn
    forceload: drv/smc

4.  Add or uncomment the following line:

    set nei:nei_forceload=1

5.  Save your changes and exit the editor.

6.  Now perform a reconfiguration boot to make your changes take effect:

    # touch /reconfigure
    # init 0

7.  Shut down the system and turn it off.

8.  Install the NE2000 or NE2000plus card and configure it according to the
    information "Valid Configurations."

9.  Turn the system on and allow it to reboot.

Note - Upon reboot, the Ethernet cards listed on this device page will no
longer be recognized by the Solaris software and cannot be used in the system
with the NE2000/NE2000plus.

10. If the newly installed NE2000/NE2000plus Ethernet card is replacing another
    network card that uses a different network driver, you need to rename the
    /etc/hostname.olddriver0 file to /etc/hostname.newdriver0 before rebooting
    a second time.

    For example, if you have replaced a 3Com EtherLink III card with a NE2000
    or NE2000 plus card, you need to run the following command as root:

    #  mv /etc/hostname.elx0 /etc/hostname.nei0

11. Perform a normal reboot to bring your network into operation:

    # reboot

Configuring the Device

The NE2000 card is configured using dip switches. These must be set prior to
installing the card. The NE2000plus card is configured using the vendor-
supplied DOS program PLUSDIAG. To use it, the NE2000plus card must first
be installed in your system.

1.  Set the IRQ to one of the interrupts listed under "Valid Configurations."

2.  Set the I/O base address to one of the values listed under "Valid
    Configurations."

3.  Set the bus speed and bus width to match that of the system.

4.  For NE2000plus cards *only*: The SHARED MEMORY address should be set
    starting from 0xD0000, increasing by 0x4000 for each additional card.

5.  See "Known Problems and Limitations" for other potential problems.

Valid Configurations

Note that some NE2000 clones may further restrict these choices.

NE2000:

o IRQ                   2, 3, 4, 5

o I/O Base Address      0x300

NE2000plus:

o IRQ                   2, 3, 4, 5, 10, 11, 12, 15

o I/O Base Address      0x300, 0x240, 0x280, 0x2C0

o Shared Memory         0xD0000-0xDC000

Known Problems and Limitations

o If data corruption errors occur while an NE2000/NE2000plus card is installed,
  check the bus speed that is set on the card. (This is a configurable option
  on some clone cards.) Some cards may not run reliably at 16 MHz, and must be
  configured to run at 8 MHz.

o Some NE2000/NE2000plus clones may misidentify slot width, or may not work
  with all mode or jumper settings. For example, some NE2000plus clones may
  only work in both data modes (I/O and shared memory), depending on the system
  configuration.

  Workaround: Try a different bus slot, if the card misdetects a 16-bit slot
  for an 8-bit slot. For NE2000plus clones, try both data modes by either
  setting the jumpers or using the DOS configuration program.

o If the NE2000 card is not recognized by the Solaris operating environment,
  it's possible the clone does not sufficiently resemble the NE2000 hardware;
  improper configuration setup may also cause this failure.

o If the system is hanging or the NE2000 card is not recognized by the Solaris
  software, it may be necessary to reset the bus speed or I/O recovery time
  (which may be settable in the system BIOS). General bus noise may also affect
  the behavior of certain NE2000 clones; try swapping devices into different
  slots until the card begins to function satisfactorily.

o If the system hangs after booting with a NE2000/NE2000plus card installed,
  but it doesn't hang if you remove the card, check the following:

  o The NE2000/NE2000plus card has not been jumpered for 16-bit operation, or
    has not been placed in a 16-bit slot. Some cards misdetect slot type. See
    "Preparing for Configuration."

  o The NE2000/NE2000plus clone is too poorly implemented to be recognizable.
    Replace the card.

  o The NE2000/NE2000plus card has not been configured properly. See
    "Avoiding Possible Device Conflicts" and "Configuring the Device."

SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS Elite16,
EtherCard PLUS (8416, 8216, 8013, 8003)

Description

The SMC 8416, 8216, and 80x3 family of cards are Ethernet adapters for ISA
and Micro Channel bus architectures.

Device Configuration

Preparing for Configuration

Since memory is shared, you must disable the motherboard cache in the region
where the Ethernet shared memory is mapped.

Avoiding Possible Device Conflicts

o The SMC EtherCard Elite16 Ultra cards (8216xxx) should be installed in a
  16-bit slot. Data corruption may occur if an 8-bit slot is used.

o AST systems that have DPT boards with the AST BIOS installed are known to
  conflict with SMC cards set to I/O port 0x300. For these system
  configurations, set the SMC card to a valid setup that does not use I/O port
  0x300.

o Wyse Decision systems are known to conflict with SMC cards set to I/O port
  0x300. For these system configurations, set the SMC card to a valid setup
  that does not use I/O port 0x300.

o The EtherCard PLUS (8003) board has a limited amount of on-board memory,
  which causes very poor NFS(TM) system performance. To avoid this problem, NFS
  system mounts over the 8003 interface must use a 4-Kbyte read/write buffer
  size. See the mount_nfs(1M) manual page for more details on configuring
  NFS. This problem can also impact installation of Solaris x86 over the
  network, causing occasional NFS complaints (which can be ignored).

  Since Solaris SPARC(TM) systems have 8-Kbyte defaults, SPARC NFS file servers
  will interact poorly with 8003 adapters until the buffer sizes are reduced.

Configuring the Device

Software Procedure

1.  Consult your Device Configuration Worksheet to see if your SMC network
    adapter needs to be reconfigured.

2.  If necessary, reconfigure using the software setup program provided by SMC.

Note - Some versions of SMC's EZSTART utility can restrict the system media
types to 10Base-T or AUI connection even if BNC connection is actually being
used. Disable "Automatic Media Detection," and select the Custom and Setup
options to set the Network Interface explicitly to BNC or another connector
type.

Software Procedure for the SMC EtherEZ (8416)

Use the following steps in addition to the previous software procedure steps:

Note - The SMC EISA configuration utilities don't properly configure the SMC
EtherEZ (8416). Instead, use the EZSETUP program as explained below.

1.  Install the EZSETUP program with SMC's EZSTART program.

    Choose the Custom Install button and install the EZSETUP program which is
    listed under Miscellaneous Utilities.

2.  Run the EZSETUP program with the disable Plug and Play option:

    C:> ezsetup -nopnp

3.  Run EZSETUP with no options.

4.  Answer the configuration questions, being sure to disable automatic cable
    type detection and Plug and Play.

Hardware Procedure

1.  Consult your Device Configuration Worksheet to verify that your SMC network
    adapter does not need to be configured.

2.  If you must set jumpers, refer to the SMC documentation.

Valid Configurations

SMC EtherCard Elite16 Ultra (8216xxx) and SMC EtherEZ (8416xxx) network
adapters use software procedures to configure:

Shared Memory Address            Between 0xC0000 and 0xDE000

The information in the following table is only used for EtherCard PLUS
(WD/SMC 8003xxx) cards that use jumpers to set the configuration:

==============================================================================
IRQ      I/O Address    Base Memory Address (Board RAM)
------------------------------------------------------------------------------
3        0x280          0xD0000

5        0x2A0          0xD4000

5        0x300          0xD4000
==============================================================================


SMC Ether 10/100 (9232)

Description

The SMC Ether 10/100 (9232) board is an EISA-based Ethernet controller
supporting both 10Base-T and 100Base-TX networks. Although the hardware
supports a DMA mode of operation, the Solaris drivers do not make use of it.

The SMC Ether 10/100 board is supported by the Solaris smcf driver.

Device Configuration

Preparing for Configuration

o The board is software configured using the EISA configuration utility along
  with the file supplied by SMC. There are no jumpers on the board.

o The board can be configured for either 10 Mbps or 100 Mbps. Operation at the
  higher speed using the RJ-45 connector requires use of a Category 5 UTP
  (Unshielded Twisted Pair) cable.

o The EISA configuration utility also allows setting of the IRQ and DMA
  channels. The Solaris drivers do not make use of the DMA capabilities of the
  board, and do not require the selection of any particular DMA channel. The
  optional ROM is not used by the Solaris drivers and should be disabled.

Configuring the Device

Use the EISA configuration utility to select the desired network speed and IRQ.
Set the ROM base address and DMA channel to Disabled.

Valid Configurations

The following configuratiions are valid for the SMC Ether 10/100:

o Speed         10 Mbps or 100 Mbps
o IRQ           3, 5, 7, 9, 10, 11, 15
o DMA Channel   Disabled
o ROM Address   Disabled

The SMC Ether 10/100 I/O address is determined by slot number. The DMA
channel and ROM are not used.

FDDI Network Adapters

Rockwell Network Systems (RNS) 2200 Series FDDI PCI Adapters

Description

The RNS 2200 is a low-cost FDDI adapter for the PCI bus. It supports extended
FDDI address detection and matching, and provides host-programmable
control of an external optical bypass relay (OBR) for dual-attached station
configurations. There are no jumpers or other user-configurable devices.

Device Configuration

To install the 2200 adapter, refer to 2200 User's Guide, and also to the
installation instructions provided with your specific 2200 driver.

Supported physical network configurations are:

o Fiber dual-attached station (DAS) connecting to a dual-ring FDDI network;
  each ring connection requires one optical transceiver

o Fiber single-attached station (SAS) connecting to a single-ring FDDI network

o Unshielded twisted pair (UTP) SAS

The following 2200 adapter models are available:

===============================================================================
Model     Workstation  Connector  Media
-------------------------------------------------------------------------------
2200-FD   DAS          SC         Fiber optic; optional optical bypass relay
2200-FSS  SAS          SC         Fiber optic
2200-FSM  SAS          MIC        Fiber optic
2200-CS   SAS          RJ-45      Category 5 copper UTP
2200-CD   DAS          RJ-45      Category 5 copper UTP
===============================================================================

Known Problems and Limitations

o No more than four 2200 adapters are supported per system.
o 2200 adapter diagnostics only run in DOS.

Token Ring Network Adapters

IBM 16/4, Auto16/4 Token Ring and Compatible Adapters

Description

These adapters have ISA, EISA, and Micro Channel bus versions.

Device Configuration

Preparing for Configuration

For ISA, EISA, and Micro Channel architectures, the shared RAM size should
be set to 16 Kbytes (as described in the manufacturer's documentation).

Avoiding Possible Device Conflicts

o Although the shared RAM size is set to 16 Kbytes, the Token Ring board will
  actually use 24 Kbytes. You must keep this in mind when determining address
  space conflicts with other boards in the system.

o If you set the ROM location to 0xC2000, the Token Ring board will use 24
  Kbytes starting at that location, so it will use all addresses in the range
  0xC2000 through 0xC7FFF.

Configuring the Device

1.  Consult your Device Configuration Worksheet to see if your Token Ring
    adapter needs to be reconfigured.

2.  Follow the manufacturer documentation and use the manufacturer setup
    software to configure the card.

    o Auto 16/4 Token Ring adapter in ISA systems only: Run the LANAID Program
      that comes with the adapters.

    o Auto 16/4 Token Ring adapter in MCA systems only: Install the
      configuration files from the adapter reference diskette, following the
      adapter's instructions.

    Use the "Standard Install Option" if you need to configure the following:

    o  More than one Auto 16/4 ISA adapter
    o  An Auto 16/4 ISA adapter for another computer to use
    o  The "Autosense" parameter setting

3.  Set up the Token Ring so that:

    o  The first station has autosense DISABLED
    o  All other stations can have autosense enabled

4.  Use different IRQs for each adapter when multiple Auto 16/4 ISA adapters
    are installed.

5.  When the "Ring speed listening" feature is tested, make sure the
    "Autosense" parameter is turned on.

Valid Configurations

For IBM 16/4 Token Ring and compatible adapters, the ROM location address
(ISA and EISA) must be set to one of these values.

===================================
ROM Location Address (ISA and EISA)
-----------------------------------
0xC2000
0xC6000
0xCA000
0xCE000
0xD2000
0xD6000
0xDA000
===================================

For 16/4 Token Ring adapters (Micro Channel)
and Auto 16/4 Token Ring adapters (ISA/Micro Channel):

o IRQ   2, 3, 10, 11

For 16/4 Token Ring adapters (ISA):

o IRQ   3, 6, 7

o I/O Address   Use any address in the pull-down menu. If there
                are multiple adapters installed, ensure addresses
                are not overlapped.

Known Problems and Limitations

o The ISA version of the IBM Token Ring and compatible adapters will not work
  in a system that contains a Creative Labs Sound Blaster card that is
  configured at the default I/O port address 0x220. If possible, move the Sound
  Blaster card to port address 0x240; otherwise you must remove the Sound
  Blaster device from the system.

o Two Token Ring adapters will not run in the same system.

Madge Smart 16/4 Token Ring

Description

The mtok driver supports the following devices:

o Smart 16/4 AT Ringnode/Bridgenode
o Smart 16/4 AT Plus Ringnode
o Smart 16/4 ISA Client Ringnode
o Smart 16/4 ISA Client Plus Ringnode
o Smart 16/4 EISA Ringnode/Bridgenode
o Smart 16/4 MC Ringnode/Bridgenode
o Smart 16/4 MC32 Ringnode/Bridgenode
o Smart 16/4 PCI Ringnode/Bridgenode

Some of the devices may have limitations as noted in this Device Reference
Page.

Direct Support Provided by Madge Networks Ltd.

Madge Networks Ltd. provides direct support for their Solaris device drivers.
See the documentation accompanying your Madge Ringnode/Bridgenode for
details on how to contact Madge for technical support.

Device Configuration

Preparing for Configuration

The Madge mtok driver is disabled by default to avoid possible device
conflicts with other devices. To use the mtok driver, you'll need to enable it
and disable the tr driver (IBM 16/4, Auto16/4 Token Ring and compatible
adapters). Use one of the following methods:

Note - It is possible to use the mtok and tr drivers together by commenting
out any entries having a reg property of 0xA20.

o If you are using a Driver Update to install Solaris on a system with a Madge
  Smart 16/4 controller, modify the Driver Update boot diskettes before
  installation and run the madge.bat script. See "Modifying the Driver Update
  Boot Diskettes."

o If you are adding a Madge Smart 16/4 controller to a system that has Solaris
  and a Driver Update installed, see "Enabling Support for Controllers After
  Installing Solaris x86."

Avoiding Possible Device Conflicts

The Adaptec AHA-154x (aha) driver expects to use DMA channel 5, which the
mtok TRCFG.EXE program also assumes the Madge Smart 16/4 adapter will
use. To avoid a conflict while using these adapters, place the Madge Ringnode
into the system first, and configure it to use another unused DMA channel.
Then install the Adaptec AHA-154x adapter.

Modifying the Driver Update Boot Diskettes

You must modify the Driver Update boot diskettes using DOS if you plan to
use a Driver Update to install Solaris on a system that includes a Madge Smart
16/4 controller. As a precaution, make a copy of the original boot diskettes
prior to running the special command file.

1.  Boot DOS on your system.

2.  Insert a blank 3.5-inch diskette into drive A: and format it:

    c:> format a:

3.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    c:> diskcopy a: a:

4.  Label the copy of the boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 1 Diskette for Madge
    Smart 16/4 adapters."

5.  Insert another blank 3.5-inch diskette into drive A: and format it:

    c:> format a:

6.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette" into drive
    A:, make a copy of it, and remove the diskette:

    c:> diskcopy a: a:

7.  Label the copy of the second boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 BOOT 2 Diskette for Madge
    Smart 16/4 adapters."

8.  Insert another blank 3.5-inch diskette into drive A: and format it:

    c:> format a:

9.  Insert "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette" into
    drive A:, make a copy of it, and remove the diskette:

    c:> diskcopy a: a:

10. Label the copy of the second boot diskette as "Modified."

    For example:
    "Modified Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER Diskette
    for Madge Smart 16/4 adapters."

11. Store your original boot diskettes in a safe place.

12. Insert the copy of "Solaris 2.5/2.5.1 x86 Driver Update 5 SOLARIS DRIVER
    Diskette" into drive A:.

    Make sure the diskette is writable because the contents will be modified.

13. Change to drive A: (remember DOS is still running):

    a:

14. Run the madge.bat command file:

    a: madge

Now the Driver Update boot diskettes are prepared to install the Solaris
software on your system.

Enabling Support for Controllers After Installing Solaris x86

If you already have the Solaris x86 operating environment and a Driver Update
running on your system and you want to add a Madge Smart 16/4 card:

1.  Become root.

2.  Use a text editor (such as vi) to edit the /etc/system file, and add the
    following lines:

    exclude: tr
    set mtok:mtok_forceload = 1

3.  In the /etc/system file, remove or use an asterisk (*) to comment out the
    following line:

    exclude: mtok

4.  Save your changes and exit the editor.

5.  Now perform a reconfiguration boot to make your changes take effect:

    # touch /reconfigure
    # init 0

6.  Shut down the system and turn it off.

7.  Install the Madge Smart 16/4 card and configure it according to the
    information in "Configuring the Device."

8.  Turn the system on and reboot it.

9.  If the newly installed Madge Smart 16/4 card is replacing another network
    card that uses a different network driver, you need to rename the
    /etc/hostname.olddriver0 file to /etc/hostname.newdriver0 before rebooting
    a second time.

    For example, if you have replaced a 3Com EtherLink III card with a Madge
    Smart 16/4 card, you need to run the following command as root:

    # mv /etc/hostname.elx0 /etc/hostname.mtok0

10. Perform a normal reboot to bring your network into operation:

    # reboot

Configuring the Device

Various hardware settings on the adapter, such as the ring speed and DMA
channel, can be set with switches on the adapter or using a configuration
utility supplied on the MDGBOOT diskette shipped with your Ringnode. Refer
to the documentation supplied with the Ringnode for detailed instructions.

When choosing hardware settings:

o Ensure that your Ringnode does not use the same IRQ as other adapters in your
  PC, and for AT Ringnodes, DMA channel, and I/O location.

o Make sure the selected ring speed matches that of the ring you want to
  connect to.

Note that a configuration utility must almost always be used to select features
of the adapter (for example, ring speed). If the adapter isn't functioning
properly, try alternate features, such as PIO instead of DMA, different I/O
addresses, and so on.

Diagnostics

The driver may print out an error message containing two numbers on start-
up. The following are the two most common error codes and their (possible)
causes.

o Type = 0x08 Value = 0x01

  The adapter has failed to open onto the ring. This could be caused by one of
  the following:

  o The lobe cable is not securely attached to the adapter card or cabling
    unit.

  o The ring speed setting on the card does not match the actual ring speed.

  o Insertion onto the ring has been prevented by ring management software.

  o The ring is beaconing.

  o A ring parameter server on the ring has crashed.

o Type = 0x07 Value = 0x10

  The adapter test DMA/PIO transfer has failed. This usually means that the
  adapter is in PIO mode and there is some interrupt clash.

If other errors are encountered, try running the Madge-supplied DOS
diagnostics program to further isolate the problem.

Known Problems and Limitations

The following problems and limitations have been found with the Madge mtok
driver, and may affect operation. Contact Madge for technical support on these
issues, as required.

o When the mtok driver is enabled, the following messages print on the screen
  when the system startup scripts run ifconfig:

  configuring network interfaces: ip_rput: DL_ERROR_ACK for 29
  errno 1, unix0
  ip: joining multicasts failed on mtok0
  will use link layer broadcasts for multicast

  These messages can be ignored.

o Very heavy network stress may result in Madge adapter hangs, or panics.

  Workaround: Restrict network access to one service (such as nfs, rcp, tcp) at
  a time if possible, and keep both the ring and the mtok driver from becoming
  saturated. This is more likely to occur with Micro Channel systems.

o Disconnected adapters may not operate normally, failing to open onto the
  ring, and thus failing to ifconfig properly under Solaris.

  Workaround: Keep any Madge token ring adapters connected to a properly
  configured ring at all times.

o Using the dynamic module loading and unloading features of the Solaris kernel
  with the mtok driver may lead to error messages and possibly
  panics.
 
  Workaround: Do not configure the mtok driver manually; instead, perform a
  reconfiguration boot as needed to reconfigure the device:

  # touch /reconfigure
  # init 0

o The Solaris 2.5/2.5.1 mtok driver does not yet support rplboot. Thus,
  netbooting is not fully supported.

o The Solaris 2.5/2.5.1 mtok driver uses a non-standard PCI framework for
  consistency with the Solaris 2.4 mtok driver, and thus has the potential to
  confuse the 2.5 Solaris kernel.

  Workaround: Though no such problems have been observed, if problems occur, a
  possible workaround is to limit the number of PCI devices in use on a machine
  with Madge 16/4 PCI adapters.

Audio Cards

Analog Devices AD1848 and Compatible Devices

Description

The Analog Devices AD1848 is a DMA-capable Stereo Codec chip that
provides an interface to both ISA and EISA buses for implementation on a
computer motherboard or add-in card. It provides 8- and 16-bit mono and
stereo digitized sound recording and playback over a wide range of sampling
rates, and includes a digital sound processor and mixing capability.

Selected AD1848-based devices are supported by the sbpro device driver.
Some audio devices based on other compatible chips are also supported by
that driver. Refer to "Tested Compatible Devices" below.

Note - Many audio devices in the marketplace have advertising or
documentation stating that they are "compatible" with other audio devices.
However, many of those devices are not 100 percent compatible at the
hardware level, and are not supported by Solaris. Refer to "Tested Compatible
Devices" to see which devices have been tested under Solaris.

Note - Some cards based on the AD1848 or compatible chips also support
more advanced audio features, such as FM synthesis, advanced signal
processing, advanced wave effects, and MIDI capability; however, the sbpro
driver does not currently support these advanced features.

The features and interfaces that are supported by the Solaris sbpro driver are
described in the audio(7) and sbpro(7) manual pages.

Device Configuration

Preparing for Configuration

o Device configuration information is stored in the sbpro.conf file, usually in
  the /platform/i86pc/kernel/drv directory. To use any of the audio devices in
  "Tested Compatible Devices," you must first install Solaris x86, and then
  edit the sbpro.conf file.

o You must know the hardware jumper settings for the I/O address, interrupt
  request (IRQ), and DMA channel of the device, as appropriate.

o If your system or device has non-volatile memory where a configuration
  utility stores the device's I/O address, IRQ, and DMA channel, you must know
  what settings you have chosen for those parameters.

o If your device has no IRQ or DMA jumpers, and has no non-volatile memory for
  storing those parameters, you must choose a suitable IRQ and DMA channel for
  the audio device that do not conflict with other devices.

Note - Many audio devices come with a software utility that allows you to
select the IRQ and DMA settings used by the card. In many cases, this utility
does not really record these parameters in non-volatile memory, but instead
records them in a configuration file used by DOS to set the card's
configuration at each reboot. Such configuration files are not used by Solaris
and do not affect the operation of the card under Solaris.

Avoiding Possible Device Conflicts

o Be sure any I/O address jumper setting on your card does not conflict with
  any other card in your system. If it conflicts, reconfigure the setting.

o The audio device cannot share IRQ settings with any other card installed in
  your system. If the hardware-jumpered or software-configured IRQ setting
  conflicts with any other device, change the IRQ jumper setting for the audio
  device to one listed under "Valid Configurations."

Configuring the Device

Hardware Configuration

1.  Consult your Device Configuration Worksheet to see if your audio device
    needs to be reconfigured.

2.  If the device's I/O address conflicts with another device, change the I/O
    address using the manufacturer's instructions.

3.  If the device's IRQ conflicts with another device, change the IRQ parameter
    using the manufacturer's instructions.

4.  If the device's DMA channel conflicts with another device, change the DMA
    parameter using the manufacturer's instructions.

5.  Record any changes in I/O address, DMA channel, or IRQ setting on your
    Device Configuration Worksheet.

Enabling Support for the Audio Device

1.  Install Solaris x86.

2.  Become root.

3.  Update the sbpro.conf file:

    a.  Change directories to the location of the kernel configuration files:

        # cd /platform/i86pc/kernel/drv

    b.  Edit the sbpro.conf kernel configuration file.

        This is an ASCII file that can be edited using any text editor, such as
        vi. Find the commented entries corresponding to device type
        MWSS_AD184x. Uncomment the entry that corresponds to the I/O address of
        your audio device, and modify the interrupts and dma-channels
        properties to reflect the settings of your device. The I/O address can
        be found in the reg property. Use the device-specific procedures later
        in this Device Reference Page to determine what values are appropriate
        for each device.

    c.  Save your changes and exit the editor.

4.  Remove the boot diskette from the drive if you have not already done so.

5.  Perform a reconfiguration boot to make your changes take effect:

    # touch /reconfigure
    # reboot

Tested Compatible Devices

The following AD1848 and compatible devices have been tested:

o Compaq DeskPro XL Business Audio with built-in AD1847 chip
o Turtle Beach Tropez card with CS4231 chip

Some other 100 percent hardware-compatible devices may also function using
the sbpro driver; however, they have not been tested or certified with Solaris.

Valid Configurations

The possible settings for the supported devices are listed here. Defaults are
_underlined_.

Note - The sbpro support for the AD1848 and compatibles uses one DMA
channel for both play and record; simultaneous play/record is not supported
in this driver. sbpro.conf file entries for the devices listed below should
specify only one DMA channel.

Compaq DeskPro XL Business Audio With Built-in AD1847 Chip

o I/O Address   _0x530_, 0x604, 0xE80, 0xF40
o IRQ           7, 9, 10, 11
o DMA Channel   0, 1, 3
o Type          MWSS_AD184x

o There are no default values for the IRQ and DMA channel; they must be
  specified in the sbpro.conf file.

o The I/O address is set using the Compaq DeskPro XL EISA configuration utility
  (ECU). That utility also allows you to specify the DMA channel, but whatever
  you specify there is overridden by the value you specify in the sbpro.conf
  file entry. The DMA channel you choose should nonetheless be specified to the
  ECU, for help in avoiding DMA channel device conflicts.

This is an example sbpro.conf entry for a Compaq DeskPro XL Business
Audio device configured to I/O address 0xE80, IRQ 9, DMA channel 3:

name="sbpro" class="sysbus" type="MWSS_AD184x"
    reg=-1,27,0,1,0xe80,8 interrupts=5,9 dma-channels=3;

Turtle Beach Tropez Card With CS4231 Chip

o I/O Address   0x530
o IRQ           7, 9, 10, 11
o DMA Channel   0, 1, 3
o Type          MWSS_AD184x

o There are no default values for the IRQ and DMA channel; they must be
  specified in the sbpro.conf file.

o The MWSS I/O address on the Tropez card is always 0x530 at power-up. It can
  only be changed by software after the system is booted, and Solaris does not
  do that. Therefore, the Tropez card is only supported at I/O address 0x530.

o The Tropez card comes with a software utility for selecting the IRQ, DMA, and
  MWSS compatibility I/O address settings used by the card. However, that
  utility does not record those parameters in non-volatile memory, but in a
  configuration file used by DOS to set the card's configuration at each
  reboot. Such configuration files are not used by Solaris and do not affect
  the operation of the card under Solaris. The I/O address used by Solaris is
  always 0x530, and the IRQ and DMA channel are selected based on the entries
  in the sbpro.conf file.

This is an example sbpro.conf entry for a Turtle Beach Tropez card
configured to IRQ 10, DMA channel 1:

name="sbpro" class="sysbus" type="MWSS_AD184x"
    reg=-1,25,0,1,0x530,8 interrupts=5,10 dma-channels=1;

Known Problems and Limitations

o Output volume is controlled by software. Be sure any audio volume thumbwheel
  on your system is turned to the maximum volume setting; otherwise you may not
  hear any sound.

o Consult your manufacturer's documentation to determine if the microphone jack
  for your device is a mono jack or a stereo jack. Be sure your microphone plug
  matches; if it doesn't, use a suitable adapter.

o "Line-in" and "aux" jacks typically require "line level" voltages, such as
  output from a tape or CD player "line-out" jack, or from a powered (battery-
  operated) microphone. "Mic" jacks typically require lower voltages. Consult
  your manufacturer's documentation for the exact requirements of your device.

o Any Crystal Semiconductor CS4231-based devices supported by this driver are
  programmed in AD1848-compatibility mode. This driver does not include special
  support for the more advanced CS4231 features.

o Simultaneous play and record is not supported by the sbpro driver.

o Some devices are able to detect that the IRQ you specified is "in use" by
  another device in the system. If this condition is detected, the driver
  prints an error message like:

  sbpro: MWSS_AD184x IRQ 7 is 'in use.'

  If that happens, you must change the IRQ setting of either the audio device
  or the conflicting device. Some devices are not able to detect such a
  conflict; in that case the driver will go ahead and try to use the card, but
  that will likely result in the system hanging when the card is first
  used. Thus, it is important to choose an IRQ that does not conflict with
  other devices.

o The sbpro driver supports A-law encoding on AD1848 and compatible
  devices. However, audiotool(1) does not recognize that support and produces
  an error message if you attempt to select A-law encoding.

  Workaround: Use audioplay(1) to play A-law encoded audio files, or use
  audioconvert(1) to convert the A-law sample into a format that audiotool will
  accept, such as 16-bit linear. User-written applications can select A-law
  format using the sbpro driver on AD1848 and compatible devices.

Compaq DeskPro XL Business Audio With Built-in AD184x Chip

o Some system units have the headphone jack wired with its Left and Right
  channels reversed, so you hear Left output in your right ear and vice versa.
  The line-out jack at the back of the system unit does not have this problem.

o Some system units have the audio input jack on the back of the system unit
  wired to the "Internal" input port, while some are wired to "Line In." If you
  use the audio input jack on the back of your system unit, you can determine
  which input port to select by plugging in an active sound source to the jack
  and then using the audiocontrol(1) program's record panel to alternately
  select "Line In" and "Internal" audio input ports and noticing which one
  results in audible sound. Be sure the "Record Volume" and "Monitor Volume"
  sliders are turned up high enough that you can hear the output. If the
  "Internal" button does not appear on the audiocontrol record panel, use the
  "Line In" selection when using the audio input jack on the back of the system
  unit. The microphone jack on the keyboard is always selected using the
  "Microphone" button on audiocontrol.

o The quality of sound is likely to be better when using an external microphone
  and speakers, not the ones built into the keyboard.

Creative Labs Sound Blaster Pro

Description

The Creative Labs Sound Blaster Pro audio cards are DMA-capable ISA bus
plug-in cards. They provide 8-bit mono and stereo digitized sound recording
and playback over a wide range of sampling rates. Each card also includes a
digital sound processor and mixing capability.

Sound Blaster Pro cards are supported by the sbpro device driver. Some audio
devices designated as "Sound Blaster Compatible" are also supported by that
driver. Refer to "Tested Compatible Devices" below.

Note - Many audio devices in the marketplace have advertising or
documentation stating that they are "Sound Blaster Compatible." However,
many of those devices are not 100 percent compatible at the hardware level,
and are not supported by Solaris. Refer to "Tested Compatible Devices" below
to see which "Sound Blaster Compatible" devices have been tested under
Solaris.

The features and interfaces that are supported by the Solaris sbpro device
driver are described in the audio(7) and sbpro(7) manual pages.

Device Configuration

Preparing for Configuration

o Device configuration information is stored in the sbpro.conf file, usually in
  the /platform/i86pc/kernel/drv directory. The sbpro.conf file supports Sound
  Blaster Pro cards with factory default DMA settings.

o If you have a Sound Blaster Pro card with a nonstandard DMA setting, you must
  first install Solaris x86, and then edit the sbpro.conf file.

o You must know the hardware jumper settings for the I/O address, interrupt
  request (IRQ), and DMA channel.

Avoiding Possible Device Conflicts

o If the the I/O address jumper setting on your Sound Blaster card conflicts
  with another card in your system, reconfigure the setting.

o The Sound Blaster Pro card cannot share IRQ settings with any other card
  installed in your system. If the hardware-jumpered IRQ setting conflicts with
  any other device, change the IRQ jumper setting on the Sound Blaster card to
  one listed under "Valid Configurations." The most common conflicts occur with
  the LPT1 parallel port, a serial port, or network card.

Configuring the Device

Hardware Configuration

1.  Consult your Device Configuration Worksheet to see if your Sound Blaster
    card needs to be reconfigured.

2.  If the card's I/O address conflicts with another device, remove the card
    and change the I/O address using the manufacturer's instructions.

3.  If the card's jumpered IRQ conflicts with another device, change the IRQ
    parameter using the manufacturer's instructions.

4.  If the jumpered DMA channel conflicts with another device, change the DMA
    parameter using the manufacturer's instructions.

5.  Record any changes in I/O address, DMA channel, or IRQ setting of the board
    on your Device Configuration Worksheet.

Enabling Support for Sound Blaster Pro

1.  Install Solaris x86.

2.  Become root.

3.  If you changed the card's DMA channel to a value other than 1, update the
    sbpro.conf file:

    a.  Change directories to the location of the kernel configuration files:

    # cd /platform/i86pc/kernel/drv

    b.  Edit the sbpro.conf kernel configuration file.

        This is an ASCII file that can be edited using any text editor, such as
        vi. Change the dma-channels property for the SBPRO entry whose I/O
        address and IRQ setting match the hardware setting of your card.

    c.  Save your changes and exit the editor.

4.  Remove the boot diskette from the drive if you have not already done so.

5.  Perform a reconfiguration boot to make your changes take effect:

    # touch /reconfigure
    # reboot

Tested Compatible Devices

The sbpro driver supports the ISA Sound Blaster Pro card from Creative Labs.
In addition, the following "compatible" devices have been tested:

o Toshiba Portege 610CT
o Toshiba Satellite Pro with built-in ESS688 chip

Some other 100 percent hardware-compatible devices may also function using
the sbpro driver; however, they have not been tested or certified with Solaris.

Valid Configurations

The possible settings for the Sound Blaster Pro card are listed here. Defaults
are _underlined_.

o I/O Address   _0x220_, 0x240
o IRQ           2, _5_, _7_, 10
o DMA Channel   0, _1_, 3

Known Problems and Limitations

o Output volume is controlled by software. Be sure the volume thumbwheel on the
  back of the card is turned to the maximum volume setting; otherwise you may
  not hear any sound.

o Microphone input is treated as a mono source; however, all the jacks on the
  back of the Sound Blaster card are stereo jacks. If your microphone has a
  mono plug, convert it to stereo using an appropriate adapter.

o The ISA version IBM Token Ring and compatible adapters will not work in a
  system that contains a Sound Blaster card configured at the default I/O port
  address 0x220. If possible, move the Sound Blaster card to port address
  0x240; otherwise, remove the Sound Blaster device from the system.

Creative Labs Sound Blaster 16/Sound Blaster AWE32

Description

The Creative Labs Sound Blaster 16 and Sound Blaster AWE32 audio cards are
DMA-capable ISA bus plug-in cards. They provide 8- and 16-bit mono and
stereo digitized sound recording and playback over a wide range of sampling
rates, and each includes a digital sound processor and mixing capability.

Note - Some of the cards also support more advanced audio features, such as
FM synthesis, advanced signal processing, advanced wave effects, and MIDI
capability; however, the sbpro driver does not currently support these
advanced features. The features and interfaces that are supported by the
Solaris sbpro driver are described in the audio(7) and sbpro(7) manual
pages.

Note - Some Sound Blaster cards support optional non-audio capabilities such
as SCSI interfaces and CD-ROM interfaces. These interfaces are not supported
by the sbpro driver. The Sound Blaster 16 optional SCSI-2 interface is
supported by the Solaris aic driver. See the "Adaptec AIC-6360/
AHA-1522A/AHA-1520A/AHA-1510A/AHA-1530P/1532P HBAs/Sound
Blaster 16 SCSI-2 (SCSI)" Device Reference Page for configuration information
for the SCSI controller on this card.

Device Configuration

Preparing for Configuration

o If you have a Sound Blaster 16 card with IRQ and DMA jumpers, the jumper
  settings on the card will determine the IRQ and DMA channels to be
  used. However, if you have a Sound Blaster 16 card without audio IRQ and DMA
  jumpers or a Sound Blaster AWE32 card, you must first install Solaris x86,
  and then edit the sbpro.conf file. To do this, you must know the I/O address
  jumper setting of the card and what IRQ and DMA channels you plan to use.

o The audio subsystem of the Sound Blaster 16 needs its own I/O (port) address
  and an IRQ, distinct from those of the optional SCSI subsystem.

Avoiding Possible Device Conflicts

o Be sure the I/O address jumper setting on your Sound Blaster card does not
  conflict with any other card in your system; if it does, reconfigure the
  jumper setting.

o If your Sound Blaster card has both an audio and a SCSI-2 interface, select
  an I/O address for each interface to prevent conflicts with other configured
  devices.

o The Sound Blaster card cannot share IRQ settings with any other card
  installed in your system. The most common conflicts occur with the LPT1
  parallel port, a serial port, or network card.

  o If a hardware-jumpered IRQ setting conflicts with any other device, change
    the IRQ jumper setting on the Sound Blaster card to one listed under "Valid
    Configurations."

  o If your Sound Blaster card does not have an audio IRQ jumper, the IRQ used
    is determined by the entry you edit in the sbpro.conf file. In this case,
    choose an IRQ that does not conflict with any other device in the system.

Configuring the Device

Hardware Configuration

Note - Make sure you set the jumpers for the audio interface and not for the
SCSI, if your Sound Blaster card has both an audio and a SCSI-2 interface.

1.  Consult your Device Configuration Worksheet to see if your Sound Blaster
    card needs to be reconfigured.

2.  If the card's I/O address conflicts with another device, remove the card
    and change the I/O address according to the manufacturer's instructions.

Note - If you have a Sound Blaster 16 card without audio IRQ and DMA
jumpers or you have a Sound Blaster AWE32 card, you must specify the
dma-channels property in the sbpro.conf file after Solaris is installed. See
"Enabling Support for Sound Blaster 16 and AWE32."

3.  If you have a Sound Blaster 16 SCSI-2 and you intend to use the SCSI
    interface, you may have to set the jumpers that control the SCSI I/O
    address.

    See the "Adaptec AIC-6360/Sound Blaster 16 SCSI-2 (SCSI)" Device Reference
    Page for information on setting the Sound Blaster 16 SCSI-2 card.

4.  Record any changes on your Device Configuration Worksheet.

Enabling Support for Sound Blaster 16 and AWE32

1.  Install Solaris x86.

2.  Become root.

Note - If your Sound Blaster 16 card has audio DMA jumpers, the driver uses
the DMA channels specified by those jumper settings, and you should not
specify the dma-channels property in the sbpro.conf file. Instead go to
step 4.

3.  If you have a Sound Blaster AWE32, or a Sound Blaster 16 card that has no
    audio IRQ and DMA jumpers, you must change the IRQ setting in the
    sbpro.conf kernel configuration file. Follow these steps:

    a.  Change directories to the location of the kernel configuration file:

        # cd /platform/i86pc/kernel/drv

    b.  Edit the sbpro.conf kernel configuration file.

        This file is in ASCII text that can be edited using any text editor,
        such as vi. The sbpro.conf file that is installed with Solaris contains
        detailed instructions and examples. Be sure that the specified IRQ and
        DMA settings do not conflict with other devices on the system.

    c.  Find the SB16 entry that corresponds to your card's jumpered I/O
        address, and that contains the "interrupts" value that corresponds to
        the IRQ you want to use.

    d.  Specify two DMA channels in the dma-channels property.

        The first is for an 8-bit DMA channel, the second for a 16-bit DMA
        channel.

    e.  Save your changes and exit the editor.

4.  Remove the diskette from the drive if you have not already done so.

5.  Reboot the system as shown here:

    # touch /reconfigure
    # reboot

Valid Configurations

The settings for the Sound Blaster cards are listed with the defaults
_underlined_.

Sound Blaster                   16/Sound Blaster AWE32:

o I/O address                   _0x220_, 0x240, 0x260, 0x280
o IRQ                           2, _5_, 7, 10
o 8-bit DMA channel             0, _1_, 3
o 16-bit DMA channel            _5_, 6, 7

Sound Blaster 16 SCSI-2:

o I/O address                   0x140, _0x340_
o IRQ                           _11_
o DMA channel (not used)        0, 5, 6, 7

Known Problems and Limitations

o Output volume is controlled by software. Be sure the volume thumbwheel on the
  back of the card is turned to the maximum volume setting; otherwise you may
  not hear any sound.

o Microphone input is treated as a mono source; however, all the jacks on the
  back of the Sound Blaster cards are stereo jacks. If your microphone has a
  mono plug, convert it to stereo using an appropriate adapter.

o Sound Blaster 16 and Sound Blaster AWE32 cards are both recognized as Sound
  Blaster 16 cards.

o The Sound Blaster 16 optional SCSI-2 interface cannot be used as the primary
  disk controller because it has no BIOS. The system must be booted from a disk
  attached to another controller.

o The ISA version IBM Token Ring and compatible adapters will not work in a
  system that contains a Sound Blaster card configured at the default I/O port
  address 0x220. If possible, move the Sound Blaster card to port address
  0x240; otherwise, remove the Sound Blaster device from the system.

PC Card Hardware

Modem and Serial PC Card Devices

Description

A wide range of supported modem and serial PC Card devices are based on
the 8250, 16550, or compatible UART at speeds up to 115 Kbps.

Device Configuration

Preparing for Configuration

o If a modem or serial PC Card device is recognized, the pcser device driver is
  automatically loaded, ports and IRQs allocated, and special files created (if
  they do not already exist).

o No manual device configuration is necessary or possible.

Configuring the Device

Initial Installation and Configuration

1.  Install Solaris x86, including the PCMCIA packages in the SUNWpcmc cluster.

2.  Boot the system.

3.  Insert the modem device or the serial device.

Identifying an Unrecognized Device

If you insert a PC Card modem or serial device and it isn't recognized (no
special files created under /dev/cua or /dev/term), use the  prtconf
command to try to find the problem.

1.  Run the prtconf command to see if your modem or serial card is recognized.

    An unrecognized device will appear at the end of the prtconf output. For
    example:

    # prtconf
    .  .  .
    pcmcia, instance #0
       PC,111.222/Data Masher (driver not attached)

2.  If your device is not recognized "(driver not attached)", use the add_drv
    command to add the name of your device as another known alias for pcser
    devices.

    For example, type the following at the command line:

    # add_drv -i '"PC,111.222/Data Masher"' pcser

Note - Include the double quotes in single quotes to keep the shell from
stripping out the double quotes. Use the identification string listed in the
prtconf output. The part of the string after the slash can be treated as a
comment, so use the entire string in the add_drv command. See
add_drv(1M).

Identifying an Incorrectly Recognized Device

1.  Run the prtconf command to see if your modem or serial card is erroneously
    recognized.

    If the device is incorrectly recognized as a memory card, for example, the
    output of the prtconf command could show:

    pcmcia, instance #0
        pcmem, instance #0
            pcram, instance #0

2.  Determine why this is happening and manually update the pcic.conf file.

Additional Configuration

When adding a new serial port or modem to the system, you often need to edit
configuration files so that applications can use the new communications port.
For example, the /etc/uucp/devices file needs to be updated to use UUCP
and PPP. See "UUCP Databases and Programs" in TCP/IP and Data
Communications Administration Guide.

Special Files

The serial devices located in /dev/term and /dev/cua are named by socket
number. A card inserted in socket 0 is pc0, and socket 1 is pc1. See
pcser(7).

Hot-Plugging

If a modem or serial PC Card device is unplugged while it`s in use, the driver
returns errors until the card is replaced in the socket.

The device must be closed and reopened with the card reinserted before the
device begins working again. The restart process depends on the application.
For example, a tip session automatically exits when a card in use is
unplugged. To restart the system, you must restart the tip session.

Known Problems and Limitations

Because manufacturers interpret the PC Card specifications in different ways,
some devices do not work, or work poorly. Consult the latest Solaris x86
Hardware Compatibility List for supported modems.

Copyright 1996 Sun Microsystems Inc., 2550 Garcia Avenue, Mountain View,
Californie 94043-1100, U.S.A. Tous droits rservs.

Ce produit ou document est protg par un copyright et distribu avec des
licences qui en restreignent l'utilisation, la copie, la distribution, et la
dcompilation. Aucune partie de ce produit ou de sa documentation associe ne
peut tre reproduite sous aucune forme, par quelque moyen que ce soit, sans
l'autorisation pralable et crite de Sun et de ses bailleurs de licence, s'il
y en a.

Des parties de ce produit pourront tre drives du systme UNIX(R) licenci
par Novell, Inc. et du systme Berkeley 4.3 BSD licenci par l'Universit de
Californie. UNIX est une marque enregistre aux Etats-Unis et dans d'autres
pays et licencie exclusivement par X/Open Company Ltd. Le logiciel dtenu par
des tiers, et qui comprend la technologie relative aux polices de caractres,
est protg par un copyright et licenci par des fournisseurs de Sun.

Sun, Sun Microsystems, le logo Sun, SunSoft, SunDocs, SunExpress, Solaris,
Solstice DiskSuite, et NFS sont des marques dposes ou enregistres, ou
marques de service de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres
pays. Toutes les marques SPARC, utilises sous licence, sont des marques
dposes ou enregistres de SPARC International, Inc. aux Etats-Unis et dans
d'autres pays. Les produits portant les marques SPARC sont bass sur une
architecture dveloppe par Sun Microsystems, Inc. Dell est une marque
enregistre de Dell Computer Corporation.

Les interfaces d'utilisation graphique OPEN LOOK(R) et Sun(TM) ont t
dveloppes par Sun Microsystems, Inc. pour ses utilisateurs et licencis. Sun
reconnat les efforts de pionniers de Xerox pour la recherche et le
dveloppement du concept des interfaces d'utilisation visuelle ou graphique
pour l'industrie de l'informatique. Sun dtient une licence non exclusive de
Xerox sur l'interface d'utilisation graphique Xerox, cette licence couvrant
aussi les licencis de Sun qui mettent en place l'interface d'utilisation
graphique OPEN LOOK et qui en outre se conforment aux licences crites de Sun.

Le systme X Window est un produit de X Consortium, Inc.

CETTE PUBLICATION EST FOURNIE "EN L'ETAT" SANS GARANTIE D'AUCUNE SORTE, NI
EXPRESSE NI IMPLICITE, Y COMPRIS, ET SANS QUE CETTE LISTE NE SOIT LIMITATIVE,
DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L'APTITUDE DES PRODUITS A
RPONDRE A UNE UTILISATION PARTICULIERE, OU LE FAIT QU'ILS NE SOIENT PAS
CONTREFAISANTS DE PRODUITS DE TIERS.
