Razer peripherals - ArchWiki

Jump to content

# Razer peripherals

1 language

- 日本語

From ArchWiki

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

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 driver, OpenRazer can be used to enable Razer support along with additional frontends for GUI configuration, with many more supported devices listed.

## razercfg

### Compatibility

razercfg lists the following mice models as stable:

- Razer DeathAdder 2013
- Razer DeathAdder 3500 DPI
- Razer DeathAdder Black Edition
- Razer DeathAdder Chroma
- Razer DeathAdder Classic
- Razer DeathAdder Korea PCBang Edition
- Razer Diamondback Chroma
- Razer Krait
- Razer Mamba Tournament Edition
- Razer Naga 2012
- Razer Naga 2014
- Razer Naga Classic
- Razer Naga Epic
- Razer Naga Hex (v1)
- Razer Naga Hex 2014
- Razer Taipan

And the following as stable but missing minor features:

- Razer Boomslang CE
- Razer Copperhead
- Razer Lachesis Classic

### Installation

Install razercfgAUR (or razercfg-gitAUR for bleeding edge git releases).

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`.

The factual accuracy of this article or section is disputed.

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

The factual accuracy of this article or section is disputed.

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 configuration 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

A list of compatible devices can be found here.

### Installation

Install the openrazer-daemon package. Do not forget to add your current user to the group `plugdev` with the command

    # gpasswd -a $USER plugdev

then log out and back in.

### How to use

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

- polychromaticAUR: A Qt-based (Python) front-end with effect editor
- razergenieAUR: A Qt-based front-end with custom editor
- razercommander-gitAUR: A GTK-based front-end
- Snake: A front-end able to bind mouse buttons + keyboard

### 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 blackwidowcontrolAUR. After install, run:

    # blackwidowcontrol -i

Then use the shortcut utility of your Desktop Environment 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.

### CAPS Lock makes Razer Blade Stealth crash

The crash is caused by keyboard built-in driver.

#### If using Xorg

Get the keyboard description:

    $ xinput list | grep "Set 2 keyboard"

And create the file below, here we assume the above command returned "AT Raw Set 2 keyboard".

    /etc/X11/xorg.conf.d/00-keyboard-razer.conf

    Section "InputClass"
        Identifier      "Disable built-in keyboard"
        MatchProduct    "AT Raw Set 2 keyboard"
        Option          "Ignore"    "true"
    EndSection

#### If using Xwayland

    /etc/default/keyboard

    XKBOPTIONS="ctrl:nocaps"

CAPS Lock will now be identified as another CTRL key.

Source: https://github.com/rolandguelle/razer-blade-stealth-linux/blob/master/ubuntu-18-04.md#13-caps-lock-crash

Categories:

- Mice
- Keyboards

Hidden categories:

- Pages or sections flagged with Template:Style
- Pages or sections flagged with Template:Accuracy