Re: em driver worse then fxp driver ... why?

From: Charles Swiger (cswiger_at_mac.com)
Date: 08/10/04

  • Next message: Marc G. Fournier: "Re: em driver worse then fxp driver ... why?" 
    Date: Tue, 10 Aug 2004 17:41:35 -0400
To: "Marc G. Fournier" <scrappy@hub.org>

    [ ...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
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: Marc G. Fournier: "Re: em driver worse then fxp driver ... why?"

    Relevant Pages

    • Re: em driver worse then fxp driver ... why?
      ... > I've tried in bth half and full duplex mode .. ... full duplex, Ierrs climbs, hal ... f-duplex, Collisions climb ... ... It could be that the unmanaged switch is unable to talk full-duplex ...
      (freebsd-net)
    • Checking Duplex mode?
      ... Is there any way to check my NIC's duplex mode (Full-Duplex or Half-Duplex) from Windows. ...
      (microsoft.public.windowsxp.network_web)