From: Matthew Garrett <mjg59@srcf.ucam.org>
To: giggz <giggzounet@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Problem with the Fn+F3 key. acpi problem ?
Date: Sat, 12 Jan 2008 12:17:14 +0000 [thread overview]
Message-ID: <20080112121714.GB15173@srcf.ucam.org> (raw)
In-Reply-To: <fmaaj5$jsl$1@ger.gmane.org>
On Sat, Jan 12, 2008 at 01:06:30PM +0100, giggz wrote:
> I want to associate a script (which works fine) to a key (Fn+F3). This
> key is for the video output switching and my script is a video output
> switch using xrandr.
> But when I try to associate Fn+F3 it doesn't work. I have try with the
> xen command to catch the keycode, but nothing happends when I press on
> the key. All the others Fn+F* works fine (help, hibernate, luminosity,
> sound...).
> So I want to report a bug, but I don't know if it is an acpi problem or
> a xorg problem... If anyone could help me...?
Does pressing the key generate any output in dmesg? If so, you need to
run the setkeycodes command to bind it to a keycode. If not, make sure
you have the acpi video module loaded, do
echo -n 4 >/proc/acpi/video/foo/DOS
and check whether it generates an acpi event (there'll be a log message
in /var/log/acpid.log). If so, sufficiently recent kernels ought to
generate an input event.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-01-12 12:17 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 [this message]
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
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=20080112121714.GB15173@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=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).