New device ID for K70 Lux 0x1b36 #529
Comments
|
OK, well then, I see when searching a little more that indeed 0x1b36 has been discussed. I'll try the workaround. |
|
Doing the following change in usb.h didn't help: #define P_K70_RFIRE 0x1b36 It was basically the same thing I had tried already. |
|
Another note. The Windows key doesn't work at all. |
|
Of course, usbhid.quirks doesn't work with this device ID, because there is no support for it in the kernel. I tried adding to the kernel source and rebuilt the kernel: drivers/hid/hid-ids.h: drivers/hid/usbhid/hid-quirks.c: But I didn't notice any difference with: Edit. I made some mistake here. Have to try to compile modules again. Edit 2. Compiled a new kernel with these changes, but it seems that these changes are not enough. There are some other weird issues with this keyboard. |
|
Added initial support for this keyboard #530 |
|
Updated keyboard firmware to 2.0.4 when I finally got a Windows PC connected to it. Now most things seem to work and the driver also works mostly (with my patched newdev branch). Scan mode can now be used. The right Windows key still doesn't work at all and its toggle button doesn't do anything. The ckb settings program freezes when clicking on certain things, e.g. key colors. I guess the keyboard is identified as an RGB keyboard, even though it is single color. |
|
Does your patch function with or without the kernel patch you posted here? |
|
Works fine without the kernel patch. That was just me messing around when the keyboard didn't work. Most of the problems were due to the 1.x firmware. The 2.0.4 firmware is really required. |
|
The patch just does the same thing the quirks do.
The point of usbhid.quirks is so that you can tell the kernel what
quirks to apply to what device without having to patch and recompile it.
|
|
Alright. I just bought the red variant of that and it has the same ID, it
works, sort of, with the default driver (ckb doesn't recognize it), but I'm
going to update the firmware and try it with yours.
…On Dec 1, 2016 5:37 PM, "Johan Heikkilä" ***@***.***> wrote:
Works fine without the kernel patch. That was just me messing around when
the keyboard didn't work. Most of the problems were due to the 1.x
firmware. The 2.0.4 firmware is really required.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#529 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AOQ2a8FwQc-Ttra5WERrY3fJT1_dXZmUks5rD0wZgaJpZM4K84bT>
.
|
|
Not exactly relevant for this issue, but I've created rpm packages of ckb for Fedora and Epel at https://copr.fedorainfracloud.org/coprs/johanh/ckb/ |
|
The keyboard works perfectly after the firmware update and with the patched
driver.
…On Dec 2, 2016 11:10 AM, "Johan Heikkilä" ***@***.***> wrote:
Not exactly relevant for this issue, but I've created rpm packages for
Fedora and Epel of ckb at https://copr.fedorainfracloud.
org/coprs/johanh/ckb/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#529 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AOQ2a3niolPnXndjvRwqZsWr7GDXlVQ8ks5rEEMRgaJpZM4K84bT>
.
|
A new K70 LUX blue (not RGB) has device id 0x1b36. By default, ckb (compiled from the newdev branch) wasn't able to detect the keyboard. When changing (or adding) the ID to 0x1b36 in the correct places, ckb-daemon was able to identify the device and when manually starting the daemon, also the ckb GUI utility worked. Also the multimedia keys work at this point. The big issue is however that when booting, at the point where ckb-daemon is loading, the keyboard always stops working. The only way to get the daemon to work is to (including resetting the keyboard and booting from a powered off PC) boot in BIOS mode, login and then manually start the daemon. Correction! I have to unplug it, switch to scan mode, then plug it. If I leave it in BIOS mode, it will be recognized by the daemon, but it won't work.
Some info:
Operating system:
Fedora 24
Kernel 4.8.8
lsusb|grep Corsair
Bus 003 Device 005: ID 1b1c:1b36 Corsair
relevant info from dmesg:
[ 1.493216] usb 3-6: new full-speed USB device number 3 using xhci_hcd
[ 7.149040] usb 3-6: unable to read config index 0 descriptor/all
[ 7.149100] usb 3-6: can't read configurations, error -110
[ 7.304934] usb 3-6: new full-speed USB device number 5 using xhci_hcd
[ 7.474800] usb 3-6: New USB device found, idVendor=1b1c, idProduct=1b36
[ 7.474805] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.474807] usb 3-6: Product: Corsair Gaming K70 LUX Keyboard
[ 7.474810] usb 3-6: Manufacturer: Corsair
[ 7.474812] usb 3-6: SerialNumber: 16030015AEB89C4755BB595DF5001940
[ 7.476806] input: Corsair Corsair Gaming K70 LUX Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/0003:1B1C:1B36.0001/input/input6
[ 7.477138] hid-generic 0003:1B1C:1B36.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair Gaming K70 LUX Keyboard ] on usb-0000:00:14.0-6/input0
Adding usbhid.quirks=0x1B1C:0x1B36:0x20000408 doesn't help, keyboard only seems to stop working after the kernel loads, can't even use it in single mode.
For now the keyboard can be used in BIOS mode only. Of course multimedia keys don't work.
Could it be a problem with the USB protocol, or could this be easily patched somehow? I'll still try to debug the bootup problem.
The text was updated successfully, but these errors were encountered: