From owner-freebsd-current Fri Jan 17 10:42:12 2003 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 836CB37B405 for ; Fri, 17 Jan 2003 10:42:10 -0800 (PST) Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03BAF43ED8 for ; Fri, 17 Jan 2003 10:42:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 13360 invoked from network); 17 Jan 2003 18:42:15 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 17 Jan 2003 18:42:15 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id h0HIg8UT019051; Fri, 17 Jan 2003 13:42:08 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E26FF19.77C7600E@mindspring.com> Date: Fri, 17 Jan 2003 13:42:08 -0500 (EST) From: John Baldwin To: Terry Lambert Subject: Re: bad ACPL asl's on motherboards Cc: freebsd-current@FreeBSD.ORG, "Joel M. Baldwin" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16-Jan-2003 Terry Lambert wrote: > "Joel M. Baldwin" wrote: >> I gather that there are quite a few Motherboards with bad ACPI asl's >> on them. I know that my Abit BP6 sure has problems. As a result I >> can't run ACPI. >> >> What are those of us with these motherboards supposed to to? >> >> I realize that we can use acpidump to get the asl, correct it, >> and then recompile it using iasl from the acpicatools port, to >> generate the aml that can be used during boot. > > There are several things you can do, one of which is what you > have suggested, though you do not go far enough: > > 1) Correct the ASL, make a file modification so that > FreeBSD can run on the system with the incorrect > ASL, and then *notify the motherboard and BIOS > vendors of the correction, and the reason for it*. > > 2) The ASL works *fine* with the Windows ACPI code; > *correct* the FreeBSD code so that it *also* works > fine for FreeBSD (i.e. if the FreeBSD code were a > line-for-line duplicate of the Windows code, then > FreeBSD would not be having these problems, where > Windows does not, would it...). Well, the problem here is that we don't write this code, Intel does. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message