From owner-freebsd-amd64@FreeBSD.ORG  Mon Oct 11 15:56:23 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A849316A4CE
	for <freebsd-amd64@freebsd.org>; Mon, 11 Oct 2004 15:56:23 +0000 (GMT)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2964D43D41
	for <freebsd-amd64@freebsd.org>; Mon, 11 Oct 2004 15:56:23 +0000 (GMT)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp
	id 1CH2X1-0000uQ-58; Mon, 11 Oct 2004 17:56:15 +0200
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4
To: Masahiko KIMOTO <kimoto@ohnolab.org>
In-Reply-To: Message from Masahiko KIMOTO <kimoto@ohnolab.org> 
	<20041012.004122.48404948.kimoto@ohnolab.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 11 Oct 2004 17:56:14 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-Id: <20041011155623.2964D43D41@mx1.FreeBSD.org>
cc: q@onthenet.com.au
cc: freebsd-amd64@freebsd.org
cc: markus.kovero@netsonic.fi
cc: sjr@comcast.net
cc: nakaji@jp.freebsd.org
Subject: Re: nForce3 Internal NIC on FreeBSD 
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2004 15:56:23 -0000

>  > Not sure how well this works... I keep getting:
>  > 
>  > 	nv0: device timeout (20)
>  > 
>  > errors.....
> 
> Markus Kovero has also reported that the device attached but not worked.
> Maybe he is using same machine as mine (shuttle SN85G4).
> However I can use some network applications such as ssh and cvsup 
> via nv0 fine on -CURRENT (checked out two weeks ago).
> Why?
> 

I also have the same Shuttle SN85G4, and is a diskless work station - hence
realy needs the ethernet - and im not having any problems, i've so
far 'make -j4 world' (all over the net), without a glitch.
make -j64 world failed, but that's probably another story

danny