From owner-freebsd-current@FreeBSD.ORG Sat Jul 24 22:26:54 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 4A1E416A4D0; Sat, 24 Jul 2004 22:26:54 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D28C943D1D; Sat, 24 Jul 2004 22:26:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i6OMQSJr030060; Sat, 24 Jul 2004 16:26:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 24 Jul 2004 16:26:38 -0600 (MDT) Message-Id: <20040724.162638.90063829.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <40FE1576.10206@elischer.org> References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: jhamby@anobject.com cc: freebsd-mobile@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) 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: Sat, 24 Jul 2004 22:26:54 -0000 In message: <40FE1576.10206@elischer.org> Julian Elischer writes: : Jake Hamby wrote: : > 1) Ethernet chipset not recognized. : > : > This laptop uses the SiS 648 chipset and includes a 10/100 Ethernet : > port with a Realtek 8139-compatible interface. More specifically, it : > is vendor id 0x10EC (Realtek), device id 0x8139 on PCI device : > 00:07.0, recognized as type 'RTL-8100B/8139D' by the Linux 8139too : > driver. : > : > What is even stranger is that this card shows up in a DOS-based : > hardware scan (using AIDA from the Ultimate Boot CD), but not in the : > output of pciconf. Nor does it show up in the dmesg output, even as : > an unknown device. : : probably an unsupported bridge between it and the CPU.. : I'll let the bus enumeration types handle that.. This is a known problem, but I have no clue why it happens. Since it is at 0:7:0, there's no bridges between it and the CPU. I'm guessing that there's some minor, tiny standard violation in our pci config cycle generation. Either that, or there's some power domain that isn't properly being turned on when you boot an acpi based OS. It is hard to say w/o access to the hardware. Warner