Solaris 8 (Intel Platform Edition) Device Configuration Guide

Chapter 2 Device Reference Pages

This chapter describes how to use Device Reference Pages to configure your Intel 32-bit processor architecture (IA) system to run in the Solaris operating environment and to solve configuration problems.

Using Device Reference Pages

Only devices that require special configuration for running Solaris Intel Platform Edition have Device Reference Pages.

The following table shows the Device Reference Pages provided with Solaris 8 Intel Platform Edition.

Device Type 

Solaris Driver Name  

Where to Find Device Reference Pages 

Disk Interface  

ata

"IDE/Enhanced IDE Disk Controller (Including ATAPI CD-ROM)"

SCSI Host Bus Adapters 

adp

"Adaptec AHA-2940, 2940W, 2944W, 3940, 3940W HBAs"

 

cadp

"Adaptec AHA-2940AU, 2940U, 2940U Dual, 2940UW, 2940UW Dual, 2940U2, 2940U2B, 2940U2W, 2944UW, 2950U2B, 3940AU, 3940AUW, 3940AUWD, 3940U, 3940UW, 3944AUWD, 3950U2B HBAs"

 

pcscsi

"AMD PCscsi, PCscsi II, PCnet-SCSI and QLogic QLA510 HBAs"

 

ncrs

"Compaq 32-bit Fast SCSI-2 Controller"

 

cpqncr

"Compaq 32-bit Fast Wide SCSI-2, Wide Ultra SCSI, Dual Channel Wide Ultra SCSI-3 Controllers"

 

ncrs

"LSI Logic (formerly Symbios Logic or NCR) 53C810, 53C810A, 53C815, 53C820, 53C825, 53C825A, 53C860, 53C875, 53C875J, 53C876, 53C895 HBAs"

 

symhisl

"LSI Logic (formerly Symbios) 64-bit PCI Dual Channel Ultra2 SCSI 53C896 HBAs"

 

blogic

"Mylex (BusLogic) BT-946C, BT-948, BT-956C, BT-956CD, BT-958, BT-958D HBAs"

SCSI Disk Arrays/RAID Controllers 

mega

"American Megatrends MegaRAID 428 SCSI RAID Controller"

 

smartii

"Compaq SMART-2, SMART-2DH, SMART-2SL Array Controllers"

 

dpt

"DPT PM2024, PM2044W, PM2044UW, PM2124, PM2124W, PM2144W, PM2144UW SCSI and PM3224, PM3224W, PM3334W, PM3334UW SCSI RAID HBAs"

 

chs

"IBM PC ServeRAID SCSI, ServeRAID II Ultra SCSI, ServeRAID-3 Ultra2 SCSI HBAs"

 

mlx

"Mylex DAC960PD-Ultra, DAC960PD/DAC960P, DAC960PG, DAC960PJ, DAC960PL, DAC960PRL-1, DAC960PTL-1 Controllers"

Ethernet Network Adapters 

elxl

"3Com EtherLink XL (3C900, 3C900-COMBO, 3C900B-COMBO, 3C900B-TPC, 3C900B-TPO), Fast EtherLink XL (3C905-TX, 3C905-T4, 3C905B-TX, 3C905B-T4)"

 

pcn

"AMD PCnet Ethernet (PCnet-PCI, PCnet-PCI II, PCnet-Fast)"

 

cnft

"Compaq NetFlex-3, Netelligent Controllers"

 

dnet

"DEC 21040, 21041, 21140, 21142, 21143 Ethernet"

 

ieef

"Intel EtherExpress PRO/100 (82556)"

 

iprb

"Intel EtherExpress PRO/100B (82557), EtherExpress PRO/100+ (82558, 82559)"

Token Ring Network Adapters 

mtok

"Madge Smart 16/4 Token Ring"

Audio Cards 

sbpro

"Analog Devices AD1848 and Compatible Devices"

 

sbpro

"Creative Labs Sound Blaster Pro, Sound Blaster Pro-2"

 

sbpro

"Creative Labs Sound Blaster 16, Sound Blaster AWE32, Sound Blaster Vibra 16"

PC Card (PCMCIA) Hardware 

pcic

"PC Card Adapters"

 

pcelx

"3Com EtherLink III (3C589) PC Card"

 

pcser

"Modem and Serial PC Card Devices"

 

pcram

"SRAM and DRAM PC Card Devices"

 

pcata

"Viper 8260pA, SanDisk Flash, or Any PC Card ATA Devices"

Disk Interface

IDE/Enhanced IDE Disk Controller (Including ATAPI CD-ROM)

Solaris Device Driver:

ata

Device Type:

Hard disk or CD-ROM controller 

Supported Configuration:

Two drives per controller, up to four IDE drives if both primary and secondary interfaces are available 

Preconfiguration Information

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

Supported Settings

Primary controller:

o IRQ Level: 

14 

o I/O Address: 

0x1F0 

Secondary controller:

o IRQ Level: 

15 

o I/O Address: 

0x170 

If an IDE CD-ROM drive is installed, the system BIOS parameter for that device should be:

o Drive Type: 

Not installed 

If an enhanced IDE drive is installed, set the system BIOS as follows:

o Enhanced IDE Drive: 

Enabled 


Note -

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


Known Problems and Limitations

SCSI Host Bus Adapters

Adaptec AHA-2940, 2940W, 2944W, 3940, 3940W HBAs

Solaris Device Driver:

adp

Device Type:

SCSI-2 

