Hi, I have this new keyboard which has a nice blue backlight. To operate it, one is supposed to press the useless "Scroll lock" key. It works, but as I press this key, the light turns on, but the console locks up, until I press it again, turning off the light. As you can imagine, this render this backlight useless for me... . Further more, in X the whole thing doesn't work - "Konsole" (KDE) freezes but the light wont even turn on (nothing happens if the focus is in other types of windows other than Konsole). I'm using Gentoo (~amd64) with CK-Sources kernel v2.6.21-ck2, running KDE.
I have investigated (Google showed some very similar problems but no solutions) it and this is what I concluded so far: - This keyboard has drivers for Windows but I think the reason why it works in Windows is that the Scroll lock action in Windows is not the same as in Linux. - I've tried remapping the Scroll lock key to other action, like Num lock (edited a keymap file (/usr/share/keymaps...) and used it in /etc/conf.d/keymaps). Funny thing is that the mapping works fine but the keyboard light is not turned on: I remapped the Scroll Lock to the "print screen" button and it worked - only when I pressed the print screen the light turned on - but also the console froze... :-) . So, I guess that there is some logical connection between the keyboard and the OS and only when the *logical* scroll lock mapped key is on, the light turns on (and the console input/output freezes...). - I've also grepped and scanned the kernel sources trying to find where I could "play" with some settings. I thought the direction would be to to "disconnect" the relationship between the Scroll lock key and the console freezing. Has anyone got a similar thing working? Any suggestions? Thanks, Boaz. ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
