From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 8 15:33:56 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14E6B10656AC for ; Mon, 8 Jun 2009 15:33:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2976B8FC08 for ; Mon, 8 Jun 2009 15:33:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id D39CC46B3B; Mon, 8 Jun 2009 11:33:54 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id AEC498A049; Mon, 8 Jun 2009 11:33:51 -0400 (EDT) From: John Baldwin To: Josef Moellers Date: Mon, 8 Jun 2009 10:47:17 -0400 User-Agent: KMail/1.9.7 References: <4A24D29A.5030604@ts.fujitsu.com> <200906051152.24609.jhb@freebsd.org> <4A2CC727.50806@ts.fujitsu.com> In-Reply-To: <4A2CC727.50806@ts.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906081047.17487.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 08 Jun 2009 11:33:53 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: "freebsd-acpi@freebsd.org" Subject: Re: Failure to get past a PCI bridge X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jun 2009 15:33:57 -0000 On Monday 08 June 2009 4:09:11 am Josef Moellers wrote: > 'morning, > > John Baldwin wrote: > > On Friday 05 June 2009 10:51:44 am Josef Moellers wrote: > > > >> Hello, > >> > >> Thanks for the help! > >> > >> John Baldwin wrote: > >> > >>> On Friday 05 June 2009 5:17:25 am Josef Moellers wrote: > >>> > >>> > >>>> Difficult, since I can't boot properly. > >>>> However, I have managed to get the dsdt using a SuSE Linux and have run > >>>> that through acpidump -d on a 7.2 running on a XEN virtual machine. > >>>> Here's the result. > >>>> > >>>> > >>> Hmm, your BIOS is certainly hosed. First, it does have separate processor > >>> objects: > >>> > >> [...] > >> > >> I'll show this to our BIOS people. When I talked to them before, they > >> claimed that everything were OK, since the OSes we support do come up > >> properly. > >> > > > > I think your BIOS is actually ok, sorry my e-mail was a bit of a stream of > > conciousness. > > > That's what my colleague confirmed ;-) > However, being the nice guy that he is, he provided me with a > preliminary extra special test version (he was on the brink of going on > holiday!), which presents the bridges in their numerical order (0, 1, 2, > 0xfe, 0xff). With that BIOS, I finally got access to the keyboard and > RAID controller and all and I'm installing FBSD as I'm writing this. > > So, maybe the algorithm shouldn't be "if we find a bridge with number 0 > which is not the first one, give it another number" shouldn't this be > "if we find *a* *second* bridge with number 0, give it another number"? Yes, that's bascially what my patch does. > > Ah, if you have a working machine where you can build a kernel, you can build > > an new CD using an existing ISO as a template. Simply build a GENERIC kernel > > and install it into some DESTDIR=/foo and mount the ISO image using mdconfig > > to /dist. Then do something like 'mkisofs -o new.iso -r -J -b > > boot/cdboot -no-emul-boot -x /dist/boot/kernel /dist /foo'. If that > > complains about duplicate 'boot/kernel' then you may need to copy all > > of /dist/boot to /foo/boot, install the new kernel into /foo, and > > use '-x /dist/boot /dist /foo'. > > > > Also, if this machine supports PXE boot at all, that can be a way to boot a > > test kernel as well. > Maybe that's what we'll have to do after all. Ok, let me know if it works. Thanks. -- John Baldwin