On Sun, Jul 02, 2000 at 11:02:13AM -0400, Andrew Gillham wrote:
   > If you are taking your card out of autonegotiate mode, then the switch is
   > not going to be able to figure out the duplex.  Basically you just need to
   > get a NIC that works correctly autonegotiating with your switch, or you
   > are stuck at 100Mbit/s half-duplex.  While a switch can figure out whether
   > you are talking 10Mbit/s or 100Mbit/s at it (when your NIC is not doing
   > NWAY), it has no way to know whether you can receive and transmit at the
   > same time.  I have a Netgear 4 port that has dipswitches that will let me
   > force the port to full-duplex.  My 8 port switch (Linksys DSS-8E?) doesn't
   > have any such fancy stuff so I am forced to get cards that do NWAY right
   > with NetBSD for the machines on that switch.

     The problem though is that while the card and the switch _do_ happily
   negotiate full duplex, as soon as ifconfig runs, the driver messes it up,
   turning off full duplex, no matter what I specify.  So the problem is not
   with the card, but apparently with the driver.  I gather then that what
   you're telling me is that until tlp does NWAY, I'm out of luck.  Is that
   right?  Is there some way I can tell/patch tlp to not mess with the
   autonegotiated speed/duplex settings?



I use the tlp driver with a D-link quad 21143 card.  Running with 1.4P, it
happly autoselects 100Mbits full-duplex when attached to a Linksys 5 port
switch.  It also happly selects 10Mbits half-duplex when attached to a
normal hub.  I'v never had to tell it anything about the speed or duplex.

I probably missed it, but what is being sent as arguments to ifconfig??




Brad Spencer - brad@anduin.eldar.org   http://anduin.eldar.org
[finger brad@anduin.eldar.org for PGP public key]