Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Apr 1996 23:46:20 -0500
From:      Jim Fleming <JimFleming@unety.net>
To:        "CombsSF@salem.ge.com" <CombsSF@salem.ge.com>, "'Nate Williams'" <nate@sri.MT.net>
Cc:        FreeBSD Hackers List <hackers@FreeBSD.org>
Subject:   RE: ifconfig <whatever> link1 problems
Message-ID:  <01BB266E.C18382A0@webster.unety.net>

next in thread | raw e-mail | index | archive | help
On Tuesday, April 09, 1996 4:31 PM, Nate Williams[SMTP:nate@sri.MT.net] wrote:
@> I've been trying to use the 'ifconfig <whatever net device> inet <address>
@> <netmask> <broadcast> link[0-2] up' syntax with 3Com cards ('509 and '589)
@> on FreeBSD 2.0.5-Release, 2.1.0-Release, and on 2.1.0-Release with the
@> 'pccard-test-960328' patches with no luck at all.  On the 205 and the 210
@> systems it has no effect at all.  On the 210-pccard system 'link2' (the
@> UTP choice) does nothing, the 'link0' or 'link1' causes a hard system lock
@> [ can't even get into the kernel debugger!]  With any of these systems,
@> the only way I've been able to switch xceiver types is with the 3Com
@> config disk!
@
<snip>
@
@However, I'm not sure you can switch between the two connectors 'on the
@fly'.
@

The 3C509B is the standard card in our ISA-based systems. It has many interesting
traits which appear to be a result of its ability to coexist with several such cards and
to be autoconfigured via Port 100. Evidently, multiple cards listen on the Port and
respond at various times. This makes for some potentially unpredictable results but
this appears to only be when the system is first powered up.  Also, the three interface
options (TP, BNC, and AUI) make it a more complex card. The AUI interface is rarely
used and in early drivers seemed to be the default interface.

As you point out, the 3Com configure disk can be used to force the right settings
into the non-volatile memory. (The old days of jumpers on cards seem easier at times)
Even with pre-set values, I have found the cards "move around". They seem to have
a life of their own.

One thing to note is that the system has to have power removed after changing the
Plug & Play setting. Just for good measure, we remove power when all changes are
made via the 3Com utility. When we are really paranoid, we take the card out of the
system and reseat it, although I do not believe this does anything.

Also, these cards used to work in our systems only when Plug & Play was disabled.
Now we have found that they only work with Plug and Play enabled. We have never
been able to figure out why.

We have been able to change the interface from Twisted Pair (10 Base T) to Thin Net
(BNC and coax) on the fly. Old versions of the drivers did not do this because the
logic did not allow the combination of Link0 and Link1 bits to select the right interface.
It is my understanding that this was fixed. By on the fly, I mean once when the system
boots or during reconfiguration not on a per packet basis.

The newer cards and the movement to 100 Mbps interfaces has prompted a rethinking
of the Link0 and Link1 settings. There is a table somewhere that describes how the
new and old settings interwork.

In general, these are great cards. They exhibit more mysterious behavior than any
interface card we have used. Despite this, we continue to use only these cards
because they work once they find the right groove.

--
Jim Fleming
UNETY Systems, Inc.
Naperville, IL 60563

e-mail: JimFleming@unety.net




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BB266E.C18382A0>