From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Pedro I. Sanchez" Subject: Re: Help with the DSDT for an Acer Ferrari 3400 laptop Date: Tue, 28 Dec 2004 21:51:06 -0500 Message-ID: <41D21B9A.4020409@rogers.com> References: <41D0F15D.8000201@rogers.com> <20041228105611.GF9606@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20041228105611.GF9606-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Bruno Ducrot Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Bruno Ducrot wrote: > On Tue, Dec 28, 2004 at 12:38:37AM -0500, Pedro I. Sanchez wrote: > >>Hello, >> >>I'm new to this ACPI world and I'd like your help to fix the dsdt.dsl >>file that I got with this laptop. I followed the steps in the ACPI FAQ >>to disassemble the bin file and ended up with a source file that >>compiles with 8 errors and 1 warning using the Intel ASL compiler. >> >>For your reference the problem I want to fix is that I have no control >>over the fan which is always on, quite annoying. Even though my Linux >>kernel has compiled ACPI fan support the directory /proc/acpi/fan is >>empty. I'm running vanilla kernel 2.6.10 with Debian-AMD64. >> >>The good news is that the 8 errors are actually the same one spread all >>over the source file. So fixing it once will fix the whole file. The bad >>news is that I don't know how to fix it :| >> >>The Error >>--------- >>dsdt.dsl 4480: If (LLess (\_PR.CPU0._PPC, Local1)) >>Error 1022 - Object does not exist ^ (\_PR.CPU0._PPC) >> >>The error is repeated every time the object \_PR.CPU0._PPC appears in >>the code. I read in the FAQ that one possible solution is to use the >>statement >> >> External(\_PR.CPU0._PPC) >> >>to tell the compiler that this is an external object. However I don't >>understand where this External statement should go. I've tried putting >>it at the beginning of the file and inside the Scope(\_PR) section which >>simply reads >> >> Scope (\_PR) >> { >> Processor (CPU0, 0x00, 0x00004010, 0x06) {} >> } >> >>In both cases the compiler complains. So, where shall this External >>statement go? > > > They go to a SSDT table likely. If you do something like: > sudo ./acpidmp SSDT > ssdt > and > iasl -d ssdt > you should get those external statements. > I'm looking for acpidmp in my Debian box but I can't find it, it's not in the pmtools package. And I can't find it in the Intel's download page either (http://www.intel.com/technology/iapc/acpi/downloads.htm). Where can I get it? Also, what am I supposed to do after disassembling the ssdt? > >>The Warning >>----------- >>dsdt.dsl 4287: Method (SMSL, 0, NotSerialized) >>Warning 2019 - ^ Not all control paths return a value (SMSL) >> >>I added a Return (0x00) statement at the very end of the method and the >>warning disappeared. But, is this right? Following my signature you will >>find the code of the offending method including my extra line. > > > Could you send me the original DSDT please (or better the full acpidmp) > or even better provide a link? > You will find the DSDT and some other files at http://www.colcan.biz > I don't think it's very problematic, but I need to look a little bit > further to be sure. This method is "internal" and is called by other > methods, so need to check what those methods do with the return value. > > Cheers, > Thank you for your follow up. -- Pedro ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/