Solaris 2.4(TM) x86 Driver Update 7 Guide 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. Part No: 802-4056-10 SunSoft Revision A, July 1995 A Sun Microsystems, Inc. Business Copyright (c) 1995 Sun Microsystems, Inc. All rights reserved. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A. Copyright (c) 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 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, Solaris PEX, SunOS, OpenWindows, DeskSet, ONC, ONC+, NFS, Wabi, XGL, and XIL are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and may be protected as trademarks in 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 and Display PostScript are trademarks of Adobe Systems, Inc. 3Com and EtherLink are registered trademarks of 3Com Corporation. Adaptec and AHA are trademarks or registered trademarks of Adaptec, Inc. AMD, PCnet , PCscsi and PCnet-SCSI are trademarks or registered trademarks of Advanced Micro Devices, Inc. AST is a registered trademark of AST Research, Inc. ATI, GRAPHICS ULTRA+, GRAPHICS ULTRA PRO, Mach32, Mach64, and WINTURBO are trademarks or registered trademarks of ATI Technologies, Inc. BocaBoard is a trademark of Boca Research, Inc. RAMDAC is a trademark of Brooktree Corporation. BT-542B, BT-545C, BT-545S, BT-742A, and BT-747S are registered trademarks of BusLogic Inc. Compaq, ProSignia, ProLiant, Systempro, and QVision are trademarks or registered trademarks of Compaq Computer Corporation. CompuServe is a service mark of CompuServe Incorporated. Sound Blaster, Sound Blaster 16, and Sound Blaster AWE32 are trademarks of Creative Technology Ltd. Dell is a registered trademark of Dell Computer Corporation. Stealth 32, Stealth 64, Viper Pro, Viper SE, and Viper VLB are trademarks of Diamond Computer Systems, Inc. DECpc is a trademark of Digital Equipment Corporation. DPT is a registered trademark of Distributed Processing Technology. EtherExpress, Intel, and Pentium are trademarks or registered trademarks of Intel Corporation. Intergraph is a registered trademark of Intergraph Corporation. IBM, Micro Channel, and PS/2 are registered trademarks of International Business Machines Corporation. IslandPaint is a registered trademark of Island Graphics Corporation. Matrox, MGA, MGA Impression, and MGA Impression Plus are trademarks or registered trademarks of Matrox Electronic Systems Ltd. NCR and SDMS are trademarks or registered trademarks of NCR Corporation. MultiSpin and NEC are registered trademarks of NEC Technologies, Inc. Versa is a trademark of NEC Corporation or its subsidiaries. Novell is a registered trademark of Novell, Inc. TRADEMARKS (Continued) Number Nine, #9GXE64, #9GXE64 Pro, #9GXE, and Imagine 128 are trademarks of Number Nine Computer Corporation. Quantum Empire is a trademark of Quantum Corporation. Orchid and Kelvin 64 are trademarks of Orchid Technology. InterLan is a registered trademark of Racal InterLan. Sony is a registered trademark of Sony Corporation. EtherCard, EtherCard PLUS Elite/A, EtherCard Elite16 Ultra, EtherEZ, and SMC are trademarks or registered trademarks of Standard Microsystems Corporation. LIGHTSPEED VL is a trademark of STB Systems, Inc. Toshiba is a registered trademark of Toshiba Corporation. Trantor, T348, and MiniSCSI Plus are trademarks or registered trademarks of Trantor Systems Ltd. TVGA is a registered trademark of Trident Microsystems Inc. ViewSonic is a registered trademark of ViewSonic. All other product, service, or company names mentioned herein are claimed as trademarks and trade names by their respective companies. All SPARC trademarks, including the SCD Compliant Logo, are trademarks or registered trademarks of SPARC International, Inc. in the United States and may be protected as trademarks in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK(TM) 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 GUI's 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. =================THIS PAGE LEFT BLANK ============================= Contents -------- About This Book xi 1. Solaris 2.4 x86 Driver Update 7 1 What's New? 2 New Device Drivers (SCSI HBA, SCSI Tape, Network) 2 New Video Support 4 PCMCIA Drivers 6 Driver Update Contents 6 Driver Update Boot Diskette 7 Driver Update Distribution Diskette 7 Driver Update Distribution (Video) Diskettes 11 Driver Update Distribution (PCMCIA) Diskette 12 Solaris 2.4 Driver Update 7 Release Notes 12 Solaris 2.4 x86 Jumbo Kernel Patch 12 Modifying the Solaris Driver Update Boot Diskette 12 Support for More Than Four Serial Ports 14 v How to Choose a Boot Disk 15 Known Problems 16 Installing Solaris Using the Driver Update Diskettes 16 Enabling Support for Sound Blaster Audio Cards After Installing Solaris 18 Adding New Drivers After Solaris Is Installed 19 Enabling Support for the Novell NE2000/NE2000plus After Installing the Driver Update 21 Disabling Drivers After Installing the Driver Update 22 Replacing a Network Card 24 Enabling Support for Sound Blaster Audio Cards After Installing the Driver Update 24 2. Solaris 2.4 x86 Driver Update 7 Video 27 Driver Update Video Contents 27 Driver Update Video Release Notes 32 Installing Driver Update Video 34 Configuring Secondary Displays 38 Known Problems 39 3. Solaris 2.4 x86 Driver Update 7 PCMCIA Support 45 PCMCIA Driver Update Contents 45 Understanding PCMCIA Hardware 46 Configuring PCMCIA Devices 47 Configuring the PCMCIA Controller 47 Hot-Plugging PCMCIA Cards 47 Installing PCMCIA Driver Update 49 vi PCMCIA Release Notes 50 Adding a PCMCIA Network Card 50 Using PCMCIA Memory Cards 51 Known Problems 52 Troubleshooting PCMCIA Device Configuration 53 A. Device Reference Pages 55 Part 1 -IDE Interface IDE Disk and CD-ROM Interface 59 Part 2 -SCSI Host Bus Adapters Adaptec AIC-6360/AHA-1522A/AHA-1520A/AHA-1510A/ AHA-1530P/1532P 62 Sound Blaster 16 SCSI-2 (SCSI) 62 Adaptec AIC-7870/AIC-7871/AIC-7872/AHA-2940/AHA-3940 PCI HBAs 67 AMD PCscsi, PCscsi II, PCnet-SCSI PCI HBAs 69 BusLogic SCSI HBAs 70 Compaq SMART SCSI Array Controller 74 DPT PM-2011/PM-2021 ISA HBAs 75 DPT PM-2012B EISA HBA 77 DPT PM-2022/PM-2122/PM-3222 EISA HBAs 79 DPT PM-2024/PM-2124/PM-3224 PCI HBAs 82 IBM DMC960 RAID Micro Channel HBAs (IBM SCSI-2 RAID, IBM SCSI-2 Fast/Wide Streaming-RAID Adapter/A) 84 IBM Micro Channel SCSI-2 Fast/Wide Adapter/A 86 Mylex DAC960P PCI Controller 88 vii NCR 53C710 (Siemens Nixdorf PCE-5S SCSI) 90 NCR 53C8xx PCI SCSI HBA (53C810, 53C815, 53C820, 53C825) 91 Trantor T348 MiniSCSI Plus Parallel HBA 93 Tricord Systems Intelligent SCSI Subsystem (ISS) HBA 95 Part 3 -Other SCSI Devices SCSI Tape Drives 97 Part 4 -Network Adapters 3Com EtherLink III (3C5x9, 3C509B) 100 AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI) 101 Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR EISA Controllers 103 Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP 105 Intel EtherExpress PRO 107 Novell NE2000, NE2000plus Ethernet 108 Novell NE3200 EISA Ethernet 112 Racal InterLan ES3210/ES3210 TP EISA Ethernet 114 SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS Elite16, EtherCard PLUS (8416, 8216, 8013, 8003) 116 Part 5 -Audio Cards Sound Blaster Pro/Sound Blaster 16/Sound Blaster AWE32 120 Part 6 -PCMCIA Hardware PCMCIA Controllers 126 PCMCIA 3Com EtherLink III (3C589) Card 130 PCMCIA Modem and Serial Cards 132 PCMCIA SRAM and DRAM Devices 135 viii B. Supplementary Video Information 139 Determining Resolution and Color Depth 139 Supported Diamond Viper (P9000) Monitor Configurations 140 Supported Intergraph G91 Monitor Configurations 141 ix =======THIS PAGE LEFT BLANK ========================== About This Book --------------- This document provides information about x86 hardware devices that are now supported on the Solaris(TM) 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, Video, 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, the "Driver Update Video Contents" section in Chapter 2, and the "PCMCIA Driver Update Contents" section in Chapter 3, 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. Typographic Conventions ----------------------- o Book titles are enclosed between the underscore character "_"; for example, _x86 Device Configuration Guide_. o Variables are shown between the "<>" characters; for example, cd /var/sadm/ xi 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 the _x86 Device Configuration Guide_. This document assumes you have fully read and understood that guide; Appendix A, "Device Reference Pages," in this document is an addendum to that guide. Likewise, the installation instructions for this Driver Update are very brief and serve only to supplement the instructions found in _x86: Installing Solaris Software_. 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 2.4 x86 Driver Update 7," provides information about what is new in this release and how to install it. Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video," provides information about the contents, installation instructions, and known problems for the video support in this Driver Update. Chapter 3, "Solaris 2.4 x86 Driver Update 7 PCMCIA Support," provides information about the contents, installation instructions, and known problems for the PCMCIA 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. Appendix B, "Supplementary Video Information," provides additional information about the video support in this release. xii Related Books ------------- You may need to refer to the following books when installing the Driver Update: o _x86 Device Configuration Guide_ Describes how to configure x86 devices before installing Solaris software. o _x86: Installing Solaris Software_ Describes how to install the Solaris software on x86 systems. o _Solaris 2.4 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_ Contains a list of supported hardware on Solaris 2.4 x86 systems. How to Obtain the Solaris 2.4 x86 Hardware Compatibility List ------------------------------------------------------------- The Solaris 2.4 x86 Hardware Compatibility List is updated monthly and available from the following sources: o email o ASCII version-Send electronic mail to x86hcl@Sun.COM. o PostScript(TM) version-Send electronic mail to x86hcl.ps@Sun.COM. o CompuServe(SM)-Type `go sunsoft` and go to the Solaris x86 library. o The WWW (http://access1.Sun.COM)-Click on "SunSoft's Support Resolutions Answer Center," select "Solaris," and then click on "x86 Hardware Compatibility List." o ASK-IT-SunSoft's Automated Support Fax-on-Demand Service o In North America, call 1-800-SUNSOFT, and use prompts 4, 1, 1, respectively. You can also call (310) 348-6219 and choose option 1. o In locations other than North America, use the following numbers to request this document: Singapore 65-733-3405 Taiwan 886-2-719-8069 Japan 03-5717-2560 United Kingdom 44-1494-510981 xiii How to Obtain Driver Updates ---------------------------- This Driver Update is posted on: o CompuServe-Type `go sunsoft` and go to the Solaris x86 Library. o FTP-Use anonymous FTP to access: o ftp.uu.net, then go to /vendor/sun/sun-doc/x-86-driver/2.4 o sunsite.unc.edu, then go to /pub/sun-info/solaris-x86/sunsoft-drivers o WWW o Open URL http://access1.Sun.COM and click on "SunSoft's Support Resolutions Answer Center," select "Solaris," and then click on "x86 Driver Information." o Open URL http://sunsite.unc.edu/pub/sun-info/solaris-x86/sunsoft-drivers How to Obtain Technical Support ------------------------------- To obtain technical support in North America, customers should call 1-800-SUNSOFT and choose option 4. Outside North America, contact your local Support provider. xiv 1. Solaris 2.4 x86 Driver Update 7 ----------------------------------- Solaris 2.4 x86 Driver Update 7 adds new support for SCSI host bus adapters, the IDE interface, network adapters, audio cards, a new SCSI tape driver, video display adapters, 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 Video and PCMCIA. Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video," contains additional information and installation instructions for the video display support in this release. Chapter 3, "Solaris 2.4 x86 Driver Update 7 PCMCIA Support," contains additional information and installation instructions for the PCMCIA device support in this release. 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." 1 What's New? ----------- New Device Drivers (SCSI HBA, SCSI Tape, Network) ------------------------------------------------- Table 1-1 lists the new and updated device drivers in Solaris 2.4 x86 Driver Update 7 that contain new functionality not included in previous Driver Updates. For a complete list of drivers included in this release, see Table 1-5 on page 8. Table 1-1 New and Updated Drivers in This Driver Update ===================================================================== SCSI HBA Drivers ---------------- adp Updated driver to add support for the Adaptec(R) AHA(TM)-3940 and AHA-3940W host bus adapters, and motherboards that integrate multiple Adaptec AIC-7870 controller chips (See Note Below) csa New driver for the Compaq(R) 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(R) PM-2024 and PM-2124 PCI host bus adapters, and the PM-3222 and PM-3224 SCSI RAID adapters iss New driver for the Tricord Systems Intelligent SCSI Subsystem Controllers mlx Updated driver to add support for the Mylex DAC960P PCI host bus adapter pcscsi New driver for the 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 SCSI Tape Driver ---------------- st SCSI tape target driver Network Drivers --------------- nfe New Ethernet driver for the Compaq NetFlex-2 DualPort ENET and NetFlex-2 ENET-TR Controllers ========================================================================== 2 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, please contact SunSoft Technical Support. Corrections to Known Problems ----------------------------- Updated versions of the following six drivers are included in this distribution to correct some known problems. Table 1-2 Updated Drivers to Correct Known Problems ======================================================= eepro Intel EtherExpress Pro eha Adaptec AHA-174x EISA HBAs esa Adaptec AIC-7770/AHA-274x/AHA-284x mcis IBM Micro Channel HBA pcn AMD PCnet-ISA/PCnet-PCI Ethernet ======================================================== 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 7: 101936-06, 101937-06, 102061-03, 102065-02, 102266-03, 102308-06, 102318-01, 102324-02, 102565-02, 102590-02, 102449-03, and 102593-02. New MP Support -------------- This Driver Update also includes 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. See "Driver Update Distribution Diskette" on page 7 for a complete list of the contents of this Driver Update. 3 New 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(R) 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." New Video Support ----------------- Table 1-3 contains a list of the new video display adapters supported in Solaris 2.4 x86 Driver Update 7 that were not supported in previous Driver Updates. Table 1-3 New Video Display Adapters Supported in This Driver Update ================================================================================ Video Display Adapters -------------------------------------------------------------------------------- Resolution and Color Depth (A=800x600; B=1024x768; C=1152x900; D=1280x1024; E=1600x1200) A B C D E Vendor/Model Bus Chipset 8 24 8 24 8 24 8 24 8 24 -------------------------------------------------------------------------------- Diamond Stealth Video DRAM PCI S3 868 x x x x x x Stealth Video VRAM PCI S3 968 x x x x x x -------------------------------------------------------------------------------- Matrox MGA Millenium PCI STORM x x x x x x x x x x -------------------------------------------------------------------------------- Nanao EizoAccel AA51 ISA F82C480 x x Nanao HA50/HL50 ISA S3 928 x x x Nanao HA60 ISA S3 928 x x x -------------------------------------------------------------------------------- 4 Table 1-3 New Video Display Adapters Supported in This Driver Update (Continued) ================================================================================ Video Display Adapters -------------------------------------------------------------------------------- Resolution and Color Depth (A=800x600; B=1024x768; C=1152x900; D=1280x1024; E=1600x1200) A B C D E Vendor/Model Bus Chipset 8 24 8 24 8 24 8 24 8 24 -------------------------------------------------------------------------------- Number Nine 9FX Motion 531 PCI S3 868 x x x x 9FX Motion 771 PCI S3 968 x x x x x x x x x -------------------------------------------------------------------------------- STB Velocity 64V PCI S3 968 x x x x x x x x ================================================================================ This Video Driver Update also adds support for higher resolutions on some display adapters that were supported in previous Driver Updates. Table 1-4 lists the ones with additional support. For a complete list of video display adapters supported in this release, see Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video." Table 1-4 Updated Video Support in this Driver Update ================================================================================ Video Display Adapters -------------------------------------------------------------------------------- Resolution and Color Depth (A=800x600; B=1024x768; C=1152x900; D=1280x1024; E=1600x1200) A B C D E Vendor/Model Bus Chipset 8 24 8 24 8 24 8 24 8 24 -------------------------------------------------------------------------------- Diamond Viper Pro PCI Weitek Power 9100 x x x x x Viper Pro VLB Weitek Power 9100 x x x x x -------------------------------------------------------------------------------- Intergraph G91* PCI Weitek Power 9100 x x x x x ================================================================================ *The Intergraph G91 also supports a resolution of 1600x1280 for 8-bit color. Support for Panning in 8-bit Mode Added --------------------------------------- This Video Driver Update adds support for panning (on some notebook computers) in 8-bit mode. Previously, this was only supported in 4-bit mode. Support for 85 kHz Refresh Rate Added ------------------------------------- This Video Driver Update also adds support for monitors with an 85 kHz refresh rate; previously, 80 kHz was the maximum refresh rate supported. 5 Modified Driver Update Video Distribution and Installation Instructions ---------------------------------------------------------- The size of the Solaris 2.4 x86 Driver Update Video distribution now requires two diskettes. To limit the problems with multi-volume distributions, the image that gets distributed is now a compressed cpio file, instead of a diskette image. Consequently, the installation instructions will be slightly different depending on whether you obtained the Video Driver Update on diskette or from on-line sources. Those who are installing from diskettes will require a few more steps than those starting with the on-line cpio image file. In either case, the installation instructions have changed from previous Driver Updates. See Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video," for the new instructions. PCMCIA Drivers -------------- The PCMCIA support in Solaris 2.4 x86 Driver Update 7 is identical to the contents of the previous Driver Update. If you have already installed the PCMCIA distribution from Solaris 2.4 x86 Driver Update 6, there is no reason to install the PCMCIA portion of this Driver Update. For more information about the PCMCIA support in this release, see Chapter 3, "Solaris 2.4 x86 Driver Update 7 PCMCIA Support." Driver Update Contents ---------------------- Solaris 2.4 x86 Driver Update 7 contains six diskettes labeled: o "Solaris 2.4 x86 Driver Update 7 CD/Disk Boot" o "Solaris 2.4 x86 Driver Update 7 Net Boot" o "Solaris 2.4 x86 Driver Update 7 Distribution" o "Solaris 2.4 x86 Driver Update 7 Distribution (Video) 1 of 2" o "Solaris 2.4 x86 Driver Update 7 Distribution (Video) 2 of 2" o "Solaris 2.4 x86 Driver Update 7 Distribution (PCMCIA)" The Boot and Distribution diskettes are intended to be used with a Solaris 2.4 x86 CD or network boot server. The "Solaris 2.4 x86 Driver Update 7 Distribution (Video)" diskettes and the "Solaris 2.4 x86 Driver Update 7 Distribution (PCMCIA)" diskette can only be used on systems that already have the Solaris 2.4 operating environment installed. The contents of the "Solaris 2.4 x86 Driver Update 7 Distribution (Video)" diskettes are discussed in Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video." 6 The contents of the "Solaris 2.4 x86 Driver Update 7 Distribution (PCMCIA)" diskette are discussed in Chapter 3, "Solaris 2.4 x86 Driver Update 7 PCMCIA Support." Driver Update Boot Diskette ---------------------------- The Solaris 2.4 operating environment can be installed on x86 systems with one of two new boot diskettes labeled "Solaris 2.4 x86 Driver Update 7 CD/Disk Boot" and "Solaris 2.4 x86 Driver Update 7 Net Boot." The Net Boot diskette is to be used when installing over a network; the CD/Disk Boot diskette is to be used when installing from a CD. Choose the one appropriate for your installation. Note - Throughout the rest of this document, the name of the Boot diskette will be referred to as "Solaris 2.4 x86 Driver Update 7 Boot" or "Driver Update Boot." 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, one or more of the Driver Update Distribution diskettes will be read. Driver Update Distribution Diskette ----------------------------------- The Driver Update Distribution diskette (labeled "Solaris 2.4 x86 Driver Update 7 Distribution") is read when the Driver Update Boot diskette is used to install Solaris. Alternatively, the Driver Update Distribution diskette can be used without the boot diskette to add new drivers to an existing x86 system running Solaris 2.4. The Driver Update Distribution diskette contains the drivers listed in Table 1-5. 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. ---------------------- *The manual page for the Solaris ieef driver (Intel EtherExpress Flash32) will also be installed with this Driver Update. This driver is included in the Solaris 2.4 x86 CD. 7 Table 1-5 New or Updated Device Drivers in This Driver Update ================================================================== SCSI HBA Drivers ---------------- adp Adaptec AIC-7870 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) 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 BusLogic SCSI HBAs (BT-440C, BT-445C, BT-445S, BT-542B(R), BT-545C(R), BT-545S(R), BT-742A(R), BT-746C, BT-747C, BT-747S(R), BT-757S, BT-946C) corvette IBM(R) SCSI-2 Fast/Wide Adapter/A 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 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 Controllers mcis Updated IBM Micro Channel HBA driver to correct some known problems 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) 8 SCSI HBA Drivers (Continued) ---------------------------- 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 IDE Interface Driver -------------------- ata Updated IDE interface driver to support ATAPI-compliant CD-ROM drives and enhanced IDE disk drives SCSI Tape Driver ---------------- st SCSI tape target driver Network Drivers --------------- 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 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 9 Network Drivers (Continued) ---------------------------- 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 driver to correct some known problems ============================================================================= 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, please contact SunSoft Technical Support. This Driver Update also includes the following new 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 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 2.4 x86 Driver Update 7: 101936-06, 101937-06, 102061-03, 102065-02, 102266-03, 102308-06, 102318-01, 102324-02, 102565-02, 102590-02, 102449-03, and 102593-02. ---------------------- *Installation of the Solaris operating environment may fail on systems with three or more processors until the new module is installed. To get around this problem, turn off all but the first two processors during installation of Solaris 2.4 or this Driver Update; after the new software is installed, shut down the system, and reboot with all processors powered on. 10 Note - If you are installing Solaris 2.4 on one the following Intergraph(R) 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 Driver Update Boot Diskette" on page 12. Note - The Novell(R) NE2000 and NE2000plus are sensitive to autoprobing by other drivers and require autoprobe reset sequences that may disturb other cards. For this reason, the Solaris nei driver is disabled by default, and special steps must be taken to enable it. See "Modifying the Solaris Driver Update Boot Diskette" on page 12 or "Enabling Support for the Novell NE2000/NE2000plus After Installing the Driver Update" on page 21. 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 Driver Update Boot Diskette" on page 12 or "Disabling Drivers After Installing the Driver Update" on page 22. 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. Driver Update Distribution (Video) Diskettes -------------------------------------------- See Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video," for a complete list of the video display adapters supported in this release. 11 Driver Update Distribution (PCMCIA) Diskette -------------------------------------------- See Chapter 3, "Solaris 2.4 x86 Driver Update 7 PCMCIA Support," for additional information about the PCMCIA devices supported in this release. Solaris 2.4 Driver Update 7 Release Notes ------------------------------------------ Solaris 2.4 x86 Jumbo Kernel Patch ---------------------------------- To avoid user-level program core dumps after installing Solaris 2.4 x86 Driver Update 7, it is recommended that you install the latest revision of the Solaris 2.4 x86 jumbo kernel patch, ID 101946. This patch is posted on: o The WWW (http://access1.Sun.COM); click on "Solaris Driver Update." o The Internet server sunsolve1.Sun.COM in the directory /pub/patches via anonymous FTP. At the minimum, install revision -01 of this patch, which can be obtained from the Patches subdirectory of the Solaris 2.4 x86 installation CD. (Revision -08 is available online as of the printing of this document.) A README file and installpatch script provide a description and instructions for installing the patch on your system. Modifying the Solaris Driver Update Boot Diskette ------------------------------------------------- Before you install the Solaris operating environment 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 Novell NE2000/NE2000plus Ethernet adapters are sensitive to autoprobing by other drivers and require reset sequences that may disturb other network cards. For this reason, the nei driver is disabled by default, and special steps must be taken to enable it. 12 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. o The Solaris elink driver may interfere with the proper operation of PCnet-ISA adapters, such as those installed on the Intergraph TD-1, TD-2, and TD-3 Personal Workstations. If you are installing the Solaris software over a network that uses a PCnet-ISA adapter, and you experience problems with the network hanging, it may be necessary to exclude the elink driver from the Driver Update Boot diskette before attempting to install again. There are scripts on the Driver Update Boot diskette for these purposes. 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" diskette into drive A and format it: format a: 3. Insert the "Solaris 2.4 x86 Driver Update 7 Boot" diskette into drive A: and make a copy of it: 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 2.4 x86 Driver Update 7 Boot for Intergraph Systems," or "Modified Solaris 2.4 x86 Driver Update 7 Boot for NE2000/NE2000plus," or "Modified Solaris 2.4 x86 Driver Update 7 Boot for IBM SCSI-2 Fast/Wide Adapter/A," or "Modified Solaris 2.4 x86 Driver Update 7 Boot for PCnet-ISA." ---------------------------------------------- Note: Solaris 2.4 x86 Driver Update 7 contains two Boot diskettes. Remember to include CD/Disk or Net on the label of the modified Boot diskette. ----------------------------------------------- 6. Put the modified Boot diskette back into drive A:. 7. Change to drive A: (remember DOS is still running): a: 8. 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 13 o For NE2000/NE2000plus support, run the nov2000.bat command file: nov2000 o For IBM SCSI-2 Fast/Wide Adapter/A support, run the corvette.bat command file: corvette o To avoid PCnet-ISA conflicts, run the pcnet.bat command file: pcnet 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." 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 /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. 14 2. Edit the file /kernel/drv/asy.conf. For each new serial port, add a line similar to the following, replacing and with the appropriate IRQ and I/O address: name="asy" class="sysbus" interrupts=12, reg=,0,0 ioaddr=; For example, if the 8-port version of the BocaBoard (TM) is configured to use addressess 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 /kernel/drv/asy.conf, asy(7), and autopush(1M). How to Choose a Boot Disk ------------------------- The choice of PCI slot or EISA slot or BIOS ROM base address may affect which disk your system chooses as the boot disk; if you want to be able to boot automatically at poweron, be sure to choose the right disk for your system. 15 Known Problems -------------- Caution - The installation program's default size for the root filesystem 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 filesystem. o There is a known problem with the Tricord MP module that causes the machine to fail when a PS/2(R) mouse is attached to it. Workaround: Do not attach a PS/2 mouse to the Tricord machine. Use the PS2/Serial combination mouse as a serial mouse. 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(R) MultiSpin(R) 4X o Pioneer DRM-604X o (1203834) Installing over a network using a 3Com EtherLink 16/16 TP adapter will not work if the card is set to TURBO mode. Workaround: Set the card to non-TURBO mode before the initial network install. Once installed, set it back to TURBO mode to take advantage of maximum performance during normal operation. Installing Solaris Using the Driver Update Diskettes ---------------------------------------------------- To install Solaris 2.4 on an x86 system, follow the instructions in _x86: Installing Solaris Software_ using the diskette labeled "Solaris 2.4 x86 Driver Update 7 Boot." 16 The procedure for installing Solaris using the Driver Update Boot diskette is almost the same as that described in _x86: Installing Solaris 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 diskette. At the start of that phase of the installation, one of the install scripts will ask you to insert the Driver Update Distribution diskette into the drive. After the new driver packages have all been added, the script will ask you to remove the diskette from the drive. In each case, it will wait for you to perform the requested action and then 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(TM) 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" below for further instructions. To install the new video display support, see Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video," for instructions. To install the new PCMCIA support, see Chapter 3, "Solaris 2.4 x86 Driver Update 7 PCMCIA Support," for instructions. 17 Enabling Support for Sound Blaster Audio Cards After Installing Solaris ----------------------------------------------------------------------- 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 "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. 18 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 Is Installed --------------------------------------------- If you already have the Solaris 2.4 software installed, the simplest way to add one of the new drivers to your system is to obtain the Driver Update Distribution diskette and install it as a patch on your Solaris 2.4 x86 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 the Driver Update Distribution diskette into drive 0. 2. Become root. 19 3. Use cpio to copy files off the diskette and run the installation script. 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/diskette0. # mkdir /tmp/Drivers # cd /tmp/Drivers # volcheck & # cpio -iduBI /vol/dev/aliases/floppy0 # ./installdu.sh -------------------------------------------------------------------- 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_. -------------------------------------------------------------------- 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" on page 24. 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" on the next page. 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" on page 22. 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" on page 22. o If you are replacing a network card with a newly supported network card, see "Replacing a Network Card" on page 24." 20 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 the Driver Update" on page 24 for instructions. To install the new video display support, see Chapter 2, "Solaris 2.4 x86 Driver Update 7 Video," for instructions. To install the new PCMCIA support, see Chapter 3, "Solaris 2.4 x86 Driver Update 7 PCMCIA Support," for instructions. Enabling Support for the Novell NE2000/NE2000plus After Installing the Driver Update ---------------------------------------------------------------------- If you already have the Solaris 2.4 operating environment 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 Solaris 2.4 x86 Driver Update 7 software. 1. Follow the instructions under "Adding New Drivers After Solaris Is Installed" on page 19 of this document to install Solaris 2.4 x86 Driver Update 7. 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: exclude: nei forceload: drv/eepro forceload: drv/el forceload: drv/elink forceload: drv/iee forceload: drv/pcn forceload: drv/smc ----------------------------------------------------- To comment out a line in the /etc/system file, place an asterisk * at the beginning of the line. ----------------------------------------------------- 21 5. Add or uncomment the following line: forceload: drv/nei ----------------------------------------------------- To uncomment a line in the /etc/system file, remove the asterisk * at the beginning of the line. ----------------------------------------------------- 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 on page 79 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" on page 24. 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 Is Installed" on page 19. 22 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. 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 ---------------------------------------------------- To comment out a line in the /etc/system file, place an asterisk * at the beginning of the line. ---------------------------------------------------- 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 (R) 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." 23 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.0 file to /etc/hostname.0 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: # mv /etc/hostname.elx0 /etc/hostname.smc0 Now perform a reconfiguration boot to make your changes take effect: # touch /reconfigure # reboot Enabling Support for Sound Blaster Audio Cards After Installing 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. 1. Become root. 24 2. Change directories to /kernel/drv: # cd /kernel/drv 3. Edit the sbpro.conf kernel configuration file. This is an ASCII file that may 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 25 ===========THIS IS A BLANK PAGE ===================== 2. Solaris 2.4 x86 Driver Update 7 Video ----------------------------------------- A brief description of the contents of the video support included in this Driver Update is followed by installation instructions and known problems. Appendix B, "Supplementary Video Information," provides additional information about the video support in this release. Read through the entire chapter once before installing the Solaris 2.4 x86 Driver Update 7 Video. Driver Update Video Contents ---------------------------- Solaris 2.4 x86 Driver Update 7 Video contains two diskettes labeled: "Solaris 2.4 x86 Driver Update 7 Distribution (Video)." The Distribution diskettes are intended to be used on Solaris 2.4 x86 systems only. Table 2-1 contains a list of video display adapters supported in this Video Driver Update. While this table includes the resolution and color depth capabilities of each adapter, it is important to note that the resolution and color depth you select are also dependent on the capabilities of your monitor and the amount of video memory on the card. See "Determining Resolution and Color Depth" in Appendix B for more information. Note - In order to get support for the Diamond Viper VLB(TM) and Diamond Viper PCI(TM) cards, you must first install the Driver Update Distribution as described in Chapter 1, "Solaris 2.4 x86 Driver Update 7." This must be done prior to installing Driver Update Video. 27 Table 2-1 Video Display Adapters Supported in This Driver Update ============================================================================= Video Display Adapters -------------------------------------------------------------------------------- Resolution and Color Depth (A=800x600; B=1024x768; C=1152x900; D=1280x1024; E=1600x1200) A B C D E Vendor/Model Bus Chipset 8 24 8 24 8 24 8 24 8 24 -------------------------------------------------------------------------------- Acer ET4000/W32* ISA ET4000/W32 x x -------------------------------------------------------------------------------- AST Manhattan 5090P** -- Cirrus Logic 5424 x -------------------------------------------------------------------------------- ATI Graphics Pro Turbo VLB ATI Mach64 x x x x x x Graphics Pro Turbo PCI ATI Mach64 x x x x x x GRAPHICS ULTRA+ ISA ATI Mach32 x x GRAPHICS ULTRA PRO ISA ATI Mach32 x x x x GRAPHICS ULTRA PRO PCI ATI Mach32 x x x x GRAPHICS ULTRA PRO VLB ATI Mach32 x x x x GRAPHICS XPRESSION PCI ATI Mach64 x x x x x GRAPHICS XPRESSION VLB ATI Mach64 x x x x x Mach64 chipset x x WINTURBO*** PCI ATI Mach64 x x x x x -------------------------------------------------------------------------------- Cirrus Logic 5420 chipset x w/512Kbyte DRAM 5424 chipset x w/512Kbyte DRAM** 5428 chipset x w/512Kbyte VRAM -------------------------------------------------------------------------------- Compaq QVision 1024 EISA TRITON x QVision 2000 PCI Matrox MGA-2 x x x x x QVision 2000 (Rev. G) PCI Matrox MGA-3 x x x x x ProLiant -- Cirrus Logic 5420 x ProSignia -- Cirrus Logic 5420 x =============================================================================== *The ET4000/W32 video cards that are shipped with Acer machines are not all the same; if you encounter any display problems when the OpenWindows environment is running, try using a different add-on board that is compatible with the Solaris operating environment. ** Video adapters based on the Cirrus Logic 5424 chipset with 512 Kbyte DRAM may not perform well in 800x600x256 mode, particularly if the selected monitor refresh reate is 60 Hz or higher. See the release note on page 32. ***The ATI WINTURBO(TM) model is equivalent to the Gateway ATI GX Mach64 PCI video card. "--" Indicates onboard video controller. 28 Table 2-1 Video Display Adapters Supported in This Driver Update -Continued- =============================================================================== Video Display Adapters -------------------------------------------------------------------------------- Resolution and Color Depth (A=800x600; B=1024x768; C=1152x900; D=1280x1024; E=1600x1200) A B C D E Vendor/Model Bus Chipset 8 24 8 24 8 24 8 24 8 24 -------------------------------------------------------------------------------- DEC DECpc XL 590 -- Cirrus Logic 5428 x -------------------------------------------------------------------------------- Dell OptiPlex XMT 590 -- S3 864 x x x x Poweredge SP5xx -- ATI Mach32 x -------------------------------------------------------------------------------- Diamond SpeedStar 64 ISA ISA Cirrus Logic 5434 x x x x x SpeedStar 64 PCI PCI Cirrus Logic 5434 x x x x x Stealth 32 VLB Tseng Labs W32p x x x x x Stealth 32 PCI Tseng Labs W32p x x x x x Stealth 64 DRAM VLB S3 Vision 864 x x x x x Stealth 64 DRAM PCI S3 Vision 864 x x x x x Stealth 64 DRAM PCI S3 Trio64 x x x x x Stealth 64 VRAM VLB S3 Vision 964 x x x x x x x Stealth 64 VRAM PCI S3 Vision 964 x x x x x x x Stealth Video DRAM PCI S3 868 x x x x x x Stealth Video VRAM PCI S3 968 x x x x x x x x x Viper Pro PCI Weitek Power 9100 x x x x x Viper Pro VLB Weitek Power 9100 x x x x x Viper SE** PCI Weitek Power 9100 x x x x Viper VLB VLB Weitek Power 9000 x x x x Viper PCI PCI Weitek Power 9000 x x x x -------------------------------------------------------------------------------- ELSA Winner 1000 VLB S3 928 x x x Winner 2000 VLB S3 928 x x x x Winner 1000Pro-VL* VLB S3 Vision 864 x x x x x Winner 2000Pro-VL VLB S3 Vision 964 x x x x x x x x Winner 2000Pro-PCI PCI S3 Vision 964 x x x x x x x x -------------------------------------------------------------------------------- Everex FIC 864P PCI S3 Vision 864 x x x x x VGA Trio 64P PCI S3 Trio64 x x x x x ViewPoint 64P PCI S3 Vision 864 x x x x x -------------------------------------------------------------------------------- Hewlett-Packard HP NetServer LC/LE/LF -- TVGA 9000i x HP Vectra VL2 -- Cirrus Logic 5428 x x HP Vectra XM2i -- S3 Vision 864 x x x HP Vectra XU -- S3 Vision 864 x x x x -------------------------------------------------------------------------------- IBM PC Series 300-486 -- Cirrus Logic 5430 x x PC Series 300 -- S3 Vision 864 x x x x x PC Series 700 -- S3 Vision 864 x x x x x PS/ValuePoint Performance Series -- S3 Vision 864 x x x x x =============================================================================== *The ELSA Winner 1000Pro with the ATT20C498 RAMDAC is supported. **The Diamond Viper SE is currently only supported with a 64 kHz refresh rate in the 1280x1024 resolution. See known problems (1200858 and 1212168) on page 41. "--" Indicates onboard video controller. 29 Table 2-1 Video Display Adapters Supported in This Driver Update -Continued- =============================================================================== Video Display Adapters -------------------------------------------------------------------------------- Resolution and Color Depth (A=800x600; B=1024x768; C=1152x900; D=1280x1024; E=1600x1200) A B C D E Vendor/Model Bus Chipset 8 24 8 24 8 24 8 24 8 24 -------------------------------------------------------------------------------- Intel Professional/GX High Resolution -- ATI Mach32 x x x x -------------------------------------------------------------------------------- Intergraph TD-1* -- S3 928 x x x x TD-2, TD-3; (G90)** PCI Weitek Power 9000 x x x x G91**** PCI Weitek Power 9100 x x x x x -------------------------------------------------------------------------------- Matrox MGA Impression VLB Matrox MGA-1 x x x x x x MGA Impression Plus PCI Matrox MGA-3 x x x x MGA Millenium PCI STORM x x x x x x x x x x MGA Ultima VLB Matrox MGA-2 x x x x x MGA Ultima Plus PCI Matrox MGA-2 x x x x x x MGA Ultima Plus 200 PCI Matrox MGA-2 x x x x x x x x -------------------------------------------------------------------------------- Micronics Mpower 4 plus -- ATI Mach64 x x -------------------------------------------------------------------------------- miro miroCRYSTAL 20SD PCI S3 864, S3 SDAC x x x x x miroCRYSTAL 20SD PCI S3 Vision 864 x x x x x miroCRYSTAL 40SV PCI S3 Vision 964 x x x x x x x -------------------------------------------------------------------------------- Nanao EizoAccel AA51 ISA F82C480 x x Nanao HA50/HL50 ISA S3 928 x x x Nanao HA60 ISA S3 928 x x x -------------------------------------------------------------------------------- Number Nine 9FX Motion 531 PCI S3 868 x x x x 9FX Motion 771 PCI S3 968 x x x x x x x x x #9GXE*** ISA S3 928 x x x x #9GXE4*** VLB S3 928 x x x x #9GXE64 PCI S3 Vision 864 x x x x x x #9GXE64 Pro PCI S3 Vision 964 x x x x x x x x #9GXE64 PCI S3 Trio64 x x x x x Imagine 128 PCI Imagine128 x x x x x x x x ================================================================================ *To support 1152x900 or 1280x1024 resolution on the Intergraph TD-1 display adapter, you must select an interlaced monitor type when configuring the Solaris window system. Choose "Multifrequency 56kHz (up to 1280x1024 interlaced)" as the monitor type. See "Installing Driver Update (Video)" later in this chapter for information about configuring the window system. **The Intergraph G90 is synonymous with the Diamond Viper video card based on the Weitek Power 9000 chipset. When configuring an Intergraph Personal Workstation with a G90, select one of the Diamond Viper entries listed by the kdmconfig program that includes the monitor type. Be sure to read the notes in this chapter that pertain to the P9000-based Diamond Viper Video cards. ***The Number Nine #9GXE video display adapters (ISA and VESA local bus) support 24-bit color in 640x480 mode only. ****The Intergraph G91 also supports a resolution of 1600x1280 for 8-bit color. "--" Indicates onboard video controller. 30 Table 2-1 Video Display Adapters Supported in This Driver Update -Continued- =============================================================================== Video Display Adapters -------------------------------------------------------------------------------- Resolution and Color Depth (A=800x600; B=1024x768; C=1152x900; D=1280x1024; E=1600x1200) A B C D E Vendor/Model Bus Chipset 8 24 8 24 8 24 8 24 8 24 -------------------------------------------------------------------------------- Orchid Fahrenheit 1280 Plus VL VLB S3 801 x x Kelvin 64 PCI Cirrus Logic 5434 x x x x x Kelvin 64* VLB Cirrus Logic 5434 x x x x x -------------------------------------------------------------------------------- S3 Trio64 chipset x x x x x Vision 864+SDAC chipset x x x x x -------------------------------------------------------------------------------- STB LIGHTSPEED VL VLB Tseng Labs W32p x x x x x NITRO PCI PCI Cirrus Logic 5434 x x x x x x POWERGRAPH PRO PCI PCI x x x x x POWERGRAPH 64 PCI S3 Trio64 x x x x x Velocity 64V PCI S3 968 x x x x x x x x -------------------------------------------------------------------------------- Trident TVGA 9000i TVGA 9000i x ================================================================================ *Older versions of the Kelvin64 VLB card have memory addressing limitations that may cause problems if your system contains 32 Mbytes or more of RAM. See "Known Problems" on page 39 for further information. "--" Indicates onboard video controller. Table 2-2 on page 32 lists the additional notebook display support included in this Driver Update. Note that the resolution and color depth capabilities may depend on whether an external monitor is attached. 31 Table 2-2 Additional Video Support for Notebook Displays in This Driver Update ================================================================================ Resolution and Color Depth* 640x480 800x600 1024x768 ------- ------- -------- Vendor/Model Chipset 8 24 8 24 8 24 -------------------------------------------------------------------------------- Ergo Power Brick Western Digital 90C24 I -------------------------------------------------------------------------------- NEC Versa M75C Chips&Technology 65540 E,I E E Versa M75HC Chips&Technology 6554S E,I E,I E -------------------------------------------------------------------------------- Toshiba 4900CT Chips&Technology 65545 E,I E E ================================================================================ * E = With External Monitor I = With Internal Monitor Caution - Even though many notebook computers are capable of supporting external monitors at a resolution higher than 640x480, you should not change the default video resolution on a notebook computer to be anything other than what the internal monitor can support. Higher resolution video modes do not work on the integrated LCD screen; if you happen to start up the window system without an external monitor, you may not be able to see anything on the LCD screen. In some cases, this may even damage your LCD screen. See "Configuring Secondary Displays" on page 38. Driver Update Video Release Notes --------------------------------- o Support for 85 kHz Refresh Rate Added: This Video Driver Update also adds support for monitors with an 85 kHz refresh rate; previously, 80 kHz was the maximum refresh rate supported. o Support for Panning in 8-bit Mode Added: This Video Driver Update adds support for panning on the NEC Versa M75C, NEC Versa M75HC, and Toshiba 4900CT notebook computers in 8-bit mode. Previously, this was only supported in 4-bit mode. 32 o Video adapters based on the Cirrus Logic 5424 chipset with 512Kbyte DRAM may not perform well in 800x600x256 mode under the Solaris OpenWindows(TM) environment. This is particularly noticeable if the selected monitor refresh rate is 60 Hz or higher. This is a hardware limitation. To obtain the best performance in 800x600x256 mode, choose the "Multifrequency-38kHz" monitor type when configuring the window system. o If your video adapter contains the S3 Vision 864 chip, but is not in the above list of supported adapters, it may work with one of the "S3 Vision 864" entries listed by the kdmconfig program. o If your video adapter contains the S3 Vision 864 video chip with S3 SDAC, but is not in the above list of supported adapters, it may work with one of the "S3 Vision 864 with S3 SDAC" entries listed by the kdmconfig program. o If your video adapter contains the Trident TVGA(R) 9000i chip, it may work with the "Trident TVGA9000i(512k)" entry listed by the kdmconfig program. o New software in this Driver Update replaces the support for the Number Nine(TM) #9GXE(TM) ISA and VLB display adapters included in the Solaris 2.4 release. If you have one of these video boards, you will need to reconfigure your window system as described in "Installing Driver Update Video." o This Driver Update adds new software support for the following display adapters that were supported in the Solaris 2.4 release: ATI(R) GRAPHICS ULTRA+(TM) ISA ATI GRAPHICS ULTRA PRO(TM) (ISA, PCI, and VLB) If you have one of these video boards, and you want to use the new software support, reconfigure your window system as described in "Installing Driver Update Video." The kdmconfig program now has specific entries for these cards that you can select. (Prior to this Driver Update, you had to select one of the "ATI 68800" entries in order to use one of these cards.) o This Driver Update also includes software fixes to some known problems. For a list of the known problems fixed in Driver Update 7 (Video), see the README files in the directories: /var/sadm/patch/102058-07 and /var/sadm/patch/102059-07. 33 Solaris 2.4 x86 Jumbo Kernel Patch ---------------------------------- To avoid user-level program core dumps after installing the Solaris 2.4 x86 Driver Update 7 Video, it is recommended that you install the latest revision of the Solaris 2.4 x86 jumbo kernel patch ID 101946. See "Solaris 2.4 x86 Jumbo Kernel Patch" on page 12 for information on how to obtain this patch. Installing Driver Update Video ------------------------------ Note - In order to get support for the Diamond Viper VLB(TM) and Diamond Viper PCI(TM) cards, you must first install the Driver Update Distribution as described in Chapter 1, "Solaris 2.4 x86 Driver Update 7." This must be done prior to installing Driver Update Video. The contents of the Driver Update Video diskettes are installed as patches on your Solaris 2.4 x86 system. To do this, you must already have Solaris 2.4 installed and running on your x86 system. Note - When installing the Solaris 2.4 software on a system that contains one of the newly supported video cards listed in Table 2-1, if you choose to configure the window system, your card will not be included yet in the list of supported display adapters. However, you can still use a graphics-based interface to the Solaris installation program by choosing the standard 16 colors, 640x480 VGA. Alternatively, you can use a character-based interface by choosing not to configure the window system when asked. After installing the Driver Update Video software, the installation script will give you the option of configuring the window system by running the kdmconfig program. If you choose to do this, you will be asked to configure keyboard, mouse, and video card again; however, this time you will be able to select from a list that includes the newly supported video cards. 1. Become root. 34 Note - The Driver Update Video is now released as a compressed cpio image file. Consequently, if you are installing from diskettes, there are a few extra steps that need to be taken to retrieve the files. If you have obtained the Driver Update Video image file from on-line sources and you are not installing the Driver Update Video from diskettes, you can proceed directly to Step 5. ------------------------------------------------ See "How to Obtain Driver Updates on page xiv for information on obtaining Driver Updates from on-line sources. -------------------------------------------------- 2. Insert the first "Solaris 2.4 x86 Driver Update 7 Distribution (Video)" diskette into drive 0. 3. First use cpio to copy the compressed cpio image file off the diskettes. 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/diskette0. # mkdir /tmp/Drivers # cd /tmp/Drivers # volcheck & # cpio -iduBI /vol/dev/diskette0/unlabeled ---------------------------------------------- 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_. ----------------------------------------------- [This will be output on the screen:] End of Medium on "input" Change to part 2 and press RETURN key [q] 4. Insert the second Driver Update Video diskette into the drive and press Return. cpio will report the number of blocks copied. 5. Now use zcat and cpio to copy the files from the compressed cpio image file, and run the install script. # zcat vdu* | cpio -icudB # ./installdu.sh --------------------------------------- The name of the compressed cpio image file is vduimage.Z, where represents the Driver Update number. ----------------------------------------- 35 6. Configure the window system. After the Driver Update Video software has been installed, the installation script asks if you want to configure the window system. If you do not want to configure the window system at this time, you must run the following commands after the installation script ends and before you start the OpenWindows software: # kdmconfig -u # kdmconfig -cf Note - If you have one of the Number Nine #9GXE video cards installed and running on your Solaris 2.4 system, and you want to use the new software included in this Driver Update to support them, it is necessary to configure the window system at this time. If, for some reason you do not want to use the new Number Nine #9GXE video support in this Driver Update, you must back out the Driver Update Video patches. See the README files in /var/sadm/patch/102058-07 and /var/sadm/patch/102059-07 for instructions on how to back out these patches. If you want to configure the window system at this time, the kdmconfig program will be started for you. The kdmconfig program will ask you to configure your keyboard, mouse, and display adapter. The list of display adapters will appear alphabetically by vendor. To quickly scroll through the list, type the first letter of the vendor name. For example, type `M' to get to the first Matrox(R) MGA(TM) entry. Some of the names of display adapters on the list may be followed by the amount of video memory on the card. For example, `Diamond Stealth 64 (2MB)' indicates 2 Mbytes of memory on the Diamond Stealth 64(TM) card. Be sure to select an entry that matches your configuration. Note - To choose one of the Diamond Viper video card entries displayed by kdmconfig, you will need to select an entry that matches your monitor. For a complete list of supported monitors, see "Supported Diamond Viper (P9000) Monitor Configurations" in Appendix B. 36 Note - To choose the Intergraph G91 entry displayed by kdmconfig, you will need to select an entry that matches your monitor. For a list of supported monitors, see "Supported Intergraph G91 Monitor Configurations" in Appendix B. After you have selected your display adapter, you may be asked additional questions about screen size, color depth, display resolution, and monitor type. 7. Select the Correct Screen Size, Color Depth, Resolution, and Monitor from the list displayed by kdmconfig. Selecting `8' for color depth means your adapter is capable of 8-bit color (256 colors), whereas `24' means 24-bit color (224 or 16,777,216 colors). After choosing the monitor's screen size, color depth, and resolution, you will be shown a list of supported monitors (unless you have already chosen one of the Diamond Viper card entries). If you have a multisync/multifrequency monitor, check the manufacturer's documentation to find out the maximum horizontal synchronization rate supported by the monitor. For example, if you have a ViewSonic(R) 17 monitor, which has a maximum horizontal sync rate of 82 kHz, select `MultiFrequency-80kHz (up to 1600x1200@60 Hz)' as the monitor type. Note - In order to support 1152x900 or 1280x1024 resolution on the Intergraph TD-1 display adapter, you must select an interlaced monitor type when configuring the Solaris window system or it will not function properly. Choose "Multifrequency 56kHz (up to 1280x1024 interlaced)" as the monitor type. 8. Remove the diskette from drive 0. 9. Clean up the temporary workspace. # cd / # rm -fr /tmp/Drivers o If your system contains a Diamond Viper Pro VLB card, there may be an additional step you must take if the system hangs after staring the OpenWindows software. See problem number 1192967 on page 40. 37 o If your system does not have one of these Diamond Viper display adapters, the installation of the Driver Update 7 Video is complete and you can now run the openwin command to start the window system. Note - Be sure to read "Known Problems" at the end of this chapter, if you have not already done so. Configuring Secondary Displays ------------------------------ Caution - Even though many notebook computers are capable of supporting external monitors at a resolution higher than 640x480, you should not change the default video resolution on a notebook computer to be anything other than what the internal monitor can support. Higher resolution video modes do not work on the integrated LCD screen; if you happen to start up the window system without an external monitor, you may not be able to see anything on the LCD screen. In some cases, this may even damage your LCD screen. These instructions allow you to configure a secondary display for notebook computers that have an external monitor without changing the default video resolution. The configuration that will be installed will define display 0 as the internal monitor, and display 1 as the external monitor. The external monitor will be configured for 1024x768, 256 colors. 1. Become root. 2. Change to the /etc/openwin/server/etc directory. # cd /etc/openwin/server/etc 3. Copy the appropriate OpenWindows configuration file for your notebook to the file OWconfig: a. If you have a Toshiba 4900CT notebook computer, type: # cp /usr/openwin/server/etc/OWconfig.4900ct OWconfig 38 b. If you have a NEC(R) Versa(TM) M75C, type: # cp /usr/openwin/server/etc/OWconfig.vm75c OWconfig c. If you have a NEC Versa M75HC, type: # cp /usr/openwin/server/etc/OWconfig.vm75hc OWconfig Note - The OpenWindows configuration file that is being installed assumes you are using a built-in PS/2-style mouse. If you connect a PS/2-style mouse to the external mouse/keyboard port, you will need to perform a reconfiguration boot before bringing up the OpenWindows environment: ---------------------------------------- To perform a reconfiguration boot, type the commands: touch /reconfigure reboot ------------------------------------------ 4. Exit from superuser status. 5. Start the OpenWindows software, indicating which display to use. a. To use the internal display, type: openwin -display :0 b. To use the external display, type: openwin -display :1 For more information about notebook computer configuration, see the _Solaris 2.4 Notebook Supplement Guide_ (part number 801-6619-14). Known Problems -------------- Caution - (1161494) Under the Solaris operating environment, the Diamond Viper video card based on the P9000 chipset is not compatible with a motherboard that has a Symphony chipset. This combination may cause the system to panic or reboot. If the Symphony chipset is present on the motherboard, do not use the Diamond Viper video card. 39 o The VLB versions of the Diamond Viper and Diamond Viper Pro (TM) adapters do not work on some systems that have both PCI and VESA Local Bus support on the motherboard. The OpenWindows software will fail with an error message when you attempt to start it. The Solaris software expects a PCI version of the Diamond Viper boards if the system supports PCI. Workaround: Use a PCI version of the Diamond Viper adapters on those systems that support both bus types. ----------------------------------------- Note that the VLB version of the Diamond Viper SE adapter is not supported in this release. ----------------------------------------- o (1211889, 1210704) The Matrox Millenium card may exhibit problems with some high resolutions, color depths, and refresh rates. o (1210745) The Matrox(R) MGA Impression(TM) (VLB) video card does not support 1600x1200 resolution in the current release. o (1211083) Iconifying and deiconifying windows sometimes leaves extended lines on the screen when a Number Nine(TM) Imagine 128(TM) video card is installed. Workaround: Refresh the screen when this happens. o (1192967) Due to hardware conflicts on some VESA Local Bus (VLB) systems, the Diamond Viper Pro VLB card may not function when configured at the default memory address (0xa0000000). If your system appears hung with a blank screen after starting the OpenWindows software, you will need to do the following: a. Reboot your system b. Edit the file /etc/openwin/server/etc/OWconfig using a text editor such as vi. c. Change the address on the line that contains XSCREENCONFIG from 0xa0000000 to 0xc0000000. Here is a sample line: ----> class="XSCREENCONFIG" name="p9100-vlb" device="SUNWp9100" | res="1024x768" defdepth="8" size="15-inch" addr="0xa0000000" <---- board="diamond2/p9100-vlb.xqa" monitor="mfreq/mfreq64.vda" | | dpix="85" dpiy="85"; | | | Look for this line Change this field-----------------| d. Save your changes and exit the editor. e. Restart the OpenWindows software. In future releases, changes of this kind will be handled by the kdmconfig program. 40 o (1200858, 1212168) The Diamond Viper SE adapter will not run with a refresh rate above 75 kHz in 1280x1024 resolution. (See the manufacturer's manual to verify the maximum horizontal sync rates.) In the current release, however, it also does not work with a refresh rate of 56 kHz in 1280x1024 resolution. Workaround: Use a refresh rate of 64 kHz with 1280x1024 resolution. o Some VESA Local Bus motherboards do not properly support the default address range used by the Diamond Viper VLB(TM) adapter. To find a workable address for a particular system may require some experimentation. o (1193138) On systems with the QVision(TM) 1024/E video card installed, black lines may appear along a client's title bar every time it gets input focus. The symptoms occur if olwm is the window manager, and the OpenWindows.SetInput resource is set to "followmouse" in either the .Xdefaults or .OWdefaults file. Performing a refresh operation only temporarily causes the black bars to disappear. Workaround: Set the input focus to be "Click to Type" so that the OpenWindows.SetInput resource is changed from "followmouse" to "select." This can be done through the Workspace Properties menu under Miscellaneous options. Change the Set Active Window property to "Click Mouse" instead of "Move Pointer." o (1183956) The Number Nine Imagine 128 video card configured with a "MultiFrequency-64 kHz" monitor and a resolution of 1152x900 does not work under the OpenWindows environment (it will not display on the screen). This problem occurs on both 8-bit and 24-bit mode. Workaround: Use a different resolution or monitor. o (1183990) The Matrox MGA Impression Plus(TM) video card fails under the OpenWindows environment when configured with a "MultiFrequency-64 kHz" monitor at a resolution of 1280x1024, in 8-bit color mode. Workaround: Use a different resolution or monitor. o (1179142) Using a monitor frequency of 64 kHz with a Diamond Stealth 64 DRAM video card configured for 24-bit color depth and a resolution of 800x600 causes noise (sparkles) on the screen whenever the screen has to be repainted (for example, when moving a window, or scrolling within a window). Workaround: Use a different monitor frequency. 41 o (1179339) The ATI GRAPHICS ULTRA PRO VLB video card with a Mach32 (TM) graphics chip, a TI68875 BFN RAMDAC(TM), and 2 Mbytes of DRAM may not work properly if the "ATI Graphic Ultra Pro (2MB)" entry is selected when configuring the window system. Vertical bars get displayed on the screen. Workaround: If you have this version of the card, choose the "ATI Graphic Ultra Pro (1MB)" entry when configuring the window system but note that you will not be able to use a resolution of 1280x1024. Note also that the ATI GRAPHICS ULTRA PRO VLB video card with VRAM does not have this problem. o (1179340) Using the Intel Professional GX High Resolution system in 1280x1024 with 256 colors mode and an 80 kHz monitor causes problems when returning to text mode after exiting the OpenWindows environment. The foreground color is set to purple and the background color is set to blue. Workaround: Select either a different resolution, or a different monitor frequency when configuring the window system. o (1178899) On systems with video cards that use a hardware cursor, only one icon is shown when selecting multiple icons to drag and drop. This problem may be seen on video cards that contain the following chipsets: Imagine128, S3 864, S3 964, ATI Mach64 (TM), ATI Mach32, and Matrox MGA-1 and MGA-2. (See Table 2-1 on page 24 for the make and models of video cards associated with these chipsets.) Even though the multiple icons are not shown while being dragged and dropped, they are being selected and will be copied correctly. o (1176285) Programs that use the Solaris PEX(TM) extension may fail if a user's XGLHOME variable is set incorrectly. If the XGLHOME shell environment variable points to a nonexistent path (or one that doesn't contain the XGL(TM) runtime binaries), then any program that uses the Solaris PEX extension (including XGL programs on most display adapters), will cause the server to abort. Workaround: Users should be careful when setting XGLHOME prior to starting the OpenWindows environment. Prior to running the `openwin' command, make sure your XGLHOME environment variable is either not set, or points to a valid path for the system you are using. 42 o Some versions of the Orchid(TM) Kelvin 64(TM) VLB video card have memory addressing limitations that may cause problems if your system contains 32 Mbytes or more of RAM. A newer revision of this board addresses these problems. Unfortunately, there is no distinction made between revisions of this card. If your system has 32 Mbytes or more of RAM and you observe symptoms such as a fuzzy display or random vertical lines in the OpenWindows environment, contact Orchid Technology to request a newer revision of this card. o The Number Nine Imagine 128 (TM), the Number Nine #9GXE64 (TM), and the Number Nine #9GXE64 Pro (TM) video cards do not support interlaced mode. Consequently, configuring the window system using a monitor type of "MultiFrequency-38kHz (up to 1024x768 interlaced)" or "MultiFrequency-56kHz (up to 1280x1024 interlaced)," will cause the window system to fail. Workaround: Use a monitor that can support 1024x768 or 1280x1024 in non-interlaced mode. o (1177581) On systems with the Orchid Kelvin 64 PCI video card or one of the Diamond Speedstar 64 video cards installed, a few horizontal dashes may be observed on the left side of the screen during graphical operations. Workaround: Refresh the screen. o (1173469) On systems with the Diamond Stealth 64 video card installed, occasionally the mouse cursor will appear as two images that move in unison when the cursor is moved. This may last for a short period of time before the two images become one again. These same symptoms occur on systems with the Number Nine #9GXE, Number Nine #9GXE64, Number Nine #9GXE64 Pro, or the Elsa Winner 2000Pro cards. o (1173773) After running xlock, there may be a white border around the screen on systems with video cards that use the Tseng Labs W32p chipset (see Table 2-1). This border disappears after the screen is unlocked. o (1174387) On systems with the Diamond Stealth 32(TM) VLB/PCI cards, you may lose control of the mouse pointer when xfontsel is used to select a font in the Lucide font family, and a point size of 180 or above. Reset the system, if this occurs. o (1200644) When using an LCD screen at a resolution of 800x600, in 256 color mode, sometimes the image in the upper left-hand portion of the screen will expand to fill the entire screen. Workaround: Use the keys Fn-LCD/CRT three times to adjust the size and position of the screen. 43 The following problems apply only to 24-bit depth color: o (1172443) Applications that use XIL (TM) display the wrong colors when used with a 24-bit display adapter. Image Tool is an example of such an application. The problem is that XIL does not handle the byte ordering of 24-bit displays correctly; thus the colors are wrong in the displayed image. Workaround: Use an application that does not use XIL but that can display 24-bit images correctly. xv is an example of a shareware application that is available over the Internet. Note - 8-bit displays are not affected by this problem, and Image Tool works correctly with PostScript files on any display depth. o (1173985) Icon Editor dies when saving a 24-bit image to a file. o (1174561) The STB LIGHTSPEED VL(TM) video card used in 800x600 resolution, 24-bit color mode does not work properly with the Sony(R) CPD 1604S monitor. Workaround: Do not use this particular monitor type at that resolution and color depth. o Wabi(TM) will not run under 24-bit depth mode. o The IslandPaint(R) application does not work properly under 24-bit mode. All of the button icons on the left side of the window are either missing images or have incorrect ones displayed. 44 3. Solaris 2.4 x86 Driver Update 6 PCMCIA Support ------------------------------------------------- A description of the contents of the PCMCIA 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 PCMCIA device configuration in this release. Read through the entire chapter once before installing the PCMCIA support in Solaris 2.4 x86 Driver Update 7. PCMCIA Driver Update Contents ----------------------------- Solaris 2.4 x86 Driver Update 7 contains one diskette labeled: Solaris 2.4 x86 Driver Update 6 Distribution (PCMCIA). The Distribution diskette is intended to be used on Solaris 2.4 x86 systems only. The Solaris 2.4 x86 Driver Update 7 Distribution (PCMCIA) diskette contains the drivers listed in Table 3-1. A new Section 7 manual page for each of the drivers will also be installed in the appropriate manual page directory during installation. Table 3-1 PCMCIA Drivers Supported in this Driver Update ================================================================ PCMCIA Drivers -------------- pcic Intel i82365SL PC Interface Controller driver that supports controllers based on the following chips: Intel 82365SL, Vadem VG365/VG645/VG648, Cirrus Logic PD6710/PD6720, Ricoh RF5C366, and Toshiba ================================================================ 45 Table 3-1 PCMCIA Drivers Supported in this Driver Update -Continued- ================================================================ pcelx 3Com EtherLink III (3C589) PCMCIA Ethernet driver pcram PCMCIA memory card driver that supports PCMCIA SRAM and DRAM cards pcser PCMCIA serial card device driver that supports PCMCIA modem and serial cards based on the 16550 UART and its variants ================================================================ Appendix A contains device pages that explain the configuration for each of the types of PCMCIA devices listed above. The PCMCIA Driver Update also includes pcmcia, the PCMCIA nexus driver that provides card and socket services for PCMCIA device drivers (such as pcic); pcmem, the PCMCIA memory card nexus driver that supports PCMCIA memory card client drivers (such as pcram); and pcmciad, the PCMCIA user daemon that provides user-level services for pcmcia and PCMCIA card client drivers. See pcmcia(7), pcmem(7), and pcmciad(1M). Other manual pages have been updated for PCMCIA 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 PCMCIA Driver Update diskette, see the README files that get installed in the patch directories /var/sadm/patch/, where is one of the following for Solaris 2.4 x86 Driver Update 6 PCMCIA: 101908-05, 101924-02, and 101938-01. Understanding PCMCIA Hardware ----------------------------- A PCMCIA controller may be built into your computer (as on most notebook computers) or it may be an add-on card. Most have either one or two slots, and the PCMCIA controller is, itself, a device on another (usually ISA) bus. The PCMCIA controller controls the PCMCIA bus and maps PCMCIA devices onto the main (e.g., ISA) bus. The PCMCIA 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, sound cards and graphics adapters) on machines of all sizes and architectures. 46 The PCMCIA controller may support one or more types of PCMCIA devices. Type-I PCMCIA devices have a credit-card-like form factor (3.3mm). Type-II and Type-III devices are thicker (5mm and 10.5mm, respectively) and their performance is slightly slower than similar devices that are found on an ISA bus. Any controller that contains the higher-type slots should take the lower- type cards. For example, a controller with Type-III PCMCIA slots should be able to support Type-III, Type-II, and Type-I cards. But a controller with Type-I slots will only support Type-I devices. PCMCIA devices are autoconfigured; that is, I/O ports and IRQs are assigned automatically by the Solaris operating system when each device is plugged in. PCMCIA devices are hot-pluggable-they can be safely inserted and removed while a machine is running. Configuring PCMCIA Devices -------------------------- The PCMCIA software should automatically recognize any supported PCMCIA card 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 database of supported devices, you can manually add your new card to the list. This process is described in "PCMCIA Modem and Serial Cards" in Appendix A. Configuring the PCMCIA Controller --------------------------------- While PCMCIA devices are autoconfigured, it may be necessary to perform some configuration for the PCMCIA controller itself. To assign IRQs and ports to PCMCIA devices, the pcmcia nexus driver must know which of these resources are already allocated. During the installation process, a script attempts to automatically determine which resources are already allocated, but on some systems it may be necessary to manually update that information. See "PCMCIA Controllers" in Appendix A. Hot-Plugging PCMCIA Cards ------------------------- Hot-plugging a PCMCIA card 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. 47 Inserting Cards --------------- PCMCIA cards can be inserted at any time to any empty socket. If there is driver support for the card, the card is recognized and a device node is created. If /usr/lib/pcmciad is running, the driver is also loaded and the /dev entries are created as appropriate. The naming of the /dev entry is specific to the particular class of device but encodes the socket number where the card was inserted. Details of naming are device specific and documented in the PCMCIA Device Reference Pages in Appendix A, and in the PCMCIA driver manual pages. Identifying Unrecognized Cards ------------------------------ Cards that are not recognized should still show up in prtconf command output with an identifiable driver name so that an alias can be constructed if the card is otherwise supported by the system. This is most commonly needed for serial cards that don't implement the full Card Information Structure (CIS). The addition of new aliases is described in "PCMCIA Modem and Serial Cards" in Appendix A." Removing Cards -------------- PCMCIA cards can be removed at any time. The framework notifies the PCMCIA device driver that the card has been removed and leaves the policy on what to do up to the driver. Each class of devices has a different policy. See "PCMCIA 3Com EtherLink III (3C589) Card," "PCMCIA Modem and Serial Cards," and "PCMCIA SRAM and DRAM Devices" in Appendix A, "Device Reference Pages." Note - Before installing this PCMCIA Driver Update, read the information in the PCMCIA Device Reference Pages in Appendix A. 48 Installing PCMCIA Driver Update ------------------------------- The contents of the "Solaris 2.4 x86 Driver Update 7 Distribution (PCMCIA)" diskette is installed as a combination of patches and packages on your Solaris 2.4 x86 system. To install the PCMCIA Driver Update, you must already have Solaris 2.4 installed and running on your x86 system. Note - If you have an add-on PCMCIA controller, be sure to install it before installing the PCMCIA 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 PCMCIA Driver Update. This is necessary so that the system can identify the resources used by cards in the docking bay. 1. Insert the "Solaris 2.4 x86 Driver Update 7 Distribution (PCMCIA)" diskette into drive 0. 2. Become root. 3. Use cpio to copy files off the diskette, and run the installation script. 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/diskette0. # mkdir /tmp/Drivers # cd /tmp/Drivers # volcheck & # cpio -iduBI /vol/dev/aliases/floppy0 # ./installdu.sh -------------------------------------------------------- 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_. -------------------------------------------------------- 4. Remove the diskette from drive 0. 5. Clean up the temporary workspace. # cd / # rm -fr /tmp/Drivers 49 6. Perform a reconfiguration boot to enable the new PCMCIA support. # touch /reconfigure # reboot I/O ports, IRQs, and memory addresses for use by PCMCIA devices should be configured automatically. For more information, see "PCMCIA Controllers" in Appendix A, "Device Reference Pages." If you insert a PCMCIA device into your system, it should be automatically recognized and configured. For more information, see the "Hot-Plugging" sections on the individual PCMCIA Device Reference Pages in Appendix A. If you have a 3Com PCMCIA Ethernet card, there are additional installation instructions needed to enable a new network interface. This is described in the next section. PCMCIA Release Notes -------------------- Adding a PCMCIA Network Card ---------------------------- Typically, a network interface is configured when Solaris is first installed on the system. Because the PCMCIA Ethernet card is not supported during installation, it will always be necessary to update several network configuration files before it can be used. If you add a 3Com 3C589 PCMCIA card, you must update several network configuration files: 1. Create a /etc/hostname.pcelx# file (where # is a slot 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. Note - This process is described in the _TCP/IP Network Administration Guide_. 50 Using PCMCIA Memory Cards ------------------------- Typically, before using a new PCMCIA memory card, you need 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 PCMCIA memory card, most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. Note - PCMCIA memory devices don't need to be file-system structured.You can redirect the output of a tar command, for example, to a PCMCIA memory card. (But this usage is not recommended, and still requires that the memory card be formatted prior to any non-file system writes.) The sequences for creating a file systems are slightly different depending on whether the Solaris Volume Management software is used. Using PCMCIA Cards Without the Volume Manager --------------------------------------------- 1. Become root. 2. If you do not want to use vold to manage your PCMCIA 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 the 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 file system on a PCMCIA memory card. For example, a DOS pcfs file system can be created on a PCMCIA memory card in socket 1by typing: # fdformat -t dos /dev/dsk/c1t6d0s2 ------------------------------------------------------ Device naming for PCMCIA memory cards is discussed in "PCMCIA SRAM and DRAM Devices" on page 103, pcram(7), and fdformat(1). ------------------------------------------------------ 51 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 PCMCIA Memory Cards ------------------------------------------------------------ Since the Solaris Volume Management software recognizes PCMCIA memory cards, no special vold configuration is required. 1. Become root. 2. Use the fdformat command to create a pcfs file system on a PCMCIA memory card. See fdformat(1M). For example, a DOS pcfs file system can be created on a PCMCIA memory card in socket 1 by typing: # fdformat -t dos /vol/dev/aliases/pcmem1 3. After formatting is complete, the volume manager will automatically mount the device after it is physically removed and reinserted. To check this, run the mount command after reinserting the card. Known Problems -------------- o (1196569) The Solaris PCMCIA memory card 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 will likely result in a system panic. Most PCMCIA RAM cards do not contain multiple memory technologies and will not cause this problem. o (1188733) On some systems, a 3Com EtherLink III PCMCIA Ethernet card can only be used in one socket and will not work if removed and plugged into another socket. This problem can be avoided by always plugging in your PCMCIA Ethernet card into the same socket. 52 o (1198587, 1198622) If the file /etc/hostname.pcelxn has not been created, and the system is rebooted with the PCMCIA Ethernet card plugged in, the system may panic when the card is removed. On some systems, this may also cause a continuous stream of error messages similar to the following at system startup: WARNING: Adapter failed:fifo diag : WARNING: pcelx0: rx filter 5/f Workaround 1: Do not plug the network card in until after the system has been brought up. Workaround 2: If the system is rebooted with the card plugged in, configure the network card before unplugging it. The steps for configuring the network card are described in "Adding a PCMCIA Network Card" on page 50. Troubleshooting PCMCIA Device Configuration ------------------------------------------- When a PCMCIA device doesn't work, isolate the type of problem. To determine that the nexus and adapter drivers have loaded successfully, complete the following: o Use the prtconf command. If prtconf shows a device node for both pcic and pcmcia, then the software has loaded and successfully identified a PCMCIA controller. o If neither device driver is recognized, then your system does not have a supported PCMCIA controller. o If they are present, then any card that is inserted is 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." If a PCMCIA card is recognized as present when the card is in the socket before the system is booted, but is not recognized as present after the card is inserted into a running system, then complete the following troubleshooting procedures: 53 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 "Correcting Possible Conflicts" in the Device Reference Page for "PCMCIA Controllers" 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 the Device Reference Page for "PCMCIA Controllers" in Appendix A. If that does not work, try several different IRQ levels. If a PCMCIA card is not identified when inserted prior to booting the system, complete the following troubleshooting procedures: 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 PCMCIA Controllers" Device Reference Page under "Correcting Possible Conflicts." If the information there is accurate, contact SunSoft Customer Support. 54 A. Device Reference Pages ------------------------- This appendix supplements Appendix B, "Device Reference Pages," in the x86 Device Configuration Guide. It includes necessary device configuration information for hardware supported by the new or updated drivers. Use the following table to locate information about your hardware and proceed directly to those pages. ====================================================================== IDE Interface Solaris Driver ------------- -------------- IDE Disk and CD-ROM Interface ata page 59 SCSI Host Bus Adapters Solaris Driver ---------------------- --------------- Adaptec AIC-6360/AHA-1522A/AHA-1520A/ AHA-1510A/AHA-1530P/1532P aic page 62 Adaptec AIC-7870/AIC-7871/AIC-7872/AHA-2940/ AHA-3940 PCI HBAs adp page 67 AMD PCscsi, PCscsi II, PCnet-SCSI PCI HBAs pcscsi page 69 BusLogic SCSI HBAs blogic page 70 Compaq SMART SCSI Array Controller csa page 74 DPT PM-2011/PM-2021 ISA HBAs dpt page 75 DPT PM-2012B EISA HBA dpt page 77 DPT PM-2022/PM-2122/PM-3222 EISA HBAs dpt page 79 DPT PM-2024/PM-2124/PM-3224 PCI HBAs dpt page 82 55 SCSI Host Bus Adapters (Continued) Solaris Driver ----------------------------------- -------------- IBM DMC960 RAID Micro Channel HBAs (IBM SCSI-2 RAID, IBM SCSI-2 Fast/Wide Streaming-RAID Adapter/A) mlx page 84 IBM Micro Channel SCSI-2 Fast/Wide Adapter/A corvette page 86 Mylex DAC960P PCI Controller mlx page 88 NCR 53C710 (Siemens Nixdorf PCE-5S SCSI) ncrs page 90 NCR 53C8xx PCI SCSI HBA (53C810,53C815,53C820,53C825) ncrs page 91 Sound Blaster 16 SCSI-2 (SCSI) aic page 62 Trantor T348 MiniSCSI Plus Parallel HBA trantor page 93 Tricord Systems Intelligent SCSI Subsystem (ISS) HBA iss page 95 Other SCSI Devices Solaris Driver ------------------ -------------- SCSI Tape Drives st page 97 Network Adapters Solaris Driver ---------------- -------------- 3Com EtherLink III (3C5x9, 3C509B) elx page 100 AMD PCnet Ethernet (PCnet-ISA, PCnet-PCI) pcn page 101 Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR EISA Controllers nfe page 103 Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP iee page 105 Intel EtherExpress PRO eepro page 107 Novell NE2000, NE2000plus Ethernet nei page 108 Novell NE3200 EISA Ethernet nee page 112 Racal InterLan ES3210/ES3210 TP EISA Ethernet riles page 114 SMC EtherEZ, EtherCard Elite16 Ultra, EtherCard PLUS Elite16, EtherCard PLUS (8416, 8216, 8013, 8003) smc page 116 Audio Cards Solaris Driver ----------- -------------- Sound Blaster Pro/Sound Blaster 16/Sound Blaster AWE32 sbpro page 120 56 PCMCIA Hardware Solaris Driver --------------- -------------- PCMCIA Controllers pcic page 126 PCMCIA 3Com EtherLink III (3C589) Card pcelx page 130 PCMCIA Modem and Serial Cards pcser page 132 PCMCIA SRAM and DRAM Devices pcram page 135 57 Part 1 -- 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 59 Warnings -------- o (1191294) In this release, it is not possible to boot from the third or fourth IDE disk drives, although you can install Solaris software on them. o The Solaris Volume Management software does not 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(R) 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. 60 Part 2 -- 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 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. 62 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" on the next page 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 the _x86 Device Configuration Guide_ 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. 63 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. 64 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. 65 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 the _Solaris 2.4 Open Issues and Late-Breaking News_ 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. 66 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 avoid user-level program core dumps on heavily loaded systems, install patch ID 101946. See "Solaris 2.4 x86 Jumbo Kernel Patch" in Chapter 1 for information on how to obtain this patch. 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. 67 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, please 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 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 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. 68 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. 69 BusLogic SCSI HBAs Description ----------- The BusLogic SCSI host bus adapters are controllers for common disk/tape/I/O subsystem. The following models are supported: ------------------------------------- Model Bus BT-742A, BT-746C, BT-747C, BT-747S, BT-757S EISA BT-542B, BT-545C, BT-545S ISA BT-440C, BT-445C, BT-445S VESA BT-946C PCI -------------------------------------- Device Configuration -------------------- Preparing for Configuration ---------------------------- o Set the I/O address to any valid BusLogic host bus adapter I/O address except 0x330. This applies to all models of EISA, ISA, PCI, and VESA Local Bus BusLogic boards. If you use the default I/O port address, 0x330, the board will be run in Adaptec emulation mode. o If your BusLogic board model ends in "C", you must enter the AutoSCSI configuration utility and check the termination. o The PCI cards must be configured in ISA compatible mode. See the instructions under configuring the device for PCI models. 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. 70 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. 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 Models: 1. The BusLogic BT-946 board should be put into the Bus Master slot. 2. Enter the AutoSCSI utility. 3. Select "Advanced option." 71 4. Set termination as needed. 5. If the boot disk is larger than 1 Gigabyte, set the "Adapter BIOS Supports Space > 1 GB (DOS) only" option to Yes. 6. Set the Adapter to ISA-compatible mode. a. For BT-946, Revision A, B, or C: Set the value for "Set Host Bus Adapter IO Port Address as Default" to No. b. For BT-946, Revision E or later: Set the "Set ISA Compatible IO Port (PCI only)" option to Alternate. 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 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 ------------------------- 72 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 IRQ 9, 10, 11, 12, 14, 15 o I/O Address 0x334, 0x230, 0x234, 0x130, 0x134 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. 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 1540-mode. o (1180577) Systems with a BusLogic card installed may panic when tape access occurs on a system with heavy disk I/O. Workaround: Do tape backups on an idle system. 73 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. 74 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." 75 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. 76 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. 77 c. Press the down arrow to the DPT SCSI HBA to select parameters and set them as follows: o Bus Enabled o IDE Boot Address Primary o IRQ Entry noted on your worksheet o Option ROM Address Default o SCSI ID HBA Default 7 o 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. 78 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. 79 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 -------- (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. 80 (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. 81 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. 82 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. 83 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. Known Problems and Limitations ------------------------------ o If a SCSI disk drive is not defined to be part of any physical pack within a system drive, it is automatically labeled as a standby drive. If any SCSI disk drive within a system drive fails, data on a standby drive may be lost due to the standby replacement procedure. This procedure will overwrite the standby drive if the failed disk drive is configured with any level of redundancy (RAID levels 1, 5, and 6) and its size is identical to the size of the available standby drive. 84 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 85 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 (BETA) Driver Update Boot diskette using the corvette.bat file under DOS; see "Modifying the Solaris (BETA) 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 (BETA) 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 86 Known Problems and Limitations ------------------------------ o The microcode version of the SCSI-2 Fast/Wide Adapter/A board should be 0x71 or later. Boards with older versions, such as version 0x58, may cause the Solaris system to hang when using certain tape drives. The Solaris corvette driver displays a warning message if it detects an older, unsupported version of the adapter. o The IBM SCSI-2 Fast/Wide Adapter/A is currently only supported on systems with at least 32 Mbytes of memory installed. 87 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. 88 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 89 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. 90 NCR 53C8xx PCI SCSI HBA (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(TM) 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. 91 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. 92 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. 93 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 and T358 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. 94 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. 95 Part 3 -- 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(R) 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_. 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 superuser. 97 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 98 Part 4 -- 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. 100 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 The Solaris elink driver may interfere with the proper operation of PCnet-ISA adapters. If you are installing over a network that uses a PCnet-ISA Ethernet and you experience problems with the network hanging, try excluding the elink driver before attempting to install again. This is done by modifying the boot diskette using the pcnet.bat file under DOS; see "Modifying the Solaris Driver Update Boot Diskette" in Chapter 1 for instructions. o If you already have Solaris installed on your system, and after installing this (BETA) 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." 101 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 Known Problems and Limitations ------------------------------ 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. 102 Compaq NetFlex-2 DualPort ENET, NetFlex-2 ENET-TR EISA Controllers Description ----------- The Compaq NetFlex-2 DualPort ENET controller provides two Ethernet interfaces under the Solaris operating environment. The Compaq NetFlex-2 ENET-TR controller can be configured for either Ethernet or Token Ring, but only the Ethernet functionality is supported under the Solaris operating environment. Both the NetFlex-2 DualPort ENET and the NetFlex-2 ENET-TR are EISA bus controllers. Device Configuration -------------------- Preparing for Configuration --------------------------- Compaq NetFlex-2 DualPort ENET only: If the dual ported Ethernet card will be used to install Solaris over a network, the RJ-45 connector for the network must be connected to the first network port (Port 1). See the documentation that comes with the dual ported card to locate Port 1. Avoiding Possible Device Conflicts ----------------------------------- o Check for IRQ conflicts with ISA devices not defined in the EISA configuration software. o The default IRQ is 10, which can be a usable IRQ for many ISA cards, including SMC Ethernet cards, for example. Note - The Compaq NetFlex-2 DualPort ENET card shares the same IRQ for both ports. Configuring the Device ---------------------- Use the EISA configuration utility to tell the system about the card. 103 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 10Mb/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. 104 Intel EtherExpress 16, 16C, 16TP, MCA, MCA TP Description ----------- The Intel EtherExpress16 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. 105 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 106 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 107 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. In addition, the Solaris nei driver is disabled by default, and steps must be taken to enable it. There is a script (nov2000.bat) on the Driver Update Boot diskette that will disable the other drivers and enable the nei driver; see "Modifying the Solaris 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 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 ============================================================== 108 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. 109 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 "Known Problems and Limitations" for other potential problems. Valid Configurations -------------------- Note that some NE2000 clones may further restrict these choices. NE2000: o IRQ 2,3, 4, 5 o I/O Base Address 0x300 NE2000plus: o IRQ 2, 3, 4, 5, 10, 11, 12, 15 o I/O Base Address 0x300, 0x240, 0x280, 0x2C0 o SHARED MEMORY 0xD0000-0xDC000 110 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." 111 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. 112 Known Problems and Limitations ------------------------------ 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 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. 113 Racal InterLan ES3210/ES3210 TP EISA Ethernet Description ----------- The Racal InterLan ES3210 is a 32-bit Ethernet adapter for EISA-bus architecture systems. 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. The latest revision 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 are configured. Avoiding Possible Device Conflicts ---------------------------------- o Check the Interrupt Request (IRQ) level 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. 114 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 are the valid parameter ranges for the 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 recommended that they not be used. 115 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(R) 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 (R) 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 for x86 over the network, causing occasional NFS complaints (which can be ignored). 116 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 Work Sheet 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 Work Sheet 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 --------------------------------------------------------------- 117 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. 118 Part 5 -- 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 "Sound Blaster 16 SCSI-2 (SCSI)" on page 53 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 /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. 120 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: Sound Blaster Pro card with a nonstandard DMA setting Sound Blaster 16 card without audio IRQ and DMA jumpers Sound Blaster AWE32 card The sbpro.conf file must be updated after the Solaris 2.4 x86 Driver Update 7 is installed on your system. See "Enabling Support for Sound Blaster Audio Cards After Installing Solaris" 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. 121 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 Work Sheet 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 Work Sheet. 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 Work Sheet. 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 Solaris 2.4 x86 Driver Update 5 is installed on your system. Record the change on your Device Configuration Work Sheet. 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 Solaris 2.4 x86 Driver Update 7 is installed. The sbpro.conf file that gets installed with Solaris 2.4 x86 Driver Update 7 contains detailed instructions and examples. Record the change on your Device Configuration Work Sheet. 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 Work Sheet. 122 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 the Solaris 2.4 x86 Driver Update 7 is installed on your system. See "Enabling Support for Sound Blaster Audio Cards After Installing Solaris" 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: I/O Address 0x220, 0x240 ----- IRQ 2, 5, 7, 10 - - DMA Channel 0, 1, 3 - Sound Blaster 16/Sound Blaster AWE32: I/O Address 0x220, 0x240, 0x260, 0x280 ----- IRQ 2, 5, 7, 10 - 8-bit DMA Channel 0, 1, 3 - 16-bit DMA Channel 5, 6, 7 - Sound Blaster 16 SCSI-2 ports: I/O Address 0x140, 0x340 ----- IRQ 11 -- DMA Channel (not used) 0, 5, 6, 7 Limitations and 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. 123 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. 124 Part 6 -- PCMCIA Hardware PCMCIA Controllers Description ------------ The Solaris pcic driver supports PCMCIA controllers based on the Intel 82365SL and the Cirrus Logic PD6710/PD6720 chips. There is support for up to eight sockets (Type I, II, or III). Other controllers that use chips based on the Intel 82365SL design may also be supported. At the time of this Driver Update, controllers based on the following chips had also been tested: Vadem VG365/VG465/VG468, Ricoh RF5C366, and Toshiba. Most systems using one of these chips should work. The latest version of the _Solaris 2.4 x86 Hardware Compatibility List_ includes a list of systems that have been tested. (See "How to Obtain the Solaris 2.4 x86 Hardware Compatibility List" on in the front of this document.) Device Configuration --------------------- Preparing for Configuration --------------------------- Resource requirements for a system depend on the combination of devices to be used. A typical two-slot notebook computer needs at least 8 Kbytes of address space, 16 bytes of I/O space, and three free IRQs. The following are general guidelines: -------------------------------------------------------------- Address space At least 8 Kbytes are required with 4 Kbytes per slot in the 640K-1Mb range (not necessarily contiguous); if you have three slots, at least 12 Kbytes are needed I/O space At least 8 and preferably 16 bytes per slot IRQs At least one per slot, plus an additional IRQ for the pcic device driver, itself --------------------------------------------------------------- Controller Configuration ------------------------ o If you have an add-on PCMCIA controller, install it on your system prior to installing the PCMCIA Driver Update software. 126 o Some notebook computers have their built-in PCMCIA controller disabled by default. Enable it prior to installing the Solaris PCMCIA Driver Update. o If your system has a supported PCMCIA controller configured at a known address, it should be recognized automatically. No manual configuration should be necessary. Configuration of PCMCIA Cards ----------------------------- The Solaris PCMCIA 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 PCMCIA Driver Update 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 PCMCIA drivers. Note - If you are using a notebook with a docking bay, keep the notebook in the docking bay during the installation of the PCMCIA Driver Update software so 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 as described in the following three cases: o Case 1: Some device drivers do not export properties describing the resources they are using, and so an automatic scan cannot determine what resources are allocated to those drivers. This is detected automatically in the scan, and the script prints out a warning message and request for manual assistance. 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, and these are not detected by the automatic scan. In cases like these, the PCMCIA software may appear to configure properly, but some PCMCIA devices may simply not work (because they are sharing resources with other hardware). For example, some AST PowerExec notebooks reserve IRQ 15 for power management use. 127 Correcting Possible Conflicts ----------------------------- In most cases, the available resources will be determined automatically and recorded in the file /kernel/drv/pcic.conf. For proper operation, this information must be accurate. If not, ports, memory addresses, or IRQs that are in use by other devices will be allocated to PCMCIA devices. This can cause unpredictable but serious consequences. The resources available for PCMCIA 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 PCMCIA I/O card that needs an interrupt is assigned a different IRQ level. In addition, the PCMCIA controller itself uses one IRQ level. In this example, only two PCMCIA I/O cards 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,8,0xd0000,4 Many notebook computers have all the memory between 0xcc000 and 0xeffff available. This would be listed as: res-memory=0xcc000,0x14 If the notebook computer is to be used in a docking bay, the configuration should also account for any devices installed in it. 128 res-ioaddr This property, like the res-memory property, is a list of base address and length pairs. The length is 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,32,0x300,16 If the available resources recorded by the PCMCIA software in the /kernel/drv/pcic.conf file includes resources that are actually in use by other devices in the system, you must manually edit the file to remove them. For example, if your AST PowerExec notebook computer requires IRQ 15 for power management, remove 15 from the res-req property list. Note - Anytime the pcic.conf file is modified, a reconfiguration boot must be performed to make the changes take effect. Changing the Default IRQ ------------------------- There is one optional property that may be defined in the /kernel/drv/pcic.conf file. If specified, the smi property overrides the default IRQ level used by the pcic driver itself. By default, the second to the last IRQ in the res-irq list is used. If that value is unusable, or if you prefer another value, specify the IRQ level in the smi property. 1. To override the default IRQ level for the pcic driver, edit the /kernel/drv/pcic.conf file and add a line that contains `smi='. Example: To change to IRQ 9, add the following line to pcic.conf: smi=9 2. Perform a reconfiguration boot. # touch /reconfigure # reboot 129 PCMCIA 3Com EtherLink III (3C589) Card Description ----------- The 3Com 3C589 EtherLink III adapter is a Type-II (5mm) PCMCIA Ethernet card. Device Configuration -------------------- Preparing for Configuration --------------------------- It is not possible to boot or install the Solaris operating system using a PCMCIA 3Com EtherLink III card. Configuring the Device ------------------------ If the 3Com PCMCIA card 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). No manual configuration is necessary or possible. If you have inserted a 3Com PCMCIA card and it has not been recognized (no special files created), you can use the prtconf command to help identify the problem. Identifying an Unrecognized Card -------------------------------- 1. Run the prtconf command to see if your 3Com 3C589 card is recognized: # prtconf If the device is recognized, lines similar to the following will be included in the prtconf output: pcmcia, instance #0 pcelx, instance #0 2. If pcelx is not in the prtconf output, there is a problem with the PCMCIA controller configuration or the hardware. 130 Special Files ------------- Device naming in /dev follows standard LAN device naming except that the PPA 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). Additional Software Configuration --------------------------------- Because the PCMCIA Ethernet card cannot be supported during the installation of the Solaris operating system, a number of network configuration files will need to be updated before it can be used as a network interface. See "Adding a PCMCIA Network Card" in Chapter 3 for instructions. Hot -Plugging ------------ If you remove the card, any information you send is discarded, and no error messages are given. o When you reinsert the card in the same socket, the device operates normally. The behavior is similar to temporarily disconnecting a network device from the media. o If you insert the card in a different socket, a new instance of the device is created. Use the ifconfig command to mark the first instance "down," then configure the new interface. For example: # ifconfig pcelx0 down # ifconfig pcelx1 plumb Note - If you insert the card into a different socket, you will also need to modify a number of other network files to recognize the new interface name. See "Adding a PCMCIA Network Card" on page 44. o On some systems, a 3Com EtherLink III PCMCIA Ethernet card can only be used in one socket and will not work if removed and plugged into another socket. This problem can be avoided by always plugging in your PCMCIA Ethernet card into socket 0. This is documented as bug 1188733. 131 PCMCIA Modem and Serial Cards Description ----------- The pcser driver supports a wide range of PCMCIA modem and serial cards (based on the 8250, 16550, or compatible UART) at speeds up to 115-Kbyte baud. Device Configuration -------------------- Configuring the Device ---------------------- If a PCMCIA modem or serial card is recognized, the pcser device driver is automatically loaded, ports and IRQs are automatically allocated, and the special files are automatically created (if they do not already exist). No manual device configuration is necessary or possible. If you have inserted a PCMCIA modem or serial card and it has not been recognized (no special files created), you can use the prtconf command to help identify the problem. Identifying an Unrecognized Card -------------------------------- 1. Run the prtconf command to see if your modem or serial card is recognized: # prtconf o If the device is recognized, the prtconf output will include lines similar to the following: pcmcia, instance #0 pcser, instance #0 132 o If the device is not recognized, the prtconf output may include lines such as: pcmcia, instance #0 PC,111.222/Data Masher (driver not attached) 2. If your device is not recognized, you can use the add_drv command to add the name of your device as another known alias for pcser devices. Use the identification string listed in the output from prtconf. Typically, the part of the identification string following the slash can be treated as a comment, but if the string is not in the "PC,###.###" format, use the entire string in the add_drv command. For example: # add_drv -i '"PC,111.222"' pcser Note - Include the double quotes in single quotes to keep the shell from stripping out the double quotes. See add_drv(1M). Special Files -------------- The serial devices are named based on socket number. Since the name that appears in /dev/term and /dev/cua is always pcsocket number, a card inserted in socket 0 is pc0 and socket 1 is pc1. See pcser(7). Additional Software Configuration --------------------------------- When adding a new serial port or modem to the system, you often need to edit configuration files so applications can use the new communications port. For example, the /etc/uucp/Devices file needs to be updated for UUCP and PPP. See "UUCP Databases and Programs" in the TCP/IP Network Administration Guide. Hot-Plugging ------------ If a PCMCIA modem or serial card is unplugged while it is in use, the driver will return errors until the modem or serial card has been replaced in the slot. 133 Warnings -------- Because manufacturers interpret the PCMCIA specifications in different ways, some devices do not work, or work poorly. Consult the latest _Solaris 2.4 x86 Hardware Compatibility List_ for a list of modems that have been tested. See "How to Obtain the Solaris 2.4 x86 Hardware Compatibility List" in the front of this document. 134 PCMCIA SRAM and DRAM Devices Description ----------- The pcram driver supports a wide range of PCMCIA SRAM (Static RAM) and DRAM (Dynamic RAM) cards. It does not yet support Flash RAM cards. Device Configuration -------------------- Configuring the Device ---------------------- If a PCMCIA memory card is recognized, the pcram device driver is automatically loaded, the physical address is allocated, and the special files are created (if they do not already exist). No manual configuration is necessary or possible. If you have inserted a memory card and it has not been recognized (no special files created), you can use the prtconf command to help identify the problem. Identifying an Unrecognized Card -------------------------------- 1. Run the prtconf command to see if your memory card is recognized: # prtconf If the device is recognized, lines similar to the following will be included in the prtconf output: pcmcia, instance #0 pcmem, instance #0 pcram, instance #0 2. If your memory card does not appear in the prtconf output, it is not supported and cannot be used with the pcram device driver. 135 Special Files ------------- The special files created for PCMCIA memory cards act like disks and have names in the form of /dev/dsk/c#t#d#p# or /dev/dsk/c#t#d#s# (see pcram(7)). These are described below: c# slot number #, where # is relative to the slot number after any other devices in the system; for example, the first PCMCIA slot is typically 1, but if a system has two HBAs, the first PCMCIA slot would be 3 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 # Using PCMCIA Memory Cards ------------------------- Since the Solaris Volume Management software recognizes PCMCIA memory cards, no special vold configuration is required. * If you do not want to use vold to manage your PCMCIA 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. Typically, before using a new PCMCIA memory card, you need 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 PCMCIA memory card, most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. See "Using PCMCIA Memory Cards" in Chapter 3 for an example of how to create a pcfs file system on a PCMCIA memory card. 136 Note - PCMCIA memory devices don't need to be file-system structured. You can redirect the output of a tar command, for example, to a PCMCIA memory card. Hot-Plugging ------------- If your memory card is removed while in use, the device driver returns errors until a memory card has been inserted into the appropriate slot. 137 ===================THIS IS A BLANK PAGE =========================== B. Supplementary Video Information This appendix includes supplementary information about the video support provided in this Driver Update. Determining Resolution and Color Depth -------------------------------------- The resolution and pixel color depth supported by video display adapters is dependent on the amount of video memory on the card. Table B-1 shows the minimum amount of video memory that is needed to support the resolutions and pixel color depth shown. This should only be used as a general reference, however, as the modes supported by your card may differ. Check the documentation that comes with your video card and monitor for the specific modes supported. Table B-1 Minimum Memory Requirements to Support 8-Bit and 24-Bit Color Depth ============================================================================= Color Depth Resolution 8-Bit 24-Bit -------------------------------------------------- 640x480 1 MByte 2 MBytes -------------------------------------------------- 800x600 1 MByte 2 MBytes -------------------------------------------------- 1024x768 1 MByte 3 MBytes -------------------------------------------------- 1152x900 1 MByte 4 MBytes -------------------------------------------------- 1280x1024 2 MBytes 5 MBytes -------------------------------------------------- 1600x1200 2 MBytes 8 MBytes ============================================================================== 139 Supported Diamond Viper (P9000) Monitor Configurations ------------------------------------------------------ Table B-2 lists the monitors that can be used with the Diamond Viper graphics cards based on the Weitek Power 9000 (P9000) chipset supported in this Driver Update. When configuring the video adapter (kdmconfig), select only resolutions and frequencies that are supported by your monitor. If your monitor is not listed, you may be able to select a supported one that has the same resolution and synchronization rates as yours. In the following table, only the maximum resolution and horizontal and vertical frequencies supported by the monitor are listed.The kdmconfig program will display the lower resolutions supported by the monitor. Table B-2 Supported Monitors With the Diamond Viper Graphics Card ===================================================================== Maximum Hfreq Vfreq Monitor Resolution (kHz) (Hz) ----------------------------------------------------- CS1024 800x600 35.4 56.1 CS1024ni 1024x768 48.4 60.0 CS1572 FS 1280x1024 64.4 60.2 CTX 5468NI 1024x768 48.4 60.0 Fixed Frequency 800x600 35.4 56.1 HL 6955 SETK 1280x1024 64.4 60.2 IBM 8514 800x600 35.4 56.1 IBM 9515 1024x768 61.2 75.8 IBM 9517 1024x768 58.1 72.1 InterVue 20 1280x1024 81.2 76.0 MAG 17F 1152x900 56.8 60.3 NCR 3298-0240/0241 1024x768 48.4 60.0 NCR 3298-0261 1024x768 56.5 70.1 NCR 3298-0271/0272 1024x768 56.5 70.1 NEC 3FG 1024x768 48.4 60.0 NEC 3FGe 1024x768 48.4 60.0 NEC 3FGx 1024x768 48.4 60.0 NEC 4FG 1152x900 56.8 60.3 NEC 4FGe/5FGe 1152x900 56.8 60.3 NEC 5FG 1280x1024 64.4 60.2 NEC 6FG 1280x1024 78.9 74.0 ===================================================================== 140 Table B-2 Supported Monitors With the Diamond Viper Graphics Card (Continued) ===================================================================== Maximum Hfreq Vfreq Monitor Resolution (kHz) (Hz) ----------------------------------------------------- Nanao 9070u 1024x768 48.4 60.0 Nanao 9080i 1152x900 56.8 60.3 Nanao 9500 1152x900 56.8 60.3 Nanao T550i 1280x1024 64.4 60.2 Nanao T560i 1152x900 56.8 60.3 PS/V 2414-A04 1024x768 56.5 70.1 PS/V 2414-A07 1024x768 58.1 72.1 SONY 1304 1024x768 48.4 60.0 SONY 1304S 1152x900 56.8 60.3 SONY 1604S 1152x900 56.8 60.3 ViewSonic 6 1024x768 48.4 60.0 ViewSonic 7 1152x900 56.8 60.3 ===================================================================== Supported Intergraph G91 Monitor Configurations ----------------------------------------------- Table B-3 lists the supported Intergraph G91 monitor configurations in this Driver Update. When configuring the video adapter (kdmconfig), select only resolutions and frequencies that are supported by your monitor. In the following table, only the maximum resolution and horizontal and vertical frequencies supported by the monitor are listed.The kdmconfig program will display the lower resolutions supported by the monitor. Table B-3 Supported Intergraph G91 Monitor Configurations ===================================================================== Maximum Hfreq Vfreq Monitor Resolution (kHz) (Hz) ----------------------------------------------------- InterVue 20 1280x1024 81.25 76.00 InterVue 21 1280x1024 100.96 76.02 InterVue 27 1280x1024 80.07 60.25 141