+-------------------------------------------------------------+
| DC21X4 driver for Novell ODI Server |
| V2.14 |
+-------------------------------------------------------------+
1. Copyright Notice:
First Edition, April 1994
Updated, December 1994
Digital Equipment Corporation makes no representations that
the use of its products in the manner described in this
publication will not infringe on existing or future patent
rights, nor do the descriptions contained in this
publication imply the granting of licenses to make, use, or
sell equipment or software in accordance with the
description.
Copyright Digital Equipment Corporation 1994.
All rights reserved.
Copyright Novell, Inc. 1994.
Do not redistribute the driver files.
NetWare is a registered trademark of Novell Inc.
Alpha, DEC, DECchip, DECnet, Digital, PATHWORKS,
ThinWire, and the DIGITAL logo, are trademarks of
Digital Equipment Corporation.
All other trademarks and registered trademarks are the
property of their respective holders.
2. Overview:
This Readme file explains how to install the Novell NetWare
Odi server driver. This driver is currently supported for the
DECchip 21040, and the DECchip 21040 PCI Evaluation Board (EB40).
This driver also supports DECchip 21140 and
the DECchip 21140 PCI Evaluation Board (EB140).
This driver also supports DECchip 21041 and the DECchip 21041
PCI Evaluation Board (EB41).
This driver also supports DECchip 21142/3 and the DECchip 21142/3
PCI Evaluation Board (EB142/3).
3. Preinstallation Hardware and Software Requirements:
A. Hardware Requirements:
o An IBM-compatible personal computer with 80386 or higher
microprocessor and PCI bus.
o A DECchip 21040-based Ethernet adapter for that bus or
o A DECchip 21140-based Ethernet adapter for that bus or
o A DECchip 21041-based Ethernet adapter for that bus.
o A DECchip 21142/3-based Ethernet adapter for that bus.
B. Firmware Requirements:
o Fully compliant Rev. 2.0 or above PCI BIOS supplied with the PC.
o If Ethernet adapter makes use of DECchip 21050 (PCI-PCI bridge),
PCI BIOS should support PCI-PCI bridge architecture.
C. Software Revision Requirements:
o NetWare version 3.11 or above.
o Novell support modules as supplied in kit directories.
4. Supplied Files:
Table 1: The Novell NetWare ODI Server Directory Files
---------------------------------------------------------------------
README.TXT This File
---------------------------------------------------
RELEASE.TXT Provides a description of updates to the new driver.
---------------------------------------------------
DC21X4.LAN DC21X4 Novell NetWare ODI server driver. This file
supports the EB40, the EB41, the EB140 and the EB142/3
PCI boards.
---------------------------------------------------
DC21X4.LDI Novell network installation file for this driver
---------------------------------------------------
DC21X4.INF Novell network Windows 95 installation file for
this driver
---------------------------------------------------
ETHERTSM.NLM Novell TSM needed to run the ODI server driver
---------------------------------------------------
MSM.NLM Novell MSM needed to run the ODI server driver
---------------------------------------------------
NBI.NLM Novell NBI needed to run the ODI server driver
---------------------------------------------------
MSM31X.NLM Novell MSM needed to run the ODI server driver with
NetWare v3.12, and 3.11 in respective directories.
---------------------------------------------------
NBI31X.NLM Novell NBI needed to run the ODI server driver with
NetWare v3.12 ONLY.
---------------------------------------------------
PATCHMAN.NLM Novell module needed in NetWare v3.1x in addition
to MSM31X.NLM
---------------------------------------------------
A3112.NLM Novell module needed in NetWare v3.11 in addition
to MSM31X.NLM
---------------------------------------------------
LSLENH.NLM Novell module needed in NetWare v3.1x in addition
to MSM31X.NLM
---------------------------------------------------
MONITOR.NLM NetWare server MONITOR module for NetWare v3.11
---------------------------------------------------------------------
5. Installing the Hardware Boards:
A. Installing the DECchip 21040 PCI Evaluation Board
To install the EB40 see the DECchip 21040 PCI Evaluation Board
User's Guide.
B. Installing the DECchip 21140 PCI Evaluation Board
To install the EB140 see the DECchip 21140 PCI Evaluation Board
User's Guide.
C. Installing the DECchip 21041 PCI Evaluation Board
To install the EB41 see the DECchip 21041 PCI Evaluation Board
User's Guide.
D. Installing the DECchip 21142/3 PCI Evaluation Board
To install the EB142/3 see the DECchip 21142/3 PCI Evaluation Board
User's Guide.
6. Installing Software:
To install the Novell NetWare ODI Server Device Driver:
DC21X4.LAN is the Novell NetWare ODI server driver for
both the EB142/3 and the EB40, the EB41 and EB140 PCI
evaluation boards.
1. NetWare v3.1x installation (use respective directory i.e. 3.11 or 3.12):
1.1 Copy The DC21X4.LAN to the SYS:\SYSTEM directory on
the NetWare server.
1.2 Add to your AUTOEXEC.NCF the line required to load
the DC21X4.LAN and bind it. Refer to the sample
AUTOEXEC.NCF for more information (according to the
type of NetWare you are using, i.e. v3.11, 3.12 or 4.x).
2. NetWare v4.x installation:
2.1 Have ready a diskette with DC21X4.LAN and DC21X4.LDI
both from the driver's kit.
2.2 On the server's prompt type: LOAD INSTALL
2.3 When the install program comes up, choose the menu
item that refers to NETWORK DRIVERS.
Note that this menu item is on different place on
different NetWare versions (i.e. v4.0x vs. 4.1x).
2.4 Install the network driver DC21X4.LAN according to
the NetWare manual, or use the on-line instructions
and help.
NOTE: The slot numbers in Netware 3.11 are different from the
ones in Netware 3.12 and 4.x. This is due to the fact that
the 3.12 and 4.x driver (one and the same) use the NBI layer
from Novell, and the 3.11 driver does not. Novell DO NOT and
will NOT supply an NBI layer for 3.11.
7. Parameters
The following parameters belong on the server's command line, or in
the load line inside the AUTOEXEC.NCF. The general way of using these
parameters is:
LOAD <driver name> <PARAMETER NAME>... <PARAMETER NAME[=VALUE]>
Example:
LOAD <driver name> TURBO SLOT=16 FRAME=Ethernet_802.2
Driver specific parameters list (as for NetWare standard parameters,
please see the NetWare user's manual):
AUI selects AUI port on EB41, DE425 or compatible (see DE425
installation instructions to select correct jumper
settings).
TP selects TP port on EB40, EB41 and DE425 or compatible
BNC selects BNC port on EB41, DE425 or compatible (see DE425
installation instructions to select correct jumper
settings).
TP_NO_LINK_TEST selects twisted pair connection, but disables
the LINK test for specific HUBs that do not
support LINK.
TP_FULL_DUPLEX selects twisted pair connection to work in
full duplex mode.
TURBO Fixes the problem of multiple transmit
underflows and receive overflows (i.e. lose of
packets) in systems that use certain PCI
chipsets.
(**) LINE_SPEED selects line speed between 10MPBs and 100MBPs
on network cards based on DC21140.
Format: LINE_SPEED=<value>
Allowed values are: 10,100
(**) GENERAL_PURPOSE_CONTROL user override of the control value in
the GENERAL_PURPOSE register in DC21140
based network cards.
Normally, this value should not be
changed.
Format: GENERAL_PURPOSE_CONTROL=<Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
(**) GENERAL_PURPOSE_DATA user override of the data value in the
GENERAL_PURPOSE register. in DC21140
based network cards.
Normally, this value should not be
changed.
Format: GENERAL_PURPOSE_DATA=<Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
T4 run in T4 100Mbps mode
NT run under NT requester
OS2 run in NetWare for OS/2
Unixware run in UnixWare
Client32Win run in Client32 environment for windows
Client32Win95 run in Client32 environment for Windows95
Client32DOS run in Client32 environment for DOS
Notes:
------
(**) Those keywords affect ONLY DC21140/142/143 based network interface cards.
8. Driver Error messages:
Some messages also have a numerical code printed with them. The codes are
given here to the left of the message (when applicable).
50 - No PCI board found in machine!
Driver could not detect a supported NIC.
53 - Board is disabled for no apparent reason!
Board is not enabled. Normally BIOS & ECU should enable the board.
73 - Unable to allocate memory
Driver failed to allocate needed memory from the OS (receive/transmit
descriptors or needed transmit buffers).
200 - Timeout when initializing DecChip 21X4 with setup packet!
This happens mainly when the PCI slot does not support DMA accordingly.
Make sure the BIOS setup or motherboard switches are set to enable DMA or
Bus Master operation of this slot.
209 - Do not support DC21041 in DC21040 mode
The DC21041 MODE_SELECT pin is connected to VSS making it work in MODE_0,
i.e. as a virtual DC21040 in all respects. The driver does NOT support
this mode.
210 - Driver failed to locate PCI bus!
The machine is not identified as PCI (to support PCI NICs).
211 - Failed to locate DecChip 21X4 on board
Failed to identify a DecChip 21x4 signature in an PCI board.
212 - Unsupported DC21140 chip version
The DC21X4 drivers do not support DC21140 rev 1.0 chip.
If you receive this message, please make sure you have an updated rev of
your NIC.
213 - Unexpected OS behavior. Driver supports 3.11 and later
This identifies a fail of assumption regarding the OS behavior.
214 - Read bad mask value from EISA configuration
An assumption regarding data read from EISA ECU (for EISA based NICs)
failed. This might happen because of incorrect ECU file for that NIC.
215 - Read bad port size value from EISA configuration
An assumption regarding data read from EISA ECU (for EISA based NICs)
failed. This might happen because of incorrect ECU file for that NIC.
216 - Failed to read EISA configuration
An assumption regarding data read from EISA ECU (for EISA based NICs)
failed. This might happen because of incorrect ECU file for that NIC.
217 - Failed to find PCI BIOS
The machine is not identified as PCI (to support PCI NICs). This error is
generated when driver is directed to load PCI NIC (using the 'slot=xx'
keyword, and slot value is a PCI number). If the driver is loaded without
specifying slot number, the driver checks for PCI support, and
in this case will generate another error message (please refer to error
number 210 - Driver failed to locate PCI bus).
218 - Bad PCI BIOS status
PCI BIOS returned a fail status in one of the calls. Please check the BIOS
version and BIOS correctness using an external utility.
219 - Bad PCI BIOS Register err
PCI BIOS returned a fail status in one of the calls. Please check the BIOS
version and BIOS correctness using an external utility.
220 - PCI BIOS failed to initialize DecChip 21040 CBIO reg!
PCI BIOS has initialized a DWORD register in the NIC's configuration
space (at offset 10Hex) with illegal value. Please check the BIOS version
and BIOS correctness using an external utility. Also verify that your
BIOS setup enables I/O and initialize correctly the device in this PCI
slot.
221 - PCI board disappeared...
PCI BIOS is not consistent with returned values per this NIC.
222 - Unsupported TSM version (need x.yz and above)!
This driver supports EtherTSM.NLM of version as specified and higher.
223 - DC21X4 Tx babbles on slot x. Driver halted this slot's NIC.
This is a watchdog put in the driver to make sure the transmit does not
babble on the cable.
224 - DC21X4 detected PCI bus error on slot x (bus error bits = xh).
Driver halted this slot NIC due to that identified error.
225 - PCI BIOS assigned DecChip 21040 an illegal interrupt number
PCI BIOS has initialized a byte register in the NIC's configuration
space (at offset 3CHex) with illegal value. Please check the BIOS version
and BIOS correctness using an external utility. Also verify that your
BIOS setup enables interrupt, assigns a reasonable interrupt value and
initialize correctly the device in this PCI slot.
226 - Could not handle Turbo switch successfully
Failed to operate the 'Turbo' mechanism from one of the following
reasons: - Unknown chipset on the motherboard
- PCI BIOS returned a fail status in one of the calls involved
with operating this mechanism.
227 - Internal CRC table corrupted
Driver found an error in internal CRC table.
228 - Could not handle chipset bug workaround successfully
Failed to operate chipset bug workaround because PCI BIOS returned a
fail status in one of the calls involved with operating this mechanism.
229 - This machine Host to PCI bridge has a known bug. Driver limits DC21X4
bursts as a workaround.
230 - This machine Host to PCI bridge has a known bug when
using cache in WB mode which may cause data corruption or system hang
Please change the cache mode to WT (Write Through) as a workaround
This machine Host to PCI bridge has a known bug that might violate system
integrity. Driver cannot be responsible for outcome, therefor it will
not load in this case. Putting the machine in write-through mode (cache)
makes the system safe to work with. Driver will load in that case.
240 - Unable to locate or read the Ethernet ROM address on board!
This might happen due to bad data stored in the IEEE serial ROM, an error
when reading it, or a wrong data structure burnt into the ROM.
244 - Serial ROM - Read failed
Driver failed to read the IEEE serial flash ROM due to hardware handshake
failure. Make sure the IEEE flash ROM on your NIC is operational using
external utility.
245 - The selected media is unsupported
The selected media is unsupported by the device.
246 - Cannot initalize the network card (CreateNIC failed)
Cannot initalize the network card (CreateNIC failed)
The CreateNIC routine failed, and we cannot initalize the nic
247 - NOT USED.
248 - This machine PCI chipset has a problem that might cause
excessive transmit underflows. Driver works around this, but
performance may be affected.
9. Serial ROM version support
Driver version | Serial ROM version | Serial ROM Burn program version
------------------|--------------------------|-----------------------------------
1.02 and below | Legacy format | No such program
1.03 and 1.04 | Extended Legacy format | SROM v1.00
1.05 to 1.10 | ROM format version 1.00 | SROM v1.01, v1.02, v1.03
2.00 | ROM format version 3.00 | SROM v3.00
2.13 | ROM format version 4.00 | not yet available
Note: The Legacy format is DEC's classical ethernet address format.
The extended legacy format is a middle version between the Legacy
and format version 1.00. It should NOT be used anymore.
The v1.00 format is the current serial ROM format.
Note that the added functionallity in SROM version from v1.01 and up
till SROM v1.03 can be found at the SROM release notes and README file.
10. Hotline and Support Information:
Call the Digital Semiconductor Information Line for information
and technical support:
United States and Canada 1-800-332-2717
TTY (United States only) 1-800-332-2515
Outside North America +1-508-568-6868
Ordering Digital Semiconductor Products
To order Digital's Alpha semiconductor products, contact your
local Digital sales office. When working with your sales
representative, you may be able to take advantage of discounts
and volume pricing.
To order Digital Semiconductor samples or Sample Kits call
1-800-DIGITAL.
You can order the following from Digital:
21040-AA DECchip 21040 PCI Ethernet LAN Controller
21140-AA DECchip 21140 PCI Fast Ethernet LAN Controller
21050-AA DECchip 21050 PCI-to-PCI Bridge
21A40-01 DECchip 21040 PCI Evaluation Board Kit
21A40-02 Quad DECchip 21040 PCI Evaluation Board Kit
21A40-03 DECchip 21140 PCI Fast Ethernet Evaluation Board Kit
21A50-01 DECchip 21050 Evaluation Board Kit
Ordering Associated Literature
Digital Semiconductor documentation and literature is
available with the products. For a complete list and
for information about ordering, contact the Digital
Semiconductor Information Line.
Associated Ethernet Controller Literature:
EC-N0280-72 DECchip 21040 PCI-Ethernet LAN Controller
Data Sheet
EC-QC0BA-TE DECchip 21140 PCI Fast Ethernet LAN Controller
Data Sheet
Ordering Third-Party Literature
You can order the following third-party literature
directly from the vendor:
Title Vendor
----------------------------------------------------------
PCI System Design Guide PCI Special Interest Group
N/S HH3-15A
5200 N.E. Elam Young Pkwy
Hillsboro, Oregon 97124-6497
1-503-696-2000
----------------------------------------------------------
Electronic Orders
To place an order through your account at the Electronic Store,
dial 1-800-234-1998, using a modem set to 2400- or 9600-
baud. You must use a VT terminal or terminal emulator set
at 8 bits, no parity. If you need assistance using the
Electronic Store, call 1-800-DIGITAL (1-800-344-4825) and
ask for an Electronic Store specialist.
Telephone and Direct Mail Orders
From Call Write
__________________________________________________________
U.S.A. DECdirect Digital Equipment Corporation
Phone: P.O. Box CS2008
1-800-DIGITAL Nashua, NH 03061
(1-800-344-4825)
FAX: 603-884-5597
Puerto Phone: Digital Equipment Corporation
Rico 809-781-0505 3 Digital Plaza, 1st Street
FAX: 809-749-8377 Suite 200
Metro Office Park
San Juan, Puerto Rico 00920
Canada Phone: Digital Equipment of Canada Ltd.
1-800-267-6215 100 Herzberg Road
FAX: 613-592-1946 Kanata, Ontario, Canada K2K 2A6
Attn: DECdirect Sales
International - Local Digital subsidiary or
approved distributor
Internal DTN 264-3030 U.S. Software Supply Business
orders 603-884-3030 Digital Equipment Corporation
FAX: 603-884-9690 10 Cotton Road
Nashua, NH 03063-1260
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.