On Fri, 2014-02-07 at 13:52 +0000, echo083 wrote: > false config ? so that's not a bug ? There is a longstanding bug in ethtool that when auto-negotiation is enabled you have to specify both speed and duplex to change the advertised modes. > i tried forcing autoneg but it didn't change the speed : > ethtool -s eth0 speed 1000 duplex full autoneg on That ought to work. > full output of ethtool eth0 : > ethtool eth0 > Settings for eth1: Is it eth0 or eth1? Sure you're not getting ports confused? ethtool -p may be helpful if you have multiple Ethernet ports. > Supported ports: [ TP ] > Supported link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Supports auto-negotiation: Yes > Advertised link modes: Not reported This line is weird and is surely a driver bug. > Advertised pause frame use: No > Advertised auto-negotiation: Yes > Speed: 100Mb/s > Duplex: Full [...] I seem to remember that some systems pair an Atheros gigabit controller with a 100M PHY, so they don't support gigabit Ethernet. However the driver should be able to detect and report the actual capabilities. Can you re-check the specifications for your system or network card, to see whether it is supposed to support gigabit Ethernet? Ben. -- Ben Hutchings It is a miracle that curiosity survives formal education. - Albert Einstein
Attachment:
signature.asc
Description: This is a digitally signed message part