Difference between revisions of "Razer peripherals"

From ArchWiki
Jump to navigation Jump to search
(1. razer-drivers/openrazer isn't new and the name of the project changed recently)
(Installation: Revert the last two edits as they don't add anything useful, except working around broken AUR helpers)
 
(13 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
[[Category:Mice]]
 
[[Category:Mice]]
 
[[Category:Keyboards]]
 
[[Category:Keyboards]]
[[bg:Razer]]
 
 
[[ja:Razer]]
 
[[ja:Razer]]
{{Poor writing|Various style issues, structure lacking}}
+
{{Style|Various style issues, structure lacking}}
 +
 
 +
{{Note|This page refers to Razer's mice and keyboards. If you were looking for the laptop, see [[Razer Blade]].}}
 +
 
 
There are currently no official drivers for any Razer peripherals in Linux. However, Michael Buesch has created a tool called [http://bues.ch/cms/hacking/razercfg.html razercfg] to configure Razer mice under Linux. There also exist scripts to enable macro keys of Razer keyboards.
 
There are currently no official drivers for any Razer peripherals in Linux. However, Michael Buesch has created a tool called [http://bues.ch/cms/hacking/razercfg.html razercfg] to configure Razer mice under Linux. There also exist scripts to enable macro keys of Razer keyboards.
  
 
Another package, {{AUR|openrazer-meta}} can be used to enable Razer support along with {{AUR|polychromatic}} or {{AUR|razergenie}} for GUI configuration. Supported devices are [https://openrazer.github.io/#devices listed here]
 
Another package, {{AUR|openrazer-meta}} can be used to enable Razer support along with {{AUR|polychromatic}} or {{AUR|razergenie}} for GUI configuration. Supported devices are [https://openrazer.github.io/#devices listed here]
  
== Razer Peripherals ==
+
== razercfg ==
  
 
=== Compatibility ===
 
=== Compatibility ===
Line 34: Line 36:
 
=== Installation ===
 
=== Installation ===
  
Download and install {{AUR|razercfg}} or {{AUR|razercfg-git}} for bleeding edge git releases from the [[AUR]].  
+
Download and install {{Pkg|razercfg}} or {{AUR|razercfg-git}} for bleeding edge git releases from the [[AUR]].  
  
 
You also need to edit your {{ic|/etc/X11/xorg.conf}} file to disable the current mouse settings by commenting them out as in the following example, where also some defaults are set as suggested by the author:
 
You also need to edit your {{ic|/etc/X11/xorg.conf}} file to disable the current mouse settings by commenting them out as in the following example, where also some defaults are set as suggested by the author:
Line 77: Line 79:
 
"static" can probably be changed to spectrum or breathing, and mode/color lines can be removed if led is set to "off".
 
"static" can probably be changed to spectrum or breathing, and mode/color lines can be removed if led is set to "off".
  
== Razer Blade ==
+
== OpenRazer ==
  
Razer Blade is Razer's line of gaming laptops. There is currently a 12" model (Razer Blade Stealth), 14" model (Razer Blade), and a 17" model (Razer Blade Pro). Due to the proprietary SBUI trackpad on the 17" model, it will be extremely difficult to get it to work without extensive USB protocol reversing.
+
=== Compatibility ===
  
=== 2016 version (Razer Blade & Razer Blade Stealth) ===
+
==== Keyboards ====
 +
* Razer BlackWidow Ultimate 2012
 +
* Razer BlackWidow Classic (Alternate)
 +
* Razer Anansi
 +
* Razer BlackWidow Ultimate 2013
 +
* Razer BlackWidow Classic
 +
* Razer DeathStalker Expert
 +
* Razer BlackWidow Chroma
 +
* Razer DeathStalker Chroma
 +
* Razer Blade Stealth
 +
* Razer Orbweaver Chroma
 +
* Razer BlackWidow Tournament Edition Chroma
 +
* Razer Blade QHD
 +
* Razer Blade Pro (Late 2016)
 +
* Razer BlackWidow Chroma (Overwatch)
 +
* Razer BlackWidow Ultimate 2016
 +
* Razer BlackWidow X Chroma
 +
* Razer BlackWidow X Ultimate
 +
* Razer BlackWidow X Tournament Edition Chroma
 +
* Razer Ornata Chroma
 +
* Razer Ornata
 +
* Razer Blade Stealth (Late 2016)
 +
* Razer BlackWidow Chroma V2
 +
* Razer Blade (Late 2016)
 +
* Razer Blade Stealth (Mid 2017)
  
The normal installation process works in general with the exceptions enumerated below.
+
==== Mice ====
 +
* Razer Orochi 2011           
 +
* Razer Mamba 2012 (Wired)     
 +
* Razer Mamba 2012 (Wireless) 
 +
* Razer Imperator 2012         
 +
* Razer Ouroboros 2012         
 +
* Razer Taipan                 
 +
* Razer Naga Hex (Red)         
 +
* Razer Orochi 2013           
 +
* Razer Naga 2014             
 +
* Razer Naga Hex               
 +
* Razer Abyssus 2014           
 +
* Razer DeathAdder Chroma     
 +
* Razer Mamba (Wired)         
 +
* Razer Mamba (Wireless)       
 +
* Razer Mamba Tournament Edition
 +
* Razer Orochi (Wired)         
 +
* Razer Diamondback Chroma     
 +
* Razer Naga Hex V2           
 +
* Razer Naga Chroma           
 +
* Razer Abyssus V2             
 +
* Razer DeathAdder Elite       
  
==== Killer Wireless Network Adapter ====
+
==== Mousemats ====
 +
* Razer Firefly
  
Killer Wireless adapters no longer require special firmware to function, and will work right out of the box.
+
==== Headsets ====
 +
* Razer Kraken 7.1 Classic
 +
* Razer Kraken 7.1 Chroma
 +
* Razer Kraken 7.1 V2
  
{{Remove|Avoid manual tinkering for {{ic|/lib}} paths. There is {{Aur|ath10k-firmware-qca9887-git}}{{Broken package link|package not found}}, which packages below. Why not use that?}}
+
==== Other devices ====
Blade 2016 with Killer 1535 will, however, drop connection upon heavy load. A possible solution is to use the [https://github.com/kvalo/ath10k-firmware/ git] version of ath10k as following:
+
* Razer Nostromo
 +
* Razer Orbweaver
 +
* Razer Tartarus
 +
* Razer Tartarus Chroma
 +
* Razer Core
 +
* Razer Chroma Mug Holder
  
Remove the included firmware:
+
=== Installation ===
 
 
{{bc|<nowiki>
 
# rm -r /lib/firmware/ath10k/QCA6174/
 
</nowiki>}}
 
 
 
Download the latest firmware using {{Pkg|wget}} or your favorite browser:
 
 
 
{{bc|<nowiki>
 
$ wget https://github.com/kvalo/ath10k-firmware/archive/master.zip
 
</nowiki>}}
 
 
 
Unzip the downloaded file using your preferred method and copy to /lib/firmware/ath10k/:
 
 
 
{{bc|<nowiki>
 
# cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/
 
</nowiki>}}
 
 
 
Rename some files:
 
 
 
{{bc|<nowiki>
 
# cd /lib/firmware/ath10k/QCA6174/hw2.1/
 
# mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin
 
# cd /lib/firmware/ath10k/QCA6174/hw3.0/
 
# mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin
 
</nowiki>}}
 
 
 
Reboot and test.
 
 
 
==== Touchpad ====
 
 
 
[[Install]] the {{Pkg|xf86-input-libinput}} package: this is also the only one that will enable natural scrolling. See [[Libinput]] for more information on this driver.
 
 
 
Alternatively, if you prefer using the [[Touchpad Synaptics]] driver, [[install]] the {{Pkg|xf86-input-synaptics}} package.
 
 
 
If you have issues with the touchpad not working after resuming from sleep, restarting the module i2c_hid seems to work.
 
 
 
==== Touchscreen ====
 
 
 
While the touchscreen will provide basic functionality out of the box, it is best to use {{AUR|touchegg}} to configure multitouch gestures. These include two-finger scrolling, right-click, etc.
 
 
 
==== Graphics Drivers ====
 
 
 
The graphics card works OK with the standard intel drivers which you can [[install]] with the {{Pkg|xf86-video-intel}} package.  See [[Intel graphics]] for more information on installation and configuration.
 
 
 
Issues with screen flickering seem to be resolved by changing ''AccelMethod'' to ''uxa'' as described in the [[Intel_graphics#SNA_issues|SNA issues]] section.
 
 
 
{{bc|<nowiki>
 
# cat >/etc/X11/xorg.conf.d/20-intel.conf
 
Section "Device"
 
  Identifier  "Intel Graphics"
 
  Driver      "intel"
 
  Option      "AccelMethod"  "uxa"
 
  #Option      "AccelMethod"  "sna"
 
EndSection
 
</nowiki>}}
 
 
 
If you experience screen tearing while scrolling add the following line to the conf above:
 
{{ic| Option "TearFree" "true"}} and set the "AccelMethod" to "sna" and comment out "uxa"
 
 
 
If you have an Intel Kaby Lake chip [[wikipedia:Kaby_Lake]], and the issue is not fixed with the conf above, add to {{ic|1=i915.enable_rc6=0}} to the [[kernel parameters]].
 
 
 
==== Hybrid graphics ====
 
 
 
If the discrete Nvidia GPU is switched off before starting Xorg or Wayland, then the system freezes. The only possible solution is to manually disable/enable the discrete card after starting the graphical session.
 
However there is a ACPI DSDT fix available which fixes this problem. Check the [https://github.com/m4ng0squ4sh/razer_blade_14_2016_acpi_dsdt repository] for more information.
 
 
 
==== Suspend Loop ====
 
Suspending (Close laptop lid) does not seem to work with a basic installation. The lid state transitions from "open" to "closed" correctly the first time (and the system suspends), but after resuming from suspend by opening the lid, the lid state does not change back to "open". This results in the laptop entering a suspend loop because systemd monitors the lid state, sees that the lid is closed, and suspends the system.
 
 
 
A [https://bugzilla.kernel.org/show_bug.cgi?id=187271 bug] was filed against the kernel ACPI driver in November 2016. It contains a fair amount of documentation on the issue along with a workaround which seems to solve the problem.
 
 
 
To work around the issue, add the following to your [[kernel parameters]]:
 
 
 
{{bc|<nowiki>
 
button.lid_init_state=open
 
</nowiki>}}
 
 
 
This will instruct the acpi driver to generate an extra open event when waking from suspend which will keep the system up.
 
 
 
You can check that the setting was acknowledged:
 
{{bc|<nowiki>
 
# cat /sys/module/button/parameters/lid_init_state
 
open
 
</nowiki>}}
 
 
 
And also view all boot parameters:
 
{{bc|<nowiki>
 
$ cat /proc/cmdline
 
initrd=\initramfs-linux.img ... button.lid_init_state=open
 
</nowiki>}}
 
 
 
===== GRUB =====
 
For example, to make changes permanent on [[GRUB]] systems, edit {{ic|# /etc/default/grub}} and append {{ic|1=button.lid_init_state=open}} to the {{ic|GRUB_CMDLINE_LINUX_DEFAULT}} line. After the change, the line might look like this (mileage may vary depending on the kernel params already set):
 
 
 
{{bc|<nowiki>
 
GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open"
 
</nowiki>}}
 
 
 
Then automatically re-generate the grub.cfg file with:
 
{{bc|<nowiki>
 
# grub-mkconfig -o /boot/grub/grub.cfg
 
</nowiki>}}
 
 
 
==== Tweaking ====
 
 
 
If you are using [[GNOME]], the ''gnome-tweak-tool'' can be used to adjust the window and font scaling. A font scale of ''1.25'' puts the font sizes closer to how they are displayed by default in Windows 10.
 
 
 
If you are using an external monitor that is not [[HiDPI]], you can use ''xrandr'' to alter the scaling of the external monitor using the instructions for [[HiDPI#Multiple_displays|Multiple Displays]]. You may have better results though running [[GNOME]] on [[Wayland]]. When installed, clicking the gear icon in [[GDM]] will allow you to select ''Gnome On Wayland'' and will default to that in the future.
 
 
 
==== Audio ====
 
 
 
On the latest 'KabyLake' Intel CPU, if you also have a dual-boot with Windows, you might experience some audio issues when booting to Windows and restarting on Linux. The problem is no sound from the speakers and some cracking noises on the headphones - especially when using the touchpad -.
 
No official solution has been posted yet, but a quick hack is to completely shut down the computer (so power off, not restart).
 
 
 
==== Webcam ====
 
 
 
Setting the uvcvideo option "quirks=128" appears to let the webcam work at 720p30, thus enabling [https://hangouts.google.com Google Hangouts] support. {{Pkg|cheese}} works after changing resolution to 720p and relaunching. Multiplying the quirk by a power of 2+ further improves video quality to a point. "quirks=512" seems to work best for one user.
 
 
 
{{hc|1=/etc/modprobe.d/uvcvideo.conf|2=
 
## fix issue with built-in webcam
 
options uvcvideo quirks=512
 
}}
 
 
 
==== Keyboard ====
 
 
 
The {{AUR|openrazer-meta}} package enables backlight control capabilities (including effects) and macro controls. You may use {{AUR|polychromatic}} or {{AUR|razercommander-git}} for a GUI to set the keyboard options.
 
 
 
=== 2014 version ===
 
 
 
==== Problems ====
 
 
 
[http://forum.notebookreview.com/razer/751074-2014-razer-blade-14-linux.html Source]
 
* touchpad  (multitouch, although this may be a kernel bug that has since been fixed)
 
* keys to increase/decrease screen illumination not working
 
* keys to increase/decrease keyboard illumination not working
 
 
 
==== Possible trackpad solution ====
 
 
 
[https://bbs.archlinux.org/viewtopic.php?id=173356&p=2 Source]
 
 
 
{{bc|
 
git clone https://github.com/aduggan/hid-rmi.git -b rb14 # and then install it
 
depmod -a
 
}}
 
 
 
Then [[install]] the {{pkg|synaptics}}{{Broken package link|replaced by {{Pkg|xf86-input-synaptics}}}} package.
 
 
 
Feature still not working: pinch to zoom, 3rd mouse button.
 
 
 
=== 2013 version ===
 
 
 
==== What works ====
 
 
 
[https://bbs.archlinux.org/viewtopic.php?id=173356 Source]
 
 
 
* Wireless
 
* Switchable graphics
 
* Bluetooth
 
* Keyboard light (HW controlled)
 
* UEFI boot
 
* Trackpad (only on Linux 4.0+ '''without''' libinput-based X.Org input driver (xf86-input-libinput) thanks to [http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/log/drivers/hid/hid-rmi.c?h=for-3.20/rmi Andrew Duggan's work]).
 
 
 
==== Problems ====
 
 
 
[http://forum.notebookreview.com/razer/729380-razer-blade-pro-under-linux.html Source]
 
 
 
* SwitchBlade UI does not work due to lack of drivers.
 
* <strike>Trackpad scrolling does not work.</strike>
 
  
==== Possible trackpad solution ====
+
[[Install]] the {{AUR|openrazer-meta}} package. Don't forget to add your current user to the group {{ic|plugdev}} with the command {{ic|sudo gpasswd -a $USER plugdev}} and logging out and back in.
  
[https://bbs.archlinux.org/viewtopic.php?id=173356&p=2 Source]
+
=== How to use ===
  
{{bc|<nowiki>
+
The recommended way is to use a graphical front-end for interfacing with the drivers.
git clone https://github.com/aduggan/hid-rmi.git -b rb14 # and then install it
 
depmod -a
 
</nowiki>}}
 
  
Then [[install]] the {{pkg|synaptics}}{{Broken package link|replaced by {{Pkg|xf86-input-synaptics}}}} packages.
+
* {{AUR|polychromatic}}: A WebKit-based front-end featuring profiles
 +
* {{AUR|razergenie}}: A Qt-based front-end
 +
* {{AUR|razercommander}}: A GTK-based front-end
  
Feature still not working: pinch to zoom, 3rd mouse button
+
=== Troubleshooting ===
  
{{Expansion|The SBUI works as a trackpad, but no linux drivers currently exist. Does it even work for basic trackpad functionality?}}
+
Visit the [https://github.com/openrazer/openrazer/wiki/Troubleshooting Troubleshooting page] in the OpenRazer wiki.
  
 
== Razer keyboards ==
 
== Razer keyboards ==
There are currently two Python scripts available to enable macro keys under Linux:
+
There are currently two Python scripts available to enable the extra M1 - M5 macro keys, that certain Razers have, under Linux:
 +
Note that this does not allow to assign any content to Macro keys, it merely will enable the sending of keycodes. For Razers without M1 -M5 extra keys there is no point using this tool.
 
=== Blackwidow Control ===
 
=== Blackwidow Control ===
 
====Features====
 
====Features====
Line 292: Line 180:
 
After install run as root
 
After install run as root
 
  $ blackwidowcontrol -i
 
  $ blackwidowcontrol -i
Then use the shortcut utility of your Desktop Enviroment to map the keys
+
Then use the shortcut utility of your Desktop Enviroment to map the keys, i.e. to actually use the macro keys for something useful. For example, the "KDE global shortcuts" GUI (find it in system settings) can assign macros to a key on any keyboard, not just Razers.
  
 
=== Blackwidow macro scripts ===
 
=== Blackwidow macro scripts ===
 
==== Features ====
 
==== Features ====
* Works with BlackWidow Ultimate and Stealth 2013 (unknown whether it works with other versions)
+
* Works with BlackWidow Ultimate and Stealth 2013 (unknown whether it works with other versions or keyboard models)
 +
* adding the "021e" ID for Ornata Chroma makes the Game-mode feature (white "G" LED) work on Ornata Chroma as well.
 
* Uses Python 2
 
* Uses Python 2
 
* Bundles scripts to create and execute macros
 
* Bundles scripts to create and execute macros

Latest revision as of 10:41, 4 May 2019

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

Reason: Various style issues, structure lacking (Discuss in Talk:Razer peripherals#)
Note: This page refers to Razer's mice and keyboards. If you were looking for the laptop, see Razer Blade.

There are currently no official drivers for any Razer peripherals in Linux. However, Michael Buesch has created a tool called razercfg to configure Razer mice under Linux. There also exist scripts to enable macro keys of Razer keyboards.

Another package, openrazer-metaAUR can be used to enable Razer support along with polychromaticAUR or razergenieAUR for GUI configuration. Supported devices are listed here

razercfg

Compatibility

razercfg lists the following mice models as stable:

  • Razer DeathAdder Classic
  • Razer DeathAdder 3500 DPI
  • Razer DeathAdder Black Edition
  • Razer DeathAdder 2013
  • Razer DeathAdder Chroma
  • Razer Krait
  • Razer Naga Classic
  • Razer Naga 2012
  • Razer Naga 2014
  • Razer Naga Hex
  • Razer Taipan

And the following as stable but missing minor features:

  • Razer Lachesis
  • Razer Copperhead
  • Razer Boomslang CE

Installation

Download and install razercfg or razercfg-gitAUR for bleeding edge git releases from the AUR.

You also need to edit your /etc/X11/xorg.conf file to disable the current mouse settings by commenting them out as in the following example, where also some defaults are set as suggested by the author:

/etc/X11/xorg.conf
 Section "InputDevice"
    Identifier  "Mouse"
    Driver  "mouse"
    Option  "Device" "/dev/input/mice"
 EndSection

It is important to only have Mouse and not Mouse# listed in xorg.conf.

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: Why reboot? (Discuss in Talk:Razer peripherals#)

Restart the computer, then enter:

# udevadm control --reload-rules

Then start the razerd daemon and possibly enable it.

Using the Razer Configuration Tool

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: Button configuration reported to not work (Discuss in Talk:Razer#Button configuration in razercfg or qrazercfg)

There are two commands you can use, one for the command line tool razercfg or the Qt-based GUI tool qrazercfg.

From the tool you can use the 5 profiles, change the DPI, change mouse frequency, enable and disable the scroll and logo lights and configure the buttons.

If the colors reset on reboot edit the config file directly and test with another reboot:

/etc/razer.conf
# Configure LEDs
led=1:GlowingLogo:on
led=1:Scrollwheel:on
mode=1:Scrollwheel:static
color=1:Scrollwheel:0000FF
mode=1:GlowingLogo:static
color=1:GlowingLogo:FFFFFF

"static" can probably be changed to spectrum or breathing, and mode/color lines can be removed if led is set to "off".

OpenRazer

Compatibility

Keyboards

  • Razer BlackWidow Ultimate 2012
  • Razer BlackWidow Classic (Alternate)
  • Razer Anansi
  • Razer BlackWidow Ultimate 2013
  • Razer BlackWidow Classic
  • Razer DeathStalker Expert
  • Razer BlackWidow Chroma
  • Razer DeathStalker Chroma
  • Razer Blade Stealth
  • Razer Orbweaver Chroma
  • Razer BlackWidow Tournament Edition Chroma
  • Razer Blade QHD
  • Razer Blade Pro (Late 2016)
  • Razer BlackWidow Chroma (Overwatch)
  • Razer BlackWidow Ultimate 2016
  • Razer BlackWidow X Chroma
  • Razer BlackWidow X Ultimate
  • Razer BlackWidow X Tournament Edition Chroma
  • Razer Ornata Chroma
  • Razer Ornata
  • Razer Blade Stealth (Late 2016)
  • Razer BlackWidow Chroma V2
  • Razer Blade (Late 2016)
  • Razer Blade Stealth (Mid 2017)

Mice

  • Razer Orochi 2011
  • Razer Mamba 2012 (Wired)
  • Razer Mamba 2012 (Wireless)
  • Razer Imperator 2012
  • Razer Ouroboros 2012
  • Razer Taipan
  • Razer Naga Hex (Red)
  • Razer Orochi 2013
  • Razer Naga 2014
  • Razer Naga Hex
  • Razer Abyssus 2014
  • Razer DeathAdder Chroma
  • Razer Mamba (Wired)
  • Razer Mamba (Wireless)
  • Razer Mamba Tournament Edition
  • Razer Orochi (Wired)
  • Razer Diamondback Chroma
  • Razer Naga Hex V2
  • Razer Naga Chroma
  • Razer Abyssus V2
  • Razer DeathAdder Elite

Mousemats

  • Razer Firefly

Headsets

  • Razer Kraken 7.1 Classic
  • Razer Kraken 7.1 Chroma
  • Razer Kraken 7.1 V2

Other devices

  • Razer Nostromo
  • Razer Orbweaver
  • Razer Tartarus
  • Razer Tartarus Chroma
  • Razer Core
  • Razer Chroma Mug Holder

Installation

Install the openrazer-metaAUR package. Don't forget to add your current user to the group plugdev with the command sudo gpasswd -a $USER plugdev and logging out and back in.

How to use

The recommended way is to use a graphical front-end for interfacing with the drivers.

Troubleshooting

Visit the Troubleshooting page in the OpenRazer wiki.

Razer keyboards

There are currently two Python scripts available to enable the extra M1 - M5 macro keys, that certain Razers have, under Linux: Note that this does not allow to assign any content to Macro keys, it merely will enable the sending of keycodes. For Razers without M1 -M5 extra keys there is no point using this tool.

Blackwidow Control

Features

  • confirmed to work with regular BlackWidow, BlackWidow 2013 and BlackWidow Ultimate Stealth 2014
  • should also work with BlackWidow Ultimate, BlackWidow Ultimate 2013 and BlackWidow 2014
  • does not work with BlackWidow (Ultimate) 2016 yet
  • uses Python 3
  • allows to control the status of the LED
  • contains a file with udev rule so macro keys will be enabled automatically when the keyboard is plugged in

How to Use

Install it from AUR blackwidowcontrolAUR After install run as root

$ blackwidowcontrol -i

Then use the shortcut utility of your Desktop Enviroment to map the keys, i.e. to actually use the macro keys for something useful. For example, the "KDE global shortcuts" GUI (find it in system settings) can assign macros to a key on any keyboard, not just Razers.

Blackwidow macro scripts

Features

  • Works with BlackWidow Ultimate and Stealth 2013 (unknown whether it works with other versions or keyboard models)
  • adding the "021e" ID for Ornata Chroma makes the Game-mode feature (white "G" LED) work on Ornata Chroma as well.
  • Uses Python 2
  • Bundles scripts to create and execute macros

Troubleshooting

Mouse randomly stops working

Note: This is tested on ASUS N550JV using mouse Razer Orochi 2013. Laptop probably has faulty charging port and therefore it sometimes directly affects connected mouse USB port and causes similar issues.

If your razer mouse stops working after some time, however, led flashes or lights up, but reboot and re-plugging does not help, try the following commands.

Unload ehci_pci and ehci_hcd modules:

# rmmod ehci_pci
# rmmod ehci_hcd

Disconnect the mouse, wait a few seconds and run the following commands to load modules back:

# modprobe ehci_hcd
# modprobe ehci_pci

Connect the mouse and it should be working.