geekhack
geekhack Community => Keyboards => Topic started by: FSund on Fri, 13 April 2012, 15:16:28
-
Have anyone heard of this problem before, and know if there's anything to do about it?
I just got my first mechanical keyboard, a Zowie Celeritas Pro. But after connecting it to my laptop running Xubuntu (temporary while I wait for my RMA'd motherboard), none of the modifier keys seem to work. I've tried connecting the keyboard to a machine running Windows 7, and everything works like it should there.
I tried searching, and I found some similar issues, but no solutions. Apparently it's some kind of driver issue, that needs to be fixed by Zowie.
- https://bugs.archlinux.org/task/24505
-
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum
-
Just tried it, and all of the modifier keys are registered as exactly the same as my laptop's keyboard.
$ sudo showkey
kb mode was RAW
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]
press any key (program terminates 10s after last keypress)...
keycode 28 release
keycode 42 press # Left Shift
keycode 42 release
keycode 29 press # Left Ctrl
keycode 29 release
keycode 125 press # Windows button
keycode 125 release
keycode 56 press # Left Alt
keycode 56 release
keycode 100 press # AltGr
keycode 100 release
keycode 127 press # Menu button
keycode 127 release
keycode 97 press # Right Ctrl
keycode 97 release
keycode 54 press # Right Shift
keycode 54 release
-
The link in your post answers your question, I think: it appears that there are quirks in the way this keyboard sends scan codes, which may be fixed in future with an updated X11 driver.
Do you have an active ps/2 to USB adapter (i.e. one with an embedded chip and probably a little LED that lights up when connected)? If so, try chaining through that: Zowie keyboard --> USB to ps/2 adapter --> active ps/2 to USB adapter --> computer. The theory is that if the chip in the active adapter can "understand" your keyboard it might work, because the chip simulates a USB keyboard.
I can't guarantee success, but I've seen this trick work for other similar weird keyboard compatibility issues. If you try it, please post back here with results.
-
I think I already answered in this thread, but my post seems to have disappeared somehow..?
Anyway: I tried the trick you mentioned, after reading about it in another thread here on GH. I'm using the purple USB to PS/2 adapter that came with the keyboard, and a generic 2xPS/2 to 1xUSB adapter that I got from Dealextreme a while back. And now the keyboard works (almost) perfect! The "greater than/smaller than"-key next to the left shift, and the media keys on the F-buttons don't work, but I guess this is caused by the keyboard just getting some generic drivers now:
Before:
$ lsusb
[...]
Bus 007 Device 002: ID 2345:0101
[...]
Now:
$ lsusb
[...]
Bus 007 Device 005: ID 13ba:0017 Unknown PS/2 Keyboard+Mouse Adapter
[...]
Thanks a lot! Now I just have to hone my typing technique (I'm using most of my fingers, but not in a very organized way, and I make a lot of errors), as I'm only getting around 70 wpm at max.
-
https://bugzilla.kernel.org/show_bug.cgi?id=46491#c3 - worked for me