[tulip] problem with LNE 100Tx v4.1
Hank Barta
hbarta@enteract.com
Wed, 15 Nov 2000 18:58:42 -0600 (CST)
On Wed, 15 Nov 2000, Chris Reed wrote:
> Date: Wed, 15 Nov 2000 18:05:20 +0000
> From: Chris Reed <cr212@iname.com>
> To: tulip@scyld.com
> Subject: Re: [tulip] problem with LNE 100Tx v4.1
>
> By outgoing connections, do you mean TCP? And does UDP (e.g. name lookups)
> somehow work just fine? Did you try earlier versions of the module before
> this one? Are you using a switch or a hub?
Yes, it is easy to test TCP (ftp, telnet). I'm using a Linksys
10/100 hub. I've tried versions of the module current with
2.2.14 and 2.2.17 kernels, along with the 'current' and 'test'
version of the driver from Becker's site.
> I had very similar problems. I gave up, and put my old card back in the
> machine, leaving the LNE100TX in. Then, when I rebooted, both cards were
> working fine. (Removed my old card, and the LNE100TX still worked). What I
> *think* was happening is that the card was put into a broken state when I
> tried to use the old drivers, and when I switched the machine off to add the
> old network card, it reset itself. This was with a 100Mbit switch, so I
> think what happened was that the card was in half duplex, and the switch in
> full duplex. This, I *think*, is why ping worked (single packets at a time)
> whereas TCP doesn't (lots of packets in quick succession when you establish
> a connection).
Very good point! I don't often power down my box and most boots
try to load an unsuccessful module before I try to load a
modified version. I deleted the tulip modules in /lib/modules/...
and shut down *and* powered off before trying again. Unfortunately
it did not help.
(tulip-diag describes the card as being in half duplex mode and the
box for the router says nothing about full duplex operation, so I
believe that these are correct.)
thanks,
hank
--
Hank Barta White Oak Software Inc.
hbarta@enteract.com Predictable Systems by Design.(tm)
Beautiful Sunny Winfield, Illinois