From owner-freebsd-current@FreeBSD.ORG Mon Oct 4 01:26:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BB3216A4CE for ; Mon, 4 Oct 2004 01:26:35 +0000 (GMT) Received: from fed1rmmtao02.cox.net (fed1rmmtao02.cox.net [68.230.241.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 181D443D48 for ; Mon, 4 Oct 2004 01:26:35 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by fed1rmmtao02.cox.net (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041004012633.KHLZ26240.fed1rmmtao02.cox.net@mezz.mezzweb.com> for ; Sun, 3 Oct 2004 21:26:33 -0400 Date: Sun, 03 Oct 2004 20:26:49 -0500 To: freebsd-current@freebsd.org References: <200410031812.i93IC79a000175@istari.comcast.net> <20041003203402.GB26177@xor.obsecurity.org> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20041003203402.GB26177@xor.obsecurity.org> User-Agent: Opera M2/7.54 (Linux, build 751) Subject: Re: Networking problems with 5.3-BETA6/7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Oct 2004 01:26:35 -0000 Resend, but only to freebsd-current. Somehow, my client has dropped freebsd-current from the CC. On Sun, 3 Oct 2004 13:34:02 -0700, Kris Kennaway wrote: > On Sun, Oct 03, 2004 at 10:28:04PM +0200, Dag-Erling Sm?rgrav wrote: >> "Stephen J. Roznowski" writes: >> > I'm trying to install 5.3-BETA6 onto an HP Presario SA4000Z. [AMD64 >> > using an nForce3 250 chipset]. I've also upgraded to RELENG_5 and the >> > problem remains. >> > >> > The network configures as "fwe0" and appears to have the correct IP >> > address, but if I attempt to ping the gateway, I get a "Host is down" >> > error. I've tried using "fwip0" instead, but I get the same error. >> >> fwe0 is the Firewire interface, not the Ethernet interface. The >> nVidia nForce3 Ethernet interface is not supported. David O'Brien >> apparently has a driver for it which he hasn't committed yet; you >> could ask him for the sources. Just wondering if it includes PCI/SMBus? I have nForce2 MCP chipest (not AMD64, just i386) with Gigabit Ethernet, so hope his driver will working on nForce2 as I don't mind to test it if it will working with nForce2. > /usr/ports/net/nvnet? The problem with nvnet is that... It's very out of date. The author of nvnet or whomever (programmer) will have to update to match nvidia.com's newer nForce driver for add more IDs and might (not sure) require update some more codes than just IDs. Cheers, Mezz > Kris -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org