From owner-freebsd-questions@FreeBSD.ORG Mon Jun 28 15:24:24 2004 Return-Path: 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 2003E16A4CE for ; Mon, 28 Jun 2004 15:24:24 +0000 (GMT) Received: from mail.u4eatech.com (blackhole.u4eatech.com [195.188.241.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35E6F43D49 for ; Mon, 28 Jun 2004 15:24:23 +0000 (GMT) (envelope-from richard.williamson@u4eatech.com) Received: by mail.u4eatech.com (Postfix, from userid 503) id 69D4A360968; Mon, 28 Jun 2004 16:24:21 +0100 (BST) Received: from apus.u4eatech.com (apus.degree2.com [172.30.40.129]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.u4eatech.com (Postfix) with ESMTP id 6F5E436097C; Mon, 28 Jun 2004 16:24:10 +0100 (BST) Message-Id: <6.1.1.1.2.20040628161506.0a8ff458@cygnus> X-Sender: richard@cygnus X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1 Date: Mon, 28 Jun 2004 16:21:59 +0100 To: Simon Barner , freebsd-questions@freebsd.org From: "Richard P. Williamson" In-Reply-To: <20040625155220.GB873@zi025.glhnet.mhn.de> References: <20040601110940.GA65805@marvin.penguinpowered.org> <20040601115441.GA87441@zi025.glhnet.mhn.de> <6.1.0.6.2.20040601140015.0accf008@cygnus> <20040601143002.GB35382@zi025.glhnet.mhn.de> <6.1.1.1.2.20040625152908.027992a0@cygnus> <20040625155220.GB873@zi025.glhnet.mhn.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 Subject: Re: Intel Ethernet card not being detected X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2004 15:24:24 -0000 At 16:52 25/06/2004. Simon Barner had this to say: >Richard P. Williamson wrote: > >[...] > >Here another thing you could try: I once had a problem with a 3Com NIC >not being detected properly when the driver was compiled statically into >the kernel. > >Removing it and using the module instead made it work... Nope, still no joy. However my boot is telling me userland is out of sync with the kernel now, so I'm not prepared to say "it didn't work" yet. Per the numbers returned by pciconf, this is a 82559 rev 0x8, which is in the table of supported devices. According to the code, however, if the device claims to be 10Mb only, then it isn't even handed to the miibus code to configure. I'm still working my way through the code to determine if the 10Mb-ness is being reported by the devices directly, or if this is the code's interpretation based on other data requested. The two additional 82559 rev 0x8s (on the plug-in PCI card) are correctly being passed to the miibus, and this is annoying. Thanks for your time in this, anyway. MfG, rip