John Sved wrote, On 07/28/2003 04:14 PM:
Jul 28 08:03:46 xxxx1 kernel: 8139too Fast Ethernet driver 0.9.26 Jul 28 08:03:46 xxxx1 kernel: PCI: Found IRQ 11 for device 00:0b.0 Jul 28 08:03:46 xxxx1 kernel: eth0: RealTek RTL8139 Fast Ethernet at 0xd912e000,
00:e0:7d:78:ae:0d, IRQ 11 Jul 28 08:03:46 xxxx1 kernel: eth0: Identified 8139 chip type 'RTL-8139B' Jul 28 08:03:46 xxxx1 kernel: eth0: Setting half-duplex based on auto-negotiated
partner ability 0000.
This is saying the hub/switch you are plugging into has the problem with autonegotiation.
As you can seen the auto negotiation set half-duplex. using
xxxx1:~ # ethtool -s eth0 autoneg on <snip>
So, as you can see, the autonegotiation during boot forced half-duplex. the ethtool command to autonegotiate forced full duplex.
I'm sorry, I didn't see where the ethtool forced full-duplex.
I do not know why. Maybe its a timing thing. In any case the "fix" is to execute the ethtool command later or after the 8139too module has been loaded. That is why I asked where one can insert the ethtool command.
It has been my experience that since the speed was slowed based on what you are connecting to, it is probably correct (unless you are connected via cross-over with the other computer off). I know you said it is much faster, but is it reliable?
Note, mii-diag is not provided with 8.2 or earlier versions.
I have used it since 6.4. It is in the netdiag package. I am using 8.2 presently. BTW, rtl8139-diag will tell you exactly what it is running. Maybe between modinfo and rtl8138-diag and mii-diag, you can figure out what will work for forcing full-duplex. You might want to check your collisions when set that fast to be sure it is the autonegotiation of your connection that is not working. HTH -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.