From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bruno Pr?mont <bonbons@linux-vserver.org>
Cc: Linux Input <linux-input@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"R. J. Wysocki" <Rafal.Wysocki@fuw.edu.pl>
Subject: Re: Input+S3: extra keycodes forgotten after suspend
Date: Fri, 16 May 2008 16:38:07 -0400 [thread overview]
Message-ID: <20080516163318.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <200805162225.44284.bonbons@linux-vserver.org>
Hi Bruno,
On Fri, May 16, 2008 at 10:25:43PM +0200, Bruno Pr?mont wrote:
> On my Acer TravelMate 660 I lose keycodes for the extra keys (dritek
> extensions) after resume.
>
> The system runs setkeycodes during boot sequence to initialize key codes
> for the extra keys as below:
>
> /usr/bin/setkeycodes KEYCODES="e025 138 e026 141 e027 171 e074 148 e073 149 e055 229 e056 230 e057 227 e058 228"
> # Fn + F1 ~ e025 => 138 [KEY_HELP] (Help)
> # Fn + F2 ~ e026 => 141 [KEY_SETUP] (Notebook Manager)
> # Fn + F3 ~ e027 => 171 [KEY_CONFIG] (Power Options)
> # Mail ~ e06c => 155 [KEY_MAIL] (EMail)
> # WWW ~ e032 => 150 [KEY_WWW] (Browser)
> # P1 ~ e074 => 148 [KEY_PROG1] (P1)
> # P2 ~ e073 => 149 [KEY_PROG2] (P2)
> # Bluetooth ~ e058 => 228 [KEY_BLUETOOTH_DISABLE] (Disable Bluetooth)
> # Bluetooth ~ e057 => 227 [KEY_BLUETOOTH_ENABLE] (Enable Bluetooth)
> # Wireless ~ e056 => 230 [KEY_WLAN_DISABLE] (Disable WLAN)
> # Wireless ~ e055 => 229 [KEY_WLAN_ENABLE] (Enable WLAN)
> # Vol UP ~ e030 => 115 [KEY_VOLUMEUP] (Increase Volume)
> # Vol DOWN ~ e02e => 114 [KEY_VOLUMEDOWN] (Decrease Volume)
> # Vol Mute ~ e020 => 113 [KEY_MUTE] (Mute volume)
>
> After resume I end up with the following messages when pressing the keys:
> [ 779.695675] atkbd.c: Unknown key pressed (translated set 2, code 0xd6 on isa0060/serio0).
> [ 779.695675] atkbd.c: Use 'setkeycodes e056 <keycode>' to make it known.
> [ 779.705218] atkbd.c: Unknown key released (translated set 2, code 0xd6 on isa0060/serio0).
> [ 779.705218] atkbd.c: Use 'setkeycodes e056 <keycode>' to make it known.
> [ 781.603912] atkbd.c: Unknown key pressed (translated set 2, code 0xd5 on isa0060/serio0).
> [ 781.603912] atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known.
> [ 781.613564] atkbd.c: Unknown key released (translated set 2, code 0xd5 on isa0060/serio0).
> [ 781.613564] atkbd.c: Use 'setkeycodes e055 <keycode>' to make it known.
> [ 782.772662] atkbd.c: Unknown key pressed (translated set 2, code 0xd7 on isa0060/serio0).
> [ 782.772662] atkbd.c: Use 'setkeycodes e057 <keycode>' to make it known.
> [ 782.782390] atkbd.c: Unknown key released (translated set 2, code 0xd7 on isa0060/serio0).
> [ 782.782390] atkbd.c: Use 'setkeycodes e057 <keycode>' to make it known.
> [ 783.461807] atkbd.c: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
> [ 783.461807] atkbd.c: Use 'setkeycodes e058 <keycode>' to make it known.
> [ 783.471544] atkbd.c: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
> [ 783.471544] atkbd.c: Use 'setkeycodes e058 <keycode>' to make it known.
>
>
> Is this kind of issue known, what are the options to get kernel to remember the
> keycode mappings after s2ram?
>
Do you unload atkbd or perhaps i8042 for s2ram? Or do you see that
keyboard is detected again (in dmesg) after resume?
--
Dmitry
next prev parent reply other threads:[~2008-05-16 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 20:25 Input+S3: extra keycodes forgotten after suspend Bruno Prémont
2008-05-16 20:38 ` Dmitry Torokhov [this message]
2008-05-16 21:00 ` Bruno Prémont
2008-05-19 15:50 ` Dmitry Torokhov
2008-05-19 16:45 ` Bruno Prémont
2008-05-21 17:55 ` Dmitry Torokhov
2008-05-21 20:08 ` Bruno Prémont
2008-05-21 20:38 ` Dmitry Torokhov
2008-05-23 4:44 ` Dmitry Torokhov
2008-05-23 20:57 ` Bruno Prémont
2008-05-27 5:52 ` Dmitry Torokhov
2008-05-27 20:52 ` Bruno Prémont
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=20080516163318.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Rafal.Wysocki@fuw.edu.pl \
--cc=bonbons@linux-vserver.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).