razer_bcd service is not running in my system

[jsanzdev]

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!

[lah7]

1. I presume this is the Cinnamon desktop edition? The .desktop probably wants editing, I had to do the same for the MATE desktop.

(I think we ought to remove the "OnlyShowIn=Unity;MATE;" entry)

---

2. What do you see when you type:
   sudo service razer_bcd start

[jsanzdev]

Hello, yes I'm using the Cinnamon desktop edition.

sudo service razer_bcd start
razer_bcd start/post-stop, process 12904

[terricain]

Also the mamba isn't fully integrated into the daemon. You'll have to use the raw driver files for that

[incryptx]

Does someone have a fix for this?

I get the graphic shown above, with the D-Dbus with the razer_bcd error?

I also get the application icons and clicking on the razer taskbar icon does nothing.

I blew up my system following some instructions about root level permissions for D-Bus and how easy it is to muck it up, which I apparently did.

Also, when "making" this, I get some "system violation" about poorly written code?

What's that about?

A fix or solution, would be nice.

New to all of this.

Thanks

[terricain]

@incryptx

Also, when "making" this, I get some "system violation" about poorly written code?

Examples of this would help.

[incryptx]

It's some dialog presented by Ubuntu 14.04 in a GUI Window referencing
the package would not work, and giving me two buttons, "Continue Anyway"
or "Cancel". I think it may be from the repository?

On 02/24/2016 12:45 PM, Terry Cain wrote:

@incryptx https://github.com/incryptx

Also, when "making" this, I get some "system violation" about
poorly written code?

Examples of this would help.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[terricain]

I don't think anything in this repo would bring up such dialog. If you could get a screenshot that would help more.

[incryptx]

I'll try!

On 02/24/2016 02:23 PM, Terry Cain wrote:

I don't think anything in this repo would bring up such dialog. If you
could get a screenshot that would help more.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[incryptx]

Ok,

In following your instructions from the readme, there is a "typo" in the
line which changes directories, and ends in the word "drive".

This word should be "driver" and those who cut & paste the line will get
an error, path not found.

|git clone --depth=1
https://github.com/pez2001/razer_blackwidow_chroma_driver.git cd
razer_blackwidow_chroma_*drive"r"* |

Install the packages needed to build the software:

|sudo apt-get install -y dpkg-dev libdbus-1-dev jq libsdl2-dev
libsdl2-image-dev libfftw3-dev |

Build the software and driver:

|make |

Build the package:

|./package_for_ubuntu.sh OR ./package_for_debian.sh|

After I built the .deb file and installed it with ./ubuntu.sh, the
warning comes from the "Ubuntu System OS" warning of "bad code" which
can break the system, and warning not to install this. I ignored the
warning and installed anyway, and now on backups, I get warnings that
DBus could not be backed up.

I think the error might be associated or repo-ed by building the .deb
and installing with Ubuntu.sh on Ubuntu (which is based on debian)/

I wonder if I installed the .deb with the ./debian.sh if I would still
get the warning, or if it would allow it to work?

I will attempt to take a screenshot (but as I just came from Windows and
this stuff is new), I will need to figure out how first, and then remove
the package and attempt to reinstall it.

Thanks for the assist here.

On 02/24/2016 07:46 PM, IT Support wrote:

I'll try!

On 02/24/2016 02:23 PM, Terry Cain wrote:

I don't think anything in this repo would bring up such dialog. If
you could get a screenshot that would help more.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[terricain]

How did you install the deb?

[incryptx]

Through USC, by right clicking on the .deb

I was going to try both processes today, installing from the .deb and
installing pure debian and see if I could capture some screens?

Right now, I have a problem with the build tools on the same machine,
which this install (via DBus) blew the OS and had to be rebuilt. Now
rebuilt, I am reloading build tools and one is balking.

Depends: libsdl2-2.0-0 (= 2.0.2+dfsg1-3ubuntu1.1)

Something about wayland and mesa i386 binaries. Attempting to resolve
the issues now.

