From: Greg Sarjeant <greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>
To: "Scott T. Smith" <scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org>
Cc: "acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: broken power button
Date: Thu, 05 Feb 2004 22:33:55 -0500 [thread overview]
Message-ID: <1076038435.5849.8.camel@localhost> (raw)
In-Reply-To: <1076036158.4792.12.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
Apologies for sending this twice, Scott. I forgot to copy the list.
Hi Scott,
I have the same issue with my power button on my Gateway 200X (which
I think is roughly the same machine as the Dell X200). It appears to be
an issue with fixed-feature power buttons. I opened bug 1920 to address
the problem. You can check it out here:
http://bugzilla.kernel.org/show_bug.cgi?id=1920
Thanks,
Greg
On Thu, 2004-02-05 at 21:55, Scott T. Smith wrote:
> APM will let me suspend to RAM and restore, but the touchpad is broken
> the whole time.
>
> So I'm trying ACPI -- ACPI seems to suspend successfully, but it will
> not wake up. I have to unplug the battery and power supply for 10+
> minutes to reset it.
>
> I think it's related to the power button. I notice that the power
> button does not generate any events via acpid (but if I close the lid,
> or press Fn-ESC, then I do see events). However, if I hold the power
> button down for 4 seconds, the machine does shut off immediately.
> (Holding it down for 4+ seconds while frozen does nothing).
>
> In tracing this further, I noticed that the ASL lists the button 'PWRB',
> while ACPI (via dmesg) lists the button 'PWRF'. I think (can someone
> clarify this?) that this is the difference between a "fixed hardware
> power button" and a "control method power button."
>
> I tried renaming all references to PWRB to PWRF and recompiling, but
> that did no good. I think (again, can someone clarify this?) that I
> need to set the PWR_BUTTON flag, but I don't know how to do that. There
> is a reference to SLP_BUTTON in the dsdt.asl file, but it's in a
> comment.
>
> Am I on the right track here?
>
> oh, specs: 2.6.2-rc2-mm1 (ACPI v20040116), Dell Lattitude X200 (P3M
> 800), patched DSDT to cope with battery issue.
>
> Scott
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-06 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 2:55 broken power button Scott T. Smith
[not found] ` <1076036158.4792.12.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06 3:33 ` Greg Sarjeant [this message]
[not found] ` <1076038435.5849.8.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-02-06 5:07 ` Scott T. Smith
[not found] ` <1076044045.4744.10.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06 12:46 ` Greg Sarjeant
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 17:17 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB686-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-06 17:38 ` Scott T. Smith
[not found] ` <1076089128.4731.1.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06 17:53 ` greg
2004-02-06 17:53 ` Scott T. Smith
2004-02-11 8:02 Yu, Luming
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=1076038435.5849.8.camel@localhost \
--to=greg-qniyhhqvzb9kr2e5yswmoq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=scott-j3vAvQ9dNB9ByuSxxbvQtw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox