From owner-freebsd-acpi@FreeBSD.ORG Thu May 12 20:01:51 2005 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4B3416A4CE for ; Thu, 12 May 2005 20:01:51 +0000 (GMT) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68D3143D79 for ; Thu, 12 May 2005 20:01:51 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 3039 invoked from network); 12 May 2005 20:01:50 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender )AES256-SHA encrypted SMTP for ; 12 May 2005 20:01:50 -0000 Received: from [10.50.41.242] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j4CK1eJw066859; Thu, 12 May 2005 16:01:41 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Thu, 12 May 2005 15:08:23 -0400 User-Agent: KMail/1.8 References: <20050510061713.GA5437@svzserv.kemerovo.su> <200505111525.20199.jhb@FreeBSD.org> <4282D5B2.A26212BC@kuzbass.ru> In-Reply-To: <4282D5B2.A26212BC@kuzbass.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505121508.23926.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Eugene Grosbein Subject: Re: 5.4: pci_link problem on 440BX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2005 20:01:51 -0000 On Thursday 12 May 2005 12:04 am, Eugene Grosbein wrote: > John Baldwin wrote: > > > I'm afraid that I don't understand quite right. > > > The message "no PRT entry" is here only when pci_link is disabled > > > and then problem disappears. What makes you guess that BIOS is broken? > > > > We shouldn't print that message unless pci_link is enabled. When > > pci_link is disabled we shouldn't even be looking at PRT entries. Can > > you try booting a 6.0-snapshot CD and seeing if it works ok? > > I can install 5.4 to another free slice and upgrade it to HEAD using cvs, > will that do? Sure, but I just wanted to see if the 6.0 CD booted ok and worked once it had booted rather than a full blow installation. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org