Adapters:

Adaptec AHA-2940, AHA-2940W, AHA-2944W, AHA-3940, AHA-3940W 

Chips:

Adaptec AIC-7850, AIC-7860, AIC-7870, AIC-7880, AIC-7895 

Bus Type:

PCI 

Preconfiguration Information

The Plug N Play SCAM Support option is not supported.

Known Problems and Limitations

Configuration Procedure

Using the Adaptec configuration utility:

Adaptec AHA-2940AU, 2940U, 2940U Dual, 2940UW, 2940UW Dual, 2940U2, 2940U2B, 2940U2W, 2944UW, 2950U2B, 3940AU, 3940AUW, 3940AUWD, 3940U, 3940UW, 3944AUWD, 3950U2B HBAs

Solaris Device Driver:

cadp

Device Types:

SCSI, SCSI with Ultra SCSI option, SCSI-3, Ultra SCSI 

Adapters:

Adaptec AHA-2940AU, AHA-2940U, AHA-2940U Dual, AHA-2940UW, AHA-2940UW Dual, AHA-2940U2, AHA-2940U2B, AHA-2940U2W, AHA-2944UW, AHA-2950U2B, AHA-3940AU, AHA-3940AUW, AHA-3940AUWD, AHA-3940U, AHA-3940UW, AHA-3944AUWD, AHA-3950U2B 

Chips:

Adaptec AIC-7880, AIC-7880 (Rev B), AIC-7890, AIC-7890A, AIC-7890AB, AIC-7891B, AIC-7895, AIC-7896, AIC-7897 

Bus Type:

PCI 

Preconfiguration Information

Known Problems and Limitations

Configuration Procedure

Using the Adaptec configuration utility:

AMD PCscsi, PCscsi II, PCnet-SCSI and QLogic QLA510 HBAs

Solaris Device Driver:

pcscsi

Device Type:

SCSI 

Adapter:

QLogic QLA510 

Chips:

AMD 53C974 (PCscsi), 53C974A (PCscsi II), Am79C974 (PCnet-SCSI) (SCSI device only) 

QLogic FAS974 

Bus Type:

PCI 

Systems Supported:

PCnet-SCSI chip is integrated in the HP Vectra XU 5/90 and Compaq Deskpro XL systems 

Preconfiguration Information

Only the SCSI portion of the PCnet-SCSI host bus adapter is discussed here; the net portion requires a separate Solaris driver (pcn). See "AMD PCnet Ethernet (PCnet-PCI, PCnet-PCI II, PCnet-Fast)" for configuration information about Ethernet capabilities.

Known Problems and Limitations

Compaq 32-bit Fast SCSI-2 Controller

Solaris Device Driver:

ncrs

Device Type:

SCSI-2 

Adapter:

Compaq Integrated 32-bit Fast-SCSI-2/P, 53C810 chip 

Bus Type:

PCI 

This is a third-party driver developed by Compaq Computer Corporation. For support and information about possible updates to this driver, contact Compaq at http://www.compaq.com.

Preconfiguration Information

Supported Settings

o BIOS Hard Drive Geometry: 

<= 1 GB: 64 Heads, 32 Sectors  

> 1 GB: 255 Heads, 63 Sectors 

Compaq 32-bit Fast Wide SCSI-2, Wide Ultra SCSI, Dual Channel Wide Ultra SCSI-3 Controllers

Solaris Device Driver:

cpqncr

Device Type:

SCSI 

Adapters:

Compaq 32-bit Fast Wide SCSI-2, Wide Ultra SCSI, and Dual Channel Wide Ultra SCSI-3 Controllers in Compaq Servers: 

825 Add-on PCI, Integrated 825 PCI, 875 Add-on PCI, Integrated 875 PCI, Integrated 876 PCI 

 

Bus Type:

PCI 

This is a third-party driver developed by Compaq Computer Corporation. For support and information about possible updates to this driver, contact Compaq at http://www.compaq.com.

Preconfiguration Information

Configuration Procedure

  1. Install the Solaris software.

  2. Modify the driver configuration file /kernel/drv/cpqncr.conf.

    This file specifies the valid configurable parameters for the driver:

    • tag_enable: This property enables or disables tagged queuing support by the driver and can be set to the following values:

      • 0 - Disabled (Default)

      • 1 - Enabled

    • alrm_msg_enable: This property enables or disables Alarm messages due to faults in the Compaq Storage system connected to the 825, 875, or 876 controller. The valid values are:

      • 0 - Disabled

      • 1 - Enabled (Default)

    • debug_flag: This property enables or disables debug messages from the driver. The valid values are:

      • 0 - Disabled (Default)

      • 1 - Enabled

    • queue_depth: This property specifies the number of active requests the driver can handle for a controller. The maximum and default value for this property is 37; the minimal value is 13. You can reduce the value to support multiple controllers if you cannot allocate enough memory while trying to load the driver.

    • board_id: This property specifies additional controller IDs the driver has to support. The driver currently supports Compaq 825, 875, and 876 controllers. It recognizes the board ID for Compaq 825 Fast Wide SCSI-2, Compaq 875 Wide Ultra SCSI, and Compaq Dual Channel Wide Ultra SCSI-3 controllers by default.

    • ignore-hardware-nodes: Set this property to 0 if present.

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

    # touch /reconfigure
    # reboot
    

LSI Logic (formerly Symbios Logic or NCR) 53C810, 53C810A, 53C815, 53C820, 53C825, 53C825A, 53C860, 53C875, 53C875J, 53C876, 53C895 HBAs

