I tried to install this driver (because I got the Blackwidow Chroma) and it seems that some SDL libraries are missing. When I execute the install_driver.sh file, I get this:

In file included from razer_chroma.c:1:0:
razer_chroma.h:17:22: fatal error: SDL2/SDL.h: Datei oder Verzeichnis nicht gefunden
#include "SDL2/SDL.h"
^
compilation terminated.
make[1]: *** [razer_chroma.o] Fehler 1
make: *** [librazer_chroma] Fehler 2
In file included from razer_chroma.c:1:0:
razer_chroma.h:17:22: fatal error: SDL2/SDL.h: Datei oder Verzeichnis nicht gefunden
#include "SDL2/SDL.h"
^
compilation terminated.
make[1]: *** [razer_chroma.o] Fehler 1
make: *** [librazer_chroma] Fehler 2

"Datei oder Verzeichnis nicht gefunden" is german for "File or Folder is not found"
"Fehler" is german for "Error"
(for all those guys that don't understand german ^^)

You should also add the dependencies of this driver to the description... 😃

So I followed the directions for debian and when I execute the command sudo systemctl start razer_bcd it says

Job for razer_bcd.service failed. See 'systemctl status razer_bcd.service' and 'journalctl -xn' for details.

I did that and this is what I got:
Pastebin

I also looked in /sys/bus/hid/devices/

0003:046D:C283.0002  0003:1532:003E.0004  0003:1532:011A.0009  0003:1532:011A.000B
0003:1532:003E.0003  0003:1532:003E.0005  0003:1532:011A.000A  0003:1532:0504.0001

nothing that matches the pattern the script is looking for.

Any assistance you can give will be greatly appreciated.

EDIT: I have a Razer Blackwidow (2013?) and a Razer Naga Epic Chroma connected.

Hi Guys

The build etc was smooth, but then the dpkg -i runs it gives an error saying it cannot start the job.

Manually running the service start also fails.

wolfen@wolfen-HP:/usr/share/razer_bcd$ sudo service razer_bcd start
start: Job failed to start

Where can I look for more info?

I saw this in dpkg.log

2016-02-14 12:43:36 status installed razer-chroma-driver:amd64 1.0.0

Could you write some detailed documentation of the daemon and how to interact with it (specifically using DBUS). Sending messages via DBUS is easy, it would help to know what to send the daemon.

I would like to start writing a GUI, the node editor in blender shouldn't be difficult with a bit of OpenGL and GTK. From what I can gather there are render nodes and they are stored in a list and are updated in a loop.

Am I right in thinking that if one wanted to set the keyboard to static colour mode they would skip the daemon and tell the driver to do it? (From what I can see the daemon should be more than capable to do static colour)

First of all, thank you for the driver!

I noticed that the above file does not show up even if the kernel module seems loaded.

What could I have done wrong? I am using a 3.2.0-3-amd64 kernel.

Hey man,

As I mentioned I cannot seem to figure out how to get this working.

My keyboard is just showing some randomly colored purple keys in the middle of my keyboard. I have downloaded and ran your script and attempted to run a few of the driver scripts to get any affects working but none will do anything or make any chages to the keyboard.

Any advice?

Thanks

I have written a on-the-fly macro recorder/ player called MacroW
It is working with a Razer Blackwidow Chroma.

1 - As you have more keyboards maybe could help extend the list of supported ones? Tell me if works with your devices ?

2 - Maybe add the MacroW script has one of its dependencies so that 'razer_chroma_drivers' have on the fly macro recording and playback ?

https://github.com/igorbb/MacroW

here is the output of the comand:

::\033[32m COMPILING librazer_chroma.so\033[0m
================================
::\033[32m COMPILING librazer_chroma.so [DEBUG]\033[0m
========================================
::\033[32m COMPILING razer_bcd [SHARED]\033[0m
================================
::\033[32m COMPILING razer_bcd daemon\033[0m
==============================
::\033[32m COMPILING razer_bcd daemon [DEBUG]\033[0m
======================================
/usr/bin/ld: cannot find -lrazer_chroma_debug
collect2: error: ld returned 1 exit status
Makefile:34: recipe for target 'daemon_debug' failed
make[1]: *** [daemon_debug] Error 1
Makefile:26: recipe for target 'razer_daemon' failed
make: *** [razer_daemon] Error 2

Hello,
Thank you for working on this driver.

Here are some bugs I had during tests:

Compilation:

I had to modify razer_blackwidow_chroma_driver/daemon/fx/Makefile
I had to comment:
ifeq ($(LIBFFTW3), 0) and endif
I don't know why this ifeq doesnt work.

UI and tray applet:

goldorak razer_blackwidow_chroma_driver # ./gui/chroma_controller/chroma_controller.py 
Traceback (most recent call last):
  File "./gui/chroma_controller/chroma_controller.py", line 22, in <module>
    import razer.daemon_dbus
**ImportError: No module named 'razer'**

goldorak razer_blackwidow_chroma_driver # ./gui/tray_applet/razer_tray_applet.py 
Traceback (most recent call last):
  File "./gui/tray_applet/razer_tray_applet.py", line 7, in <module>
    import appindicator
**ImportError: No module named appindicator**

dynamic:

some rgb arguments are not well parsed ?

example:

cat fps.template

    2
    255 255 0
    1234
    [...]

goldorak dynamic-examples # cat fps.template |../dynamic

Enter r g b: Enter str: Setting keys of [1234] to 0 255 0...
Setting 1...
Setting 2...
Setting 3...
Setting 4...
Done!
[...]
Exiting...

Key bindings:

• using a french AZERTY keyboard, some keys mismatch since they are setup for qwerty. I had to indicate Q when the key was A on my keyboard (for example in examples/dota_keys.c)
• And I think some keys binding are incorrect:
  I had to indicate Z key to setup the Y key, or Y to setup Z

example:

        razer_convert_ascii_to_pos('Z',&pos);
        razer_set_key_pos(chroma->keys,&pos,&light_blue);

will setup the Y key in light blue.

I noticed that on the main page it says support for the Blackwidow Ultimate 2016 is in progress, so I'm not sure how much to expect; I just got an Ultimate Stealth 2016 keyboard and installed the driver, and when I try to start it, /var/log/upstart/razer_bcd.log contains:

Unknown device, --name=, --path=, or absolute path in /dev/ or /sys expected.
Unknown device, --name=, --path=, or absolute path in /dev/ or /sys expected.
Binding device (*:1532:020[39]*) to hid-generic

At a glance, I can see that in 95-razerkbd.rules, it does not have a line that matches my keyboard; the product ID according to lsusb is 0214.

Mind if I add support for my ultimate2013 to the driver/daemon?

Hi!
I just started messing around with the library, and i am trying to light up the Ctrl, Alt, and Shift keys.
razer_convert_ascii_to_pos works just fine for setting letter keys, but how can i set the ctrl key? it's not in the ascii table.

Can you create a file in the repo that lists x-y pairs to keys?

Hello and thank you for doing this!

I'm using Kubuntu 14.04 and managed to install the Ubuntu 14.04 version just fine.
The Desktop entries did not get registered properly but that does not bother me.

When I try to manually run python /usr/share/razer_chroma_controller/chroma_controller.py to open the GUI it plops the following error:

 ~  python /usr/share/razer_chroma_controller/chroma_controller.py 
  File "/usr/share/razer_chroma_controller/chroma_controller.py", line 130
    js_exec.exec()
               ^
SyntaxError: invalid syntax

I have no clue about where to start debugging this. Any ideas? I think I'm missing a dependency or maybe it is really a bug.

PD: Also, after installing and restarting the keyboard turned green instead of cycling through all the colors, so I assume the daemon is working.

Hello,

Notes:

• I own blackwidow chroma tournament edition.
• I've replaced the 0x0203 product id by 0x0209 which corresponds to my keyboard.
• I am familiar with C but not with kernel development.

After looking at the source and adding a few prints I managed to partially trace my problem.
It failed to open /sys/bus/hid/devices/0003:1532:0209.0006/mode_custom. This file simply doesn't exist.
I suppose the kernel module is supposed to create it so userland can talk to the driver.
The kernel module seems loaded: lsmod | grep razer reports the following:

razerkbd               18592  0 
hid                   102264  3 hid_generic,razerkbd,usbhid
usbcore               195340  5 ehci_hcd,ehci_pci,razerkbd,usbhid,xhci_hcd

Do you have an idea about what could have wrong? Is there additional information that I could provide that would help resolving the issue?

Thanks,

Edit: Kernel version: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux.

It cant start in Ubuntu 15.10

This is an issue I've got for quite a while but basically in the daemon_dbus.py this line
self.dbus_daemon_object = system_bus.get_object("org.voyagerproject.razer.daemon", "/")
is crashing, going to say each time: "Failed to connect to the dbus service. Is the razer_bcd service running?"
I tried running razer_bcd directly from the compiled version or anything(I have very few experience with daemons) and restarted countless of times without any clues.

The less clueless hints I succeeded to get was that:

sudo bash razer_bcd_ubuntu force-reload
Restarting Razer Keyboard daemon razer_bcd
start-stop-daemon: warning: failed to kill 31008: No such process
Starting razer blackwidow chroma daemon as a daemon

While it says the daemon is in the work, it also says it cannot find latest instance, and this goes each time I do a force-reload.

A lot might've gone wrong and I know that but having really few experience w/ linux daemons is not helping on my hand, and what I can say for sure is that there's something wrong with the way the daemon is running on my system
(For who cares modded version of Kubuntu by myself)
So sorry if I really made an obvious mistake or anything, but I'm beeing clueless this time beeing.

I tried this on xubuntu 15.04 and it does not seem to work.

Is there an uninstall script?

Hello,

can you give a roadmap about written driver for the Razer DeathStalker?
Is there a way to help coding porting the driver?

I'm still really a beginner at all this DBUS stuff, but I see you have provided a

razer_bcd_controller

to use to communicate via the cli. I have read through the help it provides and your readme page, but I still don't get it. Can someone please just give me a simple command line way to set the keyboard brightness to say 10/255 20/255 etc ?

Thank you for a clear, concise write up on installation. This is what terminal said:

sudo dpkg -i /tmp/razer-chroma-driver_1.0.0_amd64.deb
Selecting previously unselected package razer-chroma-driver.
(Reading database ... 263589 files and directories currently installed.)
Preparing to unpack .../razer-chroma-driver_1.0.0_amd64.deb ...
Unpacking razer-chroma-driver (1.0.0) ...
dpkg: dependency problems prevent configuration of razer-chroma-driver:
 razer-chroma-driver depends on libfftw3-3 (>= 3.3.3-7ubuntu3); however:
  Package libfftw3-3 is not installed.

dpkg: error processing package razer-chroma-driver (--install):
 dependency problems - leaving unconfigured
Processing triggers for gnome-menus (3.13.3-6ubuntu1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for bamfdaemon (0.5.2~bzr0+15.10.20150627.1-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.58ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (225-1ubuntu9) ...
Processing triggers for dbus (1.10.0-1ubuntu1) ...
Errors were encountered while processing:
 razer-chroma-driver

How can I find out what errors were encountered?
I opened up Ubuntu software center afterwards and it said 'errors were encountered, do you want to fix them?'
I said yes and saw some files come and go in the tmp directory. But looking for 'razer' in the 'installed' items reveals nothing. Even when 'show technical items' is clicked at the bottom of software center.

It seems like it doesn't detect my Razer Mamba TE, if I use the python library and tell it to enumerate the devices, it only lists the firefly.

>>> import razer.daemon_dbus
>>> import razer.keyboard
>>> daemon = razer.daemon_dbus.DaemonInterface()
Successfully connected to dbus service.
>>> daemon.enumerate_devices()
Device ID 0
Device Type "Razer Firefly", Device Serial "ST1531135701269"
[{'index': 0, 'type': dbus.String('Razer Firefly'), 'serial': dbus.String('ST1531135701269')}]

Are there any log files I could provide? I checked /var/log/upstart/razer_bcd.log but the file doesn't seem to exist.

I was trying to install this and i got this on the ./package_for_ubuntu.sh step

rm: cannot remove ‘/razer-chroma*.deb’: No such file or directory
dpkg-deb: building package razer-chroma-driver' in/tmp/tmp.k6ycKYsRpC.deb'.
dpkg-name: warning: cannot move '/tmp/tmp.k6ycKYsRpC.deb' to existing file

thanks for your work btw :)

Greetings,
I used to use this when I was using Ubuntu and it worked perfectly, but now that I've switched to Arch I get a problem when compiling "razer kernel modules".
Here is the "sudo make -s all install" command output:

\n::\033[32m COMPILING librazer_chroma.so\033[0m
================================
\n::\033[32m COMPILING librazer_chroma.so [DEBUG]\033[0m
========================================
\n::\033[32m COMPILING razer_bcd [SHARED]\033[0m
================================
\n::\033[32m COMPILING razer_bcd daemon\033[0m
==============================
\n::\033[32m COMPILING razer_bcd daemon [DEBUG]\033[0m
======================================
\n::\033[32m COMPILING pez2001 fx collection [DEBUG]\033[0m
===========================================
\n::\033[32m COMPILING pez2001 fx mixer [DEBUG]\033[0m
======================================
\n::\033[32m COMPILING pez2001 fx light blast [DEBUG]\033[0m
============================================
\n::\033[32m COMPILING pez2001 fx progress bar [DEBUG]\033[0m
============================================
\n::\033[32m COMPILING pez2001 fx compute fft [DEBUG]\033[0m
============================================
\n::\033[32m COMPILING pez2001 fx collection\033[0m
===================================
\n::\033[32m COMPILING pez2001 fx mixer\033[0m
==============================
\n::\033[32m COMPILING pez2001 fx light blast\033[0m
====================================
\n::\033[32m COMPILING pez2001 fx progress bar\033[0m
====================================
\n::\033[32m COMPILING pez2001 fx compute fft\033[0m
====================================
\n::\033[32m COMPILING razer_bcd controller [SHARED]\033[0m
===========================================
\n::\033[32m COMPILING razer_bcd controller\033[0m
=========================================
\n::\033[32m COMPILING razer_bcd controller [DEBUG]\033[0m
=================================================
\n::\033[32m COMPILING examples [DEBUG]\033[0m
==============================
\n::\033[32m COMPILING examples\033[0m
======================
\n::\033[32m COMPILING snake game\033[0m
======================
\n::\033[32m COMPILING razer kernel modules\033[0m
========================================
Makefile:10: recipe for target 'razer_drv' failed
make: *** [razer_drv] Error 2

Not sure what the problem is...

Should we consider packaging up the current code and creating packages for various systems? To do that, it would be essential to start tracking versions ("releases") when new major changes are made to the code.

Packages could be committed in a dist/ folder. A PPA (for Ubuntu users) would be nice so that general users can have updates pushed to their systems.

Suggested distros to focus packages for:

• Ubuntu 15.10 (deb)
• Ubuntu 14.04 (deb)
• Debian 8 (deb)
• Fedora 23 (rpm)
• openSUSE? (rpm)

--- Based on distros mentioned in this repo.
--- Primarily focused on amd64?

In your bash scripts where you check if the device is a mouse type, would it not be better to check that the usb interface number equals 2?

I believe you could simplify the search for the right device as when its bound to the razerkbd driver it should be symlinked to the drivers directory like /sys/bus/hid/drivers/razerkbd/0003:1532:0203.0011

Would you mind me submitting a pull request with some changes?
Also I wouldn't mind packaging this up to be installed on deb and rpm based distros. This would be great for debian/ubuntu users as then we could integrate it with dkms so that the kernel driver will get rebuild when the kernel is updated

I get this error when I am trying to run command as described in the readme file for non-debian distros:

make -s all install

The output seems like this issue but i didn't find any answers.
Is it possible to install this driver on Fedora?
Thanks in advance.

This is made for linux correct?

Hi. I'm thinking about buying Orbweaver Chroma, is it possible that this driver would support it? Thanks!

Hello, I have linux mint 17.3 and I try to install the driver in my system. I have a few problems.

1- I don't have the .desktop app in my system. I have to go manualy to /usr/share/razer_chroma_controller to initiate the app.

2- The second thing when I use the app it says that.

I have razer mamba 2012.

Thanks for the help!

As featured in Synapse. Would be a nice little addition to the default effects. 😉

Is it possible to have effects to work with profiles ? I don't mean custom effect just the combination of the two. Let's take an example : We set a profile where all key are shade of blue and then we apply the reactive effect with a red color.

1. Is it possible through configuration ?
2. Could it be added to the library ? (I could help)
3. Impossible because of the firmware of some other reason ?

Thks a lot for those drivers (razer should thks you too because this is the reason I bought this keyboard)

I can't seem to get this to build on my machine (Ubuntu 15.04).

razer_bcd fails to build because it can't link against atan2. It's weird, because everything seems to be linking with -lm, so I'm kind of stumped.

:: COMPILING razer_bcd [SHARED]
================================
gcc razer_daemon.c  `pkg-config --cflags dbus-1` -DUSE_DBUS -Wl,-E -Wall -Wextra -W -w -Os -std=c99 -DMAJOR_VERSION=0 -DMINOR_VERSION=2 -fPIC -DPIC -DLINUX -D_XOPEN_SOURCE=700 -lm -ldl `pkg-config --libs dbus-1`  librazer_chroma.so -o razer_bcd 
librazer_chroma.so: undefined reference to `atan2'

Is there any chance I could get write permission to your repo? I managed to create a profile from your driver that I think people would like to use. It essentially is a non-collision detecting version of the old game "Snake".

Thanks by doing this. My BlackWidow is now working on Debian.
I managed to install on Debian 8.3 installing these dependencies:

$ apt-get install python3-dbus python3-dbus.mainloop.qt
$ apt-get install gir1.2-webkit-3.0

Profile Edition does not have ISO profiles.
Thus It is not possible do edit RGB profiles for some keys.

The following error happens on fresh install of deb based distros:
ValueError: Namespace WebKit not available
This is due to a dependancie not beeing told to the deb package, beeing the gtk+3 package for ubuntu(guess that's the same for debian)

How to set up a default effect for after login?

Issued #26 has been closed without any solution or suggestion to identify the cause of the problem.

The problem is still there:

ls: cannot access /sys/bus/hid/drivers/razerkbd: No such file or directory

That means that it is not possible to control the lights or activate the M keys.

You did a really god job. This is so nice, where can I donate?
I'm also thinking of writing a small program when I find a bit time (will not be a real GUI, but a small program in the command line which asks you question and so on, will be as simple as possible) where you can save static colors for each key or several keys (you can select a color, press keys which should have this color and then save or even select predefined key groups like num block or letters). I eventually add other effects like another color while clicking, transitions and fading etc.

By the way, is there a keycode for the razer symbol on the bottom?

Okay! I replied to the other issue just to get your attention. I've now got the driver installed on my machine thanks to the new debian install script. I have working lights and my keyboard is currently on a red fade. I went through your dota layout tutorial and compiled it. It works, but only for a second. (it flashes that layout for like one moment, but stays red fade). How do I get it to "stick" with that layout instead of the red one? So far I've tried adding an infinite while loop, but that just made it flash the red layout a bunch. I assume there's a way to push the layout you want to use to the razer_bcd executable, but I'm not sure how? I know you're busy, and I really appreciate all the work you've done on this so far, it really is fantastic. Any help would be much appreciated!

shibumi-xx

At my dev team, we have a Razer Blackwidow Chroma, Razer Firefly, and a Razer Mamba.
It seems as though we can't configure a keyboard if you have the pad and mouse plugged in at the same time.

I was wondering if it made sense to support the normal blackwidow and other non backlit versions of razer keyboards. The point of this would be to have macro recordings and profiles. I have a razer blackwidow on fedora 23 and can help test out.

just to let you know why im not working on this right now. I will continue work in january, atm i just dont have time for it. sorry.
i will try to merge new pull requests though.
best wishes and and a happy holiday + new year

Running Ubuntu MATE 15.10 (amd64) here, I've noticed that make -s all will fail to compile when the path to my working directory contains spaces.

This is the last few lines leading up to the error:

:: COMPILING snake game
======================
 
 :: COMPILING dynamic
======================

:: COMPILING razer kernel modules
========================================
Makefile:9: recipe for target 'razer_drv' failed
make: *** [razer_drv] Error 2

The directory is /media/Data/Programming/Open Source/BlackWidow Chroma Driver/razer_blackwidow_chroma_driver - Note spaces in the path.

If I compile from /tmp/razer_blackwidow_chroma_driver, no errors occur.

Is it possible to combine effect modes from the scripts in the drivers directory?

For instance I would like to have set_spectrum.sh run, and then run set_reactive.sh 255 0 0 to make the key I typed highlight red but still have the spectrum effect going.

Looking at the templates on the chroma site it appears possible, but I am not sure how its done.

I executed activate_driver.sh and got following Error:

./activate_driver.sh

make -C /lib/modules/3.18.6-1-ARCH/build SUBDIRS=/home/localuser/git/razer_blackwidow_chroma_driver/driver all
make[1]: Entering directory '/usr/lib/modules/3.18.6-1-ARCH/build'
scripts/Makefile.build:44: arch/x86/boot/Makefile: No such file or directory
make[2]: *** No rule to make target 'arch/x86/boot/Makefile'. Stop.
arch/x86/Makefile:230: recipe for target 'bzImage' failed
make[1]: *** [bzImage] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.18.6-1-ARCH/build'
Makefile:5: recipe for target 'all' failed
make: *** [all] Error 2
insmod: ERROR: could not load module driver/razerkbd.ko: No such file or directory

@pez2001 Can I get permissions to close issues? Would be rather useful.
Also having the capability to submit issues other than bugs or beign able to assign people to issues etc... would be really helpful.

I was very excited to get this working, but to my (non)surprise several modes did not work while others worked perfectly.

Modes that worked

• Mode_game
• Mode_none
• Mode_spectrum
• Mode_wave

Modes that did not work

• Mode_breath
• Mode_custom (just went blank, not sure if theres something else i had to do)
• Mode_reactive
• Mode_static

The modes that did not work seem to all be ones that might require some kind of extra configuration, is it possible that I just missed something in my reading? How could I test if these really do not work or if I'm just not getting something?

OS: Xubuntu 3.19.0-33-generic
Keyboard: Razer Blackwidow Chroma Tournament Edition

Also interesting was that device_type was missing.

sudo make -s all install return with Makefile:7: recipe for target 'razer_kdb' failed, any idea what is going wrong?