AW: eepro100/e100 drivers fragment heavily

Todor Todorov (ttodorov@web.de)
Tue, 24 Sep 2002 18:06:20 +0200


Hi everyone,

I can confirm that the nic is set to auto-sensing/auto-negotiation.
There is no way for me to change the behaviour of the switch, it's
always auto-negotiation. Also, I cannot say to what state a port on the
switch is set at one time - if it is half- or full-duplex etc.

But it would seem that I have some sort of hardware problem, my guess
would be the motherboard. Some problems with my cd/dvd drive occurred,
besides this the I installed win xp on the same machine as dual boot to
check it out and the network behaviour is exactly the same. Sorry, it
seems to be false alarm.

Cheers,
Todor

-----Ursprüngliche Nachricht-----
Von: Feldman, Scott [mailto:scott.feldman@intel.com]
Gesendet: Montag, 23. September 2002 22:04
An: 'Todor Todorov'; linux-kernel@vger.kernel.org
Betreff: RE: eepro100/e100 drivers fragment heavily

Todor Todorov wrote:

> The computer is a
> Dell Inspiron 8000 laptop with an internal Actiontec
> modem/nic combo pci card based on the Intel Pro chip, running
> Debian. I observed this behaviour with the eepro100 drivers
> in 2.4.19, 2.4.20-pre6 and 2.4.20-pre7 and e100 drivers in
> 2.4.20-pre6 and -pre7. Pulling data from the network is fine
> and fast though, only sending is a problem. The only hint I
> have of what migh be causing the problem is something I read
> in the specs of my NWAY SOHO switch - it would allow
> full-duplex 100 MBit/sec only based on auto negotiation, if a
> nic is in forced mode (say 100 MBit full-duplex), the swith
> will allow only 100 MBit half-duplex. I tried other high
> quality switches too, but the result was the same.

Please confirm that the switch and nic are both set to auto-neg, or both
the
switch and the nic forced to the same settings (i.e. 100/half). We need
to
make sure both ends of the wire match.

-scott

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/