search

pez2001 / razer_chroma_drivers

A collection of Linux drivers for Razer Chroma devices, it supports all lighting modes and includes a daemon for advanced effects + gui configuration app
GNU General Public License v2.0
231 stars 31 forks source link

Razer Tartarus Chroma Support #131

Closed nonverbally closed 8 years ago

nonverbally commented 8 years ago

Razer Tartarus Chroma support would be a great addition. ID 1532:0208

lsusb output: http://pastebin.com/eEieqsLQ

Razer product page: http://www.razerzone.com/gaming-keyboards-keypads/razer-tartarus-chroma

It features rgb lighting, a single color for the whole keypad and many programmable keys (similar to M keys on the black widow) that default to WASD configuration unless programmed. There is an existing project that has some support for the Tartarus in Linux: https://bitbucket.org/conzar/keyboarding-master

terricain commented 8 years ago

@nonverbally does it emit any keycodes when the keys are pressed?

If you don't know, run xev and hit some keys. If stuff appears then create me a mapping between each key/button and the keycode xev reports.

nonverbally commented 8 years ago

They do emit keycodes. Here are the mappings to the keys.

Key keycode 1 23 2 24 3 25 4 26 5 27 6 66 7 38 8 39 9 40 10 41 11 50 12 52 13 58 14 54 15 55 Mode Switch 64 Up (hat switch) 111 Down (hat switch) 116 Left (hat switch) 113 Right (hat switch) 114 Bottom Thumb Button (below hat switch) 65

terricain commented 8 years ago

Ok we'll need to do some reverse engineering to get things perfect as it presents itself as a keyboard but is inherently different than one. Look here, are you able to help reverse engineering the protocol?

nonverbally commented 8 years ago

Sure. I'll review the procedure and setup the VM/wireshark environment.

nonverbally commented 8 years ago

Here are three pcaps of the three different lighting modes, Static (Green), Breathing (Green, Red), and Spectrum Cycling (Green). I followed the procedure and alternated between none and each lighting mode. There is a separate pcap file for each lighting mode in archive. RazerTartarus-lighting-pcaps.tar.gz

terricain commented 8 years ago

Can I get screenshots of synapse too :wink:

terricain commented 8 years ago

pcaps are looking good. Me being lazy im going to make a script to extract the data I want and format it nicely ;)

Does it only do static, breathing and spectrum? Can it do custom colours assigned to different keys?

On the right on the image there is 3 LEDs yellow, green, blue. What do they do (im assuming profiles). And can they change colour too?

terricain commented 8 years ago

Ok I have a driver for you to test, familiarise youself with this page.

Checkout my fork and your after the RazerTartarusChroma_0x0208 branch, this should link directly.

  1. Make the driver with make driver_verbose
  2. Load the driver with sudo insmod ./driver/razerkbd.ko
  3. Goto the wiki page, start at the Binding Driver section here.
  4. Work your way down to the Using the driver section, and then paste the output of the ls -l when your inside the device driver thing. (Aka I want to see files like device_type, get_serial etc...)

Make sense?

nonverbally commented 8 years ago

I've attached screenshots of the synapse interface. There are only those three lighting choices. The lights on the side only display the current selected keymap. You can toggle through different maps and the light will indicate which (1 through 8) by lighting combinations of the three colors. You can see this in the screenshot. Otherwise, only one color of the keys themselves can by dynamically changed. I will test out your new driver and report back.

tartarus-customizetab-synapse

tartarus-synapse-lighting

tartarus-synapse-sideview

terricain commented 8 years ago

Have you had a chance to test the driver I made? (Re the comment above)

Denlior commented 8 years ago

I've tried to test the driver you made for Razer Tartarus Chroma. Unfortunately I failed - I can't bind it to the driver. (I still can bind it back to hid-generic)

bash: echo: write error: No such device

terricain commented 8 years ago

Did you get the one from the correct branch? As it "should" work. What did you run to bind it?

Denlior commented 8 years ago

Cloned and made the driver from your RazerTartarusChroma_0x0208 branch. I failed at # echo -n "0003:1532:0208.0018" > /sys/bus/hid/drivers/razerkbd/bind step. Since then I purged all versions of Chroma Linux Drivers I had on my drive to avoid confusion and redownloaded your branch again. This time all worked as supposed to. ls -l output I get:

total 0
-r--r--r-- 1 root root 4096 авг 19 01:32 country
-r--r--r-- 1 root root 4096 авг 19 01:32 device_type
lrwxrwxrwx 1 root root    0 авг 19 01:32 driver -> ../../../../../../../../bus/hid/drivers/razerkbd
-r--r--r-- 1 root root 4096 авг 19 01:32 get_firmware_version
-r--r--r-- 1 root root 4096 авг 19 01:32 get_serial
drwxr-xr-x 3 root root    0 авг 19 01:32 hidraw
drwxr-xr-x 3 root root    0 авг 19 01:32 input
-r--r--r-- 1 root root 4096 авг 19 01:32 modalias
--w--w---- 1 root root 4096 авг 19 01:32 mode_breath
--w--w---- 1 root root 4096 авг 19 01:32 mode_spectrum
--w--w---- 1 root root 4096 авг 19 01:32 mode_static
drwxr-xr-x 2 root root    0 авг 19 01:32 power
-r--r--r-- 1 root root 4096 авг 19 01:32 report_descriptor
--w--w---- 1 root root 4096 авг 19 01:32 reset
-rw-rw---- 1 root root 4096 авг 19 01:32 set_brightness
lrwxrwxrwx 1 root root    0 авг 19 01:32 subsystem -> ../../../../../../../../bus/hid
-rw-rw---- 1 root root 4096 авг 19 01:32 test
-rw-r--r-- 1 root root 4096 авг 19 01:32 uevent
terricain commented 8 years ago

