well for xmas I got the Saitek Gaming Keyboard...such a nice key board. Anyway is there a way i could get the drivers working for the sound keys, and this little cool keypad? I checked out there website but I could not find any information on Linux or the Linux drivers.
Thank you guys for your support
Don't ever tell anybody anything. If you do, you start missing everybody.
For the sound keys, do a search for lineakd (it's also in portage, but you'll need to consult the docs on the site for setting it up for new keyboards, it's easy).
Cool little pad? more info If it's just extra keys the keyboard adds adding the keys by hand won't be too much trouble, but if it's one of those things where you drop sheets in and out I dunno...
The keys on that keypad are probably implemented in much the same way as the extra keys on those "media" and "internet" keyboards you see about the place. I know from experience with my MS Internet Keyboard Pro that these can be made to work under Linux only the exact procedure may vary depend on the WM/DE you use.
LOL, when I saw "gaming keyboard" in the thread title it brought up memories of a little thing I saw in a computer shop a month or two back: It was sort of like a laptop keyboard but on one side it had a little joystick and the other had about 9-16 buttons which could I presume be re-programmed for gaming related functions. It was sorta neat in a way, particularly for emulators but it was all too small to be all that usable.
Wasurenaide...
...watashi ga iru koto o.
Itsudatte soba ni iru yo.
I just bought one of these keyboards, I will post soon on how to program it once I have it figured out, thanx to the info on ev and for the volume controls.
examining the evbug output from the extra pad it looks like it is showing up as input2 with 0-9 mapping to codes 304-312 mode a is 313 and mode b is 314.
I'm guessing that since my keyboard is input 1 that the keypad is seen as another keyboard. I haven't looked further into how to handle that yet.
On my saitek gaming keyboard the pad shows up as a seperate event device, if that is any help.
Heres some debug info for those interested.
The command keypad shows up as its own event device on my gentoo install with
2.6.11-morph kernel (/dev/input/event4) I also have a usb mouse
hooked up. Heres my evkeyd --debug output:
blue evkeyd # evkeyd --debug
evkeyd[12169] debug: event_init
evkeyd[12169] debug: chk_dev
evkeyd[12169] info: using /dev/input/event0 on fd 5
evkeyd[12169] debug: chk_dev
evkeyd[12169] debug: chk_dev
evkeyd[12169] info: using /dev/input/event2 on fd 6
evkeyd[12169] debug: chk_dev
evkeyd[12169] info: using /dev/input/event3 on fd 7
evkeyd[12169] debug: chk_dev
evkeyd[12169] debug: chk_dev
evkeyd[12169] debug: eject_init
evkeyd[12169] debug: find_dev
evkeyd[12169] info: found cd device /dev/dvd
evkeyd[12169] debug: backlight_init
evkeyd[12169] warning: couldn't grab backlight
evkeyd[12169] info: evkeyd version 0.1pre7 running
evkeyd stops looking at event devices at event3, event0 is my tv tuner
for refrence. heres my dmesg related to the keyboard:
input: USB HID v1.11 Keyboard [Chicony USB Gaming Keyboard Pro] on
usb-0000:00:02.1-3
input: USB HID v1.11 Device [Chicony USB Gaming Keyboard Pro] on
usb-0000:00:02.1-3
input: USB HID v1.11 Gamepad [Chicony USB Gaming Keyboard Pro] on
usb-0000:00:02.1-3
heres the evtest output from the pad (i started from key 1 and went
down numerically, and hit the two mode keys at the bottom):
blue ~ # evtest /dev/input/event4
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x6a3 product 0x8000 version 0x120
Input device name: "Chicony USB Gaming Keyboard Pro"
Supported events:
Event type 0 (Sync)
Event code 0 (Sync)
Event code 1 (Key)
Event code 4 (?)
Event type 1 (Key)
Event code 304 (BtnA)
Event code 305 (BtnB)
Event code 306 (BtnC)
Event code 307 (BtnX)
Event code 308 (BtnY)
Event code 309 (BtnZ)
Event code 310 (BtnTL)
Event code 311 (BtnTR)
Event code 312 (BtnTL2)
Event code 313 (BtnTR2)
Event code 314 (BtnSelect)
Event type 4 (?)
Event code 4 (?)
Testing ... (interrupt to exit)
Event: time 1114645505.356489, type 4 (?), code 4 (?), value 589825
Event: time 1114645505.356490, type 1 (Key), code 304 (BtnA), value 1
Event: time 1114645505.356492, -------------- Config Sync ------------
Event: time 1114645505.436491, type 4 (?), code 4 (?), value 589825
Event: time 1114645505.436492, type 1 (Key), code 304 (BtnA), value 0
Event: time 1114645505.436494, -------------- Config Sync ------------
Event: time 1114645505.908490, type 4 (?), code 4 (?), value 589826
Event: time 1114645505.908491, type 1 (Key), code 305 (BtnB), value 1
Event: time 1114645505.908493, -------------- Config Sync ------------
Event: time 1114645505.988491, type 4 (?), code 4 (?), value 589826
Event: time 1114645505.988492, type 1 (Key), code 305 (BtnB), value 0
Event: time 1114645505.988493, -------------- Config Sync ------------
Event: time 1114645506.268489, type 4 (?), code 4 (?), value 589827
Event: time 1114645506.268490, type 1 (Key), code 306 (BtnC), value 1
Event: time 1114645506.268492, -------------- Config Sync ------------
Event: time 1114645506.340491, type 4 (?), code 4 (?), value 589827
Event: time 1114645506.340492, type 1 (Key), code 306 (BtnC), value 0
Event: time 1114645506.340493, -------------- Config Sync ------------
Event: time 1114645506.620491, type 4 (?), code 4 (?), value 589828
Event: time 1114645506.620492, type 1 (Key), code 307 (BtnX), value 1
Event: time 1114645506.620494, -------------- Config Sync ------------
Event: time 1114645506.692491, type 4 (?), code 4 (?), value 589828
Event: time 1114645506.692492, type 1 (Key), code 307 (BtnX), value 0
Event: time 1114645506.692493, -------------- Config Sync ------------
Event: time 1114645506.916490, type 4 (?), code 4 (?), value 589829
Event: time 1114645506.916492, type 1 (Key), code 308 (BtnY), value 1
Event: time 1114645506.916493, -------------- Config Sync ------------
Event: time 1114645506.988490, type 4 (?), code 4 (?), value 589829
Event: time 1114645506.988491, type 1 (Key), code 308 (BtnY), value 0
Event: time 1114645506.988492, -------------- Config Sync ------------
Event: time 1114645507.172491, type 4 (?), code 4 (?), value 589830
Event: time 1114645507.172492, type 1 (Key), code 309 (BtnZ), value 1
Event: time 1114645507.172493, -------------- Config Sync ------------
Event: time 1114645507.260491, type 4 (?), code 4 (?), value 589830
Event: time 1114645507.260492, type 1 (Key), code 309 (BtnZ), value 0
Event: time 1114645507.260493, -------------- Config Sync ------------
Event: time 1114645507.484492, type 4 (?), code 4 (?), value 589831
Event: time 1114645507.484493, type 1 (Key), code 310 (BtnTL), value 1
Event: time 1114645507.484494, -------------- Config Sync ------------
Event: time 1114645507.572491, type 4 (?), code 4 (?), value 589831
Event: time 1114645507.572492, type 1 (Key), code 310 (BtnTL), value 0
Event: time 1114645507.572493, -------------- Config Sync ------------
Event: time 1114645507.748490, type 4 (?), code 4 (?), value 589832
Event: time 1114645507.748492, type 1 (Key), code 311 (BtnTR), value 1
Event: time 1114645507.748493, -------------- Config Sync ------------
Event: time 1114645507.836490, type 4 (?), code 4 (?), value 589832
Event: time 1114645507.836491, type 1 (Key), code 311 (BtnTR), value 0
Event: time 1114645507.836492, -------------- Config Sync ------------
Event: time 1114645507.988491, type 4 (?), code 4 (?), value 589833
Event: time 1114645507.988492, type 1 (Key), code 312 (BtnTL2), value 1
Event: time 1114645507.988493, -------------- Config Sync ------------
Event: time 1114645508.060491, type 4 (?), code 4 (?), value 589833
Event: time 1114645508.060492, type 1 (Key), code 312 (BtnTL2), value 0
Event: time 1114645508.060493, -------------- Config Sync ------------
Event: time 1114645508.476492, type 4 (?), code 4 (?), value 589834
Event: time 1114645508.476493, type 1 (Key), code 313 (BtnTR2), value 1
Event: time 1114645508.476494, -------------- Config Sync ------------
Event: time 1114645508.548492, type 4 (?), code 4 (?), value 589834
Event: time 1114645508.548493, type 1 (Key), code 313 (BtnTR2), value 0
Event: time 1114645508.548494, -------------- Config Sync ------------
Event: time 1114645508.996492, type 4 (?), code 4 (?), value 589835
Event: time 1114645508.996493, type 1 (Key), code 314 (BtnSelect), value 1
Event: time 1114645508.996494, -------------- Config Sync ------------
Event: time 1114645509.052492, type 4 (?), code 4 (?), value 589835
Event: time 1114645509.052493, type 1 (Key), code 314 (BtnSelect), value 0
Event: time 1114645509.052493, -------------- Config Sync ------------
Last edited by DrFishstik on Mon May 30, 2005 10:15 pm, edited 1 time in total.
Admiral LSD wrote:LOL, when I saw "gaming keyboard" in the thread title it brought up memories of a little thing I saw in a computer shop a month or two back: It was sort of like a laptop keyboard but on one side it had a little joystick and the other had about 9-16 buttons which could I presume be re-programmed for gaming related functions. It was sorta neat in a way, particularly for emulators but it was all too small to be all that usable.
Hmmm,
this reminds me a lot of my saitek gamers keyboard, but there´s nothing to laugh about!!!
It is a Saitek Pro Gamer Command Unit, a usb-gamer-keyboard.
gentoo detects this perfect as "saitek pro gamer command unit" but i don´t know how to configure/use it. Unfortunately it is not detected as an external usb-keyboard, so i need a tool or something to teach the buttons.