OpenRazer is a community-led effort to support Razer peripherals on Linux.
USE flags for sys-apps/openrazer Drivers and user-space daemon to control Razer devices on GNU/Linux
||Build the OpenRazer daemon client|
||Build the OpenRazer daemon service|
||Enable subslot rebuilds on Distribution Kernel upgrades|
||Cryptographically sign installed kernel modules (requires CONFIG_MODULE_SIG=y in the kernel)|
||Allow symbol stripping to be performed by the ebuild for special files|
||Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)|
emerge --ask sys-apps/openrazer
Correctly OpenRazer can act as a backed for following packages:
- sys-apps/razercommander - a GUI OpenRazer client application,
- sys-apps/polychromatic - most feature-fill GUI configuration tool, providing also a CLI interface and a system tray icon,
- sys-apps/razer-cli - most minimal, CLI-only OpenRazer client.
The kernel modules should be automatically loaded by Udev, but can also be loaded by using the "modules" system service.
Upstream provides a systemd user service which can be enabled by the users running systemd.
OpenRazer provides a kernel module as well as a client and server implementations. Currently all OpenRazer clients rely on that server called "openrazer-daemon". So, to make all GUI/TUI clients work correctly, first the "openrazer-daemon" has to be started. This can be done by either adding it to the desktop startup scripts, xinitrc script or manually starting from the command-line.
emerge --ask --depclean --verbose sys-apps/openrazer