lineak

here are my files.

/etc/lineakkb.def, with the irrelevant portions snipped:
<snip>
[Sager]
brandname = "Sager"
modelname = "NP8887"
[KEYS]
email = 236
www = 178
user = 129
back = 144
forward = 153
play = 162
stop = 164
volumeup = 176
volumedown = 174
[END KEYS]
[END Sager]
<snip>


~/.lineak/lineakd.conf:
# LinEAK - Linux support for Easy Access and Internet Keyboards
# Copyright (c) 2001,2002 Mark Smulders <Mark@PIRnet.nl>
# http://lineak.sourceforge.net
#
# lineakd configuration file
#
# example key configuration:
# play= "xmms --play-pause"
# eject= EAK_EJECT
#
# available special actions:
# EAK_EJECT
# EAK_VOLUP
# EAK_VOLDOWN
# EAK_MUTE
# EAK_SLEEP
#

# LinEAK Configuration file for Sager NP8887

# Global settings
KeyboardType= Sager
CdromDevice= /dev/cdrom
MixerDevice= /dev/mixer

# Specific keys of your keyboard
email= "sylpheed-claws"
www= "links2 -g"
user= "bashish"
back= "xmms --rew"
forward= "xmms --fwd"
play= "xmms --play-pause"
stop= "xmms --stop"
volumeup= EAK_VOLUP
volumedown= EAK_VOLDOWN

# end lineakd.conf


and in .xinitrc:
exec lineakd -b &


you have to add the sager section in lineakkb.def yourself. mine is under the 'laptops' section of the file, but technically it doesn't matter. those numbers are X event numbers - but they may be different from mine on a 5660. it's better to test them yourself. run 'xev' and press each of the buttons, noting the event numbers for each button, and use those in lineakkb.def. (naturally, change model to NP5660, etc.)

let me know if you have any problems.

i didn't use any of the lineak config programs, i just edited the file by hand. (lineakconfig just edits ~/.lineak/lineakd.conf)

somehow, i don't think the iTouch plugin will work without an iTouch keyboard. with lineakd running, xmms shouldn't even need any plugin.

the EAK_VOLUP and EAK_VOLDOWN functions control the mixer, which (i believe) is what you want. (control the master volume, right? it works for me)

that sucks that xev freezes, i wonder why that happens. maybe check the X log?

if the volume buttons are the same x events as mine, then the rest of the buttons are probably the same, too. try text editing your lineak config files to look like mine (well, the keyboard definition - map the buttons to the commands you want), and running just 'lineakd -v' in a console and testing, and check if there are any messages. (skip the -b flag, which means background. -v for verbose)

... or did i miss something, and did running lineakd configured cause problems for you?

hmm... what version of lineak are you using?

flipping through the lineak documentation, i found a couple things you could try:

first of all, get rid of your ~/.lineak/lineakd.conf. (you can always create it again later.)

try running 'lineakd -l' and see if it lists the keyboard definition you created. then do 'lineakd -c blah', with blah being the keyboard identifier, to generate a config file. then do 'lineakd -v' and press the buttons. if it reports keycodes/presses correctly, then we know that the problem is not incorrect keycodes, and it's something with the commands for the buttons.

if keycodes are not correctly reported for the buttons you want, try running 'lineakd -c CIK18g'. (what we're trying to do is set up lineakd with a keyboard that has a _lot_ of keys - like the CIK18g. This high number of keys could possibly include yours.) run lineakd in verbose mode, press the buttons, and see if x keycodes are reported. if not, try switching to another keyboard that has lots of keys. (This is, however, not the real way to do it - therefore, it may very well not work at all)

let me know how that works out - if we clear up whether it's the keycode definitions or not, we can decide where to go from there.

that's really strange...

... but somehow, that 'alpha' in the version number makes me a little suspicious. alpha is probably the least stable version label there is. (besides CVS)

i use lineak v0.4pre3, i don't know if you want to give that one a try or not...