On 7/19/05, Jason L Tibbitts III <[EMAIL PROTECTED]> wrote: > I'm having trouble enabling flow control with the e1000 driver. I'm > running Fedora Core 3 (currently a 2.6.11-ish kernel until the new one > doesn't kill SMP machines). The e1000 driver is version > 5.6.10.1-k2-NAPI. The Ethernet ports are on the motherboard (a > SuperMicro X5DPE): > 03:02.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller > (Copper) (rev 01) > 03:02.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller > (Copper) (rev 01)
Flow control should be supported, but it is autonegotiated at link time. How do you know it isn't on? what does ethtool -d ethX show? > I've tried passing FlowControl=3 and using ethtool -A to force it on, > but the switch never sees it. In fact, I've tried poking and prodding > every related (and not-so-related) tunable on both the driver and the > switch to no avail. Did you try FlowControl=3,3 (two adapters) This is a silly question, but is the driver UP, like with 'ip l set dev ethX up' > Is there a way for me to debug the autonegotiation process so I can > see just what's going on? I tried passing "debug=16" to the module > but things don't look any different afterward. (I suspect it's not > compiled with debugging on, so I'll have to try a recompile.) yes, with make CFLAGS_EXTRA=-DDBG=1 and you'll get buried in log output but there might be something interesting in there when the driver reads the phy registers, please add a DPRINTK for ret_val in e1000_read_phy_reg, at the end. As for debugging the autoneg process, there isn't much to do with that, as it is all run by hardware, we just set up registers and reset the phy. Jesse - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
