crazybear

MSC, have you abandoned reading your emails? I send two recently, as after installing a new PSU, strangely, everything changed for the worse and I can't get the keyboard nor ckb working properly again. My situation is a bit different than most others, so I don't feel it best to post the problems/details/questions here. Thanks.

I find I have to re-install every time I boot up for the Corsair K95 to work at all - some times I have to install twice once after the other. One time it installed the ckb, but not the daemon [in 14.04]. Will it be long [should I find an older copy and install that] or will this likely be fixed soon? Thanks

Where is this new firmware available? I don't see it on the Corsair site. Thanks.

MSC, your great driver has been working like a charm now for months. Sometimes I had to just pull out the keyboard plugs and then put them back in...weird...but it solves most problem. However, I just ran into a new one that confounds me.... My OS 12.04 would not boot into GUI desktop at all. I had to use my 14.04 OS, which is not my primary at all. I'd tried most everything and was pulling my hair looking in all the wrong places. Instead of going to a desktop it would go into tty, but, stranger than that when I'd try to type into the tty, all I'd get are very strange 'characters' - non-Latin [such as diamond shapes or things that looked like Thai characters]. I finally figured out it was some interaction between the keyboard and the OS. I also found out I could unplug the keyboard and let it boot into the desktop, then replug in the keyboard....but one thing was still wrong. Caps lock was reversed...when 'on' it was off - when 'off' it was on.... Any suggestion what the fix would be? There is a program xdotool that will reverse the caps lock, but I'd rather not go that route unless I have to. Also, what might I have to do to not have to unplug the keyboard every time I turn on the machine. Thanks much for all your hard work.

On my system the boot doesn't freeze, but it takes a VERYYYYYY looooooong time with some error messages sometimes. I do NOT understand how these things work with coding of firmware nor programs, but wouldn't it be logical to assume that ONLY if Corsair took into account the Linux [and Mac] operating systems [which I believe they give NO attention to!], that any firmware update would only solve problems people are having with MS systems....just my not fully informed two cents. It would therefore follow that anyone who wishes them to devote some effort along the lines of compatibility with Mac and /or Linux should loudly and soon make their interests known to Corsair! I have, but got a very cold reception. However, if they get many such responses they may act on it!...so please all, for me and thee...move on it! MSC has done great work, but can only do so much without help from Corsair.

FWIW, my K95 RGB works fine using two USB 2 MB slots, but is NOT working at all in BIOS. I use mostly Linux and have been spending all my time working with the great new Linux driver on this Forum. Now, that it is working in Linux, I started to look at the other threads [as most of you use Windoz], and was sad to sickened to see the problems. I was RMAing a K95 [non-RGB] and suddenly was offered a K95 RGB as I had waited a loooong time [needing a NA keyboard, but living in Europe]...and had though I'd been given a present....but now wonder if I was thrown a known lemon. I can only hope a hardware fix will someday allow me to get into BIOS or use the USB 3 slot on my motherboard [GA-X58A-UD7 v.1]. Corsair, your reputation is on the line. I have Corsair memory and have never had problems with it. I've had Corsair keyboards before and only had minor problems with LEDs going out....but not being able to get into BIOS and having to have a second older keyboard on the desk to accomplish that........ The colors are very nice...but they'd be nicer if the keyboard would function as a keyboard first. I hope this all gets fixed. I'm asking if others have been able to get the K95 RGB to work at boot; and if any with a few years old GA MB have had the same problems as I - NOT working at boot up and the USB3 ports don't work for this board. Thanks.

I also want to add HEART FELT thanks to MSC for this effort. I was going to return my RGB board, as it wasn't working with Ubuntu...but now it is!..and getting better and better! A question to anyone out there with a Gigabyte MB and Award BIOS [like me]: Are you having no success [as I] with the RGB board being recognized during boot? I can't use it until the Ubuntu program starts up - leaving me to have to have two keyboards on the desk. Just wanted to know if it was the GA MB or something else. I've tried the BIOS switch, but for me it makes NO difference. Thanks. I'll report the responses to Corsair Technical Support. MSC can do nothing about this...he's great, but not a magician.

I need to correct this, I think the 'problem' comes only when ckb is not started. When it is, sound button and wheel work properly; when it is not, they do not.

Yes, I agree.....volume wheel was working a few days ago. Is not now [with latest version] on my K95 RGB. However, this seems to be only in Ubuntu 14.04 not in 12.04, for me....strange.

So, thanks to MSC, I learned that for Ubuntu you don't need to install glibc [and it is damn near impossible, it seems]...but Ubuntu has 'build-essential' already, so I could use the command "qmake && make”. That seemed to work, and added the new bin folder...but "sudo bin/ckb-daemon" only gave error messages numbered from 1 to 25 and then repeating endlessly.:confused: It also made the RGB keyboard totally unresponsive until reboot.

I'm using two OS [on separate disks] Ubuntu 12.04 and 14.04. On neither can I install glibc. It is not an option. A look on the internet gives all manner of warnings about a GHOST vulnerability unless one upgrades to a higher number glibc...but I don't see anything about installing glibc if you don't have it installed. It is the only dependancy I now lack. I can not yet run qmake and make. [oh, it seems (?) that libc6 is the 'same' as glibc. So, how do I proceed with that - which is installed. [i tried to run: "qmake && make" - that ran OK, but then running "sudo bin/ckb-daemon" only produced endless 1-25 numbered error messages. Thanks.

OK, see that now...sorry I missed it. Before I embark on this [as I mostly use Linux/Ubuntu] let me say that my older K95 functioned a a basic keyboard in Ubuntu w/o problem..but I RMA's it and now have a K95-RGB which is NOT working in Linux much of the time....some keys [or all keys] stop working suddenly...before I go this route with your wonderful project - is my new board in need of your program or to first be RMA'd again?! When it freezes up and stops giving key commands it also on turning off the computer stays lit up like a Christmas tree and sometimes spontaneously goes into nice patterns I didn't ask it to do. Nothing but unplugging it will stop this. Whether it works at all; for a while; or not at all in Ubuntu seems to be chance and can change while working - with no seeming change to programs or keyboard. Very strange behavior - even the brightness keys don't work when it goes 'odd'. Any thoughts. If it is buggy, it will be with your progam too, most likely. Thanks and thanks for your project. It is the way to go...for many / all reasons!

Hello. I'm new here and use Ubuntu Linux more than I do Windows, so this is exciting. Where in this long thread does one find the driver to download? Is it hard to install or compile? Are there instructions for this in this thread or somewhere? Thanks.