 |
|
|
|
DEC 10/100Base-T
NetWare Server
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.
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).
An IBM-compatible personal computer with 80386 or higher microprocessor and PCI bus.
A DECchip 21140-based Ethernet adapter for that
bus.
If Ethernet adapter makes use of DECchip 21050 (PCI-PCI
bridge), PCI BIOS should support PCI-PCI bridge architecture.
NetWare version 3.11 or above.
Novell support modules as supplied in kit directories.
README.TXT This File
RELEASE.TXT Provides a description of updates to the new driver.
DC21X4.LAN DC21X4 Novell NetWare ODI server driver.
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
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.
2. NetWare v4.x installation:
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.
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 .
TP selects TP port on EB40, EB41 and DE425 or compatible.
BNC selects BNC port on EB41, DE425 or compatible
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.
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.
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.
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
or PCI BIOS returned a fail status in one of the calls involved
with operating this mechanism.
Driver found an error in internal CRC table.
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.
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.
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.
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.
The selected media is unsupported by the device.
Cannot initalize the network card (CreateNIC failed)
The CreateNIC routine failed, and we cannot initalize the nic
247 - NOT USED.
Driver works around this, but performance may be
affected.
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.
Voice 1-800-829-0551
Fax 1-702-888-1001
BBS 1-702-888-1003
