setkeycodes annoyance

[utrrrongeeb]

Hi,
I'm using a Microsoft Wireless Natural MultiMedia Keyboard. In Bash, my screen gets screwed up every few seconds with messages saying

Code: Select all

atkbd.c: Unknown key pressed (translated set 2, code 0xd9 in isa0060/serio0).
atkbd.c: Use 'setkeycodes e059 <keycode>' to make it known.

atkbd.c: Unknown key pressed (translated set 2, code 0x81 in isa0060/serio0).
atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.

I'm wondering what keycode to use that will result in nothing happening, and how I can make that setting permanent.

[utrrrongeeb]

Anyone reading this post? It is a problem of large forums is that unanswered posts tend to get buried.

[Grifter]

I just don't think anyone knows what to do

[utrrrongeeb]

Thanks for pointing that out.
Ok, I'll explain more clearly:
According to manuals and help text, setkeycodes is run as setkeycodes [scancode] [keycode]. The errors from the kernel provide the scancode. I want to know what keycode will be accepted but will result in either nothing happening, or something harmless happening (such as a beep). Once I've found a functional keycode, I need to make it so it always associates the scancode wit hthe keycode, as setkeycodes is reset after a reboot. Can anyone help me with this?

[lacek]

Use the dumpkeys command to see what keycodes are recognized and which is used to what. Pick a keycode with no function (in my computer, 120 was such one), and assign your scancodes to that keycode.
To make this setting permanent, you probably need to create an init script.
If you don't know how to create an init script, this thread may help.

[utrrrongeeb]

Thanks for the help!
I'll try it the next time I'm in Debian.

[utrrrongeeb]

Thanks a lot! Now I can do my Bash work without being interrupted constantly. I used keycode 120, and the init script is something like this:

Code: Select all

#!/bin/bash
case $1 in
  start)
    setkeycodes e059 120
    setkeycodes e001 120
  ;;
  stop)
  ;;
esac

Just wondering, but how can I assign key commands to specific actions (such as launching a program) in X?

[lacek]

X keycodes has nothing to do with the console key assignments. You may find this thread useful. It discusses the using of "multimedia keyboards" under linux, but you can use the method described there to map any unknown keycodes under X.

[utrrrongeeb]

Just what I've been looking for! Thanks a lot!
I assumed it was going to have to use extra packages, as the GNOME key commands are limited. Maybe I should switch to Xfce...
In the mean time, I added more setkeycodes to the init script, and now the function keys behave like function keys, regardless of that evil F Lock. However, FLock still screws up PrtScn/SysRq, Insert, Pause/Break, and Scroll Lock. Also, it seems Bash freezes if I'm fooling around with FLock and the keys it affects.

[SpEcIeS]

If you want to stop seeing the messages you may want to add dmesg -n1 to your boot up. I have a M$ Wireless keyboard and mouse and this was one of my issues, but not anymore. However, the messages do show up on the logs.

Next setup will be Logitech.. not sacrelig

[utrrrongeeb]

I have a M$ keyboard and mouse, but I prevented the error messages from coming rather then hiding them. Look at the seventh post from the top here.

[utrrrongeeb]

Hotkeys works all right when I manually run it, but how do I make it run on startup?

Also, the "Sleep" key says it is pressed about 30 times when it's only pressed once. This can screw up everything.

[lacek]

You have to run hotkeys with the X server. That is, if you log in from console and use the 'startx' command, you have to enter the command to your .xinitrc. If you log in from kdm for example, you'll have to find a way to run hotkeys at startup. With KDE, there is a ~/.kde/Autostart directory you can symlink the application there, and KDE will start it automatically.

[utrrrongeeb]

At the moment I'm using GDM as the display manager and Gnome as the WM, but I might switch the WM to KDE or Xfce at some point. I'll look around for a file like that. Would it be for the display manager or the window manager?

Other than that, I've configured the keyboard to my preferences.

[lacek]

I don't really know which should be better. I think it doesn't really matter which will start the hotkeys program, I just used the KDE autostart feature to start it. It was the easiest solution for me.

[utrrrongeeb]

I have it working at last!!!!
Obviously, if I switch window managers, I'll have some fiddling to do, but I think I can check "keyboard" of my list. Now for the mouse, the UPS, ............