Solaris Device Driver:

ncrs

Device Type:

SCSI 

Adapters:

LSI Logic (formerly Symbios Logic or NCR) 53C810, 53C810A, 53C815, 53C820, 53C825, 53C825A, 53C860, 53C875, 53C875J, 53C876, 53C895  

Bus Type:

PCI 

Preconfiguration Information

Known Problems and Limitations

LSI Logic (formerly Symbios) 64-bit PCI Dual Channel Ultra2 SCSI 53C896 HBAs

Solaris Device Driver:

symhisl

Device Type:

SCSI 

Adapters:

SYM22910 (both channel A and B support SE and LVD mode), SYM21002 (channel A supports SE only, channel B supports both SE and LVD mode) 

Chip:

SYM53C896 

Bus Type:

PCI 

Preconfiguration Information

Known Problems and Limitations

Mylex (BusLogic) BT-946C, BT-948, BT-956C, BT-956CD, BT-958, BT-958D HBAs

Solaris Device Driver:

blogic

Device Type:

SCSI 

Adapters:

Mylex (BusLogic) BT-946C, BT-948, BT-956C, BT-956CD, BT-958, BT-958D 

Bus Type:

PCI 

This is a third-party driver developed by BusLogic, which is now owned by Mylex Corporation. For support and information about possible updates to this driver, contact Mylex at http://www.mylex.com.

Preconfiguration Information

Supported Settings

o IRQ Level: 

5, 6, 7, 8, 9, 10, 11, 12, 14, 15 

o I/O Address: 

0x334, 0x230, 0x234, 0x130, 0x134 


Note -

I/O addresses are dynamically configured for BT-946C Rev. C PCI adapters.


Known Problems and Limitations

Configuration Procedure

BT-946C, Rev. A and B Only

Insert the board into the bus master slot, and using the AutoSCSI utility:

BT-946C (Rev. C) and BT-956C

Insert the board into the bus master slot, and using the AutoSCSI utility:

Configuring Multiple Devices

Follow these guidelines when adding a second Mylex PCI controller to a system.

SCSI Disk Arrays/RAID Controllers

American Megatrends MegaRAID 428 SCSI RAID Controller

Solaris Device Driver:

mega

Device Type:

SCSI RAID 

Adapter:

American Megatrends MegaRAID 428 SCSI RAID  

Bus Type:

PCI 

This is a third-party driver developed by American Megatrends, Inc. For support and information about possible updates to this driver, contact American Megatrends at http://www.ami.com.

Configuration Procedure

  1. Press Control-M while the system is starting up to configure the controller and all logical drives.

  2. Install the Solaris software and reboot.

    You will only see a single logical drive available during installation.

  3. In the /kernel/drv/sd.conf file, add additional drives by duplicating the existing entry for target=0 and incrementing the lun field by one for each additional logical drive you want the Solaris software to recognize.

    For example, if you have a total of three logical drives configured on your adapter, you would add the following lines:

    name="sd" class="scsi" 
         target=0 lun=1;
    name="sd" class="scsi" 
         target=0 lun=2; 
  4. Reboot.

    After the system reboots, you can use additional drives.

Compaq SMART-2, SMART-2DH, SMART-2SL Array Controllers

Solaris Device Driver:

smartii

Device Type:

Disk Array 

Adapters:

Compaq SMART-2, SMART-2DH, SMART-2SL Array Controllers 

Bus Type:

PCI 

Systems Supported:

Internal and external SCSI drives on Compaq servers 

This is a third-party driver developed by Compaq Computer Corporation. For support and information about possible updates to this driver, contact Compaq at http://www.compaq.com.

Preconfiguration Information

Known Problems and Limitations

DPT PM2024, PM2044W, PM2044UW, PM2124, PM2124W, PM2144W, PM2144UW SCSI and PM3224, PM3224W, PM3334W, PM3334UW SCSI RAID HBAs

Solaris Device Driver:

dpt

Device Type:

SCSI, SCSI RAID 

Adapters:

DPT PM2024, PM2044W, PM2044UW, PM2124, PM2124W, PM2144W, PM2144UW SCSI  

DPT PM3224, PM3224W, PM3334W, PM3334UW SCSI RAID 

Bus Type:

PCI 

This is a third-party driver developed by DPT. For support and information about possible updates to this driver, contact DPT at http://www.dpt.com.

Preconfiguration Information

Known Problems and Limitations

During the system boot, if you see a message that 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.

Supported Settings

o I/O Address: 

Auto 

IBM PC ServeRAID SCSI, ServeRAID II Ultra SCSI, ServeRAID-3 Ultra2 SCSI HBAs

Solaris Device Driver:

chs

Device Type:

SCSI RAID 

Adapters:

IBM PC ServeRAID SCSI, ServeRAID II Ultra SCSI, ServeRAID-3 Ultra2 SCSI 

Bus Type:

PCI 

This is a third-party driver developed by Compaq Computer Corporation. For support and information about possible updates to this driver, contact Compaq at http://www.compaq.com.

Preconfiguration Information

Known Problems and Limitations

To prevent data loss, a SCSI disk drive that is not defined to be part of any physical pack within a logical drive won't be accessible through the Solaris operating environment.

Mylex DAC960PD-Ultra, DAC960PD/DAC960P, DAC960PG, DAC960PJ, DAC960PL, DAC960PRL-1, DAC960PTL-1 Controllers