Now thats what I want to see :). At work at the moment but ill send some commands to test when I get home

terricain commented 8 years ago

Do this as root

Ok from memory this should set it to red

echo -ne "\xFF\x00\x00" > mode_static

This to green

echo -ne "\x00\xFF\x00" > mode_static

This should enable spectrum mode

echo -n "1" > mode_spectrum

Breathing effect

echo -n "1" > mode_breath                              # Random Mode
echo -n -e "\xFF\x00\x00" > mode_breath                # Single mode (red)
echo -n -e "\xFF\x00\x00\x00\x00\xFF" > mode_breath    # Dual mode (red & blue)

Setting brightness to 50% (100% is 255)

echo -n "128" > set_brightness

Should be able to cat set_brightness to get current brightness

Also these should output stuff. (get_serial might take a few tries)

cat device_type
cat get_firmware_version
cat get_serial

If I remember correctly, theres more I can add to the driver I think but we'll wait till these work first.

terricain commented 8 years ago

Only just noticed your not the original person I was talking to. Shows how much attention I pay. Also dont worry once we get all the features were after, theres deb files on the horizon, (and arch ones too I believe) and probably RPM's after that.

GabMus commented 8 years ago

Actually Arch ones are already available. The beauty of Arch is that you can just make a packaging script (PKGBUILD) and that's all a user needs. No need to distribute binaries :)

On Fri, Aug 19, 2016, 9:21 PM Terry Cain notifications@github.com wrote:

Only just noticed your not the original person I was talking to. Shows how much attention I pay. Also dont worry once we get all the features were after, theres deb files on the horizon, (and arch ones too I believe) and probably RPM's after that.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/131#issuecomment-241111279, or mute the thread https://github.com/notifications/unsubscribe-auth/ABS6v7Zc0f6oAmQVDmK9GwhCEtkfVQmDks5qhgIxgaJpZM4In7Oi .

Denlior commented 8 years ago

Yep, I figured colour mode and brightness from driver wiki and /sys/bus/hid/drivers/razerkbd/ contents already. Everything present works fine (commands you posted other RGB colors) cat device_type gets Razer Tartarus Chroma cat get_firmware_version gets v1.0 cat get_serial gets PM1609151701453 More functionality would be great, I'm ready to test or help any other way I can. Personally I would like to be able to have keys producing other keycodes, not overlapping with normal keyboard.

terricain commented 8 years ago

@Denlior Yeah about the keys producing keycodes, in the new daemon I have an ingenious solution for that :) :) :). But first ill go back through the packet captures and decode some other stuff (all my work for this device is backed up to my old pc and cba to turn it on to get it :wink:). What functionality is missing in your eyes, (more the h/w functionality not software bits).

Denlior commented 8 years ago

Well, all keys are producing keycodes and backlight works ok. Backlight keeps it's pattern, brightness and colour on reboot, so writing to internal device memory is good too. As far as I know, only hardware bit "not working" is three led indicator. All else is software functionality.

terricain commented 8 years ago

I thought as much.

Ok Have pushed a new driver to the RazerTartarusChroma_0x0208 branch. It "should" contain some new endpoints called something like profile_led_red, profile_led_green and profile_led_blue

You should be able to write from them with

echo -n "1" > profile_led_red
echo -n "1" > profile_led_green
echo -n "0" > profile_led_red

And read if they are set by cating them.

terricain commented 8 years ago

Once that works, ill merge it with the main code and have a wonderful conflict with the driver as I have a feeling its changed a fair bit since I started this driver. Then well I guess you can test out the new daemon :smile:.

Denlior commented 8 years ago

Well, it works, but with some "issues". Distal led answers to profile_led_blue and is greenish yellow in colour actually. Middle one answers to profile_led_red and is green. Proximal one is profile_led_green and it's indigo blue. cat reads their state fine.

terricain commented 8 years ago

Ok, yeah I know red is really a yellow colour, just named it so it can be red,green,blue (as its named that in the spec I have).

Have pushed a new driver, can you confirm the files map to the correct LEDs this time.

Denlior commented 8 years ago

Yes, now blue is blue, green is green and red is yellow.

terricain commented 8 years ago

:smile: I deem this issue resolved :). Can now add that to the main codebase :). Keep an eye on my fork as soon we'll have a version 1 release. I'll need some help with you testing the dameon with the tartarus. If you want make an issue on my fork for daemon support for tartarus (and copy the contents of the 3rd post in this issue to the new issue :wink:).