Solaris(TM) Base Server 2.4 x86 Driver Update 9 Guide 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. Part No: 802-5789-10 SunSoft, Inc. Revision A, December 1995 A Sun Microsystems, Inc. Business Copyright 1995 Sun Microsystems, Inc. All rights reserved. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. Copyright 1993-1995 X Inside Incorporated. 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 UNIX System Laboratories, Inc., a wholly owned subsidiary of Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun's suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. TRADEMARKS Sun, Sun Microsystems, the Sun logo, SunSoft, the SunSoft logo, Solaris, SunOS, OpenWindows, DeskSet, ONC, ONC+, and NFS are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. OPEN LOOK is a registered trademark of Novell, Inc. PostScript is a trademark of Adobe Systems, Inc. Intel, EtherExpress, and Pentium are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks 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. 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 trademark of 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. THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN. THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAMS(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME. Contents About This Book 1. Solaris Base Server 2.4 x86 Driver Update 9 What's New? New Device Drivers (SCSI HBA, SCSI Tape, Network) PC Card (PCMCIA) Driver Support Driver Update Contents Driver Update Boot Diskette Driver Update Distribution Diskettes Solaris Base Server 2.4 x86 Driver Update 9 Release Notes Modifying the Solaris Base Server Driver Update Boot Diskette MP Support Support for SCSI Tape Driver Support for More Than Four Serial Ports Choosing the Hard Drive Your System Will Boot From After Installation Known Problems Installing Solaris Base Server Using the Driver Update Diskettes Enabling Support for Sound Blaster Audio Cards After Installing Solaris Base Server or the Driver Update Adding New Drivers After Solaris Base Server Is Installed Enabling Support for the Novell NE2000/NE2000plus After Installing the Driver Update Disabling Drivers After Installing the Driver Update Replacing a Network Card 2. Solaris Base Server 2.4 x86 Driver Update PC Card (PCMCIA) Support PC Card Driver Update Contents Understanding PC Card Devices Configuring PC Card Devices Configuring the PC Card Adapter Hot-Plugging PC Card Devices Installing the PC Card Driver Update PC Card Release Notes Using PC Card Memory Cards Troubleshooting PC Card Devices A. Device Reference Pages IDE Interface IDE Disk and CD-ROM Interface SCSI Host Bus Adapters Adaptec AIC-6360/AHA-1522A/AHA-1520A/AHA-1510A/ AHA-1530P/1532P Sound Blaster 16 SCSI-2 (SCSI) Adaptec AIC-7870/AIC-7871/AIC-7872/AHA-2940/AHA-3940 PCI HBAs AMD PCscsi, PCscsi II, PCnet-SCSI PCI HBAs BusLogic SCSI HBAs Compaq SMART SCSI Array Controller DPT PM-2011/PM-2021 ISA HBAs DPT PM-2012B EISA HBA DPT PM-2022/PM-2122/PM-3222 EISA HBAs DPT PM-2024/PM-2124/PM-3224 PCI HBAs IBM DMC960 RAID Micro Channel HBAs (IBM SCSI-2 RAID, IBM SCSI-2 Fast/Wide Streaming-RAID Adapter/A) IBM Micro Channel SCSI-2 Fast/Wide Adapter/A Mylex DAC960P PCI Controller NCR 53C710 (Siemens Nixdorf PCE-5S SCSI) NCR 53C8xx PCI SCSI HBAs (53C810, 53C815, 53C820, 53C825) Trantor T348 MiniSCSI Plus Parallel HBA Tricord Systems Intelligent SCSI Subsystem (ISS) HBA Other SCSI Devices SCSI Tape Drives Network Adapters 3Com EtherLink III (3C5x9, 3C509B) AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI) Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR EISA Controllers DEC 21040/21140 Ethernet (D-Link DE-530CT, SMC EtherPower 8432BT, SMC EtherPower 8432BTA, Znyx312, Cogent EM960TP, Cogent EM100) Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP Intel EtherExpress PRO Intel EtherExpress PRO/100 (82556) Novell NE2000, NE2000plus Ethernet Novell NE3200 EISA Ethernet Racal InterLan ES3210/ES3210 TP EISA Ethernet SMC Elite32 Ultra (8232) SMC Ether100 (9232) SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS Elite16, EtherCard PLUS (8416, 8216, 8013, 8003) Audio Cards Sound Blaster Pro/Sound Blaster 16/Sound Blaster AWE32 PC Card Hardware PC Card Adapters 3Com EtherLink III (3C589) PC Card Modem and Serial PC Card Devices SRAM and DRAM PC Card Devices About This Book This document provides information about x86 hardware devices that are now supported on the Solaris(TM) Base Server 2.4 computing environment. 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, IDE Interface, Network Adapters, PCMCIA 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.4 system with new drivers. Note - Driver Updates are cumulative distributions. Although the "What's New?" section in Chapter 1 describes what's been added since the last Driver Update, the "Driver Update Contents" section in Chapter 1, and the "PC Card Driver Update Contents" section in Chapter 2, provide 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. Information regarding the availability of new drivers can be obtained by calling SunSoft's Automated Support System at 1-800-SUNSOFT (options 4,1,1) or by sending electronic mail to support@cypress.West.Sun.COM. Before You Read This Book This document contains additional device configuration information for newly supported hardware. The importance of properly configured hardware prior to installing Solaris is discussed in x86: Installing Solaris Base Server Software. 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. Likewise, the installation instructions for this Driver Update are very brief and serve only to supplement the instructions found in that book. How This Book Is Organized A brief description of the contents of the Driver Update diskettes is followed by 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 Base Server 2.4 x86 Driver Update 9," provides information about what is new in this release and how to install it. Chapter 2, "Solaris Base Server 2.4 x86 Driver Update 9 PC Card (PCMCIA) Support" provides information about the contents, installation instructions, and known problems for the PC Card support in this Driver Update. 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: Installing Solaris Base Server Software Describes how to configure x86 devices before installing Solaris software and describes how to install the Solaris software. o x86 Device Configuration Guide Includes Device Reference Pages not provided in this document. Individual Device Reference Pages from x86 Device Configuration Guide can be obtained through ASK-IT; see the next section. o Solaris 2.4 x86 Base Server Open Issues and Late-Breaking News Describes late-breaking news about running Solaris software, including known problems with supported hardware or device drivers. o Solaris 2.4 x86 Hardware Compatibility List-Solaris Base Server Edition Contains a list of supported hardware on Solaris Base Server 2.4 x86 systems. How to Obtain Updated Hardware Compatibility Lists and Device Driver Information Note - SunSoft is in the process of making Solaris Base Server Driver Updates and Hardware Compatibility Lists available from the following sources. They may not be immediately available from all sources. If you're having problems obtaining Driver Updates and Hardware Compatibility Lists for Solaris Base Server, contact your local Solaris technical support provider. 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 and then select: "x86 Hardware Compatibility List" or "download driver updates" o FTP - Use anonymous FTP to access ftp.uu.net, then go to /vendor/sun/sun-doc/x-86-driver/2.4. o CompuServe - Type go sunsoft and go to the Solaris x86 library. o ASK-IT - SunSoft's Automated Support Fax-on-Demand Service o In North America, call one of these numbers: 1-800-SUNSOFT and choose options 4, 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-51098 Note that the World Wide Web, CompuServe, and ASK-IT also point to Support-provided installation and configuration information as well as answers to frequently asked questions. 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 local technical support provider. Chapter 1 - Solaris Base Server 2.4 x86 Driver Update 9 Solaris Base Server 2.4 x86 Driver Update 9 adds new support for SCSI host bus adapters, the IDE interface, network adapters, audio cards, a new SCSI tape driver, and PCMCIA devices. This chapter provides a brief description of what's new in this Driver Update, followed by a complete list of the contents, installation instructions, and release notes for all the drivers included in this release, except for PC Card (PCMCIA) device support. For additional information and installation instructions for the PC Card device support provided in this release, see Chapter 2, "Solaris Base Server 2.4 x86 Driver Update 9 PC Card (PCMCIA) Support." Note - Before installing this Driver Update, the newly supported hardware devices should be installed and configured according to the instructions in Appendix A, "Device Reference Pages." What's New? New Device Drivers (SCSI HBA, SCSI Tape, Network) Table 1-1 lists the new and updated device drivers in Solaris Base Server 2.4 x86 Driver Update 9 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 ========================================================================== SCSI HBA Drivers aha AHA-154xCP Device Reference Page updated. esa Probe conflicts fixed. -------------------------------------------------------------------------- IDE Interface Driver ata IDE device DDI compliance bug fixes. -------------------------------------------------------------------------- Network Drivers dnet Bug fixes, and support for AsanteFAST 10/100. -------------------------------------------------------------------------- Serial Port Drivers asy ========================================================================== Serial Driver bug fixes Note - SMC EtherPower (8432BT/8432BTA), Cogent EM960TP/EM960C (TP connector only), Cogent EM100, D-Link DE-530CT, and Znyx EtherAction ZX312 boards have been successfully tested with a generic driver for network adapters based on the DECchip 21040 Ethernet and DECchip 21140 Fast Ethernet Controllers. Other adapters may work with this driver and additional boards will be tested in the future. However, some boards have failed to work with the dnet driver (for example quad-port boards from Cogent and Znyx), and other boards have exhibited inconsistent behavior (SMC EtherPower 10/100). Support for these and other DECchip-based adapters will be included in future releases of this driver. Corrections to Known Problems For a 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/, where is one of the following for Driver Update 9: 102061-03, 102065-02, 102266-06, 102308-06, 102318-02, 102324-04, 102565-02, 102590-02, 102808-02, 102809-01, 102810-01, and 102811-02. PC Card (PCMCIA) Driver Support For information about the PC Card portion of this Driver Update. For more information about the PC Card support in this release, see Chapter 2, "Solaris Base Server 2.4 x86 Driver Update 9 PC Card (PCMCIA) Support." Driver Update Contents Solaris Base Server 2.4 x86 Driver Update 9 contains four diskettes labeled: o "Solaris Base Server 2.4 x86 Driver Update 9 Boot Diskette" o "Solaris Base Server 2.4 x86 Driver Update 9 Distribution Diskette 1 of 2" o "Solaris Base Server 2.4 x86 Driver Update 9 Distribution Diskette 2 of 2" o "Solaris Base Server 2.4 x86 Driver Update 9 Distribution (PC Card)" These diskettes are intended to be used with a Solaris Base Server 2.4 x86 CD. Note - If you received Solaris Base Server 2.4 x86 Driver Update 9 electronically, you'll need to label the diskettes you've downloaded. Driver Update Boot Diskette The Solaris Base Server 2.4 operating environment can be installed on x86 systems with the new boot diskette labeled "Solaris Base Server 2.4 x86 Driver Update 9 Boot Diskette" This Multiple Device Boot (MDB) diskette contains scripts and configuration files that enable you to boot and install your system using one of the newly supported devices. During installation of the Solaris software, the Driver Update Distribution diskettes will be read. Driver Update Distribution Diskettes The Driver Update Distribution diskettes (labeled "Solaris Base Server 2.4 x86 Driver Update 9 Distribution Diskette 1 of 2" and "Solaris Base Server 2.4 x86 Driver Update 9 Distribution Diskette 2 of 2") are read when the Driver Update Boot diskette is used to install Solaris. Alternatively, the Driver Update Distribution diskettes can be used without the boot diskette to add new drivers to an existing x86 system running Solaris Base Server 2.4. The Driver Update Distribution diskettes contain the drivers listed in Table 1-2 A new or updated Section 7 manual 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 ========================================================================== SCSI HBA Drivers adp Adaptec AIC-787x driver that supports the AHA-2940, AHA-2940W, AHA-3940, and AHA-3940W PCI-to-Fast SCSI host bus adapters, and motherboards that integrate multiple Adaptec AIC-7870 controller chips, such as the DECpc(TM) XL 590 and the Samsung Magic Power SPC8500P (See Note following this table) aha AHA-154xCP Device Reference Page updated. aic Adaptec AIC-6360 driver that supports the AHA-1530P, AHA-1532P, AHA-1522A, AHA-1520A, AHA-1510A, and the 6360-based SCSI controller embedded on the Sound Blaster 16(TM) SCSI-2 blogic Updated to provide support for native mode PCI. BusLogic SCSI HBAs (BT-440C, BT-445C, BT-445S, BT-542B, BT-545C, BT-545S, BT-742A, BT-746C, BT-747C, BT-747S, BT-757S, BT-946C) corvette IBM SCSI-2 Fast/Wide Adapter/A eha Updated Adaptec AHA-174x EISA HBAs driver to correct some known problems esa Updated Adaptec AIC-7770/AHA-274x/AHA-284x driver to fix some known problems iss Tricord Systems Intelligent SCSI Subsystem Controller mcis Updated IBM Micro Channel HBA driver to correct some known problems ncrs Updated driver to support the NCR(R) 53C815 SCSI controller and the embedded NCR 53C710 SCSI host bus adapters on Siemens Nixdorf PCE-5S systems; also updated to support systems that use PCI Configuration Mechanism #1 pcscsi AMD(R) PCscsi(TM) (Am53C974), PCscsi II (Am53C974A), and PCnet-SCSI(TM) (Am79C974) PCI host bus adapters integrated on system motherboards such as the HP Vectra XU and the Compaq DeskPro XL systems trantor Trantor(R) T348(TM) MiniSCSI Plus(TM) Parallel HBA -------------------------------------------------------------------------- SCSI RAID Drivers csa Compaq SMART SCSI Array Controllers integrated on the system motherboard of the Compaq family of ProSignia(TM), ProLiant(TM), and Systempro(R) Servers dpt Updated driver to add support for DPT PM-2024 and PM-2124 PCI host bus adapters, and the PM-3222 and PM-3224 SCSI RAID adapters mlx Updated driver to add support for the Mylex DAC960P PCI adapter and the IBM DMC960 RAID controllers (IBM SCSI-2 RAID and IBM SCSI-2 Fast/Wide Streaming-RAID Adapter/A) -------------------------------------------------------------------------- IDE Interface Driver ata Updated IDE interface driver to support ATAPI-compliant CD-ROM drives and enhanced IDE disk drives and bug fixes -------------------------------------------------------------------------- SCSI Tape Driver st SCSI tape target driver -------------------------------------------------------------------------- Diskette Driver fd New support for medium density format on 3.5-inch high- density diskettes used by NEC-DOS -------------------------------------------------------------------------- Keyboard Driver kd Updated to prevent the screen from going into unreadable white-on-white mode. -------------------------------------------------------------------------- Network Drivers dnet Updated to include AsanteFAST; (DEC21040/21140 Ethernet, Cogent EM100 Cogent EM960BT, D-Link DE- 530CT, SMC EtherPower 8432BT, SMC EtherPower 8432BTA Znyx312) eepro Intel(R) EtherExpress(TM) PRO Ethernet elink Updated 3Com(R) EtherLink(R) 16 (3C507) driver to correct some known problems iee Updated Intel EtherExpress 16 driver to fix some known problems ieef Support for Intel Ether Express PRO/100 (82556) nee Novell/Eagle Technology NE3200 Ethernet nei Novell/Eagle Technology NE2000, NE2000plus Ethernet nfe Compaq NetFlex-2 DualPort ENET and NetFlex-2 ENET-TR Controllers pcn AMD(R) PCnet(TM) driver to support integrated motherboards based on the AMD PCnet-ISA and PCnet-PCI controller chips riles Racal InterLan(R) ES3210/ES3210 TP Ethernet smc Updated driver to include support for the SMC(R) EtherEZ(TM) Ethernet adapter and to fix some known problems smceu Support for SMC Elite32 Ultra (8232) smcf Support for SMC Ether100 (9232) smce Updated SMC Elite32 driver to correct some known problems -------------------------------------------------------------------------- Audio Driver -------------------------------------------------------------------------- sbpro Updated audio driver to fix some known problems and add support for the Sound Blaster AWE32(TM) audio card -------------------------------------------------------------------------- Serial Ports Driver asy Updated to fix problems and enhance the hardware flow control functionality; the functionality works regardless of the CLOCAL flag bit. Note - 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 SunSoft Technical Support. This Driver Update also includes the following MP support: o New kernel modules to add support for the Compaq ProLiant (TriFlex) and the Tricord ES4000 MP machines. A manual page for tpf(7) will also be installed. o An updated kernel module that fixes some problems on Intel(R) MPSpec 1.1-compliant systems with more than two processors. 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/, where is one of the following for Solaris Base Server 2.4 x86 Driver Update 9: 102061-03, 102065-02, 102266-06, 102308-06, 102318-02, 102324-04, 102565-02, 102590-02, 102808-02, 102809-01, 102810-01, and 102811-02. Note - If you are installing Solaris 2.4 on one the following Intergraph systems, you will need to modify the Driver Update boot diskette 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.4 operating environment. See "Modifying the Solaris Base Server Driver Update Boot Diskette" in this chapter. Note - Certain large server class machines (such as the Compaq ProLiant series) configured with a large amount of EISA NVRAM information, or large amounts of memory, may sometimes cause the Solaris ufsboot program to fail with the following message after installation (see Bug ID 1206600): Boot: scratch memory overflow. The workaround is to run the INSTDRV.BAT DOS batch script on the Driver Update Boot diskette prior to installation. This disables device drivers for which hardware is not installed or configured at boot time by placing explicit exclude statements in the /etc/system file. Re-enabling device drivers simply involves removing the needed exclude statements from /etc/system and performing a reconfigure reboot. See "Modifying the Solaris Base Server Driver Update Boot Diskette" in this chapter for details. Note - Due to conflicts, the IBM SCSI-2 Fast/Wide Adapter/A should not be installed until the Solaris mcis driver is disabled. See "Modifying the Solaris Base Server Driver Update Boot Diskette" or "Disabling Drivers After Installing the Driver Update" in this chapter. Support for the 3Com EtherLink III (3C509B) Network Adapter This Driver Update also includes new device configuration information for the 3Com EtherLink III 3C509B network card. The Solaris elx driver included in Solaris 2.4 has been tested with this card. See Appendix A, "Device Reference Pages," for the necessary hardware configuration that must be done prior to installing the Solaris software. Solaris Base Server 2.4 x86 Driver Update 9 Release Notes Modifying the Solaris Base Server Driver Update Boot Diskette Before you install Solaris Base Server on your system, it may be necessary to modify the Driver Update Boot diskette to remove or enable certain drivers that conflict with each other. For example: o There is a known PCI/EISA I/O space overlap problem on systems that contain an NCR chip. This affects the Intergraph ISMP22 Server and the TD-5, TD-4, and 100 MHz TD-3 Personal Workstations. o The Solaris mcis driver interferes with the proper operation of the newly supported 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 can be installed. There are scripts on the Driver Update Boot diskette for driver modification. The diskette must be modified using DOS. As a precaution, you should make a backup of the original Boot diskette 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 Base Server 2.4 x86 Driver Update 9 Boot Diskette" into drive A:, make a copy of it, and then remove the diskette: diskcopy a: a: 4. Store your original Boot diskette in a safe place. 5. Label the copy of the Boot diskette as "Modified." For example: "Modified Solaris Base Server 2.4 x86 Driver Update 9 Boot Diskette for Intergraph Systems." 6. Run the batch command file. o To support the Intergraph ISMP22, TD-5, TD-4, or 100 MHz TD-3, run the intrgrph.bat command file: intrgrph o For IBM SCSI-2 Fast/Wide Adapter/A support, run the corvette.bat command file: corvette Now the Boot diskette is prepared to install the Solaris software on your system. If you have not already done so, configure your hardware as described in Appendix A, "Device Reference Pages." MP Support This Driver Update also includes kernel modules to add support for the Compaq ProLiant (TriFlex) and the Tricord ES4000 MP machines. A manual page for tpf(7) will also be installed. See "Driver Update Distribution Diskettes" for a complete list of the contents of this Driver Update. Support for SCSI Tape Driver The st driver is a SCSI tape device driver that replaces the old sctp tape driver supported in Solaris 2.4 x86. The st driver was developed on the SPARC(TM) platform and was previously supported only on Solaris 2.4 SPARC systems. It now replaces the sctp driver on x86 systems, providing the following features: o Full compatibility between Solaris SPARC and Solaris x86 platforms o Stability, robustness, and increased SCSI tape drive support o Field extensible; support for new tapes drives can be added by editing a configuration file (st.conf) o Supports tape control features required by commercial backup software, such as Legato Networker o Supports configurable write buffering (as an option) In addition, significant interoperability testing was conducted to ensure that tapes written with the older sctp driver can still be read by the new st driver. For more information about configuring tape drives, see "SCSI Tape Drives" in Appendix A, "Device Reference Pages." Support for More Than Four Serial Ports If you want to use more than four serial ports, you need to update two system files. Both /etc/iu.ap and /platform/i86pc/kernel/drv/asy.conf need to be modified to reflect the number of devices supported by the Solaris asy driver. The necessary steps are described below: 1. Edit the /etc/iu.ap file and replace the following two lines: asy 131072 131075 ldterm ttcompat asy 0 3 ldterm ttcompat with: asy 131072 131083 ldterm ttcompat asy 0 11 ldterm ttcompat These changes reflect the addition of eight new ports to the system. 2. Edit the file /platform/i86pc/kernel/drv/asy.conf. For each new serial port, add a line similar to the following, replacing IRQ and IOADDR with the appropriate IRQ and I/O address: name="asy" class="sysbus" interrupts=12,IRQ reg=IOADDR,0,0 ioaddr=IOADDR; For example, if the 8-port version of the BocaBoard is configured to use addresses 100 through 140 for its eight serial ports, the following lines would be added: name="asy" class="sysbus" interrupts=12,7 reg=0x100,0,0 ioaddr=0x100; name="asy" class="sysbus" interrupts=12,7 reg=0x108,0,0 ioaddr=0x108; name="asy" class="sysbus" interrupts=12,7 reg=0x110,0,0 ioaddr=0x110; name="asy" class="sysbus" interrupts=12,7 reg=0x118,0,0 ioaddr=0x118; name="asy" class="sysbus" interrupts=12,7 reg=0x120,0,0 ioaddr=0x120; name="asy" class="sysbus" interrupts=12,7 reg=0x128,0,0 ioaddr=0x128; name="asy" class="sysbus" interrupts=12,7 reg=0x130,0,0 ioaddr=0x130; name="asy" class="sysbus" interrupts=12,7 reg=0x138,0,0 ioaddr=0x138; 3. Perform a reconfiguration boot. # touch /reconfigure # reboot For more information, see /platform/i86pc/kernel/drv/asy.conf and the asy(7) and autopush(1M) manual pages. Choosing the Hard Drive Your System Will Boot From After Installation The choice of slot (PCI or EISA) or BIOS ROM base address may affect which hard drive your system chooses as the boot disk. Make sure you have configured your system so that the BIOS chooses the hard drive you want to boot from when your system is powered on. Known Problems Caution - The installation program's default size for the root file system may not be large enough to produce a working system on some PCI-based systems with new or updated drivers. When installing this Driver Update, you should not accept the default file system partitioning. Instead, press F4 to Customize the file system partitions, then allocate at least 20 Mbytes for the file system. o The BIOS on some systems is unable to "warm boot" Solaris when PCI devices have been in use. These systems must be reset, either by pressing a reset button or power cycling the 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 mlx or 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 Installing Solaris Base Server Using the Driver Update Diskettes To install Solaris Base Server 2.4 on an x86 system, follow the instructions in x86: Installing Solaris Base Server Software using the diskette labeled "Solaris Base Server 2.4 x86 Driver Update 9 Boot Diskette." The procedure for installing Solaris using the Driver Update Boot diskette is almost the same as that described in x86: Installing Solaris Base Server Software. There will be many times during the early booting process when the system will read data from the diskette, 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 the first and then the second of the Driver Update Distribution diskettes into the drive. After the new driver packages have all been added, the script will ask you to remove the diskette you are using 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, there may be additional steps you need to take after the Solaris software is installed on your system. See "Enabling Support for Sound Blaster Audio Cards After Installing Solaris Base Server or the Driver Update" below for further instructions. Enabling Support for Sound Blaster Audio Cards After Installing Solaris Base Server or the Driver Update To properly configure the audio cards supported in this Driver Update, it is sometimes necessary to manually edit the Solaris driver configuration file (sbpro.conf) to reflect the configuration of the card. (See the "Sound Blaster Pro/Sound Blaster 16/Sound Blaster AWE32" Device Reference Page, if you have not already done so.) This file is configured to support a Sound Blaster Pro card with factory default DMA settings, and Sound Blaster 16 cards with audio IRQ and DMA jumpers. If you have one of the following, you must edit the sbpro.conf file before your Sound Blaster card will operate correctly in the Solaris operating environment: o Sound Blaster Pro card with a nonstandard DMA setting o Sound Blaster 16 card without audio IRQ and DMA jumpers o Sound Blaster AWE32 card The following explains how to do that. Note - These instructions should be carried out after you have installed the Driver Update software and rebooted your system. 1. Become root. 2. Change directories to the location of the kernel configuration files. # cd /kernel/drv 3. Edit the sbpro.conf kernel configuration file. This is an ASCII file that can be edited using any text editor, such as vi. o If you have a SoundBlaster Pro card only: If you changed the DMA channel of the board from its default value of 1, you must update the entry in the sbpro.conf file. o If you have a Sound Blaster 16 card without audio IRQ/DMA jumpers, or a Sound Blaster AWE32 card: You must specify the dma-channels property in the sbpro.conf file. The dma-channels property must specify two DMA channels; the first for an 8-bit DMA channel; the second for a 16-bit DMA channel. Note - If your Sound Blaster 16 card has audio DMA jumpers, the driver will use the DMA channels specified by those jumper settings, and you need not specify the dma-channels property in the sbpro.conf file. If you do specify the DMA channels in the sbpro.conf file, however, they _must_ match the settings on your jumpered card. 4. Save your changes and exit the editor. 5. Remove the diskette from the drive if you have not already done so. 6. Perform a reconfiguration boot to make your changes take effect. # touch /reconfigure # reboot Adding New Drivers After Solaris Base Server Is Installed If you already have the Solaris Base Server 2.4 x86 software installed, the simplest way to add one of the new drivers is to obtain the Driver Update Distribution diskettes and install them as a patch on your 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." Follow these procedures to install the new drivers: 1. Insert "Solaris Base Server 2.4 x86 Driver Update 9 Distribution Diskette 1 of 1" into drive 0. 2. Become root. 3. Use cpio to copy files off the diskette and run the installation script. ----------------------------- To see if Volume Management software is running, type: ps -e | fgrep vold ----------------------------- The following commands assume Volume Management is running on your system. If it isn't, volcheck should not be run and the device name of the diskette drive needs to be replaced with /dev/rdiskette0. # mkdir /tmp/Drivers # cd /tmp/Drivers # volcheck & # cpio -iduBI /vol/dev/diskette0/unlabeled Please remove the diskette from drive zero. Press when ready 4. Remove the diskette from drive 0, and follow the instructions on the screen to shut down the system. The instructions include how to restart the system. 5. A second reboot may be required if you have installed new hardware that uses a new network driver. See "Replacing a Network Card." When the system comes up, the new device drivers should be completely installed and functional. However, there may be additional steps you need to take: o If you want to support an NE2000 or NE2000plus Ethernet adapter, you must enable the driver before the card is installed and configured. See "Enabling Support for the Novell NE2000/NE2000plus After Installing the Driver Update." o If you want to support an IBM SCSI-2 Fast/Wide Adapter/A, you must disable the Solaris mcis driver before the adapter is installed and configured. See "Disabling Drivers After Installing the Driver Update." o If you have a PCnet-ISA adapter and you experience network problems, you may need to disable another driver so that it won't interfere with the operation of the PCnet-ISA adapter. See "Disabling Drivers After Installing the Driver Update." o If you are replacing a network card with a newly supported network card, see "Replacing a Network Card." o If you have a Sound Blaster card, there may be additional steps you need to take after installing the Driver Update. See "Enabling Support for Sound Blaster Audio Cards After Installing Solaris Base Server or the Driver Update" for instructions. Enabling Support for the Novell NE2000/NE2000plus After Installing the Driver Update If you already have Solaris Base Server 2.4 x86 running on your system and you now want to add an NE2000 or NE2000plus Ethernet card, you need to disable the conflicting drivers that are already installed on your system. This must be done prior to installing the NE2000/NE2000plus card but after installing the Driver Update 9 software. 1. Follow the instructions under "Adding New Drivers After Solaris Base Server Is Installed" in this chapter to install Driver Update 9. 2. Become root. 3. 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: iee exclude: pcn exclude: smc exclude: tiqmouse 4. Remove or comment out the following lines: ----------------------------- To comment out a line in the /etc/system file, place an asterisk * at the beginning of the line. ----------------------------- exclude: nei forceload: drv/eepro forceload: drv/el forceload: drv/elink forceload: drv/iee forceload: drv/pcn forceload: drv/smc 5. Add or uncomment the following line: ----------------------------- To uncomment a line in the /etc/system file, remove the asterisk (*) at the beginning of the line. ----------------------------- forceload: drv/nei 6. Save your changes and exit the editor. 7. Shut down the system and power it off. 8. Install the NE2000 or NE2000plus card and configure it according to the information in Appendix A, "Device Reference Pages." 9. Reboot the system. Note - Upon reboot, the Ethernet cards listed in Table A-1 in the Novell NE2000, NE2000plus Ethernet Device Reference 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, there is an additional step you must take. See "Replacing a Network Card." Disabling Drivers After Installing the Driver Update It is sometimes necessary to disable certain Solaris drivers so that they will not interfere with the proper operation of other hardware. For example: o The Solaris mcis driver interferes with the proper operation of the IBM SCSI-2 Fast/Wide Adapter/A. Before you can install and configure this newly supported adapter, the mcis driver must be disabled. o The Solaris elink driver may interfere with the proper operation of PCnet- ISA adapters. If you already have Solaris installed on your system, and after installing this Driver Update you experience network problems with your PCnet-ISA adapter, try disabling the Solaris elink driver. To disable a driver requires modifying a system file and rebooting. 1. Install the Driver Update by following the instructions under "Adding New Drivers After Solaris Base Server Is Installed." 2. Become root. 3. Use a text editor (such as vi) to edit the /etc/system file, and add one of the following lines: o For SCSI-2 Fast/Wide Adapter/A support, add the line: exclude: mcis o For PCnet-ISA support, add the line: exclude: elink 4. Remove or comment out one the following lines. ----------------------------- To comment out a line in the /etc/system file, place an asterisk (*) at the beginning of the line. ----------------------------- o For IBM SCSI-2 Fast/Wide Adapter/A support, remove or comment out the line: forceload: drv/mcis o For PCnet-ISA support, remove or comment out the line: forceload: drv/elink 5. Save your changes and exit the editor. 6. Shut down the system and power it off. 7. Install the IBM SCSI-2 Fast/Wide Adapter/A or the PCnet-ISA adapter and configure it according to the information in Appendix A, "Device Reference Pages." 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. Note - Upon reboot, the 3Com EtherLink 16 (3C507) Ethernet card will no longer be recognized by the Solaris software, and it cannot be used in a system with the PCnet-ISA. 9. If the newly installed PCnet-ISA card is replacing another network card, there is an additional step you must take. See the next section, "Replacing a Network Card." Replacing a Network Card If you have replaced your network card with one that uses a different network driver (for example, smc), you will need to rename the /etc/hostname.olddriver0 file to /etc/hostname.newdriver0 before rebooting the second time. For example, if you have replaced a 3Com EtherLink III card with an SMC EtherEZ card, you would need to run the following command as root: # mv /etc/hostname.elx0 /etc/hostname.smc0 Now perform a reconfiguration boot to make your changes take effect: # touch /reconfigure # reboot Chapter 2 - Solaris Base Server 2.4 x86 Driver Update 9 PC Card (PCMCIA) Support A description of the contents of the PC Card support included in this Driver Update is followed by a brief overview of PCMCIA hardware, installation instructions, release notes, and troubleshooting information. Appendix A, "Device Reference Pages," provides additional information about the PC Card device configuration in this release. Read through the entire chapter once before installing the PC Card support in Solaris Base Server 2.4 x86 Driver Update 9. PC Card Driver Update Contents Solaris Base Server 2.4 x86 Driver Update 9 contains one diskette labeled: "Solaris Base Server 2.4 x86 Driver Update 9 Distribution (PC Card)." The PC Card Driver Update Distribution diskette is intended to be used on Solaris Base Server 2.4 x86 systems only and contains the drivers listed in Table 2-1. A new Section 7 manual page for each of the drivers will also be installed in the appropriate manual page directory during installation. Note - Support for a specific adapter chip does not guarantee that PC Card support will work on a platform, though it will increase the likelihood. Check Solaris 2.4 x86 Hardware Compatibility List-Solaris Base Server Edition to be certain. Table 2-1 PC Card Drivers Supported in This Driver Update ========================================================================= PC Card Drivers --------------- pcic Intel i82365SL PC Interface adapter driver that supports adapters based on the following chips: Intel 82365SL, Vadem VG365/VG465/VG468/VG469, Cirrus Logic PD6710/PD6720, Ricoh RF5C366, and Toshiba pcelx 3Com EtherLink III (3C589) Ethernet PC Card driver pcram PC Card memory card driver that supports PC Card SRAM and DRAM devices pcser PC Card serial card device driver that supports PC Card modem and serial devices based on the 16550 UART and its variants ========================================================================= Appendix A contains Device Reference Pages that explain the configuration for each of the types of PC Card devices listed above. The PC Card Driver Update also includes: o pcmcia, the PC Card nexus driver that provides card and socket services for PC Card device drivers (such as pcic) o pcmem, the PC Card memory card nexus driver that supports PC Card memory card client drivers (such as pcram) o pcmciad, the PC Card user daemon that provides user-level services for pcmcia and PC Card client drivers. See pcmcia(4), pcmem(7), and pcmciad(1M). Other manual pages have been updated for PC Card support and will be installed in the appropriate manual page directory. See fdformat(1), add_drv(1M), drvconfig(1M), dkio(7), and pcfs(7). For a complete list of the contents of the PC Card Driver Update diskette, see the README files that are installed in the patch directories /var/sadm/patch/, where is one of the following for Solaris Base Server 2.4 x86 Driver Update 9 PC Card support: 101908-05, 101924-02, and 101938-01. Understanding PC Card Devices A PC Card adapter may be built into your computer (as on most notebooks) or it may be an add-on card. Most have either one or two sockets, and the PC Card adapter is, itself, a device on another bus (usually ISA). The PC Card adapter manages the PC Card bus and maps PC Card devices onto the main bus (for example, ISA). The PC Card bus was originally developed for memory cards and notebook computers. It is now used for a wide variety of devices (including modems, network interfaces, disk drives, SCSI HBAs, audio cards, and graphics cards) on machines of all sizes and architectures. See "Using PCMCIA Cards" in Appendix G of Solaris User's Guide for further information. In the Solaris operating environment, sockets are numbered, starting with zero; whether they are numbered top-to-bottom or bottom-to-top is platform- dependent. Though sometimes marked as "1/2" or "A/B," usually sockets are not marked. To find out how sockets are numbered, either consult the hardware documentation or insert a card and see which device was created. Three types of PC Card device are supported by Solaris device drivers. They are about the size of credit cards, but have different thicknesses: o Type I: 3.3 mm o Type II: 5 mm o Type III: 10.5 mm Lower-type cards can be used in higher-type sockets. For example, an adapter with Type-III PC Card sockets should be able to support Type-III, Type-II, and Type-I cards. But an adapter with Type-I sockets will only support Type-I devices. PC Card devices are autoconfigured; that is, I/O ports and IRQs are assigned automatically by the Solaris system when each device is plugged in. PC Card devices are hot-pluggable-they can be safely inserted and removed while a machine is running. Configuring PC Card Devices The PC Card software should automatically recognize any supported PC Card device when it is plugged in and then load the appropriate device driver. If you have a device that is compatible with a supported device, but it is not included in the supported devices database, /etc/driver_aliases, you can manually add your new card to the list. This manual process applies to modem cards and is described in "Identifying an Unrecognized Device" in the "Modem and Serial PC Card Devices" Device Reference Page in Appendix A. You may also have to define aliases for a small percentage of SRAM cards that have "Attribute Memory." Configuring the PC Card Adapter While PC Card devices are autoconfigured, it may be necessary to perform some configuration for the PC Card adapter itself. The pcmcia nexus driver must know which resources are already allocated in order to assign IRQs and ports to PC Card devices. During the installation process, a script attempts to automatically determine which resources are already allocated on the system. Some systems may require that resource allocation information be provided manually. See "PC Card Adapters" in Appendix A. Hot-Plugging PC Card Devices Hot-plugging a PC Card device means that a PC card can be inserted or removed at any time, even while the machine is powered on and the Solaris software is running. Since this isn't the usual procedure for adding and removing devices, the following sections explain hot-plugging procedures. Inserting Cards A PC Card device can be inserted at any time into any empty PC Card socket. If there is driver support for the card, the card is recognized and a device node is created. When the /usr/lib/pcmciad daemon is running (which is by default), the driver is also loaded and the /dev entries for the device are created as appropriate. The name of the /dev entry is often based on the name of the device driver and usually encodes the socket number where the card was inserted. For example, the entry for the 3Com 3C589 inserted in socket 0 will be /dev/pcelx0. The Device Reference Pages in Appendix A and the PC Card driver manual pages describe the /dev entries for each device driver. Recognizing Cards A PC Card device is "recognized" when it is inserted and the appropriate /devices and /dev entries are created. If you are not sure if your card has been recognized, perform the following checks: o Run the prtconf command; the output should list the pcmcia, pcic, and the driver name for the card you inserted. o Check to see that the/devices/pcmcia directory includes devices in one of these forms: driver@socket or driver@socket:driver. Since these are specific to each device driver, consult the Device Reference Pages in Appendix A. o Check that the /dev directory includes the pcmcia device entry. Entries for the network device are also under /dev. Other entries appear in subdirectories of /dev; see the Device Reference Pages in Appendix A for each driver. Identifying Unrecognized Cards A PC Card device is "unrecognized" if the prtconf command doesn't show a correct entry for the device and if /devices and /dev entries don't exist. Two symptoms you might see for an unrecognized card are: o An entry under pcmcia in the prtconf output is not a device driver name and says "(driver not attached)." o An erroneous pcmem device is detected when the card inserted is a non-memory card. A card is not recognized if it doesn't implement the full Card Information Structure (CIS) or there is a memory conflict. o If you see "(driver not attached)", you can add a new alias to /etc/driver_aliases by using the /add_drv command. Removing Cards PC Card devices can be removed at any time. The framework notifies the PC Card device driver that the card has been removed. Each driver will then deal with the unplugged card in its own way. See "3Com EtherLink III (3C589) PC Card," "Modem and Serial PC Card Devices," and "SRAM and DRAM PC Card Devices" in Appendix A, "Device Reference Pages." Installing the PC Card Driver Update Note - Before installing this PC Card Driver Update, read the information in the PC Card Device Reference Pages in Appendix A. Also be sure that you have filled out the Device Configuration Worksheet and check that all hardware resources for your system are accounted for. Then if you have trouble identifying PC Card devices, you can consult the worksheet to see what possible device conflicts exist. The contents of the "Solaris Base Server 2.4 x86 Driver Update 9 Distribution (PC Card)" diskette is installed as a combination of patches and packages on your Solaris Base Server 2.4 x86 system. Note - If you have an add-on PC Card adapter, be sure to install it before installing the PC Card Driver Update. Note - If you are using a notebook computer with a docking bay, be sure the notebook is in the docking bay before you install the PC Card Driver Update. This is necessary so that the system can identify the resources used by cards in the docking bay. 1. Insert the "Solaris Base Server 2.4 x86 Driver Update 9 Distribution (PC Card)" diskette into drive 0. 2. Become root. 3. Use cpio to copy files off the diskette, and run the installation script. -------------------------------- To see if Volume Management software is running, type: ps -e | fgrep vold. For more information about managing diskettes and drives, see Solaris 2.4 Open Issues and Late-Breaking News. -------------------------------- The following commands assume the Solaris Volume Management software is running on your system. If it isn't, volcheck should not be run, and the device name of the diskette drive must be replaced with /dev/diskette0. # mkdir /tmp/Drivers # cd /tmp/Drivers # volcheck & # cpio -iduBI /vol/dev/aliases/floppy0 End of Medium on "input" Change to part 2 and press RETURN key [q] 4. Insert "Solaris Base Server 2.4 x86 Driver Update 9 Distribution Diskette 2 of 2" into drive 0, and press Enter. When the input is done, you will see following message: Please remove the diskette from drive zero. Press when ready. 5. Remove the diskette from drive 0, and type the following: # ./installdu.sh 6. Perform a reconfiguration boot to enable the new PC Card support. # touch /reconfigure # reboot I/O ports, IRQs, and memory addresses available for use by PC Card devices should be configured automatically. For information about manual configuration of PC Card devices, see "PC Card Adapters" in Appendix A, "Device Reference Pages." If you insert a PC Card device into your system, it should be automatically recognized and configured. For more information, see the "Hot-Plugging" sections on the individual PC Card "Device Reference Pages" in Appendix A. If you have a 3Com Ethernet PC Card, follow the additional installation instructions in the next section to enable the new network interface. Note - Reconfigure boots or use of the drvconfig command should not be necessary with PC Card devices. Any use of these features will cause the /kernel/drv/pcic.conf file to be overwritten, so changes to the smi property will be lost (#exclude: lines will remain intact). These features should only be used when non-PC Card devices are added or removed. PC Card Release Notes Using PC Card Memory Cards PC Card memory cards can be used like diskettes. They can be used to store data, or they can have file systems containing files and directories. PC Card memory devices don't need to have file systems on them, though typically, before using a new PC Card memory card, you will want to create a file system on it. DOS pcfs is a good format to use. Although you can use virtually any file system format on a PC Card memory card, most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. Note - If you want to redirect the output of a tar command (or dd or cpio) to a PC Card memory device, you must first create a file system on the card, using the fdformat command without arguments. The card will need to be reformatted before it can be written on again. The method for creating a file system is different depending on whether or not the Solaris Volume Management software is used. Both methods are described below. Using PC Card Devices Without Volume Manager 1. Become root. 2. If you do not want to use vold to manage your PC Card memory cards, comment out the use pcmem line in the /etc/vold.conf file. To comment out a line in /etc/vold.conf, add a # character to the beginning of the line using a text editor. The line would then look similar to the following: # use pcmem drive /dev/rdsk/c*s2 dev_pcmem.so pcmem%d forceload=true 3. Stop and restart Volume Manager so the change will take effect. # /etc/init.d/volmgt stop # /etc/init.d/volmgt start 4. Use the fdformat command to create a pcfs file system on the PC Card memory card. -------------------------------- Device naming for PC Card memory cards is discussed in pcram(7), fdformat(1), and "SRAM and DRAM PC Card Devices" in Appendix A, "Device Reference Pages." Solaris Base Server 2.4 x86 Driver Update 9 PC Card (PCMCIA) Support -------------------------------- Note - fdformat will destroy all existing data on the memory card. For example, a DOS pcfs file system can be created on a PC Card memory card in socket 0 by typing: # fdformat -t dos /dev/dsk/c1t6d0s2 5. Use the mount command to mount the device. For example, to mount the pcfs file system created in the previous step, on to the mount point /mnt, type: # /etc/mount -F pcfs /dev/dsk/c1t6d0s2 /mnt Using the Volume Management Software to Manage PC Card Memory Cards Since the Solaris Volume Management software recognizes PC Card memory cards, no special vold configuration is required. 1. Become root. 2. Use the fdformat command to create a pcfs file system on the PC Card memory card. See fdformat(1M). For example, a DOS pcfs file system can be created on a PC Card memory card in socket 0 by typing: # fdformat -t dos /vol/dev/aliases/pcmem0 3. After formatting is complete, Volume Manager will automatically mount the device only after the card is physically removed and reinserted. To check this, run the mount command after reinserting the card. Troubleshooting PC Card Devices When a PC Card device doesn't work, you must isolate the problem. First, determine that the nexus and adapter drivers have loaded successfully: o Use the prtconf command to see if the device nodes for both pcic and pcmcia exist. o If they do, the software has loaded and successfully identified a PC Card adapter. Any card that is inserted should be identified as an entry under the pcmcia node. If it is a supported card, then it should be usable when inserted and the prtconf output identifies the card. It should not say "(driver not attached)" or be falsely identified as a pcmem card. See "Identifying Unrecognized Cards" earlier in this chapter. o If neither device driver is recognized, your system does not have a supported PC Card adapter. If a PC Card device is recognized as present when the card is in the socket before the system is booted, but is not recognized as present when the card is hot-plugged, do the following: o If you have an AST PowerExec notebook computer: o Remove IRQ 15 from the list of usable interrupts. o Define the smi property to be 9. See "PC Card Resource Configuration Information" in the Device Reference Page for "PC Card Adapters" in Appendix A for instructions. o If your notebook computer is not an AST PowerExec, try overriding the default interrupt by using the smi property as described in "PC Card Adapters" in Appendix A. If that does not work, try several different IRQ levels. If a PC Card device is not identified when inserted prior to booting the system, do the following: o Make sure that the I/O, memory, and interrupt resources listed in the /kernel/drv/pcic.conf file are correct. These properties are described in the "PC Card Adapters" Device Reference Page under "PC Card Resource Configuration Information." If the information there is accurate, contact your technical support provider. The Intergraph TD-30 and TD-40 machines exhibit PC Card memory conflicts which can be corrected by adding one set of the following two lines to the /kernel/drv/picic.conf file and then rebooting the system. #exclude:td30 res-memory c0000 10000 #exclude:td30 res-memory d0000 40000 or #exclude:td40 res-memory c0000 10000 #exclude:td40 res-memory d0000 40000 Appendix A - Device Reference Pages This appendix supplements Appendix B, "Device Reference Pages," in x86 Device Configuration Guide. (See "How to Obtain Updated Hardware Compatibility Lists and Device Driver Information" in About This Book to obtain Device Reference Pages from that book.) It includes necessary device configuration data for hardware supported by the new or updated drivers. The following table lists the hardware supported by Driver Update 9 in the order they are found in this appendix. ====================================================================== IDE Interface Solaris Driver ------------- -------------- IDE Disk and CD-ROM Interface ata SCSI Host Bus Adapters Solaris Driver ---------------------- -------------- Adaptec AIC-6360/AHA-1522A/AHA-1520A/ aic AHA-1510A/AHA-1530P/1532P Sound Blaster 16 SCSI-2 (SCSI) aic Adaptec AIC-7870/AIC-7871/AIC-7872/AHA-2940/ adp AHA-3940 PCI HBAs AMD PCscsi, PCscsi II, PCnet-SCSI PCI HBAs pcscsi BusLogic SCSI HBAs blogic Compaq SMART SCSI Array Controller csa DPT PM-2011/PM-2021 ISA HBAs dpt DPT PM-2012B EISA HBA dpt DPT PM-2022/PM-2122/PM-3222 EISA HBAs dpt DPT PM-2024/PM-2124/PM-3224 PCI HBAs dpt IBM DMC960 RAID Micro Channel HBAs mlx (IBM SCSI-2 RAID, IBM SCSI-2 Fast/Wide Streaming-RAID Adapter/A) IBM Micro Channel SCSI-2 Fast/Wide Adapter/A corvette Mylex DAC960P PCI Controller mlx NCR 53C710 (Siemens Nixdorf PCE-5S SCSI) ncrs NCR 53C8xx PCI SCSI HBA (53C810,53C815,53C820,53C825) ncrs Trantor T348 MiniSCSI Plus Parallel HBA trantor Tricord Systems Intelligent SCSI Subsystem (ISS) HBA iss Other SCSI Devices Solaris Driver ------------------ -------------- SCSI Tape Drives st Network Adapters Solaris Driver ---------------- -------------- 3Com EtherLink III (3C5x9, 3C509B) elx AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI) pcn Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR EISA nfe Controllers DEC 21040/21140 Ethernet (D-Link DE-530CT, SMC dnet EtherPower 8432BT, SMC EtherPower 8432BTA, Znyx312, Cogent EM960TP, Cogent EM100) Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP iee Intel EtherExpress PRO eepro Intel EtherExpress PRO/100 (82556) ieef Novell NE2000, NE2000plus Ethernet nei Novell NE3200 EISA Ethernet nee Racal InterLan ES3210/ES3210 TP EISA Ethernet riles SMC Elite32 Ultra (8232) smceu SMC Ether100 (9232) smcf SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS smc Elite16, EtherCard PLUS (8416, 8216, 8013, 8003) Audio Cards Solaris Driver ----------- -------------- Sound Blaster Pro/Sound Blaster 16/Sound sbpro Blaster AWE32 PC Card Hardware Solaris Driver ---------------- -------------- PC Card Adapters pcmcia 3Com EtherLink III (3C89) PC Card pcelx Modem and Serial PC Card Devices pcser SRAM and DRAM PC Card Devices pcmem ************* IDE Interface ************* IDE Disk and CD-ROM Interface Description An IDE disk drive contains a disk controller and drive electronics. An IDE adapter supports up to two IDE drives. Solaris supports up to two IDE adapters. 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 IDE CD-ROM drive, the CD-ROM drive is the slave, and the hard disk drive is the master. 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, then 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" below. Valid Configurations Following are the IDE adapter parameter ranges: o IRQ 14 or 15 o I/O Address 0x1F0 or 0x170 Warnings o Several vendors ship PCI-equipped machines with IDE interfaces attached to the system board directly. A number of these machines use the PCI to IDE chip set designed by the CMD (part number 06040.) This chip provides two IDE interfaces. The primary IDE controller is at I/O address 0x1f0 and the secondary controller at 0x170. However this chip can not handle simultanous I/O on both IDE controllers. This defect causes Solaris to hang if both interfaces are used. The workaround for this problem is to use only the primary IDE controller at address 0x1f0. Machines known to use this chip include DELL XPS/90, HP XU/590C and American Megatrends Atlas boards. o (1191294) 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 fully support the IDE CD-ROM interface if the drive is configured as the slave. For example, the vold program does not always automatically mount CDs that are installed in the slave drive after booting (as it does for SCSI drives), and the `eject cdrom' command will not work. Workaround: The Solaris Volume Management software does support CD-ROM interface if the drive is configured as the master.You can still access the IDE CD-ROM drive that is configured as the slave manually by specifying the device name when invoking commands as user root. For example: # mount -F hsfs -r /dev/dsk/c0d1p0 /mnt o (1192383) 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). o (1189664) The Panasonic LK_MC579B IDE CD-ROM drive cannot be used to install the Solaris operating environment and is not supported. o (1191272) The Dell OptiPlex system is shipped with an IDE CD-ROM drive connected to the secondary controller. In order to work with Solaris, this drive must be configured as the slave drive attached to the first controller. ********************** SCSI Host Bus Adapters ********************** Adaptec AIC-6360/AHA-1522A/AHA-1520A/AHA-1510A/ AHA-1530P/1532P Sound Blaster 16 SCSI-2 (SCSI) Description The Adaptec AHA-1522A, AHA-1520A, AHA-1530P/1532P, and AHA-1510A cards are SCSI controllers for ISA bus systems. The AHA-1510A, AHA-1520A, and AHA-1530P provide an interface between the computer's system bus and a SCSI bus. The AHA-1522A and AHA-1532P provide floppy drive support as well. All are based on the Adaptec AIC-6360 SCSI controller chip. The Solaris aic driver also supports the SCSI-2 interface of the Sound Blaster 16 SCSI-2 audio card, which utilizes the AIC-6360 chip. The Sound Blaster 16 SCSI-2 adapter is a 16-bit ISA card, providing audio functions and a SCSI-2 interface. The aic driver can be used to drive only the SCSI controller on these cards. Note - Neither the Adaptec AHA-1510A adapter nor the SCSI interface on the Sound Blaster 16 SCSI-2 audio card can be used as a primary (boot) disk controller (as they have no BIOS). Thus, the system will have to boot from a disk attached to another controller. The audio portion of the Sound Blaster 16 SCSI-2 card requires a separate Solaris device driver (sbpro) for operation. See the "Sound Blaster Pro/Sound Blaster 16/Sound Blaster AWE32" Device Reference Page in this appendix for specific device configuration information for the audio capabilities. Device Configuration Preparing for Configuration o The SCSI subsystem of the Sound Blaster 16 SCSI-2 needs its own I/O (port) address and an IRQ, distinct from those of the audio subsystem. o For the AHA-1520A and AHA-1522A, you will need to configure the BIOS base address, the I/O (port) address, and the IRQ on the controller. The AHA-1510 needs an I/O (port) address and an IRQ only. o For the AHA-1530P and AHA-1532P, you will need to configure the BIOS base address, the I/O (port) address, and the IRQ on the controller using the on-board utility. (Use Ctrl-A to enter the on-board utility at boot time.) o Refer to the documentation that comes with the Adaptec adapter or Sound Blaster 16 SCSI-2 adapter to find out what settings the device supports. o See "Valid Configurations" for address and IRQ settings that the Solaris aic driver supports. o Determine which of the supported IRQs, I/O (port) addresses, and memory (BIOS) addresses supported by the card and the Solaris driver are available. Choose settings for the card which do not conflict with any of the other devices in your system. o The SCSI bus must be configured correctly, and terminated correctly to prevent problems. Depending on your configuration, you may need to remove the terminating resistors on the controller. Refer to x86: Installing Solaris Base Server Software for SCSI configuration information. Note - The Sound Blaster 16 SCSI-2 will never need to have its resistors removed (and they are not removable). o The AHA-1522A, AHA-1520A, AHA-1530P, and the AHA-1532P support booting from disks with over 1 gigabyte. On the AHA-1530P and AHA- 1532P, use the on-board utility (entered via Ctrl-A at boot time) to enable this option under the "Advanced Features" menu. On the AHA-1522A and AHA-1520A, add a jumper to pin 0 (rightmost pin) of jumper block J5. Avoiding Possible Configuration Conflicts o Choosing settings for the adapter which do not conflict with any other device in your system, or with the motherboard, will avoid a multitude of problems. o ISA cards can be used in EISA slots but not vice versa. If you are using the device in an EISA slot, you should obtain the appropriate EISA configuration file from the manufacturer of the device. Use the EISA configuration utility that comes with your system to inform it of the presence of and settings used by the device. Be sure to "lock" the configuration of this device in the EISA configuration utility, or it may attempt to _change_ the settings on the device through software--which isn't possible. Conversely, if the EISA configuration program doesn't know about your ISA device, it may set up another EISA card using the settings of your ISA card, which would cause conflicts. o The Adaptec AHA-1510A host bus adapter and the Sound Blaster 16 SCSI-2 SCSI interface can be run only on IRQ 11. Because of this requirement, only one AHA-1510A or Sound Blaster 16 SCSI-2 controller can be installed in a system. Configuring the Device Note - For the Sound Blaster 16 SCSI-2, make sure you are setting the jumpers for the SCSI interface and not for the audio. 1. Set the I/O address jumper to select the desired value. 2. For 1520A, 1522A, 1530P, and 1532P _only_: Set the IRQ jumper to select the desired value. 3. For 1520A, 1522A, 1530P, and 1532P _only_: Set the BIOS base memory address jumpers to select the desired value. 4. For 1520A, 1522A, 1530P, and 1532P _only_: If necessary, enable support for disks greater than 1 gigabyte. On the 1530P and 1532P, use the on-board utility (entered via Ctrl-A at boot time) to select this option under the "Advanced Features" menu. On the 1522A and 1520A, this option is set by adding a jumper to pin 0 (the rightmost pin) of jumper block J5. 5. For 1510A, 1520A, and 1522A _only_: If necessary for your SCSI configuration, remove the three terminating resistors from the controller. 6. For the 1530P and 1532P _only_: termination is set using the on-board utility. 7. For the Sound Blaster 16 SCSI-2 _only_: Disable any DMA channel that may be selected. Valid Configurations Adaptec AHA-1510A: o IRQ 11 o I/O Address 0x140, x340 Adaptec AHA-1520A, 1522A: o IRQ 9, 10, 11, 12 o I/O Address 0x140, x340 o BIOS Base Address DC000, D8000, CC000, C8000 Adaptec AHA-1530P, 1532P: o IRQ 9, 10, 11, 12 o I/O Address 0x140, x340 o BIOS Base Address DC000, D8000, D4000, D0000, CC000, C8000 Sound Blaster 16 SCSI-2: o IRQ 11 o I/O Address 0x140, x340 o DMA Channel (Not used) Note - For booting, the I/O address on the 1520A and 1522A can be set to 0x140 only with a special BIOS available from Adaptec. o Adaptec 152x devices _only_: The BIOS base address can be any available value. The default is DC000. o Sound Blaster 16 SCSI-2 _only_: No DMA channel should be selected. The driver does not support DMA. o All other settings should be set to the default factory settings (unless changes are necessary to avoid conflicts). Note - Neither the Adaptec AHA-1510A adapter nor the SCSI interface on the Sound Blaster 16 SCSI-2 audio card can be used as a primary (boot) disk controller (as they have no BIOS). Thus, the system will have to boot from a disk attached to another controller. Alternative Custom Configuration o If you have a second SCSI controller on your system, ensure that the two devices are not configured to the same IRQ, I/O address, or memory (BIOS) address. o There are special considerations when two different types of disk controllers (such as SCSI and IDE) are present on a system. Refer to x86: Installing Solaris Base Server Software for more information. Warnings (1167300) The Adaptec devices have proven sensitive to the total length of the SCSI bus. (The SCSI specification defines the maximum length of the SCSI bus, including all cables, to be 6 meters (19.6 feet).) In configurations with long cables and/or multiple external devices, this could cause random bus hangs under heavy loads. Workaround: Use shorter cables, or fewer external devices. Adaptec AIC-7870/AIC-7871/AIC-7872/AHA-2940/AHA-3940 PCI HBAs Description The Adaptec AHA-2940, AHA-2940W, AHA-3940 and AHA-3940W cards are PCI-to-Fast SCSI controllers based on the Adaptec AIC-7870, AIC-7871, or AIC-7872 chips. Device Configuration Preparing for Configuration o 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 vendor-supplied configuration utility by pressing Ctrl-A at boot time. 4. Ensure that support for more than two DOS drives is disabled. 5. For older drives, tapes, 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 gigabyte if applicable. 7. Make sure there are no IRQ conflicts between ISA cards on your system and PCI controllers. Warnings 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 SunSoft Technical Support. o On some PCI systems with an Adaptec 294x card installed, user-level programs may core dump under heavy system load (such as during installation). The problem is not with the Adaptec hardware. However, if you have installed patch ID 101946, and you continue to see user-level programs dumping core, turn off write-back CPU caching (or all caching if there is no control over the caching algorithm) using the BIOS setup facility. This problem has been observed on a number of PCI motherboards, including the following: o PCI motherboards with a 60 MHz Pentium(TM) chip, with PCI chipset numbers S82433LX Z852 and S82434LX Z850. The part number of the Intel motherboard is AA616393-007. 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 PCI motherboards with a 66 MHz Pentium chip, with PCI chipset numbers 433LX Z852 and 434LX Z882, also exhibit the problem. The motherboard part number is AA-619772-002. (Gateway 2000 uses this motherboard.) 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. AMD PCscsi, PCscsi II, PCnet-SCSI PCI HBAs Description The Solaris pcscsi driver supports the AMD PCscsi (Am53C974), PCscsi II (Am53C974A), and PCnet-SCSI (Am79C974) host bus adapters. These are all PCI devices. The PCnet-SCSI chip is currently embedded in the HP Vectra XU 5/90 and Compaq Deskpro XL 560 systems. Only the SCSI portion of the PCnet-SCSI host bus adapter is discussed here. The net portion of the AMD PCnet-SCSI chip requires a separate Solaris driver (pcnet) for operation. See the "AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI)" Device Reference Page for specific configuration information about the Ethernet capabilities. Device Configuration Preparing for Configuration o See the manufacturer's documentation for setup and cabling requirements. o Ensure the SCSI bus is properly terminated. Configuring the Device Use the motherboard CMOS or EISA setup utility to ensure that the controller is enabled, that the SCSI BIOS is enabled and does not conflict with locations used by another device, and that the IRQ settings do not conflict with another device. Warnings The SCSI Tagged Queuing option is not supported. BusLogic SCSI HBAs Description The BusLogic SCSI host bus adapters are controllers for common disk, tape, and I/O subsystems. The following models are supported: ------------------------- Model Bus ------------------------- BT-742A, BT-746C, EISA BT-747C, BT-747S, BT-757C, BT-757S BT-542B, BT-545C, ISA BT-545S BT-440C, BT-445C, VESA BT-445S BT-946C, BT-956C PCI ------------------------- Device Configuration Preparing for Configuration o For EISA, ISA, and VESA Local Bus models: Set the I/O address to any valid BusLogic host bus adapter I/O address except 0x330 and 0x230. (The factory default is 0x330, so it must be changed.) o For PCI models: o If your PCI card is model BT-946C _and_ it is labeled Rev. A or B, it needs to be supported in ISA emulation mode; use I/O address 0x334. Note - In order to determine the revision level of a BusLogic PCI card, you must look at the card itself. The revision of the card is not referenced in the documentation that comes with the card. o If your PCI card is model BT-946C and it is labeled Rev. C, it can be supported in native PCI mode. To do this, select "Advanced option," and choose "NO" for the "Host Adapter I/O Port Address as default" option. o If your PCI card is model BT-956C, or model BT-946C, Rev. E or later, it can also be supported in native PCI mode. To do this, disable the "Set ISA Compatible I/O Port (PCI Only)" option. o If your BusLogic board model ends in "C", you must enter the AutoSCSI configuration utility and check the termination. Configuring the Device For EISA Models: 1. Run the EISA configuration utility and change the factory-set I/O port address. Do _not_ use the default 0x330 I/O address. 2. If a board has a model name ending with a "C", such as the BT-746C and the BT-747C, run the BusLogic AutoSCSI configuration utility. To run the AutoSCSI utility, type Ctrl-B after you see the BusLogic Utility Banner on your screen. a. Check termination. b. The Advanced option "BIOS Support for > 2 Drives (DOS 5.0 or above)" should be set to No. 3. _For model BT-757C only_: If the system has a narrow target, turn off the "wide negotiation option" when configuring devices. For ISA and VESA Local Bus Models: 1. Set the I/O address and BIOS address with the dip switches. Do _not_ set the I/O address to 0x330. 2. If a board has a model name ending with a "C", such as the BT-545C and the BT-445C, run the BusLogic AutoSCSI configuration utility to set the IRQ and check termination. To run the AutoSCSI utility, type Ctrl-B after you see the BusLogic Utility Banner" on your screen. a. Set the IRQ. b. Check termination. c. The Advanced option "BIOS Support for > 2 Drives (DOS 5.0 or above)" should be set to No. 3. Older ISA and VESA Local Bus models of BusLogic boards, such as the BT-545S, BT-542B, and BT-445S, must have their IRQ set in two places--with switches and jumpers. The Host Interrupt Request switch and the Host Interrupt Channel jumper must have settings that match, or the board will not work. For PCI Model BT-946C, Rev. A and B only: 1. The BusLogic BT-946C (Rev. A or B) board should be put into the Bus Master slot. 2. Enter the AutoSCSI utility. 3. Select "Advanced option." 4. Set termination as needed. 5. If the boot disk is larger than 1 Gbyte, set the "Adapter BIOS Supports Space > 1 GB (DOS) only" option to Yes. 6. Set the adapter to ISA-compatible mode. Set the value for "Set Host Bus Adapter IO Port Address as Default" to No. 7. The Advanced option "BIOS Support for > 2 Drives (DOS 5.0 or above)" should be set to No. 8. Save the changes. 9. Reboot the system. 10. If your PCI motherboard is not fully PCI-specification compliant, you may have to manually configure the IRQ and BIOS address values. If the system hangs while installing the Solaris operating environment, do the following: o Check the IRQ jumpers on the motherboard, if any. o Run the CMOS utility to set IRQ and BIOS address, if any. o Run the BusLogic AutoSCSI utility. All the settings should match each other. On the BT-946C Rev. A or B adapter, the jumpers JP4 and JP5 are for configuring the BIOS address. If you need to manually configure the BIOS address, you may have to check these jumpers. 11. If you still experience problems while installing the Solaris software, set the Interrupt Pin number of the "configure Adapter" option in the BusLogic AutoSCSI utility as follows: ------------------------- Slot Interrupt Pin ------------------------- 0 A 1 B 2 C ------------------------- For more information, see the "Configuration for Non-Conforming PCI Motherboards" and the "Handling Motherboard Variations" sections of the documentation that comes with your PCI BusLogic board. For All Other PCI Models (Except BT-946C, Rev. A and B): 1. The BusLogic PCI board should be put into the Bus Master slot. 2. Enter the AutoSCSI utility. 3. Set SCSI termination as needed. 4. Select "Advanced option." 5. If the boot disk is larger than 1 Gigabyte, set the Adapter BIOS supports space > 1 GB (DOS only)" option to Yes. 6. Choose the defaults except set the 5.1 "BIOS Support for > 2 Drives (DOS 5.0 or above)" to NO. 7. Save the changes. 8. Reboot the system. 9. If you experience problems while installing the Solaris software, set the Interrupt Pin number of the "configure Adapter" option in the BusLogic AutoSCSI utility as follows: ------------------------- Slot Interrupt Pin ------------------------- 0 A 1 B 2 C ------------------------- For more information, see the "Configuration for Non-Conforming PCI Motherboards" and the "Handling Motherboard Variations" sections of the documentation that comes with your PCI BusLogic board. Valid Configurations o ISA, EISA, and VLB adapters: o IRQ 9, 10, 11, 12, 14, 15 o I/O Address 0x334, 0x230, 0x234, 0x130, 0x134 o PCI adapters: o IRQ 5, 6, 7, 8, 9, 10, 11, 12, 14, 15 o I/O Address 0x334, 0x230, 0x234, 0x130, 0x134 (Rev. A and B _only_) Note - I/O addresses are dynamically configured for PCI adapters, Rev. C or later. Multiple Controller Configuration If you have multiple BusLogic boards in the system, follow these general rules to configure multiple BusLogic controllers: o If one of the installed boards is a "C" model, it must be the primary controller. o If one of the installed boards is a PCI bus model, it must be the primary controller. o The primary controller must have an I/O address that precedes the secondary controller in the above list of Valid Configurations (as listed from left to right). For example, the primary controller may use an I/O address of 0x234, as long as the secondary controller uses either 0x130 or 0x134. o The BIOS must be disabled on the secondary controller. o Wide mode EISA and PCI adapters will support targets greater than 7 if the proper entries are added to the system configuration files, /kernel/drv/cmdk.conf (for disk), and /kernel/drv/cmtp.conf or /kernel/drv/st.conf (for tape). Warnings o Using an I/O address of 0x330 will cause the Solaris aha driver to be selected instead of the blogic native mode driver. These cards have not been tested in Adaptec AHA-1540 mode. o This release of the blogic driver fixes bug 1188122: blogic_chkerr panic while running stress test. This bug caused a panic when running heavy I/O in the presence of intermittent tape accesses. o Request updated firmware for the BT-946C (Rev. C) from BusLogic, and install Rev. E or later. o Do not run the drvconfig utility during heavy I/O involving disks and tapes with BusLogic PCI cards since it can cause data overrun errors on disks or tape. This is documented in bug 1217378: blogic data_ovr errors while stress testing (+drvconfig) on BT946C-Rev E. o BusLogic EISA/PCI cards may cause data overrun errors under high stress when your system is configured with multiple disks. This is documented in bug 1218624: blogic data_ovr errors while stress testing BT-747C Rev. A. Compaq SMART SCSI Array Controller Description The Compaq SMART SCSI Array controller supports internal and external SCSI drives on the Compaq family of ProSignia, ProLiant, and Systempro servers. It is used on an EISA bus. Device Configuration Preparing for Configuration Be sure to read the documentation that comes with your hardware. Note the following: o The SMART controller only supports 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 Run the EISA configuration utility (ECU) to configure your drives. Warnings If you want to change your RAID configuration, first delete the old configuration information using the ECU. If you physically move the disks prior to deleting the RAID configuration (or the partition information on the logical drives), you may not be able to boot your system. DPT PM-2011/PM-2021 ISA HBAs Description The DPT PM-2011 and PM-2021 host bus adapters are 16-bit SCSI controllers for an ISA or EISA bus. Device Configuration Preparing for Configuration o The EPROM revisions on the board need to be checked. The EPROM should be version 5E or later. The SmartROM should be version 2.C or later. o The Solaris operating environment supports only two DPT adapters per system. o If two DPT PM-2011 or 2021 or 3021 adapters are installed, do not install an IDE controller. o If you have an IDE adapter installed, only one DPT adapter will be supported. Avoiding Possible Device Conflicts o Since the IDE adapters are configured in the same I/O address range, ensure there is no address conflict with any IDE controller. o If you have an IDE adapter installed, IRQ 14 should not be used by the DPT adapter. Configuring the Device 1. Consult your Device Configuration Worksheet to see if the DPT PM-2011/PM-2021 SCSI HBA settings need to be changed. 2. See the DPT manual for a description of the board's jumper settings. 3. Follow the instructions in the "DPT PM-2022/PM-2122/PM-3222 EISA HBAs" Device Reference Page to disable WD1003 emulation using the DPT SCSI Storage Manager Utility diskette. Emulation mode for both drives should be set to 0 for drives zero and one, indicating "no drives present." Note - Failure to disable the emulation modes for drives 0 and 1 will result in missing drives during the system boot process. Valid Configurations The parameters for DPT PM-2011/PM-2021 host bus adapters are different for first and secondary adapters: o First Adapter: o I/O Address 0x1F0 o IRQ 15 o DMA 5 o Second Adapter: o I/O Address 0x230 o IRQ 14 or 12 o DMA 6 If you have an IDE adapter installed, the valid parameters for the first (and only) DPT adapter are as follows: o I/O Address 0x230 o IRQ 12 o DMA 6 Note - Be sure to use Edge-triggered interrupts on the PM-2011. Warnings (1199652) The DPT controller may cause the installation of the Solaris operating environment to fail due to loss of interrupts, depending on the setting of Jumper Y34. Workaround: If the software installation fails, try changing the setting of Jumper Y34 (even if the onboard floppy has already been disabled by removing Jumper Y20). Toggling this setting appears to enable the controller to function correctly. DPT PM-2012B EISA HBA Description The DPT PM-2012B host bus adapter is a SCSI controller for an EISA bus. Device Configuration Configuring the Device 1. Consult your Device Configuration Worksheet to see if your DPT PM-2012B SCSI HBA settings have to be changed. 2. Follow the DPT SmartCache Plus User's Manual for a description of its configuration program. 3. Boot DOS from the diskette drive. 4. Insert a copy of the DPT Utility diskette in the diskette drive. a. Type DPTFMT and press Enter. b. Press Enter to begin. c. Press Enter to continue. d. Press to enter SCSI ID 0 and LUN 0. e. Press to continue. f. Use the down arrow to select MS-DOS and PC DOS. g. Press Enter to write out the drive geometry. h. Press Enter to reboot. 5. Insert the user copy diskette of the EISA configuration utility (CF.EXE) containing the !DPTxxx.CFG files. a. At the A:> prompt type CFG and press Enter. b. At the Viewer Edit Details screen press Enter. c. Press the down arrow to the DPT SCSI HBA to select parameters and set them as follows: Bus Enabled IDE Boot Address Primary IRQ Entry noted on your worksheet Option ROM Address Default SCSI ID HBA Default 7 WD1003 Emulation off for both drive 0 and 1 d. Press F10 to save your changes. 6. Insert a copy of the boot diskette. 7. Press Enter to reboot DOS. Valid Configurations Following are the DPT PM-2012B SCSI HBA parameter ranges: o IRQ Any legal value between 9 and 15 Note - Make sure you use Edge-triggered interrupts. o WD1003 Emulation off o Option ROM Address Default o I/O Address zC88 (where z is a slot number from 1 to 7) Warnings o If you have used the DPTFMT utility correctly, and the board is properly seated in your machine, failure to display disk geometry may indicate a defective board. o (1183572) In order to prevent system hangs caused by improper IDE emulation, the version number of the EISA !DPTA401.CFG file should be 6B3 or later. If it is not, obtain a newer version from your vendor and rerun the EISA configuration utility. DPT PM-2022/PM-2122/PM-3222 EISA HBAs Description The DPT PM-2022, PM-2122, and PM-3222 host bus adapters are SCSI controllers for an EISA bus. The PM-3222 is a SCSI RAID adapter. Device Configuration Preparing for Configuration Check the EPROM revisions on the board. o The DPT PM-3222 adapter should have EPROM version 7A or later and SmartROM version 3.B or later. o The DPT PM-2022 and PM-2122 adapters should have EPROM version 5E or later and SmartROM version 2.D1 or later. Configuring the Device 1. Consult your Device Configuration Worksheet to see if the DPT PM-2022/PM-2122/PM-3222 SCSI HBA settings need to be changed. 2. See the DPT SmartCache III User's Manual for a description of its EISA configuration program. 3. Boot DOS from the diskette drive. 4. Insert the user copy diskette of the EISA configuration utility (CF.EXE) containing the !DPTxxxCFG files. 5. Make sure the parameters are set as shown under "Valid Configurations." 6. Run the DPT SCSI Storage Manager Utility, DPTMGR, under DOS and select Solaris as the operating system. See Chapter 4 of the DPT SmartCache III User's Manual for instructions. Note - An error message similar to the following will be displayed while DPTMGR is running: Unable to find any drivers in the DRIVERS Directory...... This message can be ignored. Valid Configurations The following are the DPT PM-2022, PM-2122, and PM-3222 SCSI HBA parameter ranges: o WD1003 Boot Address Disabled (Secondary) o IRQ Any legal value between 11 and 15, except 14 Note - Make sure you use Edge-triggered interrupts. o IDE Boot Address Disabled o SCSI BIOS ROM Address Default o HBA SCSI ID Default 7 Alternative Custom Configuration When using the EISA configuration utility supplied by DPT in conjunction with a configuration file, you enter emulation information as part of the configuration process. When you configure two drives, both should be "disabled." When asked for drive types for drives zero and one, type 0. This indicates "no drives present" and disables the WD1003 emulation mode of the adapter, allowing correct operation of the native mode driver. Warnings o (1183572) In order to prevent system hangs caused by improper IDE emulation, the version number of the EISA !DPTA410.CFG file should be 6E5 or later. If it is not, obtain a newer version from your vendor and rerun the EISA configuration utility. o (1167519) The Solaris software installation may initially fail when trying to setup the fdisk partition table on one or more disks. The failures have been observed on systems with a disk RAID configuration, where at least one disk is new or has had its partition table zeroed out. The error messages displayed are: ERROR: Could not create Fdisk partition table on disk ERROR: Could not label the disks Workaround: If the Solaris software installation fails with these error messages, restart the installation. It will most likely succeed. DPT PM-2024/PM-2124/PM-3224 PCI HBAs Description The DPT PM-2024, PM-2124, and PM-3224 are SCSI controllers for a PCI bus. The PM-3224 is a SCSI RAID adapter. 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. Warnings 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 DMC960 RAID Micro Channel HBAs (IBM SCSI-2 RAID, IBM SCSI-2 Fast/Wide Streaming-RAID Adapter/A) Description The IBM DMC960 RAID Micro Channel bus controllers include the IBM SCSI-2 RAID and the IBM SCSI-2 Fast/Wide Streaming-RAID Adapter/A. 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 IBM host bus adapter 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: The IBM DMC960 model supports 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 IBM DMC960 settings need to be changed. 2. Follow the configuration instructions in the vendor's manual. Warnings 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. o Other than the "hot replacement" of disk drives, which is described in the manufacturer's user's guide, the IBM DMC960 series does 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 manufacturer, and then reboot your system. o (1210290) Some tape drives may prematurely report "tape full" when writing to tape under heavy system load. This has been seen with the Archive Viper 150 tape drive, for example. o (1212018) 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 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. To avoid conflicts, the Solaris mcis driver must be disabled before the IBM SCSI-2 Fast/Wide Adapter/A can be installed. This is done by modifying the Driver Update Boot diskette using the corvette.bat file under DOS; see "Modifying the Solaris Base Server Driver Update Boot Diskette" in Chapter 1 for instructions. 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 Drivers After Installing the Driver Update" in Chapter 1 for instructions. Device Configuration Preparing for Configuration Ensure that the controller board is properly installed in any slot between 1 and 7. Slots 8 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. Valid Configurations o IRQ 14 o I/O Address 0x3540, 0x3548, 0x3550, 0x3558, 0x3560, 0x3568, 0x3570, 0x3578 Warnings 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. Mylex DAC960P PCI Controller Description The Mylex DAC960P is a SCSI controller used with a PCI bus. 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 of Mylex host bus adapter 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: The Mylex DAC960P model supports 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 Consult your Device Configuration Worksheet to see if the Mylex DAC960P settings need to be changed. Valid Configurations Follow the configuration information in the manufacturer's installation manual. Warnings 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. o Other than the "hot replacement" of disk drives, which is described in the manufacturer's user's guide, the Mylex DAC960P series does 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 manufacturer, and then reboot your system. o (1212018) 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 NCR 53C710 (Siemens Nixdorf PCE-5S SCSI) Description These configuration notes are for the two NCR 53C710 SCSI host bus adapters embedded on Siemens Nixdorf PCE-5S systems. Device Configuration Note - Because the Siemens Nixdorf BIOS and the Solaris fdisk program are not compatible, use the DOS version of FDISK (or equivalent utility) to create an entry in the FDISK partition table before installing the Solaris software. Create at least a 1-cylinder DOS partition starting at cylinder 0. If the DOS partition is not created, the system will fail to reboot after Solaris installation. Preparing for Configuration See the manufacturer's documentation for setup and cabling requirements. Configuring the Device Use the motherboard CMOS setup utility to make sure that the controllers are enabled and that the IRQ settings do not conflict with another system device. Warnings The SCSI Tagged Queuing option is not supported. NCR 53C8xx PCI SCSI HBAs (53C810, 53C815, 53C820, 53C825) Description The device configuration information for the NCR 53C8xx PCI SCSI host bus adapters has been updated to include support for the NCR 53C815. These configuration notes are for the NCR 53C810, 53C815, 53C820, and 53C825 PCI SCSI controllers, which are found on add-in adapters or integrated on a system motherboard. Systems may be configured with multiple controllers. Device Configuration Note - Because the NCR BIOS and the Solaris fdisk program are not compatible, use the DOS version of FDISK (or equivalent utility) to create an entry in the FDISK partition table before installing the Solaris software. Create at least a 1 cylinder DOS partition starting at cylinder 0. If the DOS partition is not created, the system will fail to reboot after Solaris installation. Preparing for Configuration An add-in card with the 53C815, 53C820, or 53C825 controller can only be used in a bus-mastering PCI slot. On motherboards with only two PCI slots usually both of the PCI slots are bus-master capable. On motherboards with three or more PCI slots, and on motherboards with several embedded PCI controllers, some of the PCI slots may not be bus-master capable. Refer to the motherboard or system documentation to determine how to set up or configure which PCI slots are bus-master capable. Avoiding Possible Device Conflicts Some PCI motherboards with the NCR SDMS BIOS and an embedded 53C810 controller do not work correctly with 53C815 or 53C82x add-in cards which also have an NCR SDMS BIOS. Some PCI motherboards with NCR SDMS BIOS but without the 53C810 controller also may not work correctly with 53C815 or 53C82x add-in cards which do not have an NCR SDMS BIOS. If you have a combination that does not work correctly, you may be able to work around these conflicts by upgrading the motherboard BIOS or the add-in card BIOS or both. Configuring the Device Run the motherboard CMOS setup or the EISA configuration utility to make sure that the controller and the bus master options are enabled and that the IRQ setting does not conflict with another system device. Warnings o The SCSI Tagged Queuing option is not supported. o Some very early PCI systems with the 53C810 chip on the motherboard do not have the interrupt pin on the chip connected. Such a system cannot be used with the Solaris software. The Solaris ncrs driver requires a correctly functioning interrupt line for the 53C810 chip. o The Wide SCSI option is not supported under the Solaris Operating environment. Some add-in 53C8xx cards include connectors for both narrow cables (in other words, 8-bit SCSI A cables) and wide cables (that is 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. Trantor T348 MiniSCSI Plus Parallel HBA Description The Trantor T348 Parallel SCSI HBA is easy to install--it has no switches, no software-settable options, and does not require any manual configuration. However, the MiniSCSI Plus adapter may require special cabling to obtain electrical power and to connect to certain devices. Device Configuration Preparing for Configuration Note - The Trantor MiniSCSI Plus host adapter obtains its electrical power from the TERMPWR signal on the SCSI cable. The adapter will not receive power and will not work unless the first (or only) device connected to it supplies TERMPWR. If you have difficulty using the adapter with Solaris, see the "Troubleshooting Notes" section of the MiniSCSI Plus User Guide or consult your Trantor dealer. The Trantor MiniSCSI Plus HBA ends in a male SCSI-1 connector, suitable for plugging into a SCSI-1 device. If you want to connect it to a SCSI-2 device, you will need a SCSI-1 to SCSI-2 cable (which has a male SCSI-1 connector on one end and a male SCSI-2 connector on the other end) and a SCSI-1 female-to- female adapter (to connect the male end of the T348 to the male end of the SCSI-1 to SCSI-2 cable). Configuring the Device To install the Trantor T348 adapter: 1. Shut down the Solaris operating environment (if it is already installed) and power down the computer. 2. Plug the T348 adapter into the selected (or only) parallel port. 3. Attach all required SCSI devices to the T348. 4. Turn on the power to all the SCSI devices. 5. Turn on the power to the computer. Warnings o The Solaris trantor driver is intended primarily to support the use of SCSI CD-ROM drives for software installation, and SCSI tape drives for backup and file transfer. Because of low data transfer rate, simultaneous use of multiple SCSI devices is not recommended. o If you need to reconfigure the system later to add other devices, make sure the T348 and all its devices are plugged in and powered up; otherwise they will be removed from the configuration. If you accidentally reconfigure without the T348 plugged in, plug the T348 in and repeat the reconfiguration process. o The T348 and attached devices must also be plugged in and powered on at boot time to be available during that session. o The Solaris operating environment does not support concurrent use of other parallel devices on the same port as the Trantor T348 or on the T348 pass- through port. If you want to switch between the T348 and some other parallel port device, such as a printer or Ethernet adapter, shut down the Solaris operating environment and power off the computer and any SCSI devices attached to the T348. With the power turned off, disconnect the old device and connect the new one. If switching to the T348, power up any SCSI devices you intend to use. Turn on the power to the computer and do a reconfiguration boot. ----------------------------------- To perform a reconfiguration boot, type the commands: touch /reconfigure reboot ----------------------------------- o If the SCSI devices attached to the T348 fail to respond after a reconfiguration boot, and the parallel port had previously been used for a different device, it might be necessary to do a second reconfiguration boot. This situation occurs when the driver from the previous device interferes with the T348 driver's attempt to detect the presence of the T348 device. o The Trantor T338 andT358 are not supported. o (1185362) The Exabyte EXB-8500 and EXB-8200 tape drives do not work under the Solaris operating environment when connected to the Trantor T348 MiniSCSI Plus parallel host bus adapter. Tricord Systems Intelligent SCSI Subsystem (ISS) HBA Description The Tricord Systems Intelligent SCSI Subsystem (ISS) controllers are multi- channel SCSI controllers supported only on the Tricord Systems Enterprise Server Models. The ISS family of controllers supports standard SCSI devices, such as disk, tape, and CD-ROM, as well as RAID groupings of SCSI disk drives. Device Configuration Preparing for Configuration Version 4.03 or later of the system BIOS is required to be able to boot the Solaris operating environment. Device Naming Convention The special files that get created on an ISS system are described in the iss(7) manual page. Warnings Regardless of the number of devices on the ISS controller, a maximum of 8 disk devices (physical or logical) will be shown by the real mode driver when installing the Solaris operating environment. This also limits the number of drives that can be used to boot Solaris. ****************** Other SCSI Devices ****************** SCSI Tape Drives Description The st (SCSI tape) driver replaces the sctp driver on x86 systems and provides the following features: o Full compatibility between Solaris SPARC and Solaris x86 platforms o Stability, robustness, and increased SCSI tape drive support o Field extensible; support for new tapes drives can be added by editing a configuration file (st.conf) o Supports tape control features required by commercial backup software, such as Legato Networker o Supports configurable write buffering (as an option) In addition, significant interoperability testing ensures that tapes written with the sctp driver can be read by the st driver. For a list of supported SCSI tape drives, see Solaris 2.4 x86 Hardware Compatibility List--Solaris Base Server Edition. Device Configuration Preparing for Configuration o If you have a supported SCSI tape drive, no configuration is necessary. o If your tape drive is not on the supported list, you will need to obtain the manufacturer's SCSI command manual (sometimes called an OEM technical manual) that contains information about the SCSI commands that control your particular tape drive. This information is needed to update the /kernel/drv/st.conf file to add support for your drive. Configuring the Device The information that is needed in the /kernel/drv/st.conf file is described in the st(7) manual page. 1. Become root. 2. Edit the file /kernel/drv/st.conf and add the appropriate lines that describe your tape drive. For example, to add an entry for the Hewlett-Packard HP35470A tape drive, the following two lines would be needed: "HP HP35470A", "HP35470A 4mm DAT", "HP70", HP70 = 1,0x34,0,0x1679,1,0x0,0; Note - The format of these lines is described in st(7); the placement of each line is shown in the file /kernel/drv/st.conf. After adding these lines, the /kernel/drv/st.conf file will look similar to this: tape-config-list= "HP HP35470A", "HP35470A 4mm DAT", "HP70", "WANGTEK 5525ES SCSI", "Wangtek 525MB QIC", "WT_5525ES_QIC", "TANDBERG 4100", "Tandberg 4100 QIC", "TANDBERG_4100_QIC", "TANDBERG 4200", "Tandberg 4200 QIC", "TANDBERG_4200_QIC"; HP70 = 1,0x34,0,0x1679,1,0x0,0; WT_5525ES_QIC = 1,0x32,512,0x467a,1,0x00,0; TANDBERG_4100_QIC = 1,0x32,512,0x463a,1,0x00,0; TANDBERG_4200_QIC = 1,0x32,512,0x463a,1,0x00,0; 3. Perform a reconfiguration boot to have your changes take effect: # touch /reconfigure # reboot **************** Network Adapters **************** 3Com EtherLink III (3C5x9, 3C509B) Description The 3Com EtherLink III (3C5x9) controllers are Ethernet controllers for the connectionless Data Link Provider Interface providing multithreaded, loadable STREAMS functionality that can be cloned. The device configuration information for the 3Com EtherLink III has been updated to include information about the 3C509B model. Device Configuration Preparing for Configuration o Configuring the 3C509 (ISA bus) adapter for EISA addressing when installed in an EISA bus system is preferred. This configuration is done by the setup software that comes with the card. o The 3C509B model is configured differently than the other models. The information under "Configuring the Device" applies only to that model. If you are not sure whether you have this model, check the packaging material that comes with your card. The "3C509B" designation should be on the outside of the box, and the network card should be labeled "Rev. B." Configuring the Device The following information applies only to the 3C509B model of the EtherLink III cards. 1. Configure the card to use a specific network interface using the configuration program that is supplied with the card. Do not use the "Auto Select" option of the configuration program. Since the "Auto Select" option is the factory default, the card must always be reconfigured. 2. The Plug and Play option should be disabled. This is particularly important on Plug and Play-capable systems. AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI) Description The Solaris pcn driver supports the PCnet family of Ethernet controllers 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 Avoiding Possible Device Conflicts o If you already have Solaris installed on your system, and after installing this Driver Update you experience network problems with your PCnet-ISA adapter, try disabling the Solaris elink driver. This is done by modifying a system file and rebooting; see "Disabling Drivers After Installing the Driver Update" in Chapter 1 for instructions. o If your system has a PCnet-ISA controller note the configuration of other add-in adapters because the PCnet-ISA controller uses I/O addresses common to many other ISA and EISA adapters. It is particularly important to verify the configuration when installing add-in adapters to a system whose motherboard embeds the AMD chip. Configuring the Device PCnet-ISA Be sure that your PCnet-ISA adapter does not conflict with other adapters configured in the system. The valid parameter settings for PCnet-ISA are listed under "Valid Configurations." PCnet-PCI PCI devices are autoconfigured by the system BIOS. No configuration is necessary. Valid Configurations The following parameters are supported for PCnet-ISA adapters: o IRQ 3, 5, 9, 10, 11 o I/O Address 0x300, 0x320, 0x340, 0x360 Warnings o In some cases, IRQ 4 may be offered as a configuration option for the 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. PCnet-PCI adapters are not affected. o Some versions of the PCnet-PCI chip have known problems which result in unreliable network operation. These chip problems can also cause the system to completely "freeze." Workaround: Unfortunately, there are no known software workarounds. If you encounter these symptoms while using an adapter based on a PCnet-PCI chip, contact the vendor of the adapter to determine if the adapter contains the version of the chip known to exhibit these problems. o (1192044) PCnet doesn't serve rpl requests until snoop is started. Any adapter supported by the Solaris pcn driver will not function as a network installation server unless the snoop command is also run using that adapter. This will be fixed in a future Driver Update. 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 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. o For the NetFlex-2 DualPort ENET, use RJ-45. o For the NetFlex-2 ENET-TR, use DB-15 or 10BaseT RJ-45. Note that the default setting (DB-9) on the NetFlex-2 ENET-TR needs to be changed. 2. Compaq Netflex-2 ENET-TR card only: Configure the Netflex-2 ENET-TR card to use 10 Mb/sec data rate. Note that the default (16 Mb/sec) on the NetFlex-2 ENET-TR needs to be changed. Valid Configurations The following IRQs are valid for this card: o IRQ 3, 5, 9, 10, 11 Warnings Promiscuous mode is not supported by the current release of the firmware for this card. DEC 21040/21140 Ethernet (D-Link DE-530CT, SMC EtherPower 8432BT, SMC EtherPower 8432BTA, Znyx312, Cogent EM960TP, Cogent EM100) Description The Solaris dnet driver supports a large family of Ethernet controllers based on the DEC 21040 and 21140 controller chips. Device Configuration Avoiding Possible Device Conflicts The following paragraphs describe several properties that can be set in the dnet.conf file. In each case the property must be placed within the entry that corresponds to your controller. That entry can be determined by looking at the device file that is created. For example, if the ls -l command returns the following: # ls -l /dev/dnet0 # lrwxrwx 1 root root dnet0 -> ../devices/isa/dnet@78,0:dnet0 the "78" in the entry corresponds to the "reg=0x000078,0,0" entry in the dnet.conf file. For example, if the entry is the following: name="dnet" class="sysbys" intr=1 reg=0x000078,0,0 parent-type="pci" change the entry to the following: name="dnet" class="sysbys" intr=1 reg=0x000078,0,0 bncaui=1 parent-type="pci" o The Solaris dnet driver is configured for optimal performance on today's 10-Mb networks, running in half-duplex mode. When used with a modern 100-Mb hub, 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. Set the bncaui=1 property in the dnet.conf driver configuration file. o Future versions of controllers based on the DEC 21140 will offer a choice between 100-Mb and 10-Mb operation. By default, the dnet driver will operate the controller at 100 Mb. To force 10-Mb operation on one of these controllers, set the mode=10 property in the dnet.conf driver configuration file. Valid Configurations The PCI configuration process varies from system to system. Follow the instructions provided by the vendor. Warnings o The controller will not autoconfigure the network media connector properly. Use the bncaui=1 property in the dnet.conf file to force use of the BNC/AUI connector in this case. o SMC EtherPower (8432BT/8432BTA), Cogent EM960TP/EM960C (TP connector only), Cogent EM100, D-Link DE-530CT, and Znyx EtherAction ZX312 boards have been successfully tested with the dnet driver for network adapters based on the DECchip 21040 Ethernet and DECchip 21140 Fast Ethernet Controllers. Other adapters may work with the dnet driver and additional boards will be tested in the future. However, some boards have failed to work with this driver (for example quad-port boards from Cogent and Znyx), and other boards have exhibited inconsistent behavior (SMC EtherPower 10/100). Support for these and other DECchip-based adapters will be included in future releases of this driver. o The current release of this driver provides 100-Mb Ethernet support; however, the driver will not be able to transfer the data at rates expected of a 100-Mb 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. Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP Description The Intel EtherExpress(TM) 16 is an Ethernet controller for the connectionless Data Link Provider Interface providing multithreaded, loadable STREAMS functionality that can be cloned. Device Configuration Preparing for Configuration When using any version of the EtherExpress 16 adapter, you must use the SOFTSET configuration utility to manually configure the appropriate connector. This DOS program is supplied by the network card manufacturer and is contained on a diskette that comes with the board. Avoiding Possible Device Conflicts The Intel EtherExpress 16 conflicts with the SMC 8013 card. If both the SMC 8013 and Intel EtherExpress 16 cards are installed in your system, data to and from the Intel EtherExpress 16 card will be randomly corrupted. Configuring the Device 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. Warnings o Autodetect is not supported. o On some fast systems, the Solaris iee driver occasionally does not correctly initialize when the system reboots. If this occurs, the network connection will not be usable. Workaround: If this situation occurs, there are two options to get around this problem: 1) reboot the system, or 2) activate the network manually by stopping and then starting the affected iee interface using the ifconfig command. For example, if the iee0 interface fails to start up, log in as the superuser and type the following commands: # ifconfig iee0 down # ifconfig iee0 up Intel EtherExpress PRO Description The Intel EtherExpress PRO is an Ethernet controller for the connectionless Data Link Provider Interface and is used with an ISA bus. Device Configuration Configuring the Device 1. The Intel EtherExpress PRO can be configured to any I/O address that does not conflict with another device. 2. Choose one of the valid IRQ values listed below. 3. For all other settings, use the defaults. Valid Configurations o IRQ 3, 5, 9, 10, 11 (10 is recommended) o I/O Address Any I/O address that does not conflict with another device; 0x300 is recommended Intel EtherExpress PRO/100 (82556) Description The Intel EtherExpress PRO/100 is an Ethernet controller. Both the EISA and PCI 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 by 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. Set your Connector Type to TPE. c. 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, 7, 12, 15 Warnings o Due to hardware restrictions, avoid installing the EISA model of the Intel EtherExpress PRO/100 card on systems with a PCI bus. o (1216921) The Intel EtherExpress PRO/100 card cannot be used as a net install boot server. o (1212022) The Intel EtherExpress PRO/100 card cannot net install at 100 Mb. 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. Workaround: 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 netmask + broadcast + -trailers up o The current release of this driver provides 100-Mb Ethernet support; however, the driver will not be able to transfer the data at rates expected of a 100-Mb 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. Novell NE2000, NE2000plus Ethernet 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 in Table A-1. If you already have the Solaris operating environment running on your system and you want to add support for the NE2000 or NE2000plus adapter, you should not install the adapter until steps have been taken to disable other drivers; see "Enabling Support for the Novell NE2000/NE2000plus After Installing the Driver Update" in Chapter 1. Table A-1 Solaris Drivers and Hardware That Conflict With the NE2000/NE2000plus =============================================================================== Solaris Driver Supported Hardware ------------------------------------------------------------------------------- eepro Intel EtherExpress PRO el 3Com EtherLink II (3C503), EtherLink II/16 (3C503-16) elink 3Com EtherLink 16 (3C507) 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.) 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 "Warnings" 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 Warnings 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 and removing the card no longer causes the system to hang, check the following: o The Solaris software has not been properly configured to support the NE2000/NE2000plus Ethernet driver. See the Caution at the beginning of this Device Reference Page. 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." Novell NE3200 EISA Ethernet Description Novell NE3200 EISA Ethernet controller. Device Configuration Preparing for Configuration o The Novell NE3200 Ethernet card must be installed in an EISA slot. o The media type must be decided before the device is configured. For example, the media type may be BNC (thin wire) or DIX (thick wire). Avoiding Possible Device Conflicts Proper EISA device configuration ensures no conflicts with other devices. Configuring the Device 1. Use the EISA configuration utility on your system to configure the controller. 2. Set the media type to either BNC or DIX. 3. Set the interrupt type to LEVEL TRIGGERED. 4. Choose an IRQ that is not taken by another device. Note that IRQs for ISA devices are not usually displayed in the EISA configuration utility. Valid Configurations All of the EISA configurable parameters are also valid under the Solaris operating environment. As with any device, be wary of interrupt sharing. Warnings o If error messages such as "no such device" are displayed when attempting to access the Ethernet card, the device is probably not configured in the EISA configuration. o (1204642) Some NE3200 clones do not work with level-triggered interrupts. If you install an NE3200 card and your system hangs while trying to configure devices after reboot, it may not work with level-triggered interrupts. Workaround: Use the EISA configuration utility to select an interrupt type of EDGE TRIGGERED instead of LEVEL TRIGGERED. Racal InterLan ES3210/ES3210 TP EISA Ethernet Description The Racal InterLan ES3210 is a 32-bit Ethernet adapter compatible with an EISA-bus. The card comes in two versions: o ES3210 supports standard Ethernet (10Base5) and thin Ethernet (10Base2). o ES3210 TP supports standard Ethernet (10Base5) and unshielded twisted-pair (10BaseT). The ES3210 cards are based on the National 8390 network interface controller. Note - Only the latest revision of the ES3210 is supported--it uses surface- mount technology; the earlier revision does not. The older boards have a white sticker on the back bearing the number 625-0136-00; the newer cards have the number 625-0367-00 or higher. Device Configuration Preparing for Configuration o The Solaris driver for the ES3210/ES3210 TP does not support I/O-mapped I/O. Since this is the default setting for each card ("Shared memory disabled"), it must be changed. An explicit address for the memory area on the board must be configured as described under "Configuring the Device." o The driver currently does not use DMA channels 0-3 since 32-bit burst mode DMA transfers cannot be accomplished on these channels. The driver forcibly uses memory-mapped I/O even when one of these DMA channels is configured. Avoiding Possible Device Conflicts o Check the IRQ levels used by devices on your system. The default setting for the IRQ on this Ethernet adapter is 3, which is typically used by COM2. IRQ 6 is typically used by the diskette controller. o The choices for shared memory on the Racal InterLan ES3210 are C0000, C4000, C8000, CC000, D0000, D4000, D8000, and DC000; however, note that C0000-C3FFF is used by the VGA BIOS, if present. Configuring the Device Use the EISA configuration utility for your system to make the following settings for the ES3210 card: 1. Select the interrupt (IRQ) the card will use. This is done at the "Interrupt Level Select" prompt. Be sure to check this. 2. Set the base address of the ES3210 memory to any available (unused) location. This is done at the "Memory Base Address Selection" prompt. Note - The default setting is "Memory Mapped Disable." The Solaris driver will not work with this setting; you must change it. Be sure that the address you choose is not being used by some other adapter, particularly an ISA adapter. Note that the EISA configuration utility cannot accurately detect conflicts with ISA cards; it relies on information you enter about these devices to determine if conflicts exist. 3. Choose a DMA channel. This is done at the "DMA Channel Select" prompt. If you choose DMA channel 0, 1, 2, or 3, DMA will not be used. Valid Configurations The following parameters are valid for the Racal InterLan ES3210: o IRQ 3, 4, 5, 6, 7, 9, 10, 11, 12, 14, 15 o Memory Base Address 0xC0000, 0xC4000, 0xC8000, 0xCC000, 0xD0000, 0xD4000, 0xD8000, 0xDC000 o DMA Channel Disable, 0, 1, 2, 3, 5, 6, 7 Warnings (1188007) The current release of the Solaris riles driver causes the network performance to degrade considerably when the Ethernet adapter is configured to use a DMA channel of 5, 6, or 7. Even though these values are valid, it is best not to use them. SMC Elite32 Ultra (8232) Description The SMC Elite32 Ultra (8232) board is an EISA based Ethernet controller supporting 10Base-T, AUI, and BNC networks. Although the hardware supports a Bus Master DMA mode of operation, the Solaris drivers do not make use of it. The SMC Elite32 Ultra board is supported by the Solaris smceu driver. Device Configuration Preparing for Configuration o The board is software configured using the EISA configuration utility along with an EISA configuration file supplied with the board by SMC. There are no jumpers on the board. o The configuration utility allows the enabling or disabling of Bus Master Mode. The Solaris drivers do not operate the card in Bus Master Mode even if the mode is enabled. It does not matter which setting is selected by the configuration utility. o You may use the configuration utility to select which Network Connection (Media) Type to use. 10Base-T is always enabled. If your network is AUI or BNC, you must use the configuration utility to ensure that the correct Network Connection Type is selected. o The configuration utility also allows selection of the IRQ and base RAM address used by the board. You must choose values for these settings that do not conflict with other boards in the system. IRQ settings should be edge-triggered. 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 IRQ and memory base address. Ensure that the Network Connection Type is correct for your network. Set the ROM base address to Disabled. Valid Configurations The following parameters are valid for the SMC Elite32 Ultra (8232): o Network Type AUI or BNC; 10Base-T o IRQ 3, 5, 7, 9, 10, 11, 15; Edge o RAM address 0xc0000 to 0xee000, 8K increments o ROM address Disabled The board's I/O address is determined by slot number. Warnings SMC's own EZStart diagnostic hangs when testing the board in a Dell Omniplex 466. The card does work in a Dell Omniplex 590 machine. If in doubt, run the diagnostic provided by SMC. SMC Ether100 (9232) Description The SMC Ether100 (9232) board is an EISA based Ethernet controller supporting both 10Base-T and 100Base-T networks. Although the hardware supports a DMA mode of operation, the Solaris drivers do not make use of it. The SMC Ether100 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 and file supplied by SMC. There are no jumpers on the board. o The board can be configured for either 10 Mb/sec or 100 Mb/sec. Operation at the higher speed using the UTP (Unshielded Twisted Pair) RJ-45 connector requires use of a Category 5 cable. o The 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 Ether100: o Speed 10 Mb/sec or 100 Mb/sec o IRQ 3, 5, 7, 9, 10, 11, 15 o DMA Channel Disabled o ROM Address Disabled The board's I/O address is determined by slot number. The DMA channel and ROM are not used. 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. An updated Solaris smc driver is provided to support the SMC EtherEZ (8416) Ethernet adapter. This updated driver supersedes the existing smc driver and will continue to support the SMC EtherCard Elite16 Ultra (8216) family of ISA bus Ethernet adapters and all the previous SMC/WD 8013 EtherCard PLUS Elite16 and EtherCard PLUS Elite/A families of ISA and Micro Channel architecture Ethernet adapters, and the EtherCard PLUS (8003) family of Ethernet adapters. The same device configuration information supplied for the SMC 8216 and 80x3 network adapters in the x86 Device Configuration Guide is repeated here for your convenience. The one exception is that the SMC EtherEZ (8416) adapter must have the Plug and Play setting disabled using the software setup program. Device Configuration Preparing for Configuration Since memory is shared, it is necessary to disable the motherboard cache in the region where the Ethernet shared memory is mapped. Avoiding Possible Device Conflicts 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, it is essential that NFS system mounts over the 8003 interface 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). o Since Solaris for SPARC has 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. 3. If using the SMC EtherEZ (8416), make sure the Plug and Play mode is disabled using the supplied software setup program. 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 for the procedure. Valid Configurations SMC EtherCard Elite16 Ultra (8216xxx) and SMC EtherEZ (8416xxx) network adapters use software procedures to configure the following: 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 ------------------------------------------------------- Warnings 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 A client desktop computer with an SMC EtherCard PLUS (8003) cannot be booted from a network. *********** Audio Cards *********** Sound Blaster Pro/Sound Blaster 16/Sound Blaster AWE32 Description The Creative Labs Sound Blaster family of audio cards comprises DMA- capable ISA bus plug-in cards that provide 8/16 bit mono/stereo digitized sound recording and playback over a wide range of sampling rates. Each card includes a digital sound processor and mixing capability. 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 audio(7) and sbpro(7). 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. Configuration information for the SCSI-2 interface is maintained in the aic.conf file. See the "Sound Blaster 16 SCSI-2 (SCSI)" Device Reference Page in this appendix for device configuration information for the SCSI controller on this card. Device Configuration Preparing for Configuration For the sbpro driver to successfully operate your Sound Blaster card, it is essential that it be configured properly. Configuration information for the driver is stored in the sbpro.conf file, usually in the directory /platform/i86pc/kernel/drv. As shipped, the sbpro.conf file is configured to support Sound Blaster Pro cards with factory default DMA settings, and Sound Blaster 16 cards with audio IRQ and DMA jumpers. If you have one of the following, you must edit the sbpro.conf file before your Sound Blaster card will operate correctly under the Solaris operating environment: o Sound Blaster Pro card with a nonstandard DMA setting o Sound Blaster 16 card without audio IRQ and DMA jumpers o Sound Blaster AWE32 card The sbpro.conf file must be updated after the Driver Update is installed on your system. See "Enabling Support for Sound Blaster Audio Cards After Installing Solaris Base Server or the Driver Update" or "Enabling Support for Sound Blaster Audio Cards After Installing the Driver Update" in Chapter 1 for instructions. Before beginning configuration, you must know the following information: o What kind of Sound Blaster card is installed in your system? Is it a Sound Blaster Pro, Sound Blaster 16, or Sound Blaster AWE32? 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. o What I/O address is your Sound Blaster card jumpered to? The default setting is I/O address 0x220. o If your card is a Sound Blaster Pro card, you also must know the jumper settings for the interrupt request (IRQ) and the DMA channel. o If your card is a Sound Blaster 16 without audio IRQ/DMA jumpers, or a Sound Blaster AWE32, you must know what IRQ and DMA channels you intend to use with the card. (If you have a Sound Blaster 16 card _with_ IRQ/DMA jumpers, the jumper settings on the card will determine the IRQ and DMA channels to be used.) 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 conflicts, you will have to reconfigure the I/O address jumper setting. o The Sound Blaster card cannot share IRQ settings with any other card installed in your system. If you have a Sound Blaster card, and its hardware- jumpered IRQ setting conflicts with any other device, change the IRQ jumper setting on the Sound Blaster card to one of the valid configurations listed under "Valid Configurations." The most common conflicts occur with the LPT1 parallel port, a serial port, or network card. 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. Configuring the Device Note - Make sure you are setting 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. If the Sound Blaster card's I/O address conflicts with another device, remove the card and change the I/O address according to the manufacturer's instructions. Record the change on your Device Configuration Worksheet. 2. If you have a Sound Blaster Pro card, and the jumpered IRQ conflicts with another device, change the IRQ parameter using the manufacturer`s instructions. Record the change on your Device Configuration Worksheet. 3. If you have a Sound Blaster Pro card, and the jumpered DMA channel conflicts with another device, change the DMA parameter using the manufacturer's instructions. If you change the DMA channel, you must also update the entry in the sbpro.conf file _after_ Driver Update 9 is installed on your system. Record the change on your Device Configuration Worksheet. 4. If you have a Sound Blaster 16 card without audio IRQ/DMA jumpers, or a Sound Blaster AWE32 card, you must specify the dma-channels property in the sbpro.conf file after Driver Update 9 is installed. The sbpro.conf file that gets installed with Driver Update 9 contains detailed instructions and examples. Record the change on your Device Configuration Worksheet. Be sure that the specified IRQ and DMA channel do not conflict with any other device on the system. 5. If you have a Sound Blaster 16 SCSI-2 and you intend to use the SCSI interface, you may have to set the jumper that controls the SCSI I/O address. See the "Sound Blaster 16 SCSI-2 (SCSI)" Device Reference Page for additional configuration information regarding the SCSI-2 interface of the Sound Blaster 16 SCSI-2 card. 6. Record any change in IRQ setting or DMA channel on your Device Configuration Worksheet. If you have a Sound Blaster Pro card with a nonstandard DMA setting, or if you have a Sound Blaster 16 card without audio IRQ/DMA jumpers, or a Sound Blaster AWE32 card, you must edit your sbpro.conf file before your Sound Blaster card will operate correctly under the Solaris operating environment. This must be done after Driver Update 9 is installed on your system. See "Enabling Support for Sound Blaster Audio Cards After Installing Solaris Base Server or the Driver Update" or "Enabling Support for Sound Blaster Audio Cards After Installing the Driver Update" in Chapter 1 for instructions. Valid Configurations The possible settings for the Sound Blaster cards are listed here. Defaults are _underlined_. Sound Blaster Pro: o I/O Address _0x220_, 0x240 o IRQ 2, _5_, _7_, 10 o DMA Channel 0, _1_, 3 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 ports: o I/O Address 0x140, _0x340_ o IRQ _11_ o DMA Channel 0, 5, 6, 7 (not used) Warnings o Under the Solaris sbpro driver, output volume is controlled by software. Be sure the volume thumbwheel on the back of the card is turned all the way up 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, you should convert it to stereo using an appropriate adapter. o (1166385) The driver currently does not distinguish between a Sound Blaster 16 card and a Sound Blaster AWE32 card. It will report both of them 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. **************** PC Card Hardware **************** PC Card Adapters Description PC Card (PCMCIA) adapters, such as the Intel i82365SL, Vadem VG365/VG465/VG468/VG469, Cirrus Logic PD6710/PD6720, Ricoh RF5C366, and Toshiba support up to eight Type I, II, or III sockets. Device Configuration Preparing for Configuration o Other adapters that use chips based on the Intel i82365SL design may also be supported. See Solaris 2.4 x86 Hardware Compatibility List for supported systems. o If you have an add-on PC Card adapter, install it on your system prior to Solaris installation. o Some notebook computers have their built-in PC Card adapter disabled by default. Enable it prior to Solaris installation. o If your system has a supported PC Card adapter configured at a known address, it should be recognized automatically. No manual configuration should be necessary. o Requirements for a system depend on the combination of devices to be used. A typical two-socket notebook computer needs at least 8 Kbytes of address space, 16 bytes of I/O space, and three free IRQs. Following are general guidelines: =============================================================================== Address At least 8 Kbytes are required with 4 Kbytes per socket space in the 640K-1MB range (not necessarily contiguous); if you have three sockets, at least 12 Kbytes are needed I/O space At least 8 and preferably 16 bytes per socket IRQs One per socket, plus an IRQ for the pcic device driver, itself =============================================================================== Configuring the Device Initial Installation and Configuration 1. Consult your Device Configuration Worksheet for address space, I/O space, and IRQs already used by system devices. 2. Insert the PC Card adapter. 3. Install Solaris x86, including the PCMCIA packages in the SUNWpcmc cluster. o If you choose to install the Entire Distribution, the PCMCIA packages are automatically included. After installation, the next reboot will automatically perform the necessary reconfiguration. o If you choose any other distribution, such as the End User Distribution, select Customize from the choices at the bottom of the Software Selection screen. Then choose PCMCIA Support from the scrolling list on the Customize Software screen. After installation, the next reboot will automatically perform the necessary reconfiguration. 4. Reboot the system. Adding PC Card Support to a Previously Installed System If you are adding PC Card support via a Driver Update, refer to "Installing the PC Card Driver Update" in the Driver Update Guide. To add PC Card support to a previously installed system, do the following: 1. Become root. 2. Use the pkgadd command and select PCMCIA Support from the Customize Software screen. 3. Do a reconfiguration reboot so that the pcmcia software automatically allocates resources: # touch /reconfigure # reboot 4. Insert the PC Card adapter and turn on the machine. 5. Do a second reboot so that the PC Card device driver begins running with the new resources allocated. Configuring PC Card Adapters The Solaris PC Card nexus driver automatically allocates address space, I/O ports, and IRQs to new cards when they are inserted. To do this, the nexus driver must have sufficient free resources and recognize what resources are already used by other drivers. o During installation of the PC Card software, a system initialization script maps out the resources used by all the other devices in the system. Resources not known to be used by another driver are assumed free for use by PC Card drivers. Note - If you are using a notebook with a docking bay, keep the notebook in the docking bay during the installation of the PC Card software. This ensures that the system can identify the resources used by cards in the docking bay. o Reconfiguration usually works automatically, but some machines may require that you provide information about resources already allocated. Three cases have been encountered: o Case 1: Some device drivers do not export properties describing the resources they use, so an automatic scan cannot determine what resources are allocated to those drivers. This situation is detected automatically by the scan, and the script prints out a warning message and request for manual assistance. See "Correcting Possible Conflicts" later in this Device Reference Page. o Case 2: Some machines may have devices for which no Solaris driver exists, and this can't be detected automatically. You will have to enter the descriptions of their resource requirements manually. o Case 3: Some machines may have reserved additional ports, memory, or IRQs that are not detected by the automatic scan. In cases like these, the PC Card software may appear to configure properly, but some PC Card devices may simply not work (because they are sharing resources with other hardware). For example, some notebooks reserve an IRQ for power management use. In a case like this, read through the hardware documentation that accompanies the machine. PC Card Resource Configuration Information The resources available for PC Card devices are defined by three properties in the pcic.conf file: =============================================================================== res-irq This property should be a complete list of the IRQ levels available for use by the pcic driver. For example, if IRQ levels 3, 9, and 15 are available, they are listed as: res-irq=3,9,15 Each PC Card I/O device that needs an interrupt is assigned a different IRQ, and the PC Card adapter uses one IRQ level. In this example, only two I/O PC Card devices can be used at the same time. res-memory This property is a list of memory base and length pairs. The length is in number of 4-Kbyte pages available. For example, if there are two blocks of memory available, one starting at 0xcc000 with 8 pages available and another at 0xd0000 with 4 pages available, the property is set up as: res-memory=0xcc000,0x8,0xd0000,0x4 Many notebook computers have all the memory between 0xcc000 and 0xeffff available: res-memory=0xcc000,0x14 If the notebook computer is to be used in a docking bay, be sure that the configuration also accounts for any devices installed in it. res-ioaddr This property, like the res-memory property, is a list in bytes, and the base address refers to I/O space. For example, if 32 bytes of I/O space are available at 0x200 and 16 bytes are available at 0x300, the property is listed as: res-ioaddr=0x200,Ox32,0x300,0x16 =============================================================================== If the available resources recorded by the PC Card software in the /kernel/drv/pcic.conf file include a resource that is actually in use by other devices in the system, you must manually edit the file to remove them. See "Correcting Possible Conflicts" below. Note - Anytime the pcic.conf file is modified, you must reboot the system for the changes to take effect. Correcting Possible Conflicts When the PC Card software cannot automatically determine which resources are available, information must be added to the /kernel/drv/pcic.conf file to identify the unavailable resources. The resources available for PC Card devices are defined by the res-irq, res-memory, and res-ioaddr properties. 1. To include information about unavailable resources, edit the /kernel/drv/pcic.conf file and add #exclude: lines. a. Each line that describes a set of reserved resources must begin with #exclude:. b. Non-blank characters after the colon are treated as a comment and ignored. For example, the string "pm" in the example below shows that you are disabling IRQ 15 because of a conflict with the Power Management resource. c. The next field should specify the res-irq, res-memory, or res-ioaddr property. See pcic(7). d. For res-irq lines, the following field should be a decimal IRQ number. For example, if a notebook computer uses IRQ 15 for Power Management, you can exclude IRQ 15 by adding the following line: #exclude:pm res-irq 15 The PC Card software would then know that IRQ 15 is not available for use by PC Card devices. e. For res-memory and res-ioaddr lines, the next two fields should be a hexadecimal base and byte count. The leading 0x should not be used. For example, if the smc device driver does not identify allocated resources automatically, add the following lines to the pcic.conf file: #exclude:smc res-irq 3 #exclude:smc res-ioaddr 280 10 #exclude:smc res-memory dc000 2000 The #exclude: lines identify IRQ 3, ports Ox280-28F, and addresses 0xDC000-0xDDFFF as unavailable for PC Card device use. 2. Reboot the system. # reboot Note - This example shows #exclude: lines identifying resources that are unavailable to PC Card devices. Changing the Default IRQ The optional (smi) property can be defined in the /kernel/drv/pcic.conf file. If specified, the smi property overrides the default IRQ level, used by the pcic driver. By default, the second to the last IRQ in the res-irq list is used. If that value is unusable, specify the IRQ level in the smi property. 1. Become root. 2. To override the default IRQ level for the pcic driver, edit the /kernel/drv/pcic.conf file and add a line that contains `smi='. (Be sure to add this line before the ; character in the file.) For example, to change to IRQ 9, add the following line to pcic.conf: smi=9 3. Reboot the system. # reboot Note - This example shows a resource being made available to the PC Card devices. Known Problems and Limitations Warning - The following problem has occurred on machines using the Vadem VG469 PC Card adapter chip. To avoid the problem, ground yourself by touching some metal on the computer case while inserting and removing the PC Card devices. o Sometimes the PC Card adapter will cause the machine to lock up. The prtconf command output may indicate that the device is in two sockets after a card is inserted in one socket. Subsequent card insertion and removal may not be detected, and the machine locks up. The machine must then be reset or power cycled. 3Com EtherLink III (3C589) PC Card Description The 3Com EtherLink III (3C589) PC Card device is a credit-card-like form factor Ethernet adapter. Device Configuration Preparing for Configuration o It is not possible to boot or install the Solaris operating environment using a 3Com EtherLink III PC Card device. o If the 3Com PC Card device is recognized, the pcelx driver will be automatically loaded, ports and IRQs will be automatically allocated, and the special files will be automatically created (if they don't already exist). o No manual configuration of the hardware is necessary or possible. Configuring the Device Initial Installation and Configuration 1. Install Solaris x86, including the PCMCIA packages in the SUNWpcmc cluster or from a PC Card Driver Update. 2. Boot the system. 3. Insert the 3Com EtherLink III PC Card device. Identifying an Unrecognized Card If you insert a 3C589 card and it isn't recognized (no special files created), use the prtconf command to try to identify the problem. 1. Run the prtconf command to see if your 3C589 card is recognized. A recognized device will appear at the end of the prtconf output. For example: # prtconf . . . pcmcia, instance #0 pcelx, instance #0 2. If pcelx does not appear in the prtconf output, there is a problem with the PC Card adapter configuration or with the hardware. Check to see whether the problem is with the card or the adapter by trying to use the card on another machine and by seeing if it works on the same machine using DOS. Installing and Configuring Additional Network Cards Because the 3C589 card is not supported during Solaris installation, you must update network configuration files before it can be used as a network interface. 1. Create a /etc/hostname.pcelx# file (where # is a socket number) to specify the host name to be associated with this interface. 2. Add an IP address for the new host name to the file /etc/inet/hosts. 3. Ensure that the associated network is listed in /etc/inet/netmasks. 4. Ensure that the Name Service Switch /etc/nsswitch.conf configuration file includes the network and local services you need. 5. Reboot the system. Note - This process is described in TCP/IP Network Administration Guide. Special Files Device naming in /dev follows standard LAN device naming except that the PPA (Physical Point of Attachment) unit number is the socket where the card resides, not the instance. That is, for the pcelx driver, /dev/pcelx0 (or PPA 0 of /dev/pcelx) is the card in socket 0, while a card in socket 1 is /dev/pcelx1 (or PPA 1 of /dev/pcelx). See pcelx(7). Hot-Plugging If you remove the 3C589 card, any information you send is discarded, and no error messages are given. When you reinsert the card in the same socket, the device operates normally. The behavior is similar to temporarily disconnecting the device from the network. Known Problems and Limitations o Network services are automatically started when a system is booted. These services are not started when a network interface is added or shut down after the system has been brought up. o On some systems, a 3Com EtherLink III PC Card Ethernet adapter can only be used in socket 0 and will not work if removed and plugged into another socket. This problem can be avoided by always plugging in your PC Card Ethernet adapter into socket 0. 3Com EtherLink III (3C589) PC Card Description The 3Com EtherLink III (3C589) PC Card device is a credit-card-like form factor Ethernet adapter. Device Configuration Preparing for Configuration o It is not possible to boot or install the Solaris operating environment using a 3Com EtherLink III PC Card device. o If the 3Com PC Card device is recognized, the pcelx driver will be automatically loaded, ports and IRQs will be automatically allocated, and the special files will be automatically created (if they don't already exist). o No manual configuration of the hardware is necessary or possible. Configuring the Device Initial Installation and Configuration 1. Install Solaris x86, including the PCMCIA packages in the SUNWpcmc cluster or from a PC Card Driver Update. 2. Boot the system. 3. Insert the 3Com EtherLink III PC Card device. Identifying an Unrecognized Card If you insert a 3C589 card and it isn't recognized (no special files created), use the prtconf command to try to identify the problem. 1. Run the prtconf command to see if your 3C589 card is recognized. A recognized device will appear at the end of the prtconf output. For example: # prtconf . . . pcmcia, instance #0 pcelx, instance #0 2. If pcelx does not appear in the prtconf output, there is a problem with the PC Card adapter configuration or with the hardware. Check to see whether the problem is with the card or the adapter by trying to use the card on another machine and by seeing if it works on the same machine using DOS. Installing and Configuring Additional Network Cards Because the 3C589 card is not supported during Solaris installation, you must update network configuration files before it can be used as a network interface. 1. Create a /etc/hostname.pcelx# file (where # is a socket number) to specify the host name to be associated with this interface. 2. Add an IP address for the new host name to the file /etc/inet/hosts. 3. Ensure that the associated network is listed in /etc/inet/netmasks. 4. Ensure that the Name Service Switch /etc/nsswitch.conf configuration file includes the network and local services you need. 5. Reboot the system. Note - This process is described in TCP/IP Network Administration Guide. Special Files Device naming in /dev follows standard LAN device naming except that the PPA (Physical Point of Attachment) unit number is the socket where the card resides, not the instance. That is, for the pcelx driver, /dev/pcelx0 (or PPA 0 of /dev/pcelx) is the card in socket 0, while a card in socket 1 is /dev/pcelx1 (or PPA 1 of /dev/pcelx). See pcelx(7). Hot-Plugging If you remove the 3C589 card, any information you send is discarded, and no error messages are given. When you reinsert the card in the same socket, the device operates normally. The behavior is similar to temporarily disconnecting the device from the network. Known Problems and Limitations o Network services are automatically started when a system is booted. These services are not started when a network interface is added or shut down after the system has been brought up. o On some systems, a 3Com EtherLink III PC Card Ethernet adapter can only be used in socket 0 and will not work if removed and plugged into another socket. This problem can be avoided by always plugging in your PC Card Ethernet adapter into socket 0. SRAM and DRAM PC Card Devices Description A wide range of PC Card (PCMCIA) SRAM (Static RAM) and DRAM (Dynamic RAM) devices is supported. Flash RAM devices are not supported. Device Configuration Preparing for Configuration o If a PC Card memory device is recognized, the pcram device driver is automatically loaded, the physical address allocated, and special files created (if they do not already exist). o No manual configuration is necessary or possible. Configuring the Device Initial Installation and Configuration 1. Install Solaris x86, including the PCMCIA packages in the SUNWpcmc cluster or from a PC Card Driver Update. 2. Boot the system. 3. Insert the card. Identifying an Unrecognized Device If you insert a memory device and it isn't recognized (no special files created), use the prtconf command. 1. Run the prtconf command to display the configuration recognized by the system. A recognized device will appear at the end of the prtconf output. For example: # prtconf . . . pcmcia, instance #0 pcmem, instance #0 pcram, instance #0 2. If your memory device does not appear in the prtconf output, it is not supported and cannot be used with the pcram device driver. Special Files The special files created for PC Card memory devices act like disks and have names in the form /dev/dsk/c#t#d#p# or /dev/dsk/c#t#d#s# (See pcram(7)). These are described below: c# controller # t# card technology type #, defined as follows: 0 Null-no device 1 ROM 2 OTPROM (One Time PROM) 3 UV EPROM 4 EEPROM 5 Flash EPROM 6 SRAM 7 DRAM d# device region of type #, usually zero p# fdisk partition # s# Solaris slice # Note - A device name can be specified either by a partition name (p#) or a slice name (s#), but not both. Using PC Card Memory Devices Since the Solaris Volume Management software recognizes PC Card memory devices, no special vold configuration is required. * If you do not want to use vold to manage your PC Card memory devices, comment out the "use pcmem" line in the /etc/vold.conf file. To comment out a line in /etc/vold.conf, add a # character to the beginning of the line. PC Card memory devices don't need to have file systems on them, though typically, before using a new PC Card memory card, you will want to create a file system on it. DOS PCFS is the best format to use. Although you can use virtually any file system format on a PC Card memory card, most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. See "Using PCMCIA Cards" in Appendix G of Solaris User's Guide. Note - If you want to redirect the output of a tar command (or dd or cpio) to a PC Card memory device, you must first create a file system on the card, using the fdformat command without arguments. The card will need to be reformatted before it can be written on again. Hot-Plugging If a memory card is removed while in use, the device driver returns errors until a memory card is inserted into the appropriate socket. The device needs to be closed and then reopened with the card reinserted in order to get it working again. If you removed the card while it was in use as a file system, unmount the file system with the umount command. Then reinsert the card and remount the file system with the mount command. If you interrupt a tar or cpio process by removing the card, you must stop the process, reinsert the card in the socket, and then restart the process. Known Problems and Limitations o The Solaris pcmem driver in this release is not capable of handling "combo" memory cards with multiple types of memory on them (for example, combined SRAM and nonvolatile FLASH). Inserting such a card into a system running the Solaris software may cause a system panic. Fortunately, most PC Card RAM adapters do not contain multiple memory technologies. o Because the PC Card memory device is designed as a pseudo-floppy diskette type, the only utility that can be used for formatting is fdformat(1). Copyright 1995 Sun Microsystems Inc. Tous droits réservés. 2550 Garcia Avenue, Mountain View, Californie 94043-1100 U.S.A. Copyright 1993-1995 X Inside Incorporated. Tous droits réservés. Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l'utilisation, la copie, et la décompliation. Aucune partie de ce produit ou de sa documentation associée ne peuvent Être reproduits sous aucune forme, par quelque moyen que ce soit sans l'autorisation préalable et écrite de Sun et de ses bailleurs de licence, s'il en a. Des parties de ce produit pourront etre derivees du système UNIX(R), licencié par UNIX System Laboratories, Inc., filiale entierement detenue par Novell, Inc., ainsi que par le système 4.3. de Berkeley, licencié par l'Université de Californie. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fourmisseurs de Sun. LEGENDE RELATIVE AUX DROITS RESTREINTS: l'utilisation, la duplication ou la divulgation par l'administration americaine sont soumises aux restrictions visées a l'alinéa (c)(1)(ii) de la clause relative aux droits des données techniques et aux logiciels informatiques du DFARS 252.227-7013 et FAR 52.227-19. Le produit décrit dans ce manuel peut Être protégé par un ou plusieurs brevet(s) americain(s), etranger(s) ou par des demandes en cours d'enregistrement. MARQUES Sun, Sun Microsystems, SunSoft, Solaris, SunOS, OpenWindows, DeskSet, ONC, ONC+, et NFS sont des marques deposées ou enregistrées par Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays. UNIX est une marque enregistrée aux Etats-Unis et dans d'autres pays, et exclusivement licenciée par X/Open Company Ltd. OPEN LOOK est une marque enregistrée de Novell, Inc. PostScript est une marque d'Adobe Systems, Inc. Intel, EtherExpress, and Pentium sont des marques deposées ou enregistrées par Intel Corporation. Toutes les marques SPARC sont des marques deposées ou enregitrées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits portant les marques sont basés sur une architecture développée par Sun Microsystems, Inc. Les utilisateurs d'interfaces graphiques OPEN LOOK(R) et Sun(TM) ont été développés par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnait les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d'utilisation visuelle ou graphique pour l'industrie de l'informatique. Sun détient une licence non exclusive de Xerox sur l'interface d'utilisation graphique, cette licence couvrant aussi les licenciés de Sun qui mettent en place OPEN LOOK GUIs et qui en outre se conforment aux licences écrites de Sun. Le système X Window est un produit du 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 REPONDRE A UNE UTILISATION PARTICULIERE OU LE FAIT QU'ILS NE SOIENT PAS CONTREFAISANTS DE PRODUITS DE TIERS. CETTE PUBLICATION PEUT CONTENIR DES MENTIONS TECHNIQUES ERRONEES OU DES ERREURS TYPOGRAPHIQUES. DES CHANGEMENTS SONT PERIODIQUEMENT APPORTES AUX INFORMATIONS CONTENUES AUX PRESENTES. CES CHANGEMENTS SERONT INCORPORES AUX NOUVELLES EDITIONS DE LA PUBLICATION. SUN MICROSYSTEMS INC. PEUT REALISER DES AMELIORATIONS ET/OU DES CHANGEMENTS DANS LE(S) PRODUIT(S) ET/OU LE(S) PROGRAMME(S) DECRITS DANS DETTE PUBLICATION A TOUS MOMENTS.