* Lenovo IdeaPad S206
@ 2013-04-26 8:46 Steve White
2013-04-27 16:15 ` Steve White
0 siblings, 1 reply; 2+ messages in thread
From: Steve White @ 2013-04-26 8:46 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
Hi,
My new Lenovo IdeaPad S206 has a special button ("OneKey recovery system"
button) that I wanted to re-map to a sleep button. I did this, and it
works well. There is also a QS key, that one could profitably re-map.
Along the way realized that the generic IdeaPad mappings of the Ubuntu 12.10
distro are largely incompatible with the keys on this computer.
So I set out to remedy that.
I'm not sure I'm following best practices though. In particular, should
existing IdeaPad rules be restricted, or should the mappings be overridden?
I have some evidence that the mappings here should also work for the S200,
but I'm pretty sure they *aren't* appropriate for the S205.
________________________________
$ cat /sys/class/dmi/id/sys_vendor
LENOVO
$ cat /sys/class/dmi/id/product_name
2638
$ cat /sys/class/dmi/id/product_version
Lenovo IdeaPad S206
________________________________
The OneKey button on this machine is perfect for a sleep button:
it is easily accessible, but impossible to press accidentally.
To simply re-map the OneKey button, I first observed:
A 0x10 press-release pair is emitted if the button is given a substantial
press, and released. After about 3 sec of continuous pressing,
a 0x11 press-release pair is emitted.
I put a rule like this under "keyboard_modulecheck":
________________________________
ENV{DMI_VENDOR}=="LENOVO*", KERNELS=="input*", ATTRS{name}=="Ideapad extra buttons", ATTR{[dmi/id]product_version}=="*S206|*S200", RUN+="keymap $name 0x10 sleep 0x11 hibernate"
________________________________
For the other keys, I have made a keymap file, which at least gets the proper
mappings going. I'm not sure if I really improved anything. See attached.
For one thing, some of the keys don't seem to make scan codes on any device
(the camera key on the F9 key.) Some seem to work regardless of how I map
them -- I guess that means they're going straight to hardware and the
system just reads the hardware state.
I'll be glad to hear what you think!
[-- Attachment #2: udev-db.txt.gz --]
[-- Type: application/x-gunzip, Size: 14526 bytes --]
[-- Attachment #3: lenovo-ideapad-s206 --]
[-- Type: text/plain, Size: 615 bytes --]
# key codes on Lenovo IdeaPad S206, and presumably the S200
0x81 reserved # disable lenovo-ideapad mapping
0xB9 reserved # disable lenovo-ideapad mapping
0xBA reserved # disable lenovo-ideapad mapping
0xF1 f6 # on F6 touchpad toggle (disabled)
0x83 rfkill # on F7 handled in module-lenovo-ideapad-s206
0xCE micmute # on F8
#???? camera # on F9 can't find this in udev
0xDB switchvideomode # on F10
0xF0 display_off # on F11
0xCC brightnessdown # on F12
0xD4 brightnessup # on ins
0x82 unknown # QS key
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Lenovo IdeaPad S206
2013-04-26 8:46 Lenovo IdeaPad S206 Steve White
@ 2013-04-27 16:15 ` Steve White
0 siblings, 0 replies; 2+ messages in thread
From: Steve White @ 2013-04-27 16:15 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi,
In the previous post, I had confused the "win" key with the "switch video"
key. This is corrected now. See attached.
I still have several questions:
switch video
------------
The key meant to switch video (mod F10) produces two scan codes.
In man showkey, there are some remarks, but I don't know what they mean.
$ keymap -i /input/event4
scan code: 0xDB
scan code: 0x19
(both scancodes emitted together only once on press,
nothing on longer hold, nothing on release)
$ showkey -s
0x19 on press
0x99 on release
** What does this mean, and how are such results to be used with udev rules?
camera off-on
-------------
I can't see that this key (mod F9) generates anything on any device,
although it does in fact seem to kill the USB-based camera.
** Any ideas?
kill key
----------
The kill key (mod F4) very effectively kills any terminal it's running
in, so I have yet to determine what scan codes it generates.
** Any ideas?
[-- Attachment #2: lenovo-ideapad-s206 --]
[-- Type: text/plain, Size: 683 bytes --]
# key codes on Lenovo IdeaPad S206, and presumably the S200
0x81 reserved # disable lenovo-ideapad mapping
0xB9 reserved # disable lenovo-ideapad mapping
0xBA reserved # disable lenovo-ideapad mapping
0xF1 f6 # mod F6 touchpad toggle (disabled)
0x83 rfkill # mod F7 handled in module-lenovo-ideapad-s206
0xCE micmute # mod F8
#???? camera # mod F9 can't find this in udev
#???? switchvideomode # mod F10 emits multiple scancodes?
0xF0 display_off # mod F11
0xCC brightnessdown # mod F12
0xD4 brightnessup # mod ins
0xDB menu # win key
0x82 unknown # QS key
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-04-27 16:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-26 8:46 Lenovo IdeaPad S206 Steve White
2013-04-27 16:15 ` Steve White
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).