Solaris Device Driver:

mlx

Device Type:

SCSI-2 RAID 

Adapters:

Mylex DAC960PD-Ultra (PCI-to-UltraSCSI)  

DAC960PD/DAC960P (PCI-to-SCSI) 

DAC960PG (PCI-to-SCSI)  

DAC960PJ (PCI-to-SCSI)  

DAC960PL (PCI-to-SCSI)  

DAC960PRL-1 (PCI-to-SCSI) 

DAC960PTL-1 (PCI-to-SCSI)  

Bus Type:

PCI 

Preconfiguration Information

Known Problems and Limitations

Ethernet Network Adapters

3Com EtherLink XL (3C900, 3C900-COMBO, 3C900B-COMBO, 3C900B-TPC, 3C900B-TPO), Fast EtherLink XL (3C905-TX, 3C905-T4, 3C905B-TX, 3C905B-T4)

Solaris Device Driver:

elxl

Device Type:

Network (Ethernet) 

Adapters:

3Com EtherLink XL (3C900, 3C900-COMBO, 3C900B-COMBO, 3C900B-TPC, 3C900B-TPO) 

Fast EtherLink XL (3C905-TX, 3C905-T4, 3C905B-TX, 3C905B-T4)  

Bus Type:

PCI 

Preconfiguration Information

Supported Settings

o Media Type: 

Auto Select 

Known Problems and Limitations

3C905B cards in a Compaq ProLiant 6500 can fail to generate interrupts. There is no known workaround for this problem. However, since some slots appear to be more prone to the problem than others, moving the card to another PCI slot might help. Also, successive reboots of the machine have succeeded in getting the card out of the wedged state.

AMD PCnet Ethernet (PCnet-PCI, PCnet-PCI II, PCnet-Fast)

Solaris Device Driver:

pcn

Device Type:

Network (Ethernet) 

Adapter:

AMD PCnet 

Chips:

PCnet-PCI, PCnet-PCI II, PCnet-Fast 

Bus Type:

PCI 

Preconfiguration Information

Known Problems and Limitations

The Solaris pcn driver does not support IRQ 4.

Compaq NetFlex-3, Netelligent Controllers

Solaris Device Driver:

cnft

Device Type:

Network (Ethernet) 

Adapters:

  • Compaq NetFlex-3/P and:

    • 10BASE-T UTP Module (included)

    • 10/100BASE-TX UTP Module (optional)

    • 100VG-AnyLAN UTP Module (optional)

    • 100BASE-FX Module (optional)

  • Compaq Netelligent 10 T PCI UTP with TLAN 2.3 or TLAN 3.03

  • Compaq Netelligent 10/100 TX PCI UTP with TLAN 2.3 or TLAN 3.03

  • Compaq NetFlex-3 PCI with TLAN 2.3 and:

    • 10BASE-T UTP Module (included)

    • 10/100BASE-TX UTP Module (optional)

    • 100VG-AnyLAN UTP Module (optional)

    • 100BASE-FX Module (optional)

  • Compaq NetFlex-3 DualPort 10/100TX PCI UTP

  • Compaq Integrated NetFlex-3 10/100 T PCI with AUI on ProLiant 2500

  • Compaq Integrated NetFlex-3 10/100 T PCI UTP/BNC on Deskpro 4000/6000 and ProLiant 800

  • Compaq Netelligent 10 T PCI UTP Version 2 with TLAN 3.03

  • Compaq Netelligent 10/100 T PCI UTP Version 2 with TLAN 3.03

Bus Type:

PCI 

This is a third-party driver developed by Compaq Computer Corporation. For support and information about possible updates to this driver, contact Compaq at http://www.compaq.com.

Preconfiguration Information

Supported Settings

NetFlex-3/P controllers:

o IRQ Level: 

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

Netelligent controllers:

o IRQ Level: 

2(9), 3, 4, 5, 6, 7, 10, 11, 12, 14, 15 

Known Problems and Limitations

Configuration Procedure

  1. Install the Solaris software.

  2. Modify the driver configuration file /platform/i86pc/kernel/drv/cnft.conf.

    This file specifies the valid configurable parameters for the driver:

    • duplex_mode: This property forces the duplex mode for the controller. It can be set to:

      • 0 - Autoconfigure (Default)

      • 1 - Half duplex

      • 2 - Full duplex

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

      • 0 - Autoconfigure (Default)

      • 10 - Force 10-Mbps media speed

      • 100 - Force 100-Mbps media speed

    • max_tx_lsts, max_rx_lsts, tx_threshold: These properties tune driver performance. The valid values are:

    Property 

    Valid Values 

    Default Value 

    max_tx_lsts

    4 to 16 

    16 

    max_rx_lsts

    4 to 16 

    16 

    tx_threshold

    2 to 16 

    16 

    • debug_flag: Set this property to 1 or 0 to enable or disable debug messages from the driver. Debug messages are disabled by default.

    • mediaconnector: Set to 1 to enable the AUI interface for the Integrated NetFlex-3 controller on ProLiant 2500 systems or to enable the BNC interface on the Integrated NetFlex-3 controller on the ProLiant 800 and Deskpro 4000/6000. The UTP interface is the default (0).

    • board_id: Set this property to support additional PCI controllers. The format of the board_id is 0xVVVVDDDD, where VVVV means vendor ID and DDDD, device ID. More than one ID can be specified, if required.

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

    # touch /reconfigure
    # reboot
    

