CKB - New Device Support #2
Labels
Comments
|
Corsair MM800 RGB Polaris... which device details are needed? |
|
Device IDs are a good place to start. Relevant output from lsub, any relevant kernel messages. That kind of thing, and a willingness to test hardware that I don't have! |
|
I suggest we write a (platform-independent) script, that outputs the necessary information, that we need to update the device-driver (as long as it has the current structure). This should enable users without technical background to help us find the correct information. |
|
I'm available to test the hardware, but probably only on weekends. Here's my output of |
|
I've modified the script slightly to give more detailed info under USB devices on Linux. @dan-santana Yours is an interesting case, as it isn't really a keyboard, nor a mouse. From what I can see so far, it is a mousepad with LEDs on it. If not, we'll have to figure out how CUE talks to it. Also, quick suggestion after looking at your dmesg, you should probably add the appropriate USB quirk for your mouse. |
|
Indeed, adding the quirks for the mouse (and keyboard too) reduced the boot time a lot! Thank you :) Yeah, it's a RGB mousepad, but with an USB passthrough port too (like K70 Lux). I tried the dev id in all device classes, The new script gave me some errors (running with Here's the output (uncompressed): |
|
K65 Non-RGB |
|
@mmolad Please download ckb-next from https://github.com/mattanger/ckb-next/archive/master.zip and run "ckb-dev-detect" |
|
@tatokis updated comment with log. |
|
Vengeance® K65 Compact Mechanical Gaming Keyboard
|
|
@tatokis as a short term solution, couldn't the K65 Non-RGB just be treated as a K70 Non-RGB? Would this be a quick fix? |
|
Apologies, got distracted by other issues.
I can add it later when I get home as its own device, but keep in mind there might be issues with Sierra.
|
|
No problem - thanks for taking a look! I just switched over to macOS professionally so finding out my favorite keyboard is incompatible is a real bummer.
|
|
Is there a plan to support K70 RGB Rapidfire? |
|
@mmolad @cmawhinney on the testing branch, 86118b3 @dtrang it's already supported. |
|
Whats the best way to update to the testing branch?
…On Tue, Jan 17, 2017 at 7:32 AM, Tasos Sahanidis ***@***.***> wrote:
@mmolad <https://github.com/mmolad> @cmawhinney
<https://github.com/cmawhinney> on the testing branch, 86118b3
<86118b3>
@dtrang <https://github.com/dtrang> it's already supported.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH74PmGAOlai2K-epwg8pVa6SAcIUCToks5rTMLRgaJpZM4K3im1>
.
|
|
I updated via rebuilding from source and still get "no devices connected"
after rebooting. The keyboard still only functions in BIOS mode, with the
other settings giving partial support (most keys don't work, like
backspace).
Shall we move this to a different issue?
…On Tue, Jan 17, 2017 at 7:47 AM, Tasos Sahanidis ***@***.***> wrote:
@mmolad <https://github.com/mmolad>
https://github.com/mattanger/ckb-next/archive/testing.zip
https://github.com/mattanger/ckb-next#building-from-source
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH74Pm-61C66yRlP5bq6U-CZPKkDuJF-ks5rTMZhgaJpZM4K3im1>
.
|
|
Interesting, it should at least recognise it.
Please open a new issue in order to better keep track of that and I'll give you something to test in a couple of hours.
|
|
Hello, I would like to have support for the VOID USB Headset. Feel free to ask me for testing. |
ghost
mentioned this issue
|
Corsair Harpoon Gaming Mouse: (Uncompressed) ckb-dev-detect - Fri Jan 27 12:17:42 AWST 2017 Kernel: Darwin 181095-SCT11938.local 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64 OS Version: USB Devices: |
|
@Camoleopard Could you please try 84e195c (testing branch) ? |
|
@tatokis Is it possible I can get a compiled version? I don't have QT and it's too big to install. |
|
@tatokis I tested this branch and it did not detect the device at all. EDIT: I restarted my laptop with my mouse connected, and CBK detected the mouse as a different mouse (I understand that) but I couldnt move my mouse, clicking worked but not movement, then I opened System Preferences, went to the mouse settings, unplugged the mouse and plugged it back in and my mouse worked again, but CBK couldn't detect it anymore. |
|
@Camoleopard please open a new issue and I'll see what can be done. |
|
Hi all, last week I purchased the K95 Platinum with brown switches. It works a treat on windows, very happy with the keyboard. However it comes as no real surprise that it doesn't get detected by ckb-next. I'm interested in looking into it in some spare time. The lsusb -v output: The ckb-dev-detect script is not much of a help for this keyboard, as it won't detect the keyboard both as regular or super user. I'm happy to help with the development for this new device, really like the work that has been done so far! |
|
@dodedodo33 I don't see why the dev detect script wouldn't detect it. It just runs lsusb and filters out only devices with the corsair vendor id. I've added your device ID in the testing branch, please test if it works, and if it doesn't, open a new issue with more details. |
|
@tatokis Thanks for the quick reply, I probably have something misconfigured with permissions or groups or something. I have tried the testing branch and opened a new issue with my findings. |
ghost
mentioned this issue
This was referenced Mar 16, 2017
ghost
mentioned this issue
ghost
mentioned this issue
ghost
pushed a commit
that referenced
this issue
May 5, 2017
This reverts commit 84e195c. Harpoon is not working when treated as Sabre, therefore removed until a proper support is added. See also: #54, #2 (comment)
|
Hello! Just got the corsair glaive rgb mouse. The following is the report from the ckb-dev-detect: ckb-dev-detect - Wed Jun 7 09:47:05 PDT 2017
Kernel: Linux lappy-tappy 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
OS Version:
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
USB Devices:
Couldn't open device, some information will be missing
Bus 001 Device 004: ID 1b1c:1b34 Corsair
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1b1c Corsair
idProduct 0x1b34
bcdDevice 1.03
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 84
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 300mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 58
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 8
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 172
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 25
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Dmesg:
[18254.088871] usb 1-1: New USB device found, idVendor=1b1c, idProduct=1b34
[18254.088882] usb 1-1: Product: Corsair Gaming GLAIVE RGB Mouse
[18254.088886] usb 1-1: Manufacturer: Corsair
[18254.133783] input: Corsair Corsair Gaming GLAIVE RGB Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:1B1C:1B34.0004/input/input18
[18254.190929] hid-generic 0003:1B1C:1B34.0004: input,hidraw2: USB HID v1.11 Mouse [Corsair Corsair Gaming GLAIVE RGB Mouse] on usb-0000:00:14.0-1/input0
[18254.191185] hid-generic 0003:1B1C:1B34.0005: item 0 1 0 8 parsing failed
[18254.191205] hid-generic: probe of 0003:1B1C:1B34.0005 failed with error -22 |
|
Is there a plan to support Glauber RGB? |
|
Corsair MM800 RGB Polaris (RGB Game Pad).. Arch Linux. The default demo rainbow mode on the Polaris is driving me crazy. Be glad to help test support for this. BTW - I also have a CORSAIR - Strafe RGB MX Silent Gaming Keyboard, ckb-next worked nearly flawless, updated firmware, programmed key colors, saved to hardware. Wasn't able to set color of the upper right lock key, everything else perfect. |
|
After glancing at the Corsair website: Media keys and g-keys seem to borrow off the K95 Platinum after initial inspection so coding wise is a copy and paste. Is this the only keyboard that does this kind of zoning? @frickler24 @light2yellow |
|
@SethBarberee Thanks for trying to add support for the K55. :) |
|
Hi! Yesterday, I purchased an M65 Pro RGB mouse from Best Buy and downloaded CKB after seeing the CUE files open not in a program, but in a folder full of readme's and .exe's. Seeing as I have an iMac, I didn't see it fit to try and open those files as I have done this before and gotten many lines of code in a text document. After downloading CKB (using my new mouse to navigate around Google and GitHub), I opened the program and immediately noticed at the top of the page that my mouse was not being detected. I have a really ugly RGB default setup right now and I would love, love, love to change it, but the program doesn't seem to detect my mouse even after countless plugins. I checked the download page to see if my mouse is supported and, surprisingly, it is! However, it's been 1 night and my mouse is still not being seen by the program. Should I just keep the colors the way they are and just use the otherwise fully functional mouse? |
|
Hi! Just got the corsair K70 Rapidfire non-rgb. The following is the report from the ckb-dev-detect: Kernel: Darwin Bengisus-MacBook-Pro.local 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64 OS Version: USB Devices: |
|
Third-ing a request for support for the MM800 mouse pad. |
|
Hi, I've a Corsair Gaming MM800 RGB POLARIS. Here is the related Do you need more information? |
|
I have a MM800 RGB Polaris mousepad as well, along with a K95 RGB Platinum. The Platinum is very well supported, but the MM800 doesn't list as a tab and constantly changes colors at the moment. Here is my skb-dev-detect report. Also, I will try and support this project with the limited hardware but more sophisticated gui programming skills I have, if needed. |
|
Please join us in IRC so we can help you better. It's hard to communicate for this kind of thing on GitHub. |
|
Did we ever get the MM800 Polaris? It's the only device in my corsair lineup that isn't recognized by ckb-next. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
If a Corsair device isn't supported, leave a comment with the device details, and it may get added eventually. Good places to start with are the outputs of lsub, dmesg, etc for the Corsair device.
The text was updated successfully, but these errors were encountered: