Jump to content

SpeedFreak01

Members
  • Posts

    17
  • Joined

Reputation

10 Good
  1. Testing again, thanks for being patient :) (To note, i didn't unplug the keyboard before testing the latest revision, was running commit b37a519 at the time) This time i checked out the latest revision (63ab888), compiled the code, copied the daemon as root to /usr/local/bin. Ran the daemon as root, keyboard connected with no issues. ckb Corsair Keyboard RGB driver v0.0.6 Setting FPS to 60 Setting default layout: us Root controller ready at /dev/input/ckb0 Connecting Corsair K95 RGB Gaming Keyboard (S/N: 0701B03EAE3618E3530D5E92F5001946) Device ready at /dev/input/ckb1 ^C Caught signal 2 Disconnecting Corsair K95 RGB Gaming Keyboard (S/N: 0701B03EAE3618E3530D5E92F5001946) Removed device path /dev/input/ckb1 Removed device path /dev/input/ckb0 I then killed the daemon as you can see above, and unplugged the keyboard. Gave the keyboard about 30 seconds of being unplugged before re-connecting it. Ran the daemon again, and this time it failed to connect. Logs: ckb Corsair Keyboard RGB driver v0.0.6 Setting FPS to 60 Setting default layout: us Root controller ready at /dev/input/ckb0 Connecting Corsair K95 RGB Gaming Keyboard (S/N: 0701B03EAE3618E3530D5E92F5001946) Error: usbdequeue (firmware.c:24): Operation not permitted Error: usbdequeue (usb.c:71): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted ^C Caught signal 2 Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (main.c:25): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (main.c:31): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (usb.c:80): Operation not permitted Error: usbdequeue (main.c:41): Operation not permitted Disconnecting Corsair K95 RGB Gaming Keyboard (S/N: 0701B03EAE3618E3530D5E92F5001946) Error: usbdequeue (usb.c:80): Operation not permitted Removed device path /dev/input/ckb1 Removed device path /dev/input/ckb0 Nov 26 16:23:31: [79798.615213] usb 8-1: USB disconnect, device number 8 Nov 26 16:23:32: [79798.890762] usb 8-1: new full-speed USB device number 9 using uhci_hcd Nov 26 16:23:32: [79799.563990] usb 8-1: New USB device found, idVendor=1b1c, idProduct=1b11 Nov 26 16:23:32: [79799.563995] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 26 16:23:32: [79799.563999] usb 8-1: Product: Corsair K95 RGB Gaming Keyboard Nov 26 16:23:32: [79799.564001] usb 8-1: Manufacturer: Corsair Nov 26 16:23:32: [79799.564004] usb 8-1: SerialNumber: 0701B03EAE3618E3530D5E92F5001946 Nov 26 16:23:32: [79799.773081] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/0003:1B1C:1B11.000E/input/input40 Nov 26 16:23:32: [79799.773385] hid-generic 0003:1B1C:1B11.000E: input,hidraw4: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard] on usb-0000:00:1d.2-1/input0 Nov 26 16:24:07: [79834.735410] usbhid 8-1:1.1: can't add hid device: -110 Nov 26 16:24:07: [79834.735433] usbhid: probe of 8-1:1.1 failed with error -110 Nov 26 16:24:42: [79869.700022] usbhid 8-1:1.2: can't add hid device: -110 Nov 26 16:24:42: [79869.700045] usbhid: probe of 8-1:1.2 failed with error -110 Nov 26 16:25:17: [79904.664643] usbhid 8-1:1.3: can't add hid device: -110 Nov 26 16:25:17: [79904.664665] usbhid: probe of 8-1:1.3 failed with error -110 Nov 26 16:25:17: [79904.743760] usb 8-1: Process 24781 (ckb-daemon) called USBDEVFS_CLEAR_HALT for active endpoint 0x81 Nov 26 16:25:32: [79919.729800] input: ckb1 as /devices/virtual/input/input41 Nov 26 16:25:33: [79920.228872] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 1 ret -110 Nov 26 16:25:33: [79920.379770] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:33: [79920.531604] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:33: [79920.683444] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.743369] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.803368] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.863221] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.923160] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.983159] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.803368] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.863221] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.923160] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79920.983159] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.043036] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.103059] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.162969] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.222910] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.282868] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.342774] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.406673] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.466690] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.526590] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.586537] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.646505] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:34: [79921.706387] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79921.766406] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79921.826350] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79921.886242] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79921.946200] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.010149] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.070008] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.130014] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.189874] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.249904] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.309814] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.369786] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.429767] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.489642] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.549589] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.609527] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.669460] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:35: [79922.729403] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79922.789335] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79922.849367] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79922.909209] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79922.969134] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.029034] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.089047] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.148963] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.208898] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.268837] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.328820] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.388731] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.448660] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:25:36: [79923.508573] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Checked out 9c28b21, did the same thing. Tried running the daemon without unplugging the keyboard first, still didn't work. Unplugged the keyboard and tested again, still no luck, same above logs. Edit: Noticed the latest commit whilst typing / testing all this, checked out cbd0981 and i think we have a winner! :) Didnt unplug the keyboard after the testing on 9c28b21. Ran the new daemon and instantly the keyboard came back up. Logs incase you're interested.. ckb Corsair Keyboard RGB driver v0.0.6 Setting FPS to 60 Setting default layout: us Root controller ready at /dev/input/ckb0 Connecting Corsair K95 RGB Gaming Keyboard (S/N: 0701B03EAE3618E3530D5E92F5001946) Error: usbdequeue (firmware.c:23): Operation not permitted Error: usbdequeue (usb.c:71): Operation not permitted Error: usbdequeue (usb.c:79): Operation not permitted Error: usbdequeue (profile.c:249): Operation not permitted Failed to set up device, trying to reset... Reset success Device ready at /dev/input/ckb1 Nov 26 16:57:17: [81821.862265] usbhid 8-2:1.1: can't add hid device: -110 Nov 26 16:57:17: [81821.862282] usbhid: probe of 8-2:1.1 failed with error -110 Nov 26 16:57:17: [81821.862368] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:59:20: [81944.736254] usb 8-2: Process 25301 (ckb-daemon) called USBDEVFS_CLEAR_HALT for active endpoint 0x81 Nov 26 16:59:25: [81949.732865] usb 8-2: Process 25301 (ckb-daemon) called USBDEVFS_CLEAR_HALT for active endpoint 0x82 Nov 26 16:59:30: [81954.727797] usb 8-2: Process 25301 (ckb-daemon) called USBDEVFS_CLEAR_HALT for active endpoint 0x83 Nov 26 16:59:35: [81959.723128] input: ckb1 as /devices/virtual/input/input47 Nov 26 16:59:35: [81960.222299] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 1 ret -110 Nov 26 16:59:35: [81960.273167] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:59:35: [81960.425147] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:59:35: [81960.481008] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:59:35: [81960.636858] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Nov 26 16:59:36: [81960.951975] usb 8-2: reset full-speed USB device number 11 using uhci_hcd I unplugged the keyboard to try the driver from scratch again and everything worked fine! So i suspect the issue is resolved for now, just needed some brute force love :P Many thanks :)
  2. To confirm, doesn't work on the latest commit cbd0981. unmodified. Only works consistently on commit b37a519 unmodified. (https://github.com/ccMSC/ckb/commit/b37a519d05648d1293353ffd364fb1911319cbc8) I tried changing the code as you suggested, but didn't see anything different in the standard output, or in the dmesg logs. Still get the constant spam as mentioned before in the dmesg logs. Will wait for another update.
  3. Bit of an update from me, loving the gui so far. The ability to select colours / patterns and adjust a range of settings is just great. Better yet is the ability to use the brightness button. Words cant express how happy i am that brightness is now working. Thank you very much :) Storing profiles and writing them to the hardware seems to work fine as well. One thing though, the changes you made to ckb-daemon in commit 11ec0b3, stopped the daemon working for me. I ended up checking out commit b37a519, which resolves the issue. ckb-daemon output ckb Corsair Keyboard RGB driver v0.0.3 Setting FPS to 60 Setting default layout: us Root controller ready at /dev/input/ckb0 Connecting Corsair K95 RGB Gaming Keyboard (S/N: 0701B03EAE3618E3530D5E92F5001946) The program halts here, and the following is spammed in dmesg [ 1754.114238] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 [ 1754.170184] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 [ 1754.226127] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 [ 1754.282073] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 [ 1754.289059] usb 8-2: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 33 rq 9 len 64 ret -110 Guessing this might have something to do with the changes to usb.c?? could be wrong though. I ended up cherry-picking the two later commits after 11ec0b3, fixed a merge conflict in usb.c where i pretty much removed anything that could set fail to 1 in the setupusb method and now the keyboard connects, and it connects much faster than it use to. Not exactly sure why this works, but maybe you might see something. Thanks again :)
  4. No worries, maybe the next firmware update from corsair will help. :) Just out of curiosity, would it be possible to bind the M1,M2 and M3 keys to the different profiles stored on the keyboard?
  5. Still seems to be working fine, no noticeable difference for me. Still getting the strange issue where F keys seem to have weird mappings after i kill the daemon and restart it. Maybe you have noticed this as well, but if you kill the daemon the keyboard still works fine. F key bindings are also correct. But as soon as you restart the driver without unplugging the keyboard and plugging it back in, the F keys are always messed up. Certainly not a massive issue though. Appreciate the work as always :biggrin:
  6. Awesome, no rush on that, keyboard is working fine as is. Haven't had a chance to play with the macro settings, will do that tonight. Also noticed that the numlock and capslock lights work correctly now. Actually amazed given these lights didn't work correctly on windows for me. The alt+left arrow combo to skip over words in a terminal seems to be working, not sure if its something you did or maybe i restarted my pc? Either way, no issues there. One other thing i have noticed, and i really need to get more examples to explain it better, but it seems if i plug the keyboard in, start the driver everything works fine, all key mappings are correct. However, if i kill the daemon and restart it, the key mappings on the keyboard seem to do some weird things, F keys will often produce odd characters etc. To fix it i need to unplug the keyboard, plug it in again, and restart the daemon. I honestly havent checked logs or anything to work out whats going on. So will leave it for now and if i can figure out a way to replicate the issues will post an update.
  7. Do you guys happen to have any documentation on how to push profiles to the device outside the CUE app?
  8. MSC you're an absolute legend!. I can now consistently get the keyboard to work using your driver. Still a bit fiddly given the fact i need to have another keyboard on hand so i can start the driver etc, but its a dam sight better than the out of the box solution from corsair :P Still a few bugs.. most of them you have listed on git already. Some key combinations do odd things, for example alt+arrow keys. Quite often I will use alt+left arrow key to quickly skip words in a terminal. At the moment that key combo produces a capital D. Been having some fun playing around with lighting combinations. Any idea if you can set the colour for the G keys? Also getting way ahead of myself here.. what do you think the chances are of being able to write to the keyboards internal memory to enable profile switching with the M keys?
  9. Appreciate the work mate, you seem to be doing a hell of a lot more for the community than the actual devs, so top job. Its really a shame, i think the keyboard has great potential but the firmware is just too buggy at the moment. Thinking i might put the keyboard aside for now and wait for corsair to release more firmware updates. Users are clearly unhappy with the device, and its abundantly clear there are issues with it, i guess its just a case of waiting for further revisions. In the meantime will keep watching this thread, whenever you update this next will do some more testing.
  10. Well, pulled down the latest commit, managed to get a little further this time in the log output, but unfortunately the keyboard died again. All the lights are on, but it just doesn't accept any key presses. Looks like the driver did a rest or something on the usb interface? I haven't really had much luck getting this keyboard to consistently initialise in linux so its in no way your drivers fault. Here are the logs, certainly seems like usbhid has issues with something. [76655.903992] hid-generic 0003:1B1C:1B11.0001: usb_submit_urb(ctrl) failed: -1 [76657.068766] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [76657.991910] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.2/usb5/5-2/5-2:1.0/0003:1B1C:1B11.0007/input/input20 [76657.992365] hid-generic 0003:1B1C:1B11.0007: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard] on usb-0000:00:1a.2-2/input0 [76692.957553] usbhid 5-2:1.1: can't add hid device: -110 [76692.957575] usbhid: probe of 5-2:1.1 failed with error -110 [76751.133606] usb 5-2: USB disconnect, device number 2 [76781.806411] usb 5-2: new full-speed USB device number 3 using uhci_hcd [76782.479678] usb 5-2: New USB device found, idVendor=1b1c, idProduct=1b11 [76782.479683] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [76782.479687] usb 5-2: Product: Corsair K95 RGB Gaming Keyboard [76782.479689] usb 5-2: Manufacturer: Corsair [76782.479692] usb 5-2: SerialNumber: <removed> [76782.688907] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.2/usb5/5-2/5-2:1.0/0003:1B1C:1B11.0008/input/input21 [76782.689380] hid-generic 0003:1B1C:1B11.0008: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard] on usb-0000:00:1a.2-2/input0 [76817.656097] usbhid 5-2:1.1: can't add hid device: -110 [76817.656118] usbhid: probe of 5-2:1.1 failed with error -110 [76852.620736] usbhid 5-2:1.2: can't add hid device: -110 [76852.620758] usbhid: probe of 5-2:1.2 failed with error -110 [76887.584308] usbhid 5-2:1.3: can't add hid device: -110 [76887.584328] usbhid: probe of 5-2:1.3 failed with error -110 So.. back to square one, getting the keyboard to work again. are there any other alternatives to the default HID driver?
  11. Will try unplugging it again when i get home later today. But the only real messages im seeing are usbhid 5-2:1.1: can't add hid device: -110 usbhid: probe of 5-2:1.1 failed with error -110 The message pops up as soon as i run the daemon. I really cant find much info on this error or what causes it. Seems others indicate this might be a power supply issue to the device, or possibly a faulty device. Im hesitant to think its a problem with the USB ports given i have tested a range of other spare USB keyboards at home and all work instantly with no issues or errors. Given a few people seem to be having the same issues, i suspect this has more to do with the k95 keyboard and dodgy firmware than anything. The keyboard works fine in windows, although im testing that on a completely different PC. I might be game to install windows on my linux box, but would rather not.
  12. Ok, now that i have basic typing functionality back with the keyboard, time to test this driver :P Unfortunately i haven't had much luck with this either, keeps throwing the error "Failed to get device info" root @ # ckb-daemon ckb Corsair Keyboard RGB driver v0.1 Root controller ready at /dev/input/ckb0 Detected K95 keyboard Failed to get device info Is there any info i can provide that might help with debugging that?
  13. Thanks for the work MSC, when i can get my RGB K95 to work correctly under linux i will do more testing and offer some feedback.
×
×
  • Create New...