From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: ACPI-Devel mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI + 3c556 - the saga continues
Date: Wed, 16 Jul 2003 13:21:40 +0200 [thread overview]
Message-ID: <20030716112140.GE4313@enigma.daemon.sh> (raw)
In-Reply-To: <3F152331.9080803-343whMTK1pU@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
hello yaroslav..
* Yaroslav Rastrigin <yarick-343whMTK1pU@public.gmane.org> [2003-07-16 12:42 +0200]:
> What conditions should be met for ACPI event to appear in /proc/acpi/event
> ?
> When I'm manually triggering LID microswitch ,f.e, I'm seeing lot's of
> ACPI
> activity in logs (with upped debug level), and I could see _LID method
> executed, but nothing appears in /proc/acpi/event, and I can't make acpid
> to suspend machine when LID is closed.
> Moreover, there are no events in /proc/acpi/event at all, alhough ACPI
> subsystem notices and handles them. Did I screwed something in my setup ,
> and
> if yes, then what to look for ?
do you know of acpid? check
http://acpid.sourceforge.net
this daemon usually logs output from /proc/acpi/event to /var/log/acpid
(among other things).
and how did you try to access p/a/event? a "tail -f" does not work, but
"cat" does.
hth,
sebastian
--
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-16 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 10:04 ACPI + 3c556 - the saga continues Yaroslav Rastrigin
[not found] ` <3F152331.9080803-343whMTK1pU@public.gmane.org>
2003-07-16 11:21 ` Sebastian Henschel [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=20030716112140.GE4313@enigma.daemon.sh \
--to=acpi-1rjuzeeg9oeb1svskn2v4q@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.