|
From: Anand R. M. <an...@gm...> - 2013-03-26 12:03:38
|
On Tue, Mar 26, 2013 at 12:09 PM, Waskiewicz Jr, Peter P <pet...@in...> wrote: > On 3/25/2013 10:56 PM, Anand Raj Manickam wrote: >> >> I m using the e1000e driver for Intel 82574L chipset . >> When the cable is plugged in and Auto Negotiated , It reports as Link >> Detected as NO. I need to do a ifconfig up eth3 to get the Link >> Detected as YES . > > > I suspect the PHY is powered down (intentionally) in this case. My guess is > the interface isn't enabled to be automatically brought up either by > NetworkManager or the SysV network init scripts (or by *gasp* systemd). > Setting the interface to be brought up on boot will solve this for you. > > The ethtool output is telling you how the driver is configured. In the case > you have below, it's ready to perform autonegotiation, but the PHY hasn't > been brought online yet (hence no link detection). It doesn't mean that the > link has already been established and autonegotiated. > > Hope this helps, > -PJ > >> Is this the expected behavior of the new driver - e1000e: Intel(R) >> PRO/1000 Network Driver - 2.2.14-NAPI . >> Is there a work around on the driver for this ? >> >> ethtool eth3 >> Settings for eth3: >> Supported ports: [ TP ] >> Supported link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Supports auto-negotiation: Yes >> Advertised link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Advertised auto-negotiation: Yes >> Speed: 1000Mb/s >> Duplex: Full >> Port: Twisted Pair >> PHYAD: 1 >> Transceiver: internal >> Auto-negotiation: on >> Supports Wake-on: pumbg >> Wake-on: g >> Current message level: 0x00000007 (7) >> Link detected: no I did try to bring up the Link on Boot but still the same behavior . I tried this option to bring PHY up alias eth2 e1000e options SmartPowerDownEnable=1 still no dice .. |