Linux driver for the Cougar 500k-700k Gaming Keyboards.
This driver solves the bug described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511511
This driver has been built and tested in Ubuntu Server 18.04 LTS, kernel 4.15.0-23-generic and latest kernel 4.18-rc3. It has been accepted in mainline kernel v4.20, but the code is still here for you to build the module for your kernel if you need to. Please refer to DKMS documentation (e.g., https://help.ubuntu.com/community/DKMS) for instructions on how to build this code as a DKMS module for your distribution.
If you use Ubuntu, you may refer to the releases folder for a precompiled .deb file.
Additionally, a Docker container can be used to cleanly compile the module and get a .deb file from it. The next sections explain how to use the provided Dockerfile to create a build container and how to use it for creating the module install package in .deb format.
Run the following command to create a Docker build image, if you don't have created it yet:
docker build -t dkmsbuilder .
Where dkmsbuilder is the container's image name (you can use your own name, but write it down for later) and . is the directory where the file Dockerfile resides (this project's root).
Run:
./build_module_package.sh dkmsbuilder
Where dkmsbuilder is the container's image name you created before (or the name you specified when creating the image). This script will search for the module's source code in the ./module directory and will leave the resulting .deb file in the directory ./build.
Note that the container has been designed to build modules as non-root user ('nobody:nogroup', to be precise). Make sure your ./build directory should be writable by nobody:nogroup, or the creation will fail due to lack of privileges.
Install the .deb file as usual. It will create a hid-cougar module for your running kernel, as well as udev rules for properly binding the keyboard to it. This rules are required because hid_generic module takes on the keyboard. The udev rules unbind the device from hid_generic, then rebind it to this module.
- All special keys (macro recording, led preferences and FN key combos) are handled by the hardware itself, so no special handling is required. Anyways, the keys are detected by the module (although it does nothing with them), so it would be good to write some kind of userspace tool to enrich the user experience.
- A lot more, for sure.