ChuckPa

Having built and done the manual install, is there any benefit to having a RPM of the software for the casual fedora user who isn't savvy enough to put the .desktop file and systemctl scripts where they belong ? If so, I offer my time to put those together in a package I am seeing one small quirk, most likely my fault, with the 'windows lock' key (upper right corner of the strafe rgb). At one time it illuminated but now does not. Window lock functionality is correct. With lock 'on', Gnome will to 'overview' / 'pilot' view as it should. Suggestions? Also not seeing the alpha and num lock (long) white leds change. Is this normal? Thanks, C

I just received my Strafe RGB. A SUPER keyboard with one small exception. It works in BIOS and in Windows right out of the box and am using it now to type this. Fedora 22 won't see it as an input device but ckb does see it. Fedora does see the usb pass-thorough port and my mouse's RF receiver without issue. It did tell me about the firmware update and I did it immediately. I've also tried swapping the USB cables (machine powered off) to no avail. Did I forget a part of the installation/setup ? Thanks, C EDIT: Disregard. ckb-daemon wasn't starting. Looking GREAT. I think Corsair could take some pointers on the UI as well. Thanks VERY much for the app and driver.

Folks, Coming to the party a bit late. Trying to replace an OE membrane keyboard with the new Strafe on Fedora 22 and 23 (23 in a KVM at present). Both are Gnome desktops. I offer up my machine and time for builds if needed. If there are any 'gotchas' as far as basic functionality is concerned (before I order it), would you please let me know so I'm ready to dive in debugging when it arrives? Thanks, Chuck