Although I run a AMD64, most of the tools and binaries for this and
steam, seem to require the i386 set to get anything done.

I was a SDET for MS on NT for ten years. Although coding is second
nature, it's been twenty years since I looked at Linux.

It's matured now. Back then it was childish and confusing.

I will take some screenshots and get back to you.

Thanks for the assist. I just don't understand why HW makers like
Logitech, Saitek, Razor, and others don't release Linux versions of
drivers just to keep there options open in the Linux community, should
the market place open, they would be set. It's also just a neighborly
thing to do.

On 02/25/2016 08:16 AM, Terry Cain wrote:

How did you install the deb?

—
Reply to this email directly or view it on GitHub
#77 (comment).

[terricain]

Not a clue, would be so much easier if razer provided a driver, and in future don't use software centre, its a pile of rubbish. Just sudo dpkg -i file.deb and then sudo apt-get install -f

[incryptx]

Attached is a screenshot recieved after attempting to install the .deb

It is a warning thrown by the Software Center.

On 02/25/2016 08:32 AM, IT Support wrote:

Through USC, by right clicking on the .deb

I was going to try both processes today, installing from the .deb and
installing pure debian and see if I could capture some screens?

Right now, I have a problem with the build tools on the same machine,
which this install (via DBus) blew the OS and had to be rebuilt. Now
rebuilt, I am reloading build tools and one is balking.

Depends: libsdl2-2.0-0 (= 2.0.2+dfsg1-3ubuntu1.1)

Something about wayland and mesa i386 binaries. Attempting to resolve
the issues now.

Although I run a AMD64, most of the tools and binaries for this and
steam, seem to require the i386 set to get anything done.

I was a SDET for MS on NT for ten years. Although coding is second
nature, it's been twenty years since I looked at Linux.

It's matured now. Back then it was childish and confusing.

I will take some screenshots and get back to you.

Thanks for the assist. I just don't understand why HW makers like
Logitech, Saitek, Razor, and others don't release Linux versions of
drivers just to keep there options open in the Linux community, should
the market place open, they would be set. It's also just a neighborly
thing to do.

On 02/25/2016 08:16 AM, Terry Cain wrote:

How did you install the deb?

—
Reply to this email directly or view it on GitHub
#77 (comment).

[incryptx]

Here are the details.

I did build and use the .deb on a user called /susan and saved the .deb

Then used it again on the same machine, but renamed the user /bill when
I installed the .deb

I see the permissions problem, and can rebuild the OS with that name to
test it again by rebuilding the .deb

BUT, this same error happened on that machine, with the proper user
name, and still gave the "bad code" pop-up.

Details:
http://pastebin.com/Q8snh3qL

in future use pastebin links

On 02/25/2016 09:49 AM, IT Support wrote:

Attached is a screenshot recieved after attempting to install the .deb

It is a warning thrown by the Software Center.

On 02/25/2016 08:32 AM, IT Support wrote:

Through USC, by right clicking on the .deb

I was going to try both processes today, installing from the .deb and
installing pure debian and see if I could capture some screens?

Right now, I have a problem with the build tools on the same machine,
which this install (via DBus) blew the OS and had to be rebuilt. Now
rebuilt, I am reloading build tools and one is balking.

Depends: libsdl2-2.0-0 (= 2.0.2+dfsg1-3ubuntu1.1)

Something about wayland and mesa i386 binaries. Attempting to resolve
the issues now.

Although I run a AMD64, most of the tools and binaries for this and
steam, seem to require the i386 set to get anything done.

I was a SDET for MS on NT for ten years. Although coding is second
nature, it's been twenty years since I looked at Linux.

It's matured now. Back then it was childish and confusing.

I will take some screenshots and get back to you.

Thanks for the assist. I just don't understand why HW makers like
Logitech, Saitek, Razor, and others don't release Linux versions of
drivers just to keep there options open in the Linux community,
should the market place open, they would be set. It's also just a
neighborly thing to do.

On 02/25/2016 08:16 AM, Terry Cain wrote:

How did you install the deb?

