From owner-freebsd-current Fri Jan 17 11:39: 3 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 58B3A37B401 for ; Fri, 17 Jan 2003 11:39:01 -0800 (PST) Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id C53AF43F1E for ; Fri, 17 Jan 2003 11:39:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 27920 invoked from network); 17 Jan 2003 19:39:06 -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 19:39:06 -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 h0HJcwUT019206; Fri, 17 Jan 2003 14:38:58 -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: <3E2856FB.2050004@speakeasy.net> Date: Fri, 17 Jan 2003 14:38:59 -0500 (EST) From: John Baldwin To: Peter Schultz Subject: Re: bad ACPL asl's on motherboards Cc: "Joel M. Baldwin" , freebsd-current@FreeBSD.ORG, Terry Lambert 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 17-Jan-2003 Peter Schultz wrote: > John Baldwin wrote: > >> 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. >> > The problem is that Mike Smith quit. If I remember correctly, he fixed > two of these for me when he was working on CURRENT. Googling `Mike > Smith freebsd acpi' gets 482 results. If someone can get close to him, > this stuff might get solved. The folks on acpi-jp@ are fairly good at fixing problems with ACPI. Mike did do a lot of work, but he wasn't the only one working on this. The acpi-jp@jp.FreeBSD.org guys have found and fixed several bugs in Intel's code and helped track down problems in BIOS ASL's. Mike didn't write the whole ACPICA stack by himself. -- 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