-
Notifications
You must be signed in to change notification settings - Fork 165
Sabre RGB not detected by ckb #311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have the same issue as well. Just bought Sabre and it does not detect it. |
Actually fairly simple :) Added here: https://github.com/ccMSC/ckb/tree/sabre Let me know if it's working properly or if there's something else I need to do. |
Hi ccMSC, I gave it a try and the mouse is detected by the application, but for some reason is now unable to move! When I ran the ckb-daemon I got this (Interrupt is mine):
I noticed that the application polls the mouse and prints c:38 until it gives up and drops the Sabre as a menu option. Keyboard also works fine throughout process. Thanks for your help. |
@ccMSC Any update to this? I've had same issues as @DivineComedy11 mouse does not move but it does detect it.. Thanks! |
Sorry, I've been away from the project for the past week so I didn't have a chance to look into it. I thought it might have been caused by the firmware, so I've merged the
|
Gave it a try, no luck unfortunately. Here's the output:
Thank you for your help. |
I just had the same problem on the sabre branch. It seems that the issue was in |
@orangeturtle739 It works!!! Thank you |
I opened a pull request for the fix: #367. |
Good spot, nice one! |
One issue I notice, not sure if anyone else has similar problems. When I turn on my computer in the morning the mouse doesn't move/detect it and I would have to either replug it back in OR run quickinstall again to get it to work. Any ideas? @orangeturtle739 |
Not quite sure. I just tried restarting my computer, and the mouse worked fine. I am running Kubuntu 16.04. |
maybe a mac issue.. |
I can't get it to work on my mac at all. What version of OS X are you running? I have 10.11.5. |
There's another bug report, can't remember which one, but there was a |
I just forked it yesterday, and put the fix on the sabre branch, which had the fw2kb branch already merged into it. So unless this mac fix was on the testing branch, I should have gotten it. |
#233 (comment)
Maybe the fix wasn't pushed to source yet
|
@orangeturtle739 I'm running 10.11.4 |
It looks like it was fixed (#233 (comment), with this package: https://dl.dropboxusercontent.com/u/16424004/ckb/ckb%20v0.2.5%2Bf05%2Blogging.pkg) but the source was not pushed, so we can't combine it with this fix. |
Hey everyone, sorry for my absence but I finally got a chance to look at this again. I'm moving all new devices into the |
Thanks! I will try it out on my mac soon. |
Changing the hwid worked with my Sabre. Probably another new version. Mine has |
Hi, I'm new to all of this (since I got the mouse yesterday). I've got a sabre RGB with ID 1b1c:1b2f and I'm running macOS 10.12. I've tried the default beta 0.2.6 > my mouse isn't recognized. I've tried the fork from https://github.com/orangeturtle739/ckb/tree/sabre > still not recognized. I've tried the newdev branch and even though my IDs are present in the usb.h my mouse is still not recognized. Am I missing something? Am I supposed to do something else than just compile from the newdev branch? |
@orangeturtle739, any luck with Mac? I have this mouse:
And I can see it defined in the
But I keep getting |
I never got it to work on a mac, and now I don't have a mac anymore to test on. Perhaps try ckb-next? This repository seems to be no longer maintained, and they might have fixed it there. |
@orangeturtle739 That worked - thanks for the tip. |
Hi, I recently bought a Sabre (CH-9303011-NA). Then, I tried https://github.com/mattanger/ckb-next#upgrading-source How do I find a matching driver? I believe its beta-v0.2.8, and how do I install that driver?? |
Ensure you are using https://github.com/mattanger/ckb-next and the daemon is running @ekcg |
How do I ensure daemon is running?? @ollieatkinson |
It worked! I'm guessing the older versions wasn't completely uninstalled, so the error keeps popping up. I uninstalled Xcode, qt, and deleted all the folders of the old ckb's. installed the binary for 0.2.8 and worked like a charm! |
Before I go into the issue, I'd like to thank ccMSC for their tireless efforts with this driver!
I have a red K70 (which is detected fine), and have recently purchased an RGB Sabre, which ckb unfortunately cannot see.
I have a feeling this is because I have a slightly newer model than the one previously supported, or at least one with a different bus ID as I get the following output when I run lsusb -d 1b1c:
(Alongside the 1b09 ID for the K70)
Stopping the daemon and running it again just picks up the k70, as you might expect. I've tried digging around, but I get the impression it's slightly more involved than adding a string somewhere, so any input would be much appreciated.
The text was updated successfully, but these errors were encountered: