Re: Realtek 8168D: no active link (188.8.131.52)
From: Jonathan Woithe
Date: Wed May 27 2009 - 20:09:35 EST
> > ethtool -s eth0 autoneg off speed 10
> > - 10 Mbps speed set
> > ethtool -s eth0 autoneg off speed 100
> > - 100 Mbps speed achieved
> > ethtool -s eth0 autoneg on speed 1000
> > - 1000 Mbps speed attained
> > The duplex setting might not be having an effect though since my switch's
> > FDx (full duplex) LED was extinguished for both the 10 and 100 Mbps cases
> > above. Explicitly setting the duplex flag using
> > ethtool -s eth0 autoneg off speed 100 duplex full
> > didn't make any difference - the FDx LED remained off.
> You turned auto negotiation off, and you are surprised that the switch
> doesn't autonegotiate full duplex?
I'm not surprised one way or the other since I have no idea what to expect
when doing these tests on this card with the patches applied. Given that
ethtool has a "duplex" option I naively thought that it controlled the
card's duplex setting. I interprete your comment to mean that duplex can't
be controlled like this and it requires autonegotiation in order to active
full duplex mode. If that's the case then so be it - I'm only reporting
what I did and what effect it had on the card.
FYI, turning off autonegotiation was the only way I had of forcing the
card's speed. If autoneg was left on the "speed 10" and "speed 100" options
made no difference - the card would always configure for 1000 Mbps.
Furthermore, in order to attain 1000 Mbps it was necessary to turn autoneg
on - with it off, "speed 1000" would result in 100 Mbps only. However, I
seem to recall reading somewhere that 1000 Mbps required autoneg so I'm not
all that surprised with that observation.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/