Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Jul 2011 16:31:25 +0000
From:      "Peter Harrison" <four.harrisons@googlemail.com>
To:        "nec556@retena.com" <nec556@retena.com> , "perryh@pluto.rain.com" <perryh@pluto.rain.com>
Cc:        "questions@freebsd.org" <questions@freebsd.org>, "mwlucas@blackhelicopters.org" <mwlucas@blackhelicopters.org>
Subject:   RE: em0 NIC slow on 8.2-p1 amd64?
Message-ID:  <4e285427.cc43d80a.4e87.5777@mx.google.com>

Next in thread | Raw E-Mail | Index | Archive | Help
Sorry for top posting. My 'phone makes it awkward.

I use ndis for the wifi connection in my netbook. Was trivial to conver=
t the Windows driver, and it works without issue.

Anyone know whether it could do 'N' class devices, to address Jerry's l=
ongstanding (and vocal, and justified) complaint - so that we can have =
an argument about why I'd rather configure my wireless manually in a te=
xt file and not have it done automagically by the OS and not be side-tr=
acked by the non-availability of drivers?



--
Peter Harrison
www.4harrisons.blogspot.com
-----Original Message-----
From: perryh@pluto.rain.com
Sent:  21/07/2011 13:05:54
To: nec556@retena.com
Cc: questions@freebsd.org; mwlucas@blackhelicopters.org
Subject:  Re: em0 NIC slow on 8.2-p1 amd64?

Eduardo Morras <nec556@retena.com> wrote:

> If it's not connected at 1 gigabit or not full duplex you can
> force it with ifconfig. If there are too much errors check the
> cable.

Last I heard, this does _not_ work with gigabit unless you can
force-configure both ends of the link.  The negotiation protocol is
such that force-configuring just one end _guarantees_ a mismatch.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd=
.org"




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4e285427.cc43d80a.4e87.5777>