—
Reply to this email directly or view it on GitHub
#77 (comment).

[incryptx]

It's not my place to say, being the lesser knowledgeable one here, but
some "dialog" in the .deb file which warns the user, "Hey, Your not
Susan" or "Your not Root, either" or "Dummy, you can't copy the .deb to
another machine" would be useful in warning us less fortunate of the
errors of our ways.

Just a thought.

On 02/25/2016 08:45 AM, Terry Cain wrote:

Not a clue, would be so much easier if razer provided a driver, and in
future don't use software centre, its a pile of rubbish. Just |sudo
dpkg -i file.deb| and then |sudo apt-get install -f|

—
Reply to this email directly or view it on GitHub
#77 (comment).

[incryptx]

I'm sure I'm making mistakes you never thought a user would do, so I will try your suggestions, rebuild the .deb on the right machine, log in as root and use your non-SC commands and see where I am.

I will post those results when I have them.

Has anyone other than you been able to use this?

I ask, because sometimes devs have tools and dependancies for build processes they don't consider when the final product works in their build environment. As well, you only have us dumb end users for beta test, and the first OP has lost interest and moved on. Let's work it out so this works for everyone. My next project, after the mouse runs, is getting my Saitek X52Pro builds to work. They are just GUI front ends and don't mess with the HID layer.

[lah7]

Attached is a screenshot recieved after attempting to install the .deb

Please could you re-add the screenshot to your previous page? GitHub doesn't accept e-mail attachments, so we haven't seen the screenshot.

From the sounds of things, that's the Ubuntu Software Centre producing the message, possibly because of how its packaged - it's not a sophisticated Debian package after all.

E: razer-chroma-driver: wrong-file-owner-uid-or-gid

Just to clarify, is your project directory on a Unix filesystem? (Not one like NTFS, as it appears you have media mounted?). Only root (sudo for Debian/Ubuntu) is needed to install the package.

Has anyone other than you been able to use this?

Works perfectly fine in Ubuntu 15.10.

[incryptx]

If I may suggest:

These should be in the "readme" if this is the preferred method of
install for uneducated users.

You know the SC is crap, but the rest of us are stuck with it.

|sudo dpkg -i file.deb|
|sudo apt-get install -f

|
|
|

[incryptx]

Bad Code Message

On 02/25/2016 10:33 AM, Luke Horwell wrote:

Attached is a screenshot recieved after attempting to install the .deb
Please could you re-add the screenshot to your previous page?
GitHub doesn't accept e-mail attachments, so we haven't seen the
screenshot.

From the sounds of things, that's the Ubuntu Software Centre producing
the message, possibly because of how its packaged - it's not a
sophisticated Debian package after all.

E: razer-chroma-driver: wrong-file-owner-uid-or-gid
Just to clarify, is your project directory on a Unix filesystem?
(Not one like NTFS, as it appears you have media mounted?). Only
root (|sudo| for Debian/Ubuntu) is needed to install the package.

Has anyone other than you been able to use this?
Works perfectly fine in Ubuntu 15.10.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[incryptx]

The .deb file was on a USB stick, probably formatted FAT32 but not NTFS
and run from there.

I guess I was dumb again and should have moved it to a local drive
first. Opps. But that did not cause th bad code error, as when I first
built the .deb file, I was /susan and I was /root.

The GUID error is most likely the Razor Mamba not being connected at the
time the .deb was run and install took place. Just a guess on my part,
but again, when first attempted, the mouse was connected and nothing has
changed. I still get the GUI for the Razer Configuration with the DBus
error first reported by the OP.

Maybe some error checking in the scripts would help. i.e., is the mouse
present? Is the user root? Is the user actually the user?

(This has always, throughout the existence of Linux, been it's
deficiency. Granted, the scripts are very simple, but unintelligent and
uninformative as well)

On 02/25/2016 10:33 AM, Luke Horwell wrote:

Attached is a screenshot recieved after attempting to install the .deb
Please could you re-add the screenshot to your previous page?
GitHub doesn't accept e-mail attachments, so we haven't seen the
screenshot.

