| View previous topic :: View next topic |
| Author |
Message |
imon fyre
n00b
Joined: 18 Dec 2003
Posts: 31
Location: sudbury on
|
 Posted: Mon Aug 23, 2004 10:30 pm Post subject: microsoft natural keyboard |
 |
|
hey all, just bought a microsoft natural keyboard, and was wondering how to get it up and running properly. eg, as many of the keys working as possible.
ive looked around on the net, and the only real information i could find was using xev and setkeycodes. |
|
| Back to top |
|
 |
Halcy0n
Developer
Joined: 17 Sep 2003
Posts: 1682
Location: Freehold, NJ
|
| Posted: Mon Aug 23, 2004 10:41 pm Post subject: |
|
|
I used xbindkeys to get the extra keys working on my keyboard. I don't have a natural anymore, but all of the keys should have a keycode assigned to them that xbindkeys picks up, or whatever you want to use to assign something to that key.
_________________
Mark Loeser
http://www.halcy0n.com |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Tue Aug 24, 2004 4:52 am Post subject: |
|
|
I have the Microsoft Natural Pro, Model RT9403 (Dell OEM) it has the built in 2 port USB hub.
| Code: |
# dmesg | grep -ie keyboard
input: USB HID v1.10 Keyboard [Microsoft Natural Keyboard Pro] on usb-0000:00:11.2-2.1
|
You'll need the normal USB stuff for your system and the HID stuff. I have these HID options in my kernel.
| Code: |
# USB Human Interface Devices (HID)
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
|
Ok make sure you have this in your Keyboard section of you xorg.conf or xf86config(-4).
| Code: |
Option "XkbModel" "microsoftpro"
|
If you do that then all your extra keys will get codes and be labled as XF86* keynames except the Search, Web/Home, Media, MyComputer(?), and Sleep buttons. You can just assign the proper names to those keys in your .Xmodmap file.
| Code: |
keycode 122 = XF86Search
keycode 130 = XF86HomePage
keycode 129 = XF86AudioMedia
keycode 198 = XF86MyComputer
keycode 227 = XF86Sleep
|
Your keycodes might be different but xev will tell you what they and those should be the the correct names for those buttons if they were detected properly by the kernel and X whichever has the problem. I think you can use other names if you want but KDE picks up on the multimedia names and you can use them as a shortcut for any app. I'd guess this works in Gnome too somehow. 
I'm getting a logitech mx duo so it will be the next challenge. |
|
| Back to top |
|
|
alkan
Guru
Joined: 06 Aug 2004
Posts: 385
Location: kasimlar yaylasi
|
| Posted: Tue Aug 24, 2004 6:24 am Post subject: |
|
|
If you still have some keys without a keycode. You can see the scancode when you press that key and look at the end of dmesg.
| Code: |
[kernel] atkbd.c: Unknown key released (translated set 2, code 0x92 on isa0060/serio0).
[kernel] atkbd.c: Use 'setkeycodes e011 <keycode>' to make it known.
|
Then assign an empty key code:
| Code: |
setkeycodes e011 211
|
Now, you can use a utility program to make those keycodes something usefull.
Hotkeys is a nice utility with osd to map those keycodes to real actions. |
|
| Back to top |
|
|
r3pek
Retired Dev
Joined: 17 Sep 2003
Posts: 568
Location: Lisbon - Portugal
|
| Posted: Tue Aug 24, 2004 9:12 am Post subject: |
|
|
or you can use this:
LinEAK |
|
| Back to top |
|
|
|
Kernel & Hardware
