debianmainused
-
Posts
43 -
Joined
Content Type
Forums
Gallery
Release Notes
Corsair Blog
Store
Profiles
Posts posted by debianmainused
-
-
No problem--still sorting out what goes where....
Just tried to upload the software sniffer run to GIThub & nothing I renamed the file to would upload (shrug), so duplicating the entry here.
First software sniffer run.
In order:
Creat new profile2
Set M1 color
Set M2 Color
Set M3 color
Upload to keyboard
Assign G1 through G6 keys in M3
Upload to keyboard
Change back profile to profile1
close software
-
Please answer the question about the kernel driver, on the kernel driver thread.
The LED/macro configuration is best done with ckb (or in another user space program). But remapping buttons is easier in the kernel driver.
I will watch the github issue so I will find the informations, there is no need to bother MSC with my kernel driver issues. So, post the captures on MSC's ckb github and post anything concerning the kernel driver on the other thread or the driver github.
No problem--still sorting out what goes where....
-
OK-installed the K90 driver & am using it now...seems to be normal so far.
lsusb reports: Bus 003 Device 008: ID 1b1c:1b0e Corsair
for f in /sys/bus/hid/devices/0003\:1B1C\:*/report_descriptor; do echo $f; xxd -g 1 "$f"; done
/sys/bus/hid/devices/0003:1B1C:1B0E.001B/report_descriptor
00000000: 05 01 09 06 a1 01 05 07 19 e0 29 e7 15 00 25 01 ..........)...%.
00000010: 75 01 95 08 81 02 75 08 95 01 81 01 05 07 19 00 u.....u.........
00000020: 2a ff 00 15 00 26 ff 00 75 08 95 06 81 00 05 08 *....&..u.......
00000030: 19 01 29 03 25 01 75 01 95 03 91 02 95 05 91 01 ..).%.u.........
00000040: c0 .
/sys/bus/hid/devices/0003:1B1C:1B0E.001C/report_descriptor
00000000: 05 0c 09 01 a1 01 05 0c 19 00 2a ff 0f 15 00 26 ..........*....&
00000010: ff 0f 75 10 95 02 81 00 c0 ..u......
/sys/bus/hid/devices/0003:1B1C:1B0E.001D/report_descriptor
00000000: 05 01 09 06 a1 01 05 07 19 e0 29 e7 15 00 25 01 ..........)...%.
00000010: 75 01 95 08 81 02 19 00 29 6f 15 00 25 01 75 01 u.......)o..%.u.
00000020: 95 70 81 02 c0
Opened a GIT ticket & will fire up the XP machine to run the captures with better information today.
Edit: First "interesting" key usage--Macro1 (M1) key will take me back to first page of thread & change the backlight color at the same time.....M2 & M3 work as per normal--color change only.
Looked at the information for usbmon--looks like Wireshark needs usbmon 1.0 or newer--my system (Debian) is using .8--alternatives or do I need to build the newer version for that capture?
-
You need to make captures while changing settings with Corsair software. Keep your captures short and simple, note everything you did while capturing.
There are few vendor specific control transfer in "corsairk40.txt" and "corasirk40-2.txt", the same ones. Two of them may be the same as for the K90: setting playback to software mode (bRequest=2), and backlight brightness to 0 (bRequest=49). Does that make sense?
Hey everyone, sorry I haven't had time for this project in the past week...life's been busy, haven't gotten many chances to work on it. Anyway, I've started up work again, planning to have v0.2.2 released soon with a few new settings and some bug fixes. {snip} Check your keyboard layout on the settings screen.Hard to tell what's going on but the protocol looks completely different from the keyboards I've encountered so far. I can try to add support anyway but it could be very difficult.
As clement said, please provide captures for simple actions (i.e. turning on CUE after the keyboard is plugged in, changing the color of one key at a time, etc) with detailed descriptions of what you did. Also, if you could open an issue ticket on the GitHub page, that would probably be a lot easier than trying to go through everything here on the forums.
Sounds good---I've made the change in the driver file & will read the post about installing/testing it. Will open a ticket on GIT about the K40 & rerun the sniffer run with the tests you want--had a small problem with the Corsair software & the sniffer--needed to reinstall the Corsair software after I ran the 3rd sniffer run--Buggy software from Corsair? :)
-
OK--I've ran USBPcap & got a traffic run--Don't know how long a run you need--According to USBPcap site--find the device to sniff--start capture & unplug/plug-in device to get descriptors....Done that. If you need something more--just tell me what you need. File is corsairk40--added .txt after so the forums would upload it.
Edit: added 2 more files--opened them with wireshark & didn't see anything different that the first one, but thought I'd add them anyway.....
-
The descriptors look like those from the non-RGB keyboards, and I was misled by the lack of RGB in the name.
From the descriptors, I think it may be harder than just add an ID in ckb to make it work. But since you have access to a Windows machine you could try to sniff the USB traffic with USBPcap.
OK--I've ran USBPcap & got a traffic run--Don't know how long a run you need--According to USBPcap site--find the device to sniff--start capture & unplug/plug-in device to get descriptors....Done that. If you need something more--just tell me what you need. File is corsairk40--added .txt after so the forums would upload it.
-
The descriptors look like those from the non-RGB keyboards, and I was misled by the lack of RGB in the name.
From the descriptors, I think it may be harder than just had an ID in ckb to make it work. But since you have access to a Windows machine you could try to sniff the USB traffic with USBPcap.
Thank you for the reply & I'll check & post the results back this weekend.
-
I don't think the K40 is a RGB keyboard. You cannot change the color of the LEDs (except with a soldering iron and new LEDs ;)).
Well, the box states that it has RGB "16.8 million color backlighting" with three levels of illumination & can do "per key colors" http://www.corsair.com/en-us/raptor-k40-gaming-keyboard
Not up to the $150 or so that the better keyboards are, but not a bad keyboard.....
Would just like to be able to use more of what it's got available.
-
Quick Question---I know that I don't have a K65 or up keyboard--Have just bought a K40 & was wondering if anyone has any pointers/ideas to just change the color (want to go from the default red to a dark blue)----running Debian Sid & am able to do debugging work--just need ideas where to start........I've got a good basic keyboard without any options.
(edit) This is for a K40 Keyboard:
dean@linux:~$ for f in /sys/bus/hid/devices/0003\:1B1C\:*/report_descriptor; do echo $f; xxd -g 1 "$f"; done
/sys/bus/hid/devices/0003:1B1C:1B0E.0001/report_descriptor
00000000: 05 01 09 06 a1 01 05 07 19 e0 29 e7 15 00 25 01 ..........)...%.
00000010: 75 01 95 08 81 02 75 08 95 01 81 01 05 07 19 00 u.....u.........
00000020: 2a ff 00 15 00 26 ff 00 75 08 95 06 81 00 05 08 *....&..u.......
00000030: 19 01 29 03 25 01 75 01 95 03 91 02 95 05 91 01 ..).%.u.........
00000040: c0 .
/sys/bus/hid/devices/0003:1B1C:1B0E.0002/report_descriptor
00000000: 05 0c 09 01 a1 01 05 0c 19 00 2a ff 0f 15 00 26 ..........*....&
00000010: ff 0f 75 10 95 02 81 00 c0 ..u......
/sys/bus/hid/devices/0003:1B1C:1B0E.0003/report_descriptor
00000000: 05 01 09 06 a1 01 05 07 19 e0 29 e7 15 00 25 01 ..........)...%.
00000010: 75 01 95 08 81 02 19 00 29 6f 15 00 25 01 75 01 u.......)o..%.u.
00000020: 95 70 81 02 c0
Edit #2:
OK, I fired up a old XP machine & installed the software & firmware updates--Got the blue I wanted & saved it to my profile---pain in the "you know where" But it worked...Really ready to assist in making the K40 added to this software......
(Unofficial) Linux / OSX Driver
in Keyboards and Mice
Posted
Here are the profile captures:
P1 with G1/W G2/A G3/S G4/D G5/O G5/M then the same
for P2 & P3
p1.txt
p2.txt
p3.txt