CardBus Ethernet 10/100+Modem 56Troubleshooting

Note: Except where otherwise indicated, the technical information in
this online documentation is valid for the following Xircom products:
RealPort2 CardBus Ethernet 10/100+Modem 56 (R2BEM), RealPort CardBus
Ethernet 10/100+Modem 56 and CardBus Ethernet 10/100+Modem 56.

IBM OS/2 Configuration Reference

The following paragraphs present configuration guidelines for the OS/2
NDIS2 and ODI drivers. An explanation of each keyword can be found in
the Keyword Alphabetical Reference.  All of the drivers described here
automatically detect the speed of the network to which the adapter is
attached (10Mbps or 100Mbps), unless otherwise noted. Speed can also be
specified with the LINESPEED keyword.  Full-duplex operation must be
explicitly configured with the LINEMODE keyword, unless the adapter is
being connected to a hub which supports n-way auto-negotiation. In this
case the adapter will auto-detect full-duplex operation. 

OS/2 NDIS Driver Configuration Notes 

The OS/2 NDIS driver CBENDIS.OS2 conforms to the Microsoft LAN Manager
Network Driver Interface Specification (NDIS) version 2.0.1. It is an
IBM OS/2-based device driver for use with OS/2 versions 2.0 and later. 

The files required for using CBENDIS.OS2 are: 

PROTOCOL.INI  	Configuration and binding information file   
CBEOS2.NIF   	Xircom installation file for Microsoft LAN Manager   
CBENDIS.OS2   	Xircom OS/2 NDIS 2.0.1 driver   

If any parameters need to be changed, use an ASCII text editor to modify
the PROTOCOL.INI file with the appropriate keywords and values.  Keyword
syntax for PROTOCOL.INI can be found below. Keywords are not case
sensitive, and can be abbreviated to a unique sequence of initial
characters (for example, IN for INTERRUPT, IO for IOADDRESS). An
explanation of each keyword can be found in the Keyword Alphabetical
Reference. 

NDIS 2.0.1 Keywords (CBENDIS.OS2) 

Keyword         Valid Values

CACHE           0, 4, 8, 16, or 32  		  
ERT             NOT PRESENT  		  
IOADDRESS       100 - FF80  		  
IRQ             3 - 15  		  
ISAIRQ   	    YES or NO  		  
LATENCY   	    0 - 255  		  
LINEMODE   	    AUTO, HALF or FULL  		  
LINESPEED   	AUTO, 10 or 100  		  
LINKDISABLE   	YES or NO  		  
MEMORY   	    C0000 - 7FFFF000  		  
MODE   	        IO or MEM  		  
NOBURST   	    YES or NO  		  
NOCHECK   	    YES or NO  		  
NOEARLYRX   	NOT PRESENT  		  
NOEARLYTX   	NOT PRESENT  		  
NOLED   	    YES or NO  		  
NOPOLL   	    YES or NO  		  
NOPREFETCH   	YES or NO  		  
NOWRITEPOST   	YES or NO  		  
PCIIRQ   	    YES or NO  		  
RXBUFFERSIZE   	1 - 30  		  
SOCKET   	    1 - 4  		  
TXBUFFERSIZE   	1 - 10  		  
VERBOSE   	    YES or NO  		  
  		 	  

OS/2 ODI Driver Configuration Notes
 
The OS/2 ODI driver CBEODI.OS2 conforms to the Novell ODI Developer's
Guide for OS/2 Client Driver Hardware Specific Modules version 2.1. It
is an IBM OS/2-based device driver for use with OS/2 versions 2.0 and
later. The Novell OS/2 workstation ODI stack including CBEODI.OS2
supports Novell's NetWare Requestor for OS/2 networking client
environment.  Files required for using CBEODI.OS2 include Novell OS/2
Requestor files and the following files:

NET.CFG  	Network configuration file   
CBEODI.OS2   	Xircom ODI driver for OS/2   

If any parameters need to be changed, use an ASCII text editor to open
and modify the NET.CFG file and insert the appropriate keywords and
values after the line LINK DRIVER CBEODI.  Keyword syntax for NET.CFG
can be found below. Keywords are not case sensitive, and can be
abbreviated to a unique sequence of initial characters (for example,
IN for INTERRUPT, IO for IOADDRESS). An explanation of each keyword can
be found in the Keyword Alphabetical Reference.

