[opensuse] Getting extra keys on a specialized keyboard to work
I'm trying to get the extra keys working on a friend's keyboard. This is one of those special keyboards (ZBoard) with loads of extra keys. It of course is supported only in Windows, and the Windows drivers are all .NET based, so no chance of fudging things in Wine. I've been trying to see if we can use 'setkey' or 'xev' to find the keycodes and 'xbindkeys' to set them to specific events, but... xev and showkey do not show any keyboard event when the extra keys are pressed. Is it possible that these extra keys are using a different bit length (eg 16 bit instead of 8 bit) and this is why xev can't read the events? Is there any other tool around that could be tested/tried to read the key events? The ZBoard has interchangeable keysets, and if we pop out the custom game-set and drop in the standard 101 key keyboard set, all keys function normally... swap with a game keyset and all the special keys seem to send no keycodes. There is very little info on the web about these keyboards... but I have seen that someone managed to get the ZBoard Merc keyboard working... but that is a different model to this one. Anyway... any ideas or hints appreciated. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Clayton escribió:
Anyway... any ideas or hints appreciated.
If your keyboard is not correctly autodetected by Sax or the autoselected keyboard model/setup is not doing what is expected, open a bug report http://bugzilla.novell.com -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
If your keyboard is not correctly autodetected by Sax or the autoselected keyboard model/setup is not doing what is expected, open a bug report http://bugzilla.novell.com
Well... since this is not a common keyboard, it is a specialized gaming keyboard, it is highly unlikely to be detected correctly. In the standard keyboard configuration, it works fine.. but in custom configs, it doesn't. I can open a bug report, but I have a strong suspicion it'll be a wontfix since it is a custom-built specialized keyboard... which is why I was trying to investigate it myself. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Clayton
-
Cristian Rodríguez