From owner-freebsd-mobile@FreeBSD.ORG Sat Oct 7 15:01:07 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04D2416A403 for ; Sat, 7 Oct 2006 15:01:07 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9185443D49 for ; Sat, 7 Oct 2006 15:01:06 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GWDfk-0001e9-00; Sat, 07 Oct 2006 17:01:04 +0200 Date: Sat, 7 Oct 2006 17:01:03 +0200 To: Torfinn Ingolfsen Message-ID: <20061007150103.GL4945@poupinou.org> References: <20060930001213.a59d721c.torfinn.ingolfsen@broadpark.no> <20061002124116.GF4945@poupinou.org> <20061002203457.22fe5007.torfinn.ingolfsen@broadpark.no> <20061003082804.GG4945@poupinou.org> <20061003205438.26110696.torfinn.ingolfsen@broadpark.no> <20061004120243.GI4945@poupinou.org> <20061005194343.18138f38.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061005194343.18138f38.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-mobile@freebsd.org Subject: Re: Acer Aspire 5672 and FreeBSD 6.2-beta1 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2006 15:01:07 -0000 On Thu, Oct 05, 2006 at 07:43:43PM +0200, Torfinn Ingolfsen wrote: > On Wed, 04 Oct 2006 14:02:43 +0200 > Bruno Ducrot wrote: > > > I would like to see the first 64 bytes, both with and without acpi. > > Ok, you'll get it. :-) > > > You mean under FreeBSD? > > Yes, it's part of the pciutils port (sysutils/pciutils). > > > If so you can use lspci -x instead of pciconf. Cheers, > Thanks. The device do not have a BAR when acpi is enabled. We therefore have to enable one. I think just by poking aroud some pci config registers onto the pci bridge will do the trick. Your ethernet card is attached to the bridge 0:1c:2. It's actually a PCIe one, and thanks to Intel we can get its datasheet at http://download.intel.com/design/chipsets/datashts/30701302.pdf Looking at this datasheet I think we have to look more carrefully to register 0x04 (halfword), 0x20h, 0x24, 0x28 and 0x2c. Looking them both with and without acpi and comparing them will allows us to know hopefully how to enable the first BAR to the correct adress for your ethernet card. In short, if you can first boot without ACPI, then perform pciconf -r -h pci0:28:2 4 pciconf -r pci0:28:2 0x20 pciconf -r pci0:28:2 0x24 pciconf -r pci0:28:2 0x28 pciconf -r pci0:28:2 0x2c Also do a dump in order to check if something else might be needed: pciconf -r -b pci0:28:2 0:256 Boot with ACPI enabled: do the same pciconf stuff, then send me the output. I think we should be able to check if restoring those registers under ACPI will configure correctly the ethernet device by doing a lspci -v -s 4:0.0 After that, we should be able to correct your problem, either by 1- hacking the DSDT, OR 2- hacking pcib.c. (at your option). Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.