[SOLVED] X.org and gaming-keyboard: no caps/num/scroll lock leds during X session
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
X.org and gaming-keyboard: no caps/num/scroll lock leds during X session
I use exclusively Slackware 64 14.1 with Kernel 3.10.17 on my AMD FX 6300 six-core PC.
I was gifted with a USB gaming keyboard (GX-gaming Imperator Pro I - Genius).
Keyboard is fine. I don't care about fancy macro gaming keys. Only the basic input device. Both the numlock and caps lock, as well as scroll lock keys work fine in a typing perspective. But, pressing any of them don't illuminate the corresponding LED indicators while IN X.org session. The indicators do work, on and off leds are illuminated, while I'm on a terminal OUT of X.org. But they do not light during X.org session, though the lock keys do work - I just can't see the leds and I have to type anything to see if they are ON or OFF.
I found out over the net that this would work, probably because my keybord wouldn't be in UTF-8 mode:
# kbd_mode -u
Indeed, now I can see the leds during a X session.
However, it messes up with another keys: the ALT-F2, used to run a command, now opens a second terminal (tty2).
I wonder if anybody else has the same problem to try to find out a solution.
Last edited by gauchao; 08-30-2014 at 01:39 PM.
I've never heard of this one, but maybe you could force the LDEs to work. I presume Slackware still has xorg.conf? If so add an entry under InputDevice
Option "XkbOptions" "caps_led:caps,num_led:num"
I've used "grp_led:scroll" successfully in the past, so I don't see why re-setting the defaults shouldn't work — no guarantee offered, though!