em driver worse then fxp driver ... why?

Marc G. Fournier scrappy at hub.org
Tue Aug 10 17:47:18 PDT 2004


'k, did someone fix something with the em driver? :(  Figuring it couldn't 
hurt to try auto-neg once more, and so far, 0 Ierrs :(  So either someone 
fixed the em problem, or the em problem was transient ... but it was 
originally the default (autoselect), and I only moved it to a hard coded 
*after* playing with all three *sigh*

Thanks ...

On Tue, 10 Aug 2004, Charles Swiger wrote:

> [ ...crossposting between stable and freebsd-net trimmed... ]
>
> On Aug 10, 2004, at 4:37 PM, Marc G. Fournier wrote:
>> I've tried in bth half and full duplex mode .. full duplex, Ierrs climbs, 
>> half-duplex, Collisions climb ...
>
> You should expect to see some collisions (1% or so) when working in 
> half-duplex mode: that's the nature of the beast.
>
> Is your Linksys switch managed or unmanaged?  If you can set both it and the 
> em to manually configured 100/FD, that would be worth trying.  I'd also try 
> swapping a cable plugged into a working fxp box with the machine using the 
> em, and see whether the problems follow, or whether the fxp system starts 
> having issues.  A bad cable or a flaky port on the switch could also be 
> causing your problems, but ethernet autonegotiation failing seems to be more 
> likely given the description.
>
> -- 
> -Chuck
>
>

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664


More information about the freebsd-net mailing list