 |
|
|
|
DEC 10/100Base-T
Novell ODI DOS Client
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, 1995, 1996.
All rights reserved.
Do not redistribute the driver files.
Copyright Novell, Inc. 1994, 1995.
Do not redistribute the driver files.
NetWare is a registered trademark of Novell Inc.
Digital Semiconductor, DEC, 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 DOS ODI Client driver.
This driver is currently supported for the:
Digital Semiconductor 21040 PCI Ethernet LAN Controller Digital Semiconductor 21041 PCI Ethernet LAN Controller Digital Semiconductor 21140 PCI Fast Ethernet LAN Controller Digital Semiconductor 21142 PCI Fast Ethernet LAN Controller Digital Semiconductor 21040 PCI Evaluation Board (EB40) Digital Semiconductor 21140 PCI Evaluation Board (EB140)
Digital Semiconductor 21041 PCI Evaluation Board (EB41)
Digital Semiconductor 21142 PCI Evaluation Board (EB142)
Digital Semiconductor 21143 PCI Evaluation Board
(EB143)
An IBM-compatible personal computer with 80386 or higher microprocessor and a PCI bus.
A Digital Semiconductor 21040-based Ethernet adapter for that bus or A Digital Semiconductor 21041-based Ethernet adapter for that bus or A Digital Semiconductor 21140-based Ethernet adapter for that bus or A Digital Semiconductor 21142-based Ethernet adapter for that bus or A Digital Semiconductor 21143-based Ethernet adapter for that bus.
B. Firmware Requirements:
Fully compliant Rev. 2.0 or above PCI BIOS supplied with the PC.
If Ethernet adapter makes use of Digital Semiconductor
21050 (PCI-PCI bridge), PCI BIOS should support PCI-PCI bridge
architecture.
MS-DOS version 3.31 or above.
Novell LSL.COM version 2.16 or above.
Novell IPXODI.COM version 3.02 or above.
Novell NETX.COM version 1.11 or above.
or
Novell VLM.EXE version 1.20B or above.
For getting the most updated revisions of Novell's files, please contact Novell at:
Novell, Inc.
Novell Labs Administration
MS E-13-1
122 East 1700 South
Provo, UT 84606
Tel: 801-429-7000
Fax: 801-429-5224
README.TXT This File
RELEASE.TXT Provides a description of updates to the new driver.
DC21X4.COM DC21X4 Novell NetWare ODI Client driver. This file supports the EB40 EB41 EB140 EB142 and EB143 PCI boards.
NET.CFG Novell network configuration file for this driver
To install the Novell NetWare ODI Client Device Driver:
DC21X4.COM is the Novell NetWare ODI client driver
for the Digital Semiconductor 21140 PCI chipset.
1. Copy the following files to a user specified directory: copy a:\NETWARE\client\*.*
2. Copy the following files provided by Novell to a user specified directory:
LSL.COM IPXODI.COM NETX.COM or VLM.EXE
3. Edit the NET.CFG file if necessary to select protocol and media type options.
NOTICE: NO NEED TO SPECIFY SLOT NUMBER, BUS ID OR INTERRUPT NUMBER!
If you specify Bus ID please notice that for PCI bus you write BUS ID PCI 4 in NET.CFG . If you specify Slot Number please notice that SLOT 1 means in PCI : The first board found in system.
4. To connect to a server, use the following loading sequence:
LSL DC21X4 IPXODI NETX or VLM LOGIN
The following parameters can be used in order to control part of the driver's operation.
These parameters are added to the driver's entry in NET.CFG . For NetWare standard parameters, please refer to NetWare user's manual.
AUI selects AUI port.
TP selects TP port. BNC selects BNC port. T4 selects T4 port. AUTOSENSE enables autosensing of media type when driver is loading (Also called Power-Up Autosense) on all types of supported cards and run-time autosensing of media type on cards based on DC21140 chip designed for supporting Run-time Autosensing. 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.
LINE_SPEED selects line speed between 10MPBs and 100MBPs on network cards based on DC21140 and DC21142.
Format: LINE_SPEED <value>
Allowed values are: 10,100
TURBO Fixes a problem of multiple transmit underflow
and receive overflow (i.e. loss of packets) in systems that use
certain PCI chipsets.
GENERAL_PURPOSE_CONTROL the user can override the control value in the GENERAL_PURPOSE register on network cards based on DC21140 and DC21142. Normally, this value should not be changed.
Format: GENERAL_PURPOSE_CONTROL <Hexadecimal Value>
Allowed values: in the range FFFF-0 hex.
GENERAL_PURPOSE_DATA the user can override the data value in the GENERAL_PURPOSE register on network cards based on DC21140 and DC21142. Normally, this value should not be changed.
Format: GENERAL_PURPOSE_DATA <Hexadecimal Value>
Allowed values: in the range FFFF-0 hex.
RX_BUFFERS Allows the user to select the amount of receive buffers to work with. More buffers means larger driver resident in memory but with higher performance.
Format: RX_BUFFERS <Hexadecimal Value> Allowed
values: in the range 2-0Bhex (12 Decimal). Default values: 12
for DC21140 based cards. 5 for DC21040 and DC21041 based cards.
SNOOZE Changes DC21041 and DC21140 power-management
mode to Power-Saving mode.
Driver selected connection is a combination of Line_Speed selection and Media type selection.
The following 2 tables describe how does the driver detirmine the actual media connection from these two parameters. First the driver determines the Line_Speed according to the following table:
None 100 (MBps) 10 10 (MBps) 100 100 (MBps)
Then the driver determines the connection type according
to the following table:
Requested Connection Requested LineSpeed Selected Connection | AUTOSENSE 10, 100 or None AUTOSENSE AUI 10, 100 or None AUI, (10MBps) BNC 10, 100 or None BNC, (10MBps) T4 100 100BaseT4 T4 10 10BaseT TP 10 10BaseT TP 100 100BaseTX TP_FULL_DUPLEX 10 10BaseT FULL_DUPLEX TP_FULL_DUPLEX 100 100BaseTX FULL_DUPLEX TP_NLT 10 10BaseT NO_LINK_TEST TP_NLT 100 100BaseTX
FATAL: Failed to lock system memory
Driver call to OS memory support routines for locking
its internal buffers and descriptors failed.
FATAL: DC21X4 driver works only with 386 or above!
The driver failed to identify the CPU as a 386 or
above the driver can run on 386 (or above) machines only.
FATAL: Slot value error!
The user has specified an illegal slot number in
NET.CFG
50 - FATAL: Board not found in system
Driver could not detect a supported NIC in the system
200 - FATAL: Timeout when initializing DC21X4 with setup packet!
This happens mainly when the PCI slot does not support
DMA. Make sure the BIOS setup or motherboard switches are set
to enable DMA or Bus Master operation of this slot.
210 - FATAL: DC21X4 Does not support this bus type
The machine is not identified as a PCI machine or
the user has specified BUS ID which is not PCI.
212 - FATAL: DC21X4 Does not support this device revision
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.
217 - FATAL: Failed to find PCI BIOS
The machine is not identified as a PCI machine (to
support PCI NICs). This error is generated when the driver is
directed to load a PCI NIC using the BUS ID keyword (in DC21X4.COM
v2.0 and above) and PCI 4 is specified, or SLOT keyword (in DC21X4
V1.02 and below), and slot value is a PCI slot number (16 and
above).
218 - FATAL: 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 - FATAL: 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 - FATAL: PCI BIOS failed to initialize DECchip 21x40 CBIO reg!
PCI BIOS has initialized a DWORD register in the
NIC's configuration space (at offset 10Hex) with illegal value
(in x86 machines this value is between 0 to FFFFHex). Please check
the BIOS using an external utility. Also verify that your BIOS
setup enables the slot the NIC is plugged in, allocates I/O addresses
to it and initializes correctly the device in this PCI slot.
222 - WARNING: KWD RXD No param
The user added the RX_BUFFERS key word in NET.CFG
but did not specify the number of buffers required. Add the number
of buffers to the KWD (such as: RX_BUFFERS 9)
222 - WARNING: KWD RXD Param too small
The number of Rx buffers specified by the user is
too small for proper driver's work. Please increase the amount
of Rx buffers in RX_BUFFERS KWD in NET.CFG The minimum number
of rx buffers is 2.
222 - WARNING: KWD RXD Param too big
The user had specified more rx buffers than the driver
can handle Please decrease the amount of Rx buffers in RX_BUFFERS
KWD in NET.CFG The maximum number of rx buffers is 16 but it may
be less depending on the driver's size.
225 - FATAL: PCI BIOS allocated an illegal Interrupt to DECchip 21x40!
PCI BIOS has initialized a byte register in the NIC's
configuration space (at offset 3CHex) with illegal value (in x86
machines legal values are between 1 to 15). Please check the BIOS
using an external utility. Also verify that your BIOS setup enables
the slot the NIC is located in, enables interrupts to this slot
and assigns a legal interrupt number to it.
226 - WARNING: Can not handle Turbo switch
Cannot operate the 'Turbo' mechanism from one of
the following reasons: The chipset on the motherboard does not
support TURBO mode. The chipset parameters are unknown to the
driver.
226 - FATAL: Failed to handle Turbo switch
Failed to operate the 'Turbo' mechanism from one
of the following reason: PCI BIOS returned a fail status in one
of the calls involved with operating this mechanism.We strongly
recommend to reboot the PC after such an Error occures
227 - FATAL: Internal CRC table corrupted
Driver found an error in internal CRC table either
because the driver file is corrupted or someone has changed the
table's contents.
228 - FATAL: 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 - WARNING: This machine Host to PCI bridge has a known bug.
Driver limits DC21X4 bursts as a workaround.
230 - FATAL: 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.
231 - WARNING: The PCI Host Bridge present in this
machine requires that the driver switch to Store and Forward Mode.
Network performance may be affected. The driver detected
a PCI Host Bridge with limited data transfer rates to be present
in the PC. it modifies DC21X4 chip parameters for working in such
a system. This may slightly slow the network performance. No further
action is needed.
240 - FATAL: Unable to locate Adapter ROM!
Driver failed either to locate the address ROM or
read it. This might happen due to bad data stored in the serial
ROM.
240 - FATAL: Failed to read ROM!
Driver failed to read the serial flash ROM due to
a hardware failure. Make sure the IEEE flash ROM on your NIC is
operational using external utility.
240 - FATAL: Unsupported ROM Version
The version (and hence the format) of the data read
from the SROM is not supported by the driver. Please run an external
utility to upgrade the Serial ROM's data.
240 - FATAL: This DS chip does not support this ROM version
This ROM version does not contain the information
needed by the driver in order to correctly activate the DS chip
located on-board. Please run an external utility to upgrade the
Serial ROM's data and add the device specific information to it.
241 - FATAL: Unsupported media selection
The NIC or device do not support the requested media
selection. Please check the available media types on the NIC and
use one of them.
242 - WARNING: Could not find an MII PHY with link.
The Power-Up autosense could not find a connected
medium, Please connect a cable to one of the ports and the Autosense
routine will automaticlly find and use it.
10. Hotline and Support Information:
Call Cubix Customer Service for information and technical support:
Voice 1-800-829-0551
Fax 1-702-888-1001
BBS 1-702-888-1003
