Date: Wed, 13 Dec 2006 01:22:41 -0600 From: Vulpes Velox <v.velox@vvelox.net> Cc: freebsd-hardware@freebsd.org Subject: Re: nVidia chipsets? Message-ID: <20061213012241.48bf5ef4@vixen42> In-Reply-To: <20061213011338.27f6fe83@vixen42> References: <elk8nt$rh2$1@sea.gmane.org> <20061212004136.4ef66c6f@vixen42> <20061212170913.GK44309@tigerfish2.my.domain> <20061213011338.27f6fe83@vixen42>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Dec 2006 01:13:38 -0600 Vulpes Velox <v.velox@vvelox.net> wrote: > On Tue, 12 Dec 2006 11:09:57 -0600 > Bruce Burden <brucegb@realtime.net> wrote: > > > On Tue, Dec 12, 2006 at 12:41:36AM -0600, Vulpes Velox wrote: > > > > > > The only problem I ever ran into was with was > > > the ethernet chipset. It was originally a bit funky in regards > > > to deciding to go unresonsive for awhile. > > > > > Hmmm, I am having that problem with my Tyan Thunder > > K8WE with the nForce4 Profession chipset using the nfe driver > > from 9/1. I have NOT used the new PHY driver from late October/ > > early November. Perhaps that is the issue? > > > > [brucegb@tigerfish2 ~]$ Dec 6 18:13:44 tigerfish2 routed[444]: > > interface nfe0 to 192.168.1.2 broken: in=0 ierr=3 out=3 oerr=0 Dec > > 6 18:13:49 tigerfish2 routed[444]: interface nfe0 to 192.168.1.2 > > restored > > > > Hmm, now I see there is a 12/11 driver... > > > > Anyway, I have an Intel GB NIC arriving soon, so I'll > > get this dealt with one way or another. :-) > > Nfe? What device is that there? Only seen the nve driver. Never mind. Just noticed it. =^.^=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061213012241.48bf5ef4>