Logitech Gaming Keyboards
Some Logitech Gaming Keyboards can work on Linux through Unofficial drivers. There are a few packages available
- the python based Gnome15 project[dead link 2019-01-10] (Backup from 2019-01-10)
- the C based g15daemon project.
- Animation support with C++ based Keyleds project.
- Gkeys support for G910 Orion Spectrum/Spark: https://github.com/JSubelj/g910-gkey-macro-support), or a fork of it supporting M keys and their profile changing ability here (https://github.com/MR-R080T/g910-gkey-macro-support) AUR (
- Some Logitech gaming mice and keyboards are remappable using and . The app includes basic LED led customization and a simple GUI interface.
AUR and its dependencies are available in the community repository. G15daemon drivers still work for the keyboards they supported, but their development was mostly dropped in 2008, the source is still available for anyone to pick up and continue their development, there are a few bugs in them that were never solved. These drivers use the AUR to interact with the G keys. There is also a AUR plugin to show system information on the LCD display.
- G15 (Orange and Blue)
- G510 (Requires Patching; Read below)
Gnome15 has a list of supported devices on its front page. The keyboards are:
- G15 (Orange and Blue)
- G510 and G510s (Partial)
- G710 / G710+
- (and Microsoft SideWinder X4 / X6, hence name)
- Logitech G710 / G710+
AUR led supports:
AUR led supports (possible lua scripting):
G510 on g15daemon
Forum Thread (This thread has more detailed instructions and might be helpful for readers from other distributions or less advanced users, it also contains a list of known issues.)
A patch was written to make the G510 keyboard fully compatible with the g15daemon drivers. It is however not compatible with g15macro and as such an alternative approach was needed (which involved heavy modifications of the original code) the result yields much better performance for than using the gnome15 drivers which can currently result in severe input lag for this keyboard.
To apply the patch you must download the g15daemon and libg15 sources with broken link: package not found] and edit their PKGBUILDs.[
To download the sources to a folder directory called "community" (the folder will be dropped into whichever directory the terminal is in) run the two following commands:
ABSROOT=. abs community/g15daemon ABSROOT=. abs community/libg15
Now enter the folders and fetch the sources for them. (Make sure to remember to download the soures for both of them)
The patch already applies the patches from the arch community repository, so remove all patches that came with g15daemon by running:
Then place the files (libg15.patch and g15daemon.patch) into the folders that your packages were downloaded into, after this you must replace the PKGBUILDS with the new ones: g15daemon, libg15 These new PKGBUILDS refer to local sources only, this means they do not fetch sources from the net if they are not present so make sure you hold on to your tar.bz2 files. If you want them to fetch these from the net you can refer to the original PKGBUILDs.
Now install the packages, libg15 comes first,AUR is required as well before you install g15daemon.
This will compile, install and clean up the extracted sources afterwards to avoid cluttering the folder. I also recommend installingAUR from AUR next. For fluff.
After the installation you need to download[dead link 2020-03-30 ⓘ] or create the macro script files, and place them into /usr/share/g15daemon/macros. If you want to create them yourself the files need to be executable and the filenames are corresponding to the label on each key (so for the G1 key use /usr/share/g15daemon/macros/G1). Normally these files should use the bash script syntax.
For commands on the G keys to work with graphical applications g15daemon must be started after the X11 session. To do this you must add these commands to your autostart/xinitrc.
sudo g15daemon && sleep 3 && g15stats
And congratulations! you have a working G510 keyboard on Linux :) With a few issues of course (known issues are in the forum thread linked to at the start of this section)