DEC 21040, 21041, 21140, 21142, 21143 Ethernet

Solaris Device Driver:

dnet

Device Type:

Network (Ethernet) 

Adapters:

DEC 21040, 21041, 21140, 21142, 21143 

Bus Type:

PCI 

Preconfiguration Information

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

Supported Settings

These successfully tested 21040/21041/21140/21142/21143-based adapters are supported.

Name/Model 

Part/Version 

Chip 21xxx

10 MB Media 

100 MB Media 

Notes 

Adaptec ANA-6911A/C 

143PA 

T B 

 

Adaptec ANA-6911A/TX 

143PA 

 

AsanteFAST 

09-00087-11 D 

140AA 

CNet PowerNIC CN935E 

041AA 

T B 

 

 

Cogent EM110 T4 

110101-01 

140 

T B 

 

Cogent EM110TX 

110001-02 06 

140AB 

 

Cogent EM110TX 

110001-03 01 

140AB 

 

Cogent EM110TX 

110001-03 14 

140AC 

 

Cogent EM440 QUAD 

440001-01 01 

140AC 

Cogent EM960C 

960001-03 06 

040AA 

T B A 

 

 

Cogent EM960C 

960001-04 02 

040AA 

T B A 

 

Cogent EM960TP 

960001-03 07 

040AA 

 

 

Cogent EM960TP 

960001-04 01 

040AA 

 

 

Cogent EM964 QUAD 

964001-00 01 

040AA 

 

 

Compex ReadyLINK ENET32 

B2 

040AA 

T B A 

 

 

D-Link DE530CT 

A2 

040AA 

T B 

 

 

D-Link DE530CT 

D2 

041AA 

T B 

 

 

D-Link DE530CT+ 

A1 

040AA 

T B 

 

 

DEC EtherWORKS 10/100 

DE500 RevD01 

140AC 

5, C 

DEC EtherWORKS PCI 10/100 

DE500-XA RevC01 

140AB 

5, C 

Diversified Tech 

651205025 1.2 

140AC 

Kingston KNE40BT 

2001585 A00 

041AA 

T B 

 

 

Kingston KNE100TX 

2001837-000.A00 

140AC 

Kingston KNE100TX 

2001837-000.B00 

140AC 

Kingston KNE100TX 

9920219-001.B00 

140AB 

Kingston KNE100TX 

9920219-002.B00 

140AC 

Linksys LNE100TX 

8EFPCI01..B1-1 

140AB 

Linksys LNE100TX 

8EFPCI01..B1-3 

140AC 

NetGear 

FA310TX-C2 

140AE 

 

NetGear 

FA310TX-C6 

140AF 

 

Osicom (Rockwell) RNS2300 

320109-02 

140AB 

 

Osicom (Rockwell) RNS2340 QUAD 

320112-00 

140AB 

SMC 8432BT 

60-600510-003 A 

040AA 

T B 

 

 

SMC 8432BT 

60-600528-001 A 

041AA 

T B 

 

 

SMC 8432BT 

61-600510-010 B 

040AA 

T B 

 

 

SMC 8432BTA 

60-600510-003 A 

040AA 

T B A 

 

 

SMC 8432BTA 

61-600510-000 

040AA 

T B A 

 

 

SMC 8432T 

60-600528-001 A 

041AA 

 

 

SMC 9332BDT 

60-600542-000 A 

140AC 

SMC 9332DST 

60-600518-002 A 

140 

X  

SMC 9332DST 

61-600518-000 B 

140 

X  

Znyx ZX311 

SA0027 01 

041AA 

T B A 

 

 

Znyx ZX312 

SA0011 04 

040AA 

T B A 

 

Znyx ZX314 QUAD 

PC0009-05 

040AA 

 

 

Znyx ZX314 QUAD 

SA0014-05 

040AA 

 

 

Znyx ZX315 DUAL 

SA0015 X2 

040AA 

T B 

 

 

Znyx ZX342 

PC0012 X2 

140 

Znyx ZX344 QUAD 

SA0019 X2 

140AA 

 

 

Znyx ZX345 

SA0025 X1 

140AB 

Znyx ZX346 QUAD 

SA0026 X1 

140AC 

Znyx ZX348 DUAL 

SA0028 X2 

140AC 

10 MB Media Codes:

100 MB Media Codes:

Notes:

Known Problems and Limitations

Intel EtherExpress PRO/100 (82556)

Solaris Device Driver:

ieef

Device Type:

Network (Ethernet) 

Adapter:

Intel EtherExpress PRO/100 (82556) 

Bus Type:

PCI 

Connector:

RJ-45 

Preconfiguration Information

Known Problems and Limitations

This driver provides 100-Mbps Ethernet support; however, the driver does not currently transfer the data at rates expected of a 100-Mbps interface.

Intel EtherExpress PRO/100B (82557), EtherExpress PRO/100+ (82558, 82559)

Solaris Device Driver:

iprb

Device Type:

Network (Ethernet) 

Adapters:

Intel EtherExpress PRO/100B (82557) 

EtherExpress PRO/100+ (82558, 82559) 

Bus Type:

PCI 

Connector:

RJ-45 

Preconfiguration Information

Known Problems and Limitations

IA based systems with the Intel EtherExpress PRO/100B or the Intel EtherExpress PRO/100+ might hang when the interface is brought down at the very instant that a packet is being received.

To avoid this, wait until the system is experiencing light or no network traffic before bringing the interface down.

