LinEAK

evilmonkey · 10-17-2004, 01:08 PM

Hello. I have a LinEAK question. I'm running SuSE 9.1, and I have a Chicony KB-9885 (it's supported by lineak, listed under "other"). I configured my VolDown button, (and it works), but for some reason, it goes for the PCM as oppossed to the main volume in the mixer. I've also configured Mute and VolUP, but those don't work at all. My misex if /dev/mixer (I believe), and I'm using klineakconfig on SuSE 9.1.

My second question is how do I get lineakd to run in the background? Right now it only runs in the console window after I explicitly call it.

Thanks!

hw-tph · 10-17-2004, 01:26 PM

Check the keyboard definition (usually /etc/lineakkbd.def) against what keyboard codes are actually generated when you press the keys on your keyboard. You may have to add a variant of the keyboard.

Concerning what the keys actually do when pressed - edit your ~/.lineak/lineakd.conf. If you use the aumix program to set the audio levels, try running man aumix to see what your options are.

I launch lineakd from my ~/.xsession file which also launches my window manager:

Code:

lineakd &
exec enlightenment    # Replace with "exec gnome-session" for a Gnome session...etc

If you use GDM, simply choose "Custom Session" as the session type when you log in.

Håkan

evilmonkey · 10-17-2004, 02:36 PM

Hmm, this is odd. I tried running "xev" in my commandline, only some keys create a response. At first, the response was what the linEAK documentation said it was suppossed to be, but the second time around, the sample response I got was something like this:

KeymapNotify event, serial 30, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Anyway, these are the buttons that seem to work in linEAK, but there are a few that don't get recognized by Linux at all. They work in Windows however, so the keyboard is fine. Is there anything I can do?

I use KAMix as the audio mixer, and I have KDE running, and I can't seem to find that session file...

Thanks!

evilmonkey · 10-17-2004, 08:56 PM

Hmmm, anyone?

*bump*

Pecunia · 10-24-2004, 10:08 AM

Quote:

My second question is how do I get lineakd to run in the background?

If you're using KDE, create a new application link to lineakd in KDE's Autostart directory. To create such a link: Start Konqueror, Go -> Autostart. Edit -> Create new -> File -> Link to application. On the "Application" tab, fill in "lineakd" as command.

Quote:

Anyway, these are the buttons that seem to work in linEAK, but there are a few that don't get recognized by Linux at all. They work in Windows however, so the keyboard is fine. Is there anything I can do?

From the lineak readme:

Quote:

Linux 2.6 can cause changes in how the keycodes are interpreted. In some cases, keys that use to work, no longer work at all. If this happens to you try the following:

1) run xev and see if X reports any keycodes for the key(s) that is/are not working. If there are keycodes being produced, you'll have to update the lineakkb.def file (usually in /etc) with the correct keycodes for your keyboard.

2) If xev does not report any keycodes for one or more of your keys, then try looking in /var/log/messages. If you have error messages in that file from atkbd.c about unknown scancodes, etc. Then somewhere in your startup scripts (at the end of /etc/rc.sysinit for example). Try binding those scancodes to keycodes with the setkeycodes command. If in doubt just use the keycode from your /etc/lineakkb.def file. Then X should produce a keycode for the key. You'll still have to follow the steps under the procedure 1 above to get lineak to recognize the keys, but it'll work.

3) If you see nothing in your /var/log/messages, and xev produces no keycodes, you can try running showkey -s as root and see if the keypresses show any scancodes. If they do, follow thre relevant part of procedure 2 above. If not, see 4.

4) If none of the above work, send an email to the linux-usb mailing list (if your keyboard is USB) or to the atkbd.c maintainer and pray they do something about it. Otherwise your screwed. Take your POS keyboard back to the store and get a supported one.

For me, in step 2, the logfile was not /var/log/messages but /var/log/kern.log. YMMV

evilmonkey · 10-24-2004, 01:35 PM

Okay, I read the Likeak manual, I don't know how I missed that. It worked, although very oddly. The keycodes I try to bind to are not the keycodes that are actually binded, so I had to play with the codes a little to avoid having conflicts. Anyways, everything worked, thanks very much.

tonto · 03-02-2006, 01:51 PM

Hi evilmonkey. I would very much appreciate if you would post the exact additions/changes you made to your configuration to make mute, volume-up etc. to respond on KB-9885.

Thanks.

Tonto