Date: Sat, 4 Sep 2004 01:31:24 -0500 From: Vulpes Velox <v.velox@vvelox.net> To: "Jeremy Messenger" <mezz7@cox.net> Cc: hardware@freebsd.org Subject: Re: motherboard has died, any recommend? nForce2? or else? Message-ID: <20040904013124.2f2af482@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <opsdsgejol9aq2h7@mezz.mezzweb.com> References: <20040825225405.SUTS4710.lakermmtao06.cox.net@smtp.east.cox.net> <20040825232842.14a8cf08@vixen42.24-119-122-191.cpe.cableone.net> <opsdp47rml9aq2h7@mezz.mezzweb.com> <20040903223930.72e603bd@vixen42.24-119-122-191.cpe.cableone.net> <opsdsgejol9aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 04 Sep 2004 01:02:33 -0500 "Jeremy Messenger" <mezz7@cox.net> wrote: > I think, I have finished with the walk throught in pciconf.. > Current, I have six 'noneN': Five are Memory controller and one is > ethernet. The USB 2.0 is already included, so I just add 'device > ehci' in kernel. I don't know if your has same USB as mine (8 USB > ports). Not sure about yours, but here it works nicely under the vr driver. > As for the ethernet, nvnet is out of date that doesn't has our ID. I > went to Nvidia's website and it has newer nforce driver that has > our ethernet support. I have contracted with the nvnet port author > and he is planning to update, then let me to test it. The nvnet in > ports tree is using nforce driver that is from 2003, btw. Try the vr driver? Those are used on some of those boards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040904013124.2f2af482>