From owner-freebsd-questions@FreeBSD.ORG Wed Mar 1 15:57:36 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 356B416A420 for ; Wed, 1 Mar 2006 15:57:36 +0000 (GMT) (envelope-from timothy@jupiter.stcl.edu) Received: from list.stcl.edu (list.stcl.edu [207.193.182.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id D721243D6A for ; Wed, 1 Mar 2006 15:57:35 +0000 (GMT) (envelope-from timothy@jupiter.stcl.edu) Received: from localhost (localhost.localdomain [127.0.0.1]) by list.stcl.edu (Postfix) with ESMTP id 8C0BC2FD2B for ; Wed, 1 Mar 2006 09:57:35 -0600 (CST) Received: from list.stcl.edu ([127.0.0.1]) by localhost (list.stcl.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18788-10 for ; Wed, 1 Mar 2006 09:57:35 -0600 (CST) Received: from neptune.stcl.edu (neptune.stcl.edu [207.193.182.201]) by list.stcl.edu (Postfix) with ESMTP id 706622FD13 for ; Wed, 1 Mar 2006 09:57:35 -0600 (CST) From: Timothy To: freebsd-questions@freebsd.org Date: Wed, 1 Mar 2006 09:57:34 -0600 User-Agent: KMail/1.8.2 References: <200603010929.23588.timothy@jupiter.stcl.edu> <4405C0E9.1070005@viviotech.net> In-Reply-To: <4405C0E9.1070005@viviotech.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603010957.34958.timothy@jupiter.stcl.edu> X-Virus-Scanned: amavisd-new at stcl.edu Subject: Re: Via Velocity Gig Ethernet will not initialize on FreeBSD 6 Release X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 15:57:36 -0000 On Wednesday 01 March 2006 09:42 am, Jordan Michaels wrote: > We just had a similar situation with an NForce4 onboard GigE NIC. We > were using a linux OS, but it turns out it was the 100mb switch we had > it plugged into. Near as I can tell, the switch and the NIC had trouble > auto-negotiating the connection rate. Once we connected the GigE NIC to > a GigE switch, the NIC worked beautifully. > > I'm not sure what "MII read timed out" means, but the OS does see the > NIC and appears to be attempting to use it. You may want to check to see > if it's the switch you're connecting to rather then the OS you're running. > > HTH! I have the same error when plugging into a D-Link DGS-108 gigabit switch or a Linksys Gigabit Workgroup switch. Both work with the same computer running Linux, but I want to run FreeBSD on this box. Thanks for the info though. Timothy