Token Ring Network Adapters

Madge Smart 16/4 Token Ring

Solaris Device Driver:

mtok

Device Type:

Network (Token ring) 

Adapters:

Madge Smart 16/4 PCI Ringnode/Bridgenode 

Smart 16/4 PCI Presto 

Bus Type:

PCI 

This is a third-party driver developed by Madge Networks. For support and information about possible updates to this driver, contact Madge at http://www.madge.com.

Preconfiguration Information

Known Problems and Limitations

When the mtok driver is enabled, the following messages appear when the system startup scripts run ifconfig:

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

These messages can be ignored.

Configuration Procedure

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

When choosing hardware settings:

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

Audio Cards

Analog Devices AD1848 and Compatible Devices

Solaris Device Driver:

sbpro

Device Type:

Audio 

Chips:

Analog Devices AD1848, Compatible Devices (on computer motherboard or add-in card)  

Bus Types:

ISA 


Note -

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


Compatible Device Information

Selected AD1848-based devices are supported by the sbpro device driver. Some audio devices based on other compatible chips are also supported.

Although many audio devices claim to be compatible with other audio devices, they are not always compatible at the hardware level and are not supported by the Solaris software. "Tested Compatible Devices" shows which devices have been tested with the Solaris operating environment.

Some cards based on the AD1848 or compatible chips also support advanced audio features that the sbpro driver does not currently support.

Tested Compatible Devices

The following AD1848 and compatible devices have been tested:

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

The Turtle Beach Tropez card might interfere with the operation of other ISA devices in the system. If installing a Tropez card in the system causes such devices to fail, run the configuration program that came with the device to select a different I/O base address for the card.

Preconfiguration Information


Note -

Many audio devices come with a software utility that allows you to select the IRQ and DMA settings. Often, this utility does not record parameters in nonvolatile memory but in a configuration file used by DOS to set the card's configuration at each reboot. This type of configuration file is not used by the Solaris software and does not affect the operation of the card with the Solaris operating environment.


Supported Settings

If your card supports Plug and Play, your device resources are configured automatically. Use the following settings for devices that don't support Plug and Play. Defaults are shown in this typeface.

Compaq Deskpro XL Business Audio With Built-in AD1847 Chip

o I/O Address: 

0x530, 0x604, 0xE80, 0xF40

The sbpro driver automatically chooses an unused DMA channel and IRQ line for the device.


Note -

The sbpro support for the AD1848 and compatibles uses one DMA channel for both play and record; simultaneous play/record is not supported.


Turtle Beach Tropez Card With CS4231 Chip

o I/O Address: 

0x530

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

The sbpro driver automatically chooses an unused DMA channel and IRQ line for the device.


Note -

The Tropez card comes with a software utility for selecting the IRQ, DMA, and MWSS compatibility I/O address settings used by the card. However, that utility does not record those parameters in nonvolatile memory, but in a configuration file used by DOS to set the card's configuration at each reboot. This type of configuration file is not used by the Solaris software and does not affect the operation of the card with the Solaris operating environment.


Known Problems and Limitations

Compaq Deskpro XL Business Audio With Built-in AD184x Chip

Creative Labs Sound Blaster Pro, Sound Blaster Pro-2

Solaris Device Driver:

sbpro

Device Type:

Audio 

Adapters:

Creative Labs Sound Blaster Pro 

Sound Blaster Pro-2 

Bus Type:

ISA 


Note -

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


Preconfiguration Information

Supported Settings

If your card supports Plug and Play, your device resources are configured automatically. Use the following settings for devices that don't support Plug and Play.

Defaults are shown in this typeface.

o IRQ Level: 

2, 5, 7, 10

o I/O Address: 

0x220, 0x240

o DMA Channel: 

0, 1, 3

Known Problems and Limitations

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

Creative Labs Sound Blaster 16, Sound Blaster AWE32, Sound Blaster Vibra 16

Solaris Device Driver:

sbpro

Device Type:

Audio 

Adapters:

Creative Labs Sound Blaster 16 

Sound Blaster AWE32 

Sound Blaster Vibra 16 

Bus Type:

ISA 


Note -

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


Preconfiguration Information

Supported Settings

If your card supports Plug and Play, your device resources are configured automatically. Use the following settings for devices that don't support Plug and Play.

Defaults are shown in this typeface.

o IRQ Level: 

2, 5, 7, 10

o I/O Address: 

0x220, 0x240, 0x260, 0x280

o 8-bit DMA Channel: 

0, 1, 3

o 16-bit DMA Channel: 

5, 6, 7

Known Problems and Limitations

PC Card (PCMCIA) Hardware

PC Card Adapters

Solaris Device Driver:

pcic

Bus Type:

PC Card 

Connectors:

Up to eight Type I, II, or III sockets 


Caution - Caution -

The Intergraph TD-30/TD-40 machine might lock up. To avoid this, ground yourself by touching some metal on the computer case while inserting and removing the PC Card devices. The prtconf command output might mistakenly indicate that the device is in two sockets. If inserting and removing the card is not detected and the machine hangs, reset the machine.


Preconfiguration Information

Configuration Procedure

Initial Installation and Configuration

  1. Consult the Configuration Assistant for address space, I/O space, and IRQs already used by system devices.

  2. Insert the PC Card adapter.

  3. Install the Solaris software.

  4. Reboot the system.

