From: "Robert M. Peterson" <robertmpeterson-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Acpi-devel digest, Vol 1 #1632 - 7 msgs
Date: Sat, 28 Feb 2004 18:15:09 -0500 [thread overview]
Message-ID: <1078010109.1436.7.camel@debian> (raw)
In-Reply-To: <20040228220646.WGNP26103.imf02aec.mail.bellsouth.net-ek0oC1U1TqqnvZpeIfgr/KQD96bmaF075NbjCUgZEJk@public.gmane.org>
On Sat, 2004-02-28 at 17:09, acpi-devel-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
wrote:
>
> Message: 5
> From: "Robert M. Peterson" <robertmpeterson-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org>
> To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Date: Sat, 28 Feb 2004 17:18:28 -0500
> Subject: [ACPI] problems with acpi_button in a 2.6 kernel running on a dell i8500
>
> The button to turn the lcd screen off (as when the lid is closed) has
> isn't functional. Also, I found this error in Dmesg: Dell Inspiron with
> broken BIOS detected. Refusing to enable the local APIC. Other areas of
> ACPI seem to be functioning properly as the battery status
> (charging/discharging) and charge level are accurately reported.
>
> Any help would be welcome
I have never used mailing lists before, so if my ettiquette is a bit
off, please excuse me; I did some more research and I have found out
that acpi does in fact properly detect my lid button events... however
it doesn't do anything after that. I am not sure if the problem is with
suspend states or what.
-Robert
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
parent reply other threads:[~2004-02-28 23:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20040228220646.WGNP26103.imf02aec.mail.bellsouth.net-ek0oC1U1TqqnvZpeIfgr/KQD96bmaF075NbjCUgZEJk@public.gmane.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1078010109.1436.7.camel@debian \
--to=robertmpeterson-bdlq13kujeylz21kgmrzwg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.