From: Justin Georgeson <justin.georgeson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: CM vs FF buttons
Date: Tue, 30 Nov 2004 10:13:28 -0600 [thread overview]
Message-ID: <62c1cd27041130081368c53f1e@mail.gmail.com> (raw)
In-Reply-To: <62c1cd2704112622137154df01-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
anybody have any input on this? It'd be really nice to get the sleep
button working
On Sat, 27 Nov 2004 00:13:28 -0600, Justin Georgeson
<justin.georgeson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I have an Inspiron 2600 laptop and the sleep button (Fn+Esc) doesn't
> seem to trigger an ACPI event. It works in Windows, so I tried
> recompiling my DSDT. But that didn't help. Checking out my dmesg
> output, I see this. I read some mention of FF vs CM on the gentoo
> forums post about fixing your DSDT. They mention a kernel patch to
> ignore FF buttons so they might be redetected as CM, but my sleep
> button is already CM. Is there a way to see it as FF?
>
> ACPI: Power Button (FF) [PWRF]
> ACPI: Sleep Button (CM) [SLPB]
>
> --
> ; Justin Georgeson
> ; "Free the mallocs, delete the news"
> ; http://www.openoffice.org
> ; http://www.boycott-riaa.com
>
--
; Justin Georgeson
; "Free the mallocs, delete the news"
; http://www.openoffice.org
; http://www.boycott-riaa.com
-------------------------------------------------------
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/
prev parent reply other threads:[~2004-11-30 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 6:13 CM vs FF buttons Justin Georgeson
[not found] ` <62c1cd2704112622137154df01-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-11-30 16:13 ` Justin Georgeson [this message]
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=62c1cd27041130081368c53f1e@mail.gmail.com \
--to=justin.georgeson-re5jqeeqqe8avxtiumwx3w@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.