Update - now ckb doesn't recognize my keyboard #298
Comments
|
I don't know if this relates, but did you update your firmware for the keyboard? I updated to the latest (2.04) and now my keyboard isn't being recognized on OS X as well. |
|
SAME HERE, USING OSK |
|
HALP |
|
Same issue on Linux build. Ckb shows the keyboard appearing and disappearing every 30 seconds or so. Also on latest firmware (2.04) |
|
Boo - corsair's firmware broke it again :( I'll try to update as soon as possible. |
|
thanks man! |
|
No worries, thank you so much! Love the work you do On Thu, Apr 21, 2016 at 4:34 AM ccMSC notifications@github.com wrote:
|
|
sigh! Should have taken a look here before updating. |
|
I upgraded my K70 RGB to the new firmware in order to see if I can fix the usbhid warning. Ckb doesn't seem to recognise the keyboard at all, however it works fine with the standard HID driver, so I am not sure if the enumeration error actually matters, unless that's what is blocking CKB from accessing the keyboard. |
@tatokis Which HID driver is that? I would like to enable it, compile a custom kernel and give it a shot. Please state the CONFIG_ to enable. Are you talking of CONFIG_HID_CORSAIR ? |
|
@philbyjohn It's usbhid/hid-generic Using the stock Ubuntu kernel config with some unrelated changes. Keep in mind that if you are running with 0x4,the linux HID driver ignores the keyboard completely. You should use the quirk suggested in the readme instead (0x20000408). It appears that the keyboard does a reset before it "stays on", as the disconnect was not caused by me. Some additional info from the ckb daemon: |
|
@tatokis @philbyjohn @lsbeuromix The above link is for K70RBG firmware 1.15 [also attached to this comment]. force downgrade using CUE on a windows box like I did and CKB will be working just fine. @ccMSC let us know if you find anything out about 2.04, from what I can see from the above comments it could break CBK altogether. |
|
@tatokis I switched back to usbhid.quirks=0x1B1C:0x1B13:0x20000408 and then did a modprobe hid_corsair but that did not work. I think the kernel tries to load hid_corsair at boot but fails. I get I don't see this error in your log message, which might be the reason why it works. Probably because I use the older stock Fedora 22 (64 bit) running 4.4.6-201.fc22.x86_64. @JackFarrand Did not know we could downgrade. Will go with this workaround in the meantime. Thanks! |
|
@philbyjohn welcome dude |
|
@JackFarrand Was 1.15 the latest version before 2.02? |
|
@Serubin 1.33 was the last one. Have a look at https://github.com/ccMSC/ckb/blob/master/FIRMWARE |
|
@tatokis Ah thanks. I'm assuming the downloads for that version are gone now? |
|
@Serubin searching for "K70RGB_app133_RC.bin" on google seems to not return any results, so I assume so. The links on the FIRMWARE file just point to the new versions. |
|
@JackFarrand as I said earlier, I use hid-generic with usbhid, no special driver: |
|
@Serubin yep, latest I could find. seems to work fine, no issues with CKB or CUE. On a side note, I only tried CUE recently, does anybody else think that CKB is FAR superior? The user interface is just so much easier to use. I think perhaps CKB is less powerful [no scripting engine yet], but CUE makes it really hard to set up a profile properly! |
|
@JackFarrand to add to my previous message, when I do # rmmod usbhid the keyboard along with every other HID device dies. |
|
@tatokis I think you meant @philbyjohn! No HID issues here! |
|
@JackFarrand Apologies, yes. I lost track of who said what at this point :p |
|
@JackFarrand Absolutely, yes. CKB is much better and easier to use. |
|
I have only used CUE two times, just to upgrade the firmware. Never set up any profiles on it. CUE isn't even installed on my main computer. Corsair should acknowledge that at some point, and offer some form of support to @ccMSC for all the great work. |
|
Well this is awkward...it seems only the K70 got the update, not the K95. So I can't actually test it until if/when the K95 version is released. That said, I have a pretty good idea of what happened. I pushed an update here for Linux users: https://github.com/ccMSC/ckb/tree/fw2kb Let me know whether or not it's working, and if not, please post a driver log. For OSX users, open a terminal and run the following commands: I'll need the output of this so I can see where the problem is. |
|
The fw2kb version, in Ubuntu 16.04, appears to get the same end result, in that the ckb-daemon runs, but as soon as I run ckb then the keyboard stops responding until I kill the daemon. I ran the daemon from the command line, and the output was as follows. The last five lines, from "Connecting 3 endpoints" onwards, repeat continuously after that. In this case the keyboard stopped responding immediately, without me having to run ckb. |
|
@hxltinh download QT5 from here: https://www.qt.io/download-open-source/ The fw2kb branch works fine with OS X. After installing QT5 I was able to build it following @4t0m1k steps above and it works perfectly with my K65 RGB and FW2.04. |
|
@mhennessie |
|
What about this one : Qt Framework is already included in it. Move the .app in your applications folder and reboot. If it doesn't work, what the result of |
|
hi @ccMSC I compiled and installed the latest 'sabre' branch but still have no working k70 :( The output is: Interesting that it now tries 9 times to get it connected... |
|
Works great on K70 RGB Fedora 24β. Thanks MSC! |
|
sorry. i use the app which the 4t0m1k post. use K70 RGB in v2.04 it doesn't work ➜ ~ sudo /Applications/ckb.app/Contents/Resources/ckb-daemon |
|
@dreamcog Did you try this one : https://dl.dropboxusercontent.com/u/16424004/ckb/ckb%20v0.2.5%2Bf05%2Blogging.pkg ? Last build from the project owner. |
|
@4t0m1k thanks. I just install the pkg which your last message said.
I cann't write the code , I just can write python or php . i don't know if someone could fix the bugs:) thanks |
|
@dreamcog You don't need Karabiner for this purpose. You can do it directly in ckb :
If you have to modify others keys, you can go in the binding menu. Maybe Karabiner is not compatible with ckb, you may uninstall it for the ckb mapping to work (maybe). |
|
@4t0m1k
thanks a lot. could you use it for your keyboard? with firmware 2.04? |
|
I am using a K65 RGB with fw 2.0.4 and the fw2kb build of CKB without any issues. My Windows key is rebound to the Alt/Option key and the Alt key is the Command key. |
|
@dreamcog I confirm that the fw2kb build works perfectly with the K65 RGB on 2.04 firmware. I think you might open a new thread for your problem : "K70 RGB / fw 2.04 / binding doesn't work". Tell that you are using ckb beta-0.2.5-f05 build from ccMSC (project owner). EDIT : Have you tried to completely remove Karabiner as this may be a compatibility issue with ckb? I think that Karabiner use a kext driver. You have to check that this kext is not running ( You can use the command |
|
@mhennessie and @4t0m1k thanks for your help。 this is only one problem that could I have the hot key like the mac keyboard? thanks :) 👍 |
|
I can modify the windows and the alt key became option and command. But seems it can not make the F1 ~ F12 became the mac hot keys |
|
@dreamcog I am able to rebind all of my F keys as normal. Since you cannot do macros with CKB yet you might need to change the keys in System Preferences - Keyboard - Shortcuts. For example Mission Control is defaulted to Control+Arrow-Up but you can change it to F3 like it is on a Mac aluminum keyboard. To use F1 & F2 as monitor brightness controls you will need some third party software if using with a hackintosh. |
|
@mhennessie I use a logitech Mouse , and can set hot keys instead of Mac's Hot key, so I can easily go back to desktop or open Application Menu :) |
|
I've just purchased the k70 rgb lux and verified that the corsair provided software works in windows. That being said, I've installed the latest version of your software and it does not seem to recognize my keyboard. the app does not even have the model tab listed. I am not sure what the next steps are as I am new to mac OSX. Ive attempted removing the app then reinstalling then rebooting a few times with no success. Ideas? Thanks in advance. |
|
I am currently experiencing a similar issue with Corsair K40 on MacOS Sierra. I've not looked into this too much but I came across the app via a YouTube video before buying the keyboard, looks awesome and thank you for releasing so that users could use the keyboard on Mac. I am getting a similar issue to @cszelesbbs in that the app is not recognising the device as being connected. Currently using version 0.26. Any suggestions would be awesome, thanks :) |
|
@jbwebesign the K40 was never a supported device. |
|
I have not been able to get the update to work yet either Sent from Apple iPhone
|
|
@mhennessie cheers for the update - I ended up taking it back because I figured this might have been the case. Thanks again. |
… temporary stack. DPIs other than Sniper and Custom must now be set using their table index. This interface, where setting the DPI directly is not available, should be more consistent with the actual use, and allows for a simpler implementation. Most importantly the index is no longer inferred based on the provided DPI. See ccMSC#298.
and others
Hello - I just updated my Command Line Tools (OS X 10.11) for Xcode, and when my computer rebooted, the ckb utility no longer recognizes my keyboard. I am able to type on it, but the key bindings I set and the awesome animation I was using no longer work. Is there anything you can do to help? Thank you!
The text was updated successfully, but these errors were encountered: