linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: giggz <giggzounet@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Re: Problem with the Fn+F3 key. acpi problem ?
Date: Sat, 08 Mar 2008 11:08:54 +0100	[thread overview]
Message-ID: <fqtor7$5mu$1@ger.gmane.org> (raw)
In-Reply-To: <fqtkjq$rod$1@ger.gmane.org>

giggz a écrit :
[snip]

>>>> In that case, try catting /proc/acpi/event and hit the button.
>> On SUSE, instead of stopping acpid, you can use:
>> acpi_listen
>> to log acpi events.
>>

in my case when I increase the level of acpi debug and hit the Fn+F3
button I don't see anything when I cat /proc/acpi/event. And it's the
same if I use acpi_listen. I launch acpi_listen and the hit the button,
but nothing appears. I just get the message I posted in the
/var/log/messages.

Guillaume

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-03-08 10:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12 12:06 Problem with the Fn+F3 key. acpi problem ? giggz
2008-01-12 12:17 ` Matthew Garrett
2008-01-12 12:33   ` giggz
2008-01-12 12:46     ` Matthew Garrett
2008-01-12 13:08       ` giggz
2008-01-22  5:47         ` Zhang Rui
2008-01-22 22:02           ` giggzounet
2008-01-12 15:02       ` giggz
2008-02-18 15:18         ` Thomas Renninger
2008-02-19  9:44           ` GiGGz
2008-03-08  8:56           ` giggz
2008-03-08  9:46             ` giggz
2008-03-08 10:08             ` giggz [this message]
2008-03-10  1:18               ` Zhao Yakui
2008-03-10 11:23                 ` Thomas Renninger
2008-03-10 18:17                   ` giggz
2008-03-11  1:52                   ` Zhang, Rui
2008-03-10 17:56                 ` giggz

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='fqtor7$5mu$1@ger.gmane.org' \
    --to=giggzounet@gmail.com \
    --cc=linux-acpi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).