Adding PC Card Support to a Previously Installed System

  1. Become root.

  2. Do a reconfiguration reboot to reallocate resources:

    # touch /reconfigure
    # reboot
    
  3. Insert the PC Card adapter and turn on the machine.

  4. Boot the system so that the PC Card device driver begins running with the new resources allocated.

Allocating IRQs

  1. Boot with the Configuration Assistant so you can review the resource usage.

  2. Select View/Edit Devices from the Device Tasks menu, and review the list of devices to see how many IRQs are being used.

    There are 16 IRQs, from 0-15. Several IRQs are already assigned. For example, IRQ 3 is reserved for the second serial port, COM2, and IRQ 7 is reserved for the parallel port.

  3. If your system has a COM2 port or a parallel port that is not being used, delete the device to free the IRQ resource for a PC Card.

    1. Select the serial port device using IRQ 3 or the parallel port using IRQ 7, and choose Delete Device.

    2. Choose Continue to return to the Device Tasks menu.

    3. Save the configuration.

  4. Boot the Solaris software.

3Com EtherLink III (3C589) PC Card

Solaris Device Driver:

pcelx

Device Type:

Network (Ethernet) 

Adapter:

3Com EtherLink III (3C589) 

Bus Type:

PC Card 

Preconfiguration Information

Known Problems and Limitations

Network services are automatically started when the system is booted. These services are not started when a network interface is added or shut down after the system has been brought up.

Configuration Procedure

Initial Installation and Configuration

  1. Install the Solaris software.

  2. Boot the system.

  3. Insert the 3Com EtherLink III PC Card device.

Identifying an Unrecognized Card

If you insert a 3C589 card and it isn't recognized (no special files created), use the prtconf command to try to identify the problem.

  1. Become root.

  2. Run the prtconf -D command to see if your 3C589 card is recognized.

    A recognized device will appear in the prtconf output. For example:

    # prtconf -D
    .  .  .
    pcic, instance #0 (driver name: pcic)        
    	.  .  .
    	network, instance #0 (driver name: pcelx)
  3. If pcelx does not appear in the prtconf output, there is a problem with the PC Card adapter configuration or with the hardware. Check to see whether the problem is with the card or the adapter by trying to use the card on another machine and by seeing if it works on the same machine using DOS.

Configuring Two or More Cards

Because the 3C589 card is not supported during Solaris installation, you must update network configuration files before one can be used as a network interface.

  1. Create a /etc/hostname.pcelx# file (where # is a socket number) to specify the host name to be associated with this interface.

  2. Add an IP address for the new host name to the file /etc/inet/hosts.

  3. Ensure that the associated network is listed in /etc/inet/netmasks.

  4. Ensure that the Name Service Switch /etc/nsswitch.conf configuration file includes the network and local services you need.

  5. Reboot the system.


    Note -

    This process is described in System Administration Guide, Volume 3.


Special Files

Device naming in /dev follows standard LAN device naming except that the PPA (physical point of attachment) unit number is the socket where the card resides, not the instance. That is, for the pcelx driver, /dev/pcelx0 (or PPA 0 of /dev/pcelx) is the card in socket 0, while a card in socket 1 is /dev/pcelx1 (or PPA 1 of /dev/pcelx). See the pcelx(7D) man page.

Hot-Plugging

If you remove the 3C589 card, any information you send is discarded, and no error messages are given.

When you reinsert the card in the same socket, the device operates normally. The behavior is similar to temporarily disconnecting the device from the network.

Modem and Serial PC Card Devices

Solaris Device Driver:

pcser

Device Type:

Modem and serial PC Card devices based on the 8250, 16550, or compatible UART at speeds up to 115 Kbps 

Bus Type:

PC Card 

Preconfiguration Information

If a PC Card modem or serial device is recognized, the pcser device driver is automatically loaded, ports and IRQs allocated, and special files created (if they don't already exist).

Configuration Procedure

Initial Installation and Configuration

  1. Install the Solaris software.

  2. Boot the system.

  3. Insert the modem or serial device.

Identifying an Unrecognized Device

If you insert a PC Card modem or serial device and it isn't recognized (no special files are created under /dev/cua or /dev/term), use the prtconf command to try to find the problem.

  1. Become root.

  2. Run the prtconf -D command to see if your modem or serial device is recognized.

    An unrecognized device will appear at the end of the prtconf output. For example:

    # prtconf -D
    .  .  .
    pcic, instance #0 (driver name: pcic)
       .  .  .
       pccard111.222 (driver not attached)
  3. If your device is not recognized "(driver not attached)", use the add_drv command to add the name of your device as another known alias for pcser devices.

    For example, type the following at the command line:

    # add_drv -i'"pccard111.222"' pcser
    

    Note -

    Include the double quotes in single quotes to keep the shell from stripping out the double quotes. Use the identification string listed in the prtconf output. Use the entire string in the add_drv command. See add_drv(1M).


Misidentifying a Recognized Device

  1. Run the prtconf -D command to see if your modem or serial device is erroneously recognized as a memory card.

    If the device is incorrectly recognized as a memory card, for example, the output of the prtconf command could show:

    # prtconf -D
    .  .  .
    pcic, instance #0 (driver name: pcic)
    	.  .  .
    	memory, instance #0 (driver name: pcmem)
    		pcram, instance #0 (driver name: pcram)
  2. Use the Configuration Assistant to identify the memory resource conflict, and add correct information for the device on the View/Edit Devices menu.

    The problem is typically a resource conflict between device memory settings. See "Identifying and Correcting Problems" in the Configuring Devices chapter of this book.

    Another possible cause for this problem is when the PC Card adapter chip is not fully supported, as with machines not listed in the Solaris 8 (Intel Platform Edition) Hardware Compatibility List.

  3. To work properly with the Solaris operating environment, all devices must be accounted for, even those the Solaris environment does not support. The Configuration Assistant software accounts for all devices in your system.

Additional Configuration

When adding a new serial port or modem to the system, you often need to edit configuration files so that applications can use the new communications port. For example, the /etc/uucp/devices file needs to be updated to use UUCP and PPP. See "Overview of UUCP" in System Administration Guide, Volume 3.

Special Files

The serial devices in /dev/term and /dev/cua are named by socket number. A card inserted in socket 0 is pc0, and socket 1 is pc1. See pcser(7D).

Hot-Plugging

If a PC Card modem or serial device is unplugged while in use, the device driver returns errors until the card is replaced in the socket.

The device must be closed and reopened with the card reinserted before the device begins working again. The restart process depends on the application. For example, a tip session automatically exits when a card in use is unplugged. To restart the system, you must restart the tip session.

SRAM and DRAM PC Card Devices

Solaris Device Driver:

pcram

Device Types:

Static RAM (SRAM), Dynamic RAM (DRAM) 

Bus Type:

PC Card 


Note -

Flash RAM devices are not supported.


Preconfiguration Information

If a PC Card memory device is recognized, the pcram device driver is automatically loaded, the physical address allocated, and special files created (if they don't already exist).

Known Problems and Limitations

Configuration Procedure

Initial Installation and Configuration

  1. Install the Solaris software.

  2. Boot the system.

  3. Insert the card.

Identifying an Unrecognized Device

If you insert a memory device and it isn't recognized (no special files created), use the prtconf command.

  1. Become root.

  2. Run the prtconf -D command to display the configuration recognized by the system.

    A recognized device will appear in the prtconf output. For example:

    # prtconf -D
    .  .  .
    pcic, instance #0 (driver name: pcic)
        .  .  .
       memory, instance #0 (driver name: pcmem)
             pcram, instance #0 (driver name: pcram)
    
  3. If your memory device does not appear at the end of the prtconf output, it is not supported and cannot be used with the pcram device driver.

Special Files

The special files created for PC Card memory devices act like disks and have names in the form /dev/dsk/c#t#d#p# or /dev/dsk/c#t#d#s#. See pcram(7D). Abbreviations used in the names are:

c# Controller #

t# Card technology type #, defined as follows:

0 Null--no device

1 ROM

2 OTPROM (One Time PROM)

3 UV EPROM

4 EEPROM

5 Flash EPROM

6 SRAM

7 DRAM

d# Device region of type #, usually zero

p# fdisk partition #

s# Solaris slice #


Note -

A device name can be specified either by a partition name (p#) or a slice name (s#), but not both.


Using PC Card Memory Devices

Since the Solaris Volume Management software recognizes PC Card memory devices, no special vold configuration is required.

    If you don't want to use vold to manage your PC Card memory devices, comment out the "use pcmem" line in the /etc/vold.conf file.

To comment out a line, insert a # character at the beginning of the line.

PC Card memory devices don't need to have file systems on them, though typically, before using a new PC Card memory card, you will want to create a file system on it. DOS PCFS is the best format to use. (You can use virtually any file system format on a PC Card memory card, but most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. See "Using a PCMCIA Memory Card" in the OpenWindows Advanced User's Guide.)


Note -

If you want to redirect the output of a tar command (or dd or cpio) to a PC Card memory device, first create a file system on the card, using the fdformat command without arguments. The card must be reformatted before it can be written on again.


Hot-Plugging

If a memory card is removed while in use, the device driver returns errors until the memory card is inserted into the appropriate socket. Close and reopen the device with the card reinserted, and the memory card will work.

Viper 8260pA, SanDisk Flash, or Any PC Card ATA Devices

Solaris Device Driver:

pcata

Device Type:

ATA PC Card 

Adapters:

Viper 8260pA 

SanDisk Flash 

Or any PC Card ATA device 

Bus Type:

PC Card 

Preconfiguration Information

If a PC Card ATA device is recognized, the pcata device driver is automatically loaded, IRQs allocated, devices nodes created, and special files created (if they don't already exist).

Known Problems and Limitations

Configuration Procedure

Initial Installation and Configuration

  1. Install the Solaris software.

  2. Boot the system.

  3. Insert the PC Card ATA device.

Identifying an Unrecognized Card

If you insert a PC Card ATA device and it isn't recognized (no special files are created), use the prtconf command to try to identify the problem.

  1. Run the prtconf -D command to see if your pcata card is recognized.

    A recognized device will appear at the end of the prtconf output. For example:

    # prtconf -D
    .  .  .
    pcic, instance #0 (driver name: pcic)
       .  .  .
       disk, instance #0
  2. If pcata does not appear in the prtconf output, there is a problem with the PC Card adapter configuration or with the hardware.

    Check to see whether the problem is with the card or the adapter by trying to use the card on another machine and by seeing if it works on the same machine using DOS.

Special Files

For PC Card devices, nodes are created in /devices that include the socket number as one component of a device name that the node refers to. However, the /prtc/dev names and the names in /dev/dsk and /dev/rdsk do follow the current convention for ATA devices, which do not encode the socket number in any part of the name. See the pcata(7D) man page.

Hot-Plugging