From the sounds of things, that's the Ubuntu Software Centre producing
the message, possibly because of how its packaged - it's not a
sophisticated Debian package after all.

E: razer-chroma-driver: wrong-file-owner-uid-or-gid
Just to clarify, is your project directory on a Unix filesystem?
(Not one like NTFS, as it appears you have media mounted?). Only
root (|sudo| for Debian/Ubuntu) is needed to install the package.

Has anyone other than you been able to use this?
Works perfectly fine in Ubuntu 15.10.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[terricain]

Yes lintian moans about the package, that is irrelevant (just a lot of spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at uni is finished but last time I checked the deb installed on both Ubuntu 14.04 and 15.04, using the dpkg and apt commands, software centre is too dumb to handle this and thankfully in 16.04 is being scrapped I believe (or 16.10 god knows)

[incryptx]

Ok. Ah, what is was to be a student.

On 02/25/2016 11:23 AM, Terry Cain wrote:

Yes lintian moans about the package, that is irrelevant (just a lot of
spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at
uni is finished but last time I checked the deb installed on both
Ubuntu 14.04 and 15.04, using the |dpkg| and |apt| commands, software
centre is too dumb to handle this.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[incryptx]

Terry

I have a clean install, no errors.

After looking at the graphic the OP posted, I think now the only ting
lacking or in error, is the "razer_bcd" service is not starting/started.

Because this is v14.04, as explained in the readme, I have an "upstart"
system as opposed to a "systemd" service system. The command "sudo
status razer_bcd" always says "razer_bcd stop/waiting" and does not
change even after rebooting.

I think the service is just stuck somehow. I read one article about the
service being "masked" somehow?

Any ideas on starting the service?

And if I get it to start, how can I insure it starts at bootup?

Thanks for the assist.

On 02/25/2016 11:23 AM, Terry Cain wrote:

Yes lintian moans about the package, that is irrelevant (just a lot of
spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at
uni is finished but last time I checked the deb installed on both
Ubuntu 14.04 and 15.04, using the |dpkg| and |apt| commands, software
centre is too dumb to handle this.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[incryptx]

Hello Terry

If I do "status razer_bcd" it returns: unknown job.

Upstart states this means the job or service has not been converted to
upstart. A converted service would typically output the current status,
i.e. Starting, Stopping, and a process ID. A non-converted service would
give an error about an unknown job.

Your readme states you included an "upstart" equivilent script or
converted service, but I don't think it is loading or active.

I think this is the reason the razer_bcd service will not start, which
leads to the dialog error when starting the Razer Chroma Application.

The init script is not running or starting. From here, I don't know what
to do or how to fix it.

Thanks for the assist.

On 02/25/2016 04:34 PM, IT Support wrote:

Terry

I have a clean install, no errors.

After looking at the graphic the OP posted, I think now the only ting
lacking or in error, is the "razer_bcd" service is not starting/started.

Because this is v14.04, as explained in the readme, I have an
"upstart" system as opposed to a "systemd" service system. The command
"sudo status razer_bcd" always says "razer_bcd stop/waiting" and does
not change even after rebooting.

I think the service is just stuck somehow. I read one article about
the service being "masked" somehow?

Any ideas on starting the service?

And if I get it to start, how can I insure it starts at bootup?

Thanks for the assist.

On 02/25/2016 11:23 AM, Terry Cain wrote:

Yes lintian moans about the package, that is irrelevant (just a lot
of spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at
uni is finished but last time I checked the deb installed on both
Ubuntu 14.04 and 15.04, using the |dpkg| and |apt| commands, software
centre is too dumb to handle this.

—
Reply to this email directly or view it on GitHub
#77 (comment).

[terricain]

@incryptx run status razer_bcd as root. Ubuntu's upstart gets very funny about who runs the status and service commands.

Could you put the /var/log/upstart/razer_bcd.log on pastebin. If its converted it to a .some_number.gz file then uncompress (or lesspipe) and put on pastebin.

[nekkz]

Same problem with Ubuntu 12.04 (elementary OS freya), using razer mamba tournament edition.

dmesg dump, after a sudo service razer_bcd start

[  585.228859] init: razer_bcd main process (4396) terminated with status 1
[  585.228873] init: razer_bcd main process ended, respawning
[  585.258179] init: razer_bcd main process (4425) terminated with status 1
[  585.258192] init: razer_bcd main process ended, respawning
[  585.278786] init: razer_bcd main process (4448) terminated with status 1
[  585.278798] init: razer_bcd main process ended, respawning
[  585.290727] init: razer_bcd main process (4471) terminated with status 1
[  585.290745] init: razer_bcd main process ended, respawning
[  585.301776] init: razer_bcd main process (4494) terminated with status 1
[  585.301784] init: razer_bcd main process ended, respawning
[  585.312930] init: razer_bcd main process (4517) terminated with status 1
[  585.312943] init: razer_bcd main process ended, respawning
[  585.325580] init: razer_bcd main process (4540) terminated with status 1
[  585.325589] init: razer_bcd main process ended, respawning
[  585.345174] init: razer_bcd main process (4563) terminated with status 1
[  585.345186] init: razer_bcd main process ended, respawning
[  585.358303] init: razer_bcd main process (4586) terminated with status 1
[  585.358317] init: razer_bcd main process ended, respawning
[  585.370537] init: razer_bcd main process (4609) terminated with status 1
[  585.370544] init: razer_bcd main process ended, respawning
[  585.381221] init: razer_bcd main process (4632) terminated with status 1
[  585.381228] init: razer_bcd respawning too fast, stopped

[terricain]

If I remember correctly the mamba may or may not be added to the daemon.

[terricain]

The mamba's been added to the daemon now. Anyone still having problems

[apol1]

I'm having trouble as well, I first installed the Chroma Linux Drivers from the website here:

https://pez2001.github.io/razer_chroma_drivers/

I followed the instructions for Ubuntu and Debian

Everything seemed to work as far as I can tell (new to Linux)

I then installed PolyChromatic from here:

https://github.com/lah7/polychromatic/releases/tag/v0.1.0

However in command line after entering ./install/install.sh I received this message:

The razer-chroma-drivers Python modules are missing!
Please install them from http://pez2001.github.io/razer_chroma_drivers/
It could be possible that they are in a different path to '/usr/lib/python3/dist-packages/razer/'

---

Continue anyway? [y]

I tried running the script as root by adding sudo, same message appeared

I still see the same error message as the screen shot above

Im running Linux Ubuntu 16.04 LTS

[GabMus]

This repo is legacy, please install the driver from terrycain's fork:
https://github.com/terrycain/razer_drivers

On Sun, Aug 14, 2016, 1:53 AM RetroEggy [email protected] wrote:

Hey guys,
I have the same issue with razer_bcd not starting. I'm using a Razer
Blackwidow X Chroma and compiled the corresponding branch, I also unbinded
the keyboard from hid generic and binded it to razer kbd. Starting
Polychromatic results in the same message as seen in the first post.
Starting razer_bcd always outputs start/post-stop and a stop/waiting
status. dmesg gives the same output as the previous users had : razer_bcd
respawning too fast, stopped. Help would be greatly appreciated:)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#77 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABS6v9OgJ0bNiyUKIY5ruQ8ZpEeoQitMks5qflj0gaJpZM4HOVlE
.

[GabMus]

As for the frontend I don't know the state of polychromatic, but my
frontend razerCommander works fine https://github.com/gabmus/razercommander

On Sun, Aug 14, 2016, 2:19 PM Gabriele Musco [email protected] wrote:

This repo is legacy, please install the driver from terrycain's fork:
https://github.com/terrycain/razer_drivers

On Sun, Aug 14, 2016, 1:53 AM RetroEggy [email protected] wrote:

Hey guys,
I have the same issue with razer_bcd not starting. I'm using a Razer
Blackwidow X Chroma and compiled the corresponding branch, I also unbinded
the keyboard from hid generic and binded it to razer kbd. Starting
Polychromatic results in the same message as seen in the first post.
Starting razer_bcd always outputs start/post-stop and a stop/waiting
status. dmesg gives the same output as the previous users had : razer_bcd
respawning too fast, stopped. Help would be greatly appreciated:)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#77 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABS6v9OgJ0bNiyUKIY5ruQ8ZpEeoQitMks5qflj0gaJpZM4HOVlE
.

[lah7]

Polychromatic still uses the original driver and daemon provided by this repository, not daemonv2 from the fork yet. Once the service works, Polychromatic will too.

To me, it looks like Razer BlackWidow X Chroma isn't supported yet.

[RetroEggy]

I tried using the razer_drivers you suggested, but I wasn't able to bind my Blackwidow X to razerkbd, that's why I switched to the Blackwidow X branch (https://github.com/terrycain/razer_drivers/tree/RazerBlackWidowXChroma_0x0216). Guess I'll have to wait until X support is integrated into the main branch then:/

[terricain]

Thats because people don't actually tell me when things work. I'll merge bwX into master in a bit

[RetroEggy]

That would be awesome! Let's hope it will work then - after all, only binding the keyboard worked, but not razer bcd. But I'd be happy to try it:D

[terricain]

@RetroEggy yeah the daemon would have to edited and I cba for that (hence I made a new one). Have you by any chance used any features of the driver so I know what works and what doesnt

[RetroEggy]

I binded the keyboard to razerkbd - that worked according to ls -l. I haven't tried anything else (well, except for trying to start razer_bcd) since my primary goal was simply to change the colours using Polychromatic.

[terricain]

If you can do it, go through this list and see what works "https://github.com/pez2001/razer_chroma_drivers/wiki/Using-the-keyboard-driver"

Skiping the mode_custom sections (as set_key_row will do that)

Also use the feature_pythonlib branch of my fork as that has some extra driver fixes

[RetroEggy]

Okay, so those are the results using the Blackwidow X branch (I've compiled the driver 3 times already this weekend, I'll get to trying the feature_pythonlib branch some time later)
cat device_type
Razer BlackWidow X Chroma
macro_keys: I'm getting no error messages, so I assume it's alright.
mode_breath: All 3 examples working!
No effect: Working!
Reactive mode: Working!
Spectrum: Working!
Pulsate: As expected, not working since it's not a Blackwidow Ultimate 2013.
Wave: Works in both directions:D
Reset: Not sure about it. The lighting effect stays the same, but I'm not getting an error message either.
Brightness: No change, but also no error.
Set logo: Not found (as expected).
set key row: Working.
Clear row: Working.
Get serial: Shows me an empty row.

I should have tried that before, that's pretty impressive to me. I can write my custom layout myself this way without the need of a frontend:D

[terricain]

Ok repeat that with the pythonlib driver at some point, as it might fix some things but looks good. Also look in dmesg for any lines containing razerkbd

:-)

[terricain]

Also what about mode_static

[RetroEggy]

Static doesn't work. dmesg outputs the following messages regarding razerkbd:
[21546.122641] Wrong Amount of RGB data provided: 1 of 67
[22387.211846] razerkbd: Unknown product ID '534'
[22402.888592] razerkbd: Unknown product ID '534'razerkbd: Unknown product ID '534'
[22447.499102] razerkbd: Unknown product ID '534'<1>[22724.597375] Wrong Amount of RGB data provided: 1 of 67
[22992.037788] razerkbd: Invalid Report Type. Start Marker: 01 id: ff Num Params: 16 Reserved: 00 Command: 82 Params: 000000000000 .
[24123.914257] razerkbd: Cannot set static mode for this device
Hope this helps:)

[terricain]

Yeah am afk atm. But should be able to fix that by end of Monday. In that case hold off trying the different driver

[terricain]

Try running get_serial a couple of times, see if it works. The unknown product id should go away with the driver in the pythonlib driver.

[RetroEggy]

Getting the serial worked the second time I tried. Interesting. I'll try the other driver after your update.

[terricain]

Is the keyboard wireless by any chance?

[RetroEggy]

No, it's wired. OS is Linux Mint 17.3, kernel 3.13.0-37-generic btw.

[terricain]

Most odd. My mamba sometimes gives me blank serial. Least it works mostly, I'll look into that at some point though it's not critical. Try the python lib copy of the driver as that should fix static and brightness

[terricain]

Also whats the output of ls -lah /dev/input/by-id

[RetroEggy]

Ok, so I installed feature_pythonlib.
cat device_type
Razer BlackWidow X Chroma
macro_keys: Again, no reaction.
mode_breath: Working.
Game mode: Working.
No effect: Working.
Reactive mode: Working.
Spectrum: Working.
Pulsate: Not found, as expected.
Static sadly still doesn't work, dmesg outputs

[ 947.459680] input: Razer Razer BlackWidow X Chroma as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/input/input16
[ 947.460002] razerkbd 0003:1532:0216.0003: input,hidraw2: USB HID v1.11 Mouse [Razer Razer BlackWidow X Chroma] on usb-0000:00:14.0-4/input2
[ 1376.471301] razerkbd: Cannot set static mode for this device

Wave: Working.
Reset: Doesn*t work.Dmesg:

[ 1649.296618] razerkbd: Unknown product ID '534'

Brightness: Doesn't work either, same as above (unknown product id)
Set logo: not found (as expected).
set key row: Working.
Clear row: Working.
Get serial: Worked at first try.

Output of ls -lah /dev/input/by-id:
ls -lah /dev/input/by-id
insgesamt 0
drwxr-xr-x 2 root root 180 Aug 16 17:22 .
drwxr-xr-x 4 root root 400 Aug 16 17:22 ..
lrwxrwxrwx 1 root root 9 Aug 16 17:06 usb-Razer_Razer_BlackWidow_X_Chroma-event-kbd -> ../event3
lrwxrwxrwx 1 root root 9 Aug 16 17:06 usb-Razer_Razer_BlackWidow_X_Chroma-if01-event-kbd -> ../event4
lrwxrwxrwx 1 root root 9 Aug 16 17:22 usb-Razer_Razer_BlackWidow_X_Chroma-if02-event-mouse -> ../event5
lrwxrwxrwx 1 root root 9 Aug 16 17:22 usb-Razer_Razer_BlackWidow_X_Chroma-if02-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Aug 16 17:06 usb-ROCCAT_ROCCAT_Kone_XTD_Optical-event-mouse -> ../event6
lrwxrwxrwx 1 root root 9 Aug 16 17:06 usb-ROCCAT_ROCCAT_Kone_XTD_Optical-if01-event-kbd -> ../event7
lrwxrwxrwx 1 root root 9 Aug 16 17:06 usb-ROCCAT_ROCCAT_Kone_XTD_Optical-mouse -> ../mouse1

(Yes, that's exactly the mouse I'm using)

Out of curiosity, I tried starting razer_bcd, but I always get

sudo service Razer_bcd start
Razer_bcd: unrecognized service

sudo service razer_bcd restart
razer_bcd: unrecognized service

sudo status razer_bcd
status: Unknown job: razer_bcd

Well, time to find out more about set_key_row:D

[terricain]

Ok razer_bcd is no more 😉
Serial will appear blank if the keyboard is busy, is just something to live with.
Mate thats just not acceptable. Get a mamba chroma 😉
reset is deprecated and will be removed soonish.

Ok, remove driver, get latest driver from feature_pythonlib and install.
Then get the output of modinfo razerkbd. Also try getting and setting brightness and setting static. Also print out the command your running to do those.

[RetroEggy]

Installed the latest version.
Modinfo tells me the following:
Mint-Desktop razerkbd # modinfo razerkbd
filename: /lib/modules/3.13.0-37-generic/kernel/drivers/usb/misc/razerkbd.ko
license: GPL v2
description: Razer Keyboard Device Driver
author: Terry Cain [email protected]
srcversion: 291CB53B6FEBECF7D45F9CF
alias: hid:b0003g_v00001532p00000209
alias: hid:b0003g_v00001532p00000216
alias: hid:b0003g_v00001532p00000203
alias: hid:b0003g_v00001532p00000205
alias: hid:b0003g_v00001532p00000214
alias: hid:b0003g_v00001532p0000011A
alias: hid:b0003g_v00001532p0000010D
alias: hid:b0003g_v00001532p0000011B
depends: hid
vermagic: 3.13.0-37-generic SMP mod_unload modversions

For static mode, I used the example provided in the instructions
Mint-Desktop razerkbd # echo -n -e "\xFF\x00\xFF" > mode_static
bash: mode_static: Datei oder Verzeichnis nicht gefunden
(That*s german for "file or directory not found")

I tried again with echo -n > mode_static and echo > mode_static (assuming that less instructions might help= but got the same result.

For brightness, I also used the example commands.
Mint-Desktop razerkbd # echo -n "0" > set_brightness
bash: set_brightness: Datei oder Verzeichnis nicht gefunden
Mint-Desktop razerkbd # echo -n "255" > set_brightness
bash: set_brightness: Datei oder Verzeichnis nicht gefunden

[terricain]

By the looks of it you didnt bind the device to the driver and/or change into the correct directory

[RetroEggy]

Brightness and static started working, despite not doing anything different. I'm confused now.

I always made sure that the binding worked by using ls -l

eggy@Mint-Desktop /sys/bus/hid/drivers/hid-generic $ sudo su
[sudo] password for eggy:
Mint-Desktop hid-generic # echo -n "0003:1532:0216.0003" > unbind
Mint-Desktop hid-generic # cd /sys/bus/hid/drivers/razerkbd
Mint-Desktop razerkbd # echo -n "0003:1532:0216.0003" > bind
Mint-Desktop razerkbd # ls -l
insgesamt 0
lrwxrwxrwx 1 root root 0 Aug 19 22:13 0003:1532:0216.0003 -> ../../../../devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.2/0003:1532:0216.0003
--w------- 1 root root 4096 Aug 19 22:13 bind
lrwxrwxrwx 1 root root 0 Aug 19 22:13 module -> ../../../../module/razerkbd
--w------- 1 root root 4096 Aug 19 22:13 new_id
--w------- 1 root root 4096 Aug 19 22:03 uevent
--w------- 1 root root 4096 Aug 19 22:13 unbind

Interestingly, the output of modinfo razerkbd did not change.
modinfo razerkbd
filename: /lib/modules/3.13.0-37-generic/kernel/drivers/usb/misc/razerkbd.ko
license: GPL v2
description: Razer Keyboard Device Driver
author: Terry Cain [email protected]
srcversion: 291CB53B6FEBECF7D45F9CF
alias: hid:b0003g_v00001532p00000209
alias: hid:b0003g_v00001532p00000216
alias: hid:b0003g_v00001532p00000203
alias: hid:b0003g_v00001532p00000205
alias: hid:b0003g_v00001532p00000214
alias: hid:b0003g_v00001532p0000011A
alias: hid:b0003g_v00001532p0000010D
alias: hid:b0003g_v00001532p0000011B
depends: hid
vermagic: 3.13.0-37-generic SMP mod_unload modversions

Well, it's working now, I'll just file this as an RTFM error;)

Thanks a lot for the support and the quick changes you made to the drivers, terrycain! It's pretty awesome what you've done so far:D

[terricain]

Lol np, my guess is that you replaced the driver but may not have unloaded it from the kernel. I've done that a fair few times. What distro you running? We have a new daemon on its way 😄

[RetroEggy]

I'm using Linux Mint 17.3. I unloaded the driver from the kernel using modprobe -r razerkbd and loaded it again using modprobe razerkbd, but the output of modinfo didn't change. Whatever, it's working, so I really can't complain:D

[terricain]

Yeah not a clue. But it's good that it's working 😄. The daemon's pretty much at v1.0, it should work fine with the chroma x. Soon well have a PPA ready so people can easily install it