te man page on BSDOS

Man page or keyword search:  
man Server   6284 pages
apropos Keyword Search (all sections)
Output format
BSDOS logo
[printable version]

TE(4)			    BSD Programmer's Manual			 TE(4)

NAME
     te - Standard Microsystems Corporation 8115T TokenCard Elite token ring
     adapter

SYNOPSIS
     te0 at isa? port 0x280 iomem 0xd8000

DESCRIPTION
     The te interface provides access to a 4 Mb/s or 16 Mb/s token ring (IEEE
     802.5) network. The 8115T must be plugged into a 16 bit ISA slot.

     The 8115T requires 32 I/O ports starting at one of the following address-
     es: 0x200, 0x220, 0x240, 0x260, 0x280, 0x300, 0x320, 0x340, 0x360, or
     0x380.  Jumpers may be used to select 0x280 or 0x300, to select any of
     the other base addresses a DOS based configuration utility must be run.
     Remember that only the I/O base address set in the configuration is used,
     all other parameters set by the DOS utility are ignored.

     Aside from the base I/O port address all configuration is done by the
     driver. A 16K block of I/O memory (aligned on a 16K boundary) is config-
     ured via the iomem keyword in the configuration. An available IRQ is al-
     located at boot time (from the set: 2(9), 3, 4, 5, 7, 10, 11, 15).

     Before the adapter can be configured up its microcode must be loaded, the
     tesetup utility is used to accomplish this. Once the microcode is loaded
     it need not be loaded again until power is lost (even a hard reset does
     not erase it). It is safe to load the microcode even if it has already
     been loaded, although the interface must be down for the microcode load
     to succeed.

     The adapter attempts to insert itself on the token ring when it is
     ifconfig 'ed up. Ring insertion typically takes around 3 seconds.	If in-
     sertion fails or if a problem occurs while inserted the adapter may re-
     move itself from the ring and initiate retries. A time delay (which in-
     creases with each failure) is imposed before each retry. If the network
     administrator sends a message to the adapter requesting it remove itself
     it will not retry insertion.

     16 bit memory cycles are used to access the 16K shared memory area. If
     this area is placed in the same 128K region (ie: 0xc0000-0xdffff) as a
     card with 8 bit shared memory or ROM that card may not function correct-
     ly.  This is not a problem for ROMs (which are only used at boot time)
     but may be a problem for another adapter with 8 bit shared memory in the
     same region.

MEDIA SELECTION
     Media related features are set via ifconfig(8).  Changing media options
     while the adapter is inserted on the ring will cause it to remove itself
     from the ring and reinsert after a short delay. This is also true of the
     promiscuous flag, if it is changed while the interface is up (by running
     or stopping tcpdump without the -p option for example) the adapter will
     remove itself from the ring then reinsert after a short delay.

DIAGNOSTICS
     Many diagnostics are generated to give ring status or report on hardware
     or configuration errors, more common ones are listed below:

     te%d: microcode not loaded
     The adapter microcode must be loaded (by the tesetup program).

     te%d: inserted in ring
     The adapter has been successfully inserted into the token ring.

     te%d: retrying initialization in %d seconds
     This messages indicates ring reinsertion will be retried after the speci-
     fied time period, this is issued during error recovery.  The adapter ei-
     ther failed to insert itself into the ring or was removed and a re inser-
     tion retry has been scheduled.

     A number of diagnostics regarding ring status may be generated if prob-
     lems are detected with ring wiring or protocol. Generalizing, these er-
     rors are:
	   o   No signal detected or wiring fault: these usually mean there is
	       a break in the wiring or nothing is plugged into the port on
	       the card.
	   o   No other sites detected: this generally happens when the lobe
	       cable isn't plugged into the MAU.
	   o   Beacon frames being transmitted or received: this usually hap-
	       pens when there is a mismatch in ring speed or a wiring prob-
	       lem. After a few seconds in this mode the adapter will remove
	       itself from the ring.

SEE ALSO
     intro(4),	inet(4),  arp(4),  ifconfig(8),	 tesetup(8)

HISTORY
     Written by Eric Varsanyi of BSDI for BSD/OS 2.1.

BSDI BSD/OS			 June 26, 1996				     2
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server BSDOS

List of man pages available for BSDOS

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net