Donald J. Becker (becker@super.org) wrote:
: In article <1993Jul21.144239.17632@b11.b11.ingr.com> jon@stimpy.b11.ingr.com (Jonathan Wilson) writes:
: >
: >Anyone seen this problem with Linux 0.99PL10 (SLS) and the current NET-2?
: >We have ThickWire Ethernet connections (external transceivers). However,
: >if I don't put a terminator on the ThinWire connector on the 3C503, I get
: >"receiver overruns", etc. on the console and TCP/IP basically fails to work.
: >I don't mind leaving a terminator on the ThinWire socket, but wonder why
: >Linux requires this and everything else (PC/TCP under DOS, Windows NT) works
: >fine without the terminator. 

: The problem is that the 3c503 device driver uses the built-in thinnet port by
: default.  While the 3c503 might work with an external transceiver in
: this mode, it should really be set up to use the correct transceiver.

: To use the AUI port, the "interface number" for the device
: must be set to a non-zero value.  Eventually this will be an ioctl()
: call, but for now you must make a new kernel with "-DEL2_AUI" set
: while you are making  linux/net/tcp/3c503.o.

I thought it was also set in linux/net/inet/el.c.

: (I'm considering incrementing the "interface number" value each time
: there seems to be a network cable problem.  Comments anyone?)

I would like to see something like this done. That or have an ascii
configuration file seperate from the kernel that is read in at boot. Its real
annoying having to recompile the kernel just because I use thick and the guy
next to me uses thin. The one good point, though, is there is nothing like
recompiling the kernel to find out what else needs fixing (libraries, include
files, gcc, lilo, etc.) :-)

: -- 

: Donald Becker                                        becker@super.org
: Supercomputing Research Center
: 17100 Science Drive, Bowie MD 20715                      301-805-7482