From: giggz <giggzounet@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Re: Problem with the Fn+F3 key. acpi problem ?
Date: Sat, 12 Jan 2008 16:02:53 +0100 [thread overview]
Message-ID: <fmakts$gqs$1@ger.gmane.org> (raw)
In-Reply-To: <20080112124619.GA15578@srcf.ucam.org>
Matthew Garrett a écrit :
> On Sat, Jan 12, 2008 at 01:33:38PM +0100, giggz wrote:
>
>> What is the acpi video module ?
>
> If you have /proc/acpi/video, it's loaded.
>
>> I don't have any /var/log/acpid.log
it seems to be normal that I don't have any /var/log/acpid.log :
according to the NEWS.debian.gz from acpid package :
" Starting with version 1.0.6 acpid uses syslog instead of its own logging
mechanism. During the upgrade of this package the old log files and the
logrotate configuration file are backed up to
/var/backups/acpid-cruft.tar.gz and are removed from the filesystem."
So if I understand I must look at the syslog and message...but I don't
see anything in these two file...
How can I increase the level of debugging ?
>
> In that case, try catting /proc/acpi/event and hit the button.
>
Have a nice we
-
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
next prev parent reply other threads:[~2008-01-12 15:04 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 [this message]
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
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='fmakts$gqs$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 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.