From owner-freebsd-questions@FreeBSD.ORG Sat Jun 21 15:19:03 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9A4A106566C for ; Sat, 21 Jun 2008 15:19:03 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.181]) by mx1.freebsd.org (Postfix) with ESMTP id 6C7D48FC0C for ; Sat, 21 Jun 2008 15:19:03 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by ik-out-1112.google.com with SMTP id c30so1067280ika.3 for ; Sat, 21 Jun 2008 08:19:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=x2QYkGtD5EiHarF3DL+giAb3oZSGeECzZpc0anvvdHw=; b=r6NUctoFxFwaKIN6x1qFenCHOOGFidKaHwdwx8xN85PI52PKV2jxNK/I90ChK7oFax FfnG/Y7DDhNW7bsoXtoYNPEJbpr9YMLwKDhfQcij9epFz81GWogxOOGjo7U9qas6YdCu lSqQDBxUXb94W9r09/HiyhsBAXYJw3Ch8boRs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=lUQwW/jpHk0c1wDAL6aFYMUqM5GMipOMMBtiffR0ZPR8sqqyflZyo11435CtKEueiI mQaL0c5SpULtfyL6kBg8m5C2dqEuaNmLD5al7U1EI3Oq5NUk63zXXv4l9gXSrwTNwfR6 /5eAN6k9S9/JNI4GLYMkEAgVsxnC+IO/vkeB4= Received: by 10.210.54.19 with SMTP id c19mr4217603eba.168.1214061539885; Sat, 21 Jun 2008 08:18:59 -0700 (PDT) Received: by 10.210.22.4 with HTTP; Sat, 21 Jun 2008 08:18:59 -0700 (PDT) Message-ID: <3c0b01820806210818i2afd3d68w225694ee03d06767@mail.gmail.com> Date: Sat, 21 Jun 2008 11:18:59 -0400 From: "Alexander Sack" To: "Pietro Cerutti" In-Reply-To: <3c0b01820806200846j3cab7b60j447e798ac415bba4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3c0b01820806200743r79a246e9h7500d1d1889c0fb3@mail.gmail.com> <485BCA10.5010801@FreeBSD.org> <18032095.post@talk.nabble.com> <485BCEAB.4030907@FreeBSD.org> <3c0b01820806200846j3cab7b60j447e798ac415bba4@mail.gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: ACPI CA Embedded Controller (EC) error messages MSI notebook X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2008 15:19:03 -0000 On Fri, Jun 20, 2008 at 11:46 AM, Alexander Sack wrote: > On Fri, Jun 20, 2008 at 11:37 AM, Pietro Cerutti wrote: >> |> I have a MSI-1034 (M662) Core2 Duo. Attached is my (patched) asl. Dunno >> |> if it can be of any use for you, though.... >> |> >> |> >> | >> | Thanks Pietro, I really appreciate this. Can I ask by chance, does this >> | turn on your battery indicator light on your front panel on your MSI >> | notebook? >> >> This was working anyway, IIRC. > > Ah yea well mine is now completely off charging or not.... :(! I > thought this could be related to the status handler for the battery > but on second thought this maybe something else. > >> | >> | Also, what's the downside of changing ASL? Can I brick my notebook? >> I just >> | have to ask since I am assuming I will be changing the underlying AML >> | generated which I suppose can cause chaos (i.e. I want to make sure I can >> | reset it). >> >> No, it just changes the ACPI code used by the operating system. It >> doesn't modify anything in your laptop. If it doesn't work, just disable >> it and reboot :) > > Ah, I got it. I get confused. The ASL is groked by the core CA > (which provides the main table API for the kernel). Duh! (my ACPI is > rusty) > > Ok, let me look at it some more and see if I can integrate it in for > the battery status section...I'd like to try to get this notebook to > be fully functional if possible! Well still no dice and my battery status light remains off. Question, how did you patch this (or where did you get it patched)? The issue is still CA complaining there isn't a handler for the region. -aps