On Wed, Dec 17, 2008 at 1:07 PM, Luigi Rizzo wrote:
> On Wed, Dec 17, 2008 at 12:59:17PM -0800, Paul Saab wrote:
> > are you looking for if_em or em?
>
> also, wasn't the em driver renamed to ixgb or something like that ?
>
No... Maybe you need igb
are you looking for if_em or em?
On Wed, Dec 17, 2008 at 12:56 PM, Uwe Grohnwaldt wrote:
> with latest src, there were no messages about if_em in dmesg. miwi built
> src from 2008-07-27 - there the device was active.
>
> Paul Saab wrote:
>
>> does dmesg show the dev
does dmesg show the device failing to attach?
On Wed, Dec 17, 2008 at 11:37 AM, Uwe Grohnwaldt wrote:
> hi,
>
> i've forgotten the cc, sry.
>
> chers,
> uwe
>
> howdy,
>
> miwi and me tried to update a freebsd-current server to the todays src.
> after the update my em0-device disappeared. inform
driver. However, this is a more obscure
> bug that occurs on some hardware, and it seems to require that you have
> a management BMC, this is what Paul Saab is seeing, there is not a final
> fix for this issue yet.
>
> Note that both these problems only occur with the esb2lan type NIC
Brad wrote:
Source exists for newer Broadcom Gig chips (575x and derivatives) yet
there is no documentation available for that either.
Documentation does exist, just not publically.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org
Simon L. Nielsen wrote:
On 2005.10.31 13:29:44 -0800, Doug Barton wrote:
As I mentioned in my previous post, I have been using earthlink's IPv6
experiment to get an IPv6 connection at home. I am therefore trying to use
it as much as possible to see what works, and what breaks. FreeBSD makes i
We've gotten to the point that we'd like to also extend SACK support to
RELENG_4. When reporting any issues, please include a tcpdump or any
relevant information to help in debugging any issues (core files etc).
http://yogurt.org/FreeBSD/sack4.diff
__
Jon Noack wrote:
Eli Dart wrote:
Careful there.one major reason I use FreeBSD is that, compared
with the other operating systems I can use, major breakages are rare.
I expect the policy that prevents you from deploying the most
featureful OS available is there to avoid the late-night pain
re
Marko Zec wrote:
I've prepared a more or less blind backport of the TCP SACK code which was
recently introduced in -CURRENT. Didn't put the patch through lots of
testing, but it just seems to work... The patch is available from the URL
bellow and should apply cleanly against both 4.10-RELEASE
Ruslan Ermilov wrote:
Dear networkers,
I'm looking for a Broadcom BCM5704[S] technical datasheet. If anyone has
such a beast, or knows how one could obtain it, please let me know.
As john pointed out, you can only get this under NDA from broadcom.
What exactly are you trying to solve? I ha
[EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
Paul Saab
Technical Yahoo
[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
Do You .. uhh .. Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
implementation
> kit and build your own.
You still need the code to drive the nic, and noone gives this out.
I have the latest stuff at:
http://people.freebsd.org/~ps/pxeroms/
Unfortunately you need windows to extract the files.. I can put up
a few more of the files later when I get back fro
12 matches
Mail list logo
