Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Apr 2001 06:06:34 -0500
From:      Greg Putrich <gregp@n0qds.org>
To:        "Matthew Rezny" <mrezny@umr.edu>
Cc:        "net@freebsd.org" <net@freebsd.org>
Subject:   Re: Intel Gigabit NIC problem
Message-ID:  <20010404110634.224AFA5@skeezix.n0qds.org>
In-Reply-To: <200104040849.DAA21587@mrelay.cc.umr.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
I had the exact same problem with FreeBSD 4.1.1 and 4.2. It seems that 
Intel changed the chipset (as you saw) and now it doesn't work quite 
right. I gave up and got a 3Com gigabit ethernet NIC and that one is 
working fine. The Intel card is sitting in it's box right now.

     Greg

On Wednesday, April 4, 2001, at 02:49 , Matthew Rezny wrote:

> I'm posting this to a few lists that I hope I might get some info from.
>
> I have been using the fxp driver for quite a while with good results, 
> so when it came time to get some gigabit stuff I
> looked and saw the wx driver. I decided it would be convenient to stick 
> with Intel for several reasons. So now I have a
> handful of Compaq NC3131 boards with NC6132 modules.
>
> The NC3131 is a 64bit PCI card with a DEC 21154 (later revs have a chip 
> stamped Intel but its id is the same as the
> DEC) PCI bridge and a couple Intel 82558 chips. It also has an 
> expansion connector. The NC6132 module plugs onto
> this card to add a gigabit fiber port. The docs say its an Intel 82542 
> chip, though the actual chip on the boards are
> stamped LSI.
>
> I put them in a few machines here. A couple are x86 boxes with Windows 
> 2000 and/or Linux, for which the Intel drivers
> work and they interconnect fine. The other is an Alpha running FreeBSD 
> 4.2. The fxp and wx drivers load fine, but I have
> problems when I connect the gigabit port to another one of the 
> machines. The FreeBSD machine repeated prints
> "wx0: receive sequence error" while the other machine is overwhelmed 
> with 100% kernel/system CPU usage such
> that its barely responsive.
>
> Does anyone have any idea what's going on, if there's any hope of 
> fixing this, and what the solution would be?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010404110634.224AFA5>