From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 12:43:34 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 5E16F16A41F for ; Sun, 24 Jul 2005 12:43:34 +0000 (GMT) (envelope-from paul.richards@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF16743D45 for ; Sun, 24 Jul 2005 12:43:33 +0000 (GMT) (envelope-from paul.richards@gmail.com) Received: by nproxy.gmail.com with SMTP id g2so91145nfe for ; Sun, 24 Jul 2005 05:43:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=LbnmE52CQKR5XMAtREb9N2TFG7UQnF81uZO+7Y/Z+WDh1HziTbMAdRcuLOnT3y6wGfhvef1rSdgvmyPLlnrJS1Pxo4Tt7bOORg/4YpMBPUfgIml+7hlhlgS2UfcHwco90+FkM7i8bIW3kGPtgdtwIgrDisKy74ltsK4zhrnEy3A= Received: by 10.48.250.11 with SMTP id x11mr129464nfh; Sun, 24 Jul 2005 05:43:32 -0700 (PDT) Received: by 10.48.250.2 with HTTP; Sun, 24 Jul 2005 05:43:31 -0700 (PDT) Message-ID: Date: Sun, 24 Jul 2005 13:43:31 +0100 From: Paul Richards To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: 6.0 BETA1: "nve0: device timeout(..)" on amd64 with nForce4 ethernet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Richards List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2005 12:43:34 -0000 Hi, I have an amd64 machine with onboard nForce4 ethernet. When I attempt to use the interface nve0 I get no data transfer and errors reporting: nve0: device timeout(..) I reported this same problem a couple of months ago but nobody seemed to know of a solution. I decided to try the 6.0 BETA1 release to see if it had been fixed but unfortunately the answer is no. I hope this report is helpful in someway, --=20 Paul Richards