ODI (CBEODI.OS2) Keywords 

Keyword      	Valid Values   

CACHE   	    0, 4, 8, 16, or 32   
ERT   	        NOT PRESENT   
IOADDRESS   	100 - FF80   
IRQ   	        3 - 15   
ISAIRQ   	    YES or NO   
LATENCY   	    0 - 255   
LINEMODE   	    AUTO, HALF or FULL   
LINESPEED   	AUTO, 10 or 100   
LINKDISABLE   	YES or NO   
MEMORY   	    C0000 - 7FFFF000   
MODE   	        IO or MEM   
NOBURST   	    YES or NO   
NOCHECK   	    YES or NO   
NOEARLYRX   	NOT PRESENT   
NOEARLYTX   	NOT PRESENT   
NOLED   	    YES or NO   
NOPOLL   	    YES or NO   
NOPREFETCH   	YES or NO   
NOWRITEPOST   	YES or NO   
PCIIRQ   	    YES or NO   
RXBUFFERSIZE   	1 - 30   
SOCKET   	    1 - 4   
TXBUFFERSIZE   	1 - 10   
VERBOSE   	    YES or NO   
 
OS/2 Modem Enabler Configuration Notes 

CBMODEM.OS2 will automatically search for the next available COM port.
If there is a conflict, it will be necessary to manually assign the
com port. This is done by using the COMx keyword with CBMODEM.OS2. For
example, to force the com port to COM4, the following line would be put
in CONFIG.SYS: 

 C:\IBMCOM\MACS\CBMODEM.OS2 COM4 

Prior to assigning a COM port, it is necessary to find an available COM
port. To find one, run OS/2's Hardware Manager. Hardware Manager will
display a list of COM parts that are being used. In Hardware Manager,
COM ports are listed as Serial_(Port -1) Serial Controller. The
following table is an example of how the ports are listed: 

Serial_0 Serial Controller  	COM1   
Serial_1 Serial Controller   	COM2   
Serial_2 Serial Controller   	COM3   
Serial_3 Serial Controller   	COM4   

Example:

Hardware Manager displays the following serial ports in use:  

Serial_0 Serial Controller
Serial_3 Serial Controller  

This means that COM1 and COM4 are being used. Therefore, CBMODEM.OS2
should use the next available COM port, COM2.  CBMODEM.OS2 would be
loaded with the following line in CONFIG.SYS:

 DEVICE=C:\IBMCOM\MACS\CBMODEM.OS2 COM2 

CBMODEM.OS2 must be loaded before COM.SYS and CBENDIS.OS2 or CBEODI.OS2 

OS/2 Modem Enabler Keywords (CBMODEM.OS2) 

Keyword  		Valid Values   
CACHE       	0, 8, 16, or 32   	
COMx   	        Auto, 1-4   	
IOADDRESS   	Hardware dependent   	
IRQ   	        3 - 15   	
ISAIRQ   	    No value required   	
LATENCY   	    0 - 255   	
MEMORY   	    Hardware dependent   	
NOCHECK   	    No value required   	
PCIIRQ   	    No value required   	
VERBOSE   	    No value required   	

Driver Keywords Alphabetical Reference

AUTOPOLARITY allows autonegotiation of cable polarity to be turned off.
Default is ON. 

CABLEDETECT turns the automatic cable detect feature on or off. When on,
cable detect senses when there is no LAN cable attached to the card, and
puts the adapter into a low-power mode.  Normal power is restored when
the cable is reattached. 

DYNAMICLINKDETECT determines whether the network cable must be attached
for the driver to load, and whether the driver detects cable removal and
insertion.  When set to OFF, the driver will fail to load if the network
cable is not attached (and a link is not detected) at startup.  When ON
(default), the driver will load at startup and network cable removal and
insertion will be detected at any time.  Turn this parameter OFF if you
are experiencing TCP/IP problems when using Dial-Up Networking. 

EARLYRECEIVE turns the Xircom Advanced Look-ahead Pipelining feature on
or off.  Can be used to troubleshoot network problems.  Use of this
keyword may negatively impact performance. 

EARLYTRANSMIT turns the early transmit feature on or off.  Can be used
to troubleshoot network problems. Use of this keyword may negatively
impact performance.

INITIALIZATION DELAY prevents forwarding of network requests for a
user-selectable period of time.  Delays can be added in the range of
from 1 to 60 seconds.  In most cases a delay of from 1 to 3 seconds
will be sufficient to resolve problems with forwarding of network
traffic.

INTERRUPTNUMBER specifies a hardware interrupt for use by the adapter.
If the computer system uses PCI interrupts on the CardBus bridge, this
parameter is ignored unless InterruptStyle is set to ISA-IRQ. 

INTERRUPTSTYLE forces the driver to use ISA IRQ routing or PCI IRQ
routing.  Some CardBus bridges have the capability of supporting both PCI
and ISA style IRQ routing.  Valid parameters are AutoDetect, PCI-IRQ, and
ISA-IRQ. 

IOBASEADDRESS specifies the base I/O address of the Xircom adapter I/O
ports, in hexadecimal notation.  The Xircom CardBus adapter requires 128
contiguous I/O addresses if run in I/O mode.  If using memory-mapped I/O
mode, no I/O ports are necessary.  If not used, driver will detect an
I/O port automatically. 

LINE_CONFIGURATION sets full NWay negotiation active by default (Auto)
and ignores the Line_Negotiation keyword.  If speed and duplex setting
are forced using the Line_Configuration keyword, the Line Negotiation
keyword can be used to eliminate negotiation messages.

LINEMODE selects either half-duplex or full-duplex mode for the network.
Valid parameters are AutoDetect, Half-Duplex, and Full-Duplex.  Selecting
full-duplex enables the CardBus Ethernet 10/100+Modem 56 to send and
receive data simultaneously when connected to a full-duplex hub. 

LINESPEED forces operation to 10 or 100Mbps.  Valid parameters are
AutoDetect, 10Mbps, and 100Mbps. 

LINE_NEGOTIATION sends NWay messaging at all speeds and duplex settings,
whether or not settings are forced.  Default is On. Off disables NWay
messaging when Line Configuration settings are forced, allowing an
immediate link if required by special circumstances. 

LINKINTEGRITY can be used to turn link integrity off for non-IEEE
10Base-T networks. Default is ON. 

MEMORYBASEADDRESS specifies the host PC memory location for the Xircom
adapter in hexadecimal notation, when MODE MEMORY (memory-mapped I/O) is
being used (see MODE). 

MODE when set to IO disables requests for memory-mapped mode on systems
that only support an I/O-driven card.  The MEMORY setting provides
increased performance on computers that allow simultaneous availability
of memory and I/O resources. 

NDISVERSION allows automatic NDIS version selection for installs under
Windows 2000, 98, and 95. AutoSelect (the default) will choose the
highest NDIS version supported by the operating system.  The user can
also manually switch between the different supported versions of NDIS
by going to NDISVERSION in the network properties of the adapter and
selecting the required driver.  Only drivers supported by the operating
system will be shown.  NDIS driver selection is not supported by Windows
NT 4.0.  The NDIS4 driver can be installed by default from the root of
the Xircom compact disc. 

NETWORKADDRESS can be used to override the adapter's unique network node
address by specifying a different node address.  

Caution: The NETWORK ADDRESS setting should be modified only by a network
administrator.   

PACKETPRIORITY enables support of priority-tagged frames, which are frames
that carry an IEEE 802.1p user priority value in their MAC header.  It is
supported only under Windows 98 Second Edition and Windows 2000, and only
with the NDIS5 driver.  If set to ON under NDIS3 or NDIS4, it will be
automatically reset to OFF and the computer will restart. 

PCCARD SOCKET identifies the number of the host computer's PC slot or
socket into which the Xircom CardBus adapter is inserted. Valid
parameters are AutoDetect, 1, 2, and 3.  If a socket number is specified,
only the specified socket is checked for the Xircom adapter.  Under
AutoDetect, the driver will automatically check all slots for the Xircom
CardBus adapter. 

RECEIVEBUFFERSIZE sets size of the adapter receive packet buffer. This is
a decimal number in the range 1 - 100. Each packet adds approximately
1520 bytes to the resident size of the driver. 

TRANSMITBUFFERSIZE sets the size of the adapter transmit packet buffer.
This is a decimal number of transmit packets in the range 1 - 100. Each
packet adds approximately 1520 bytes to the resident size of the driver.
