(Unofficial) Linux / OSX Driver

Which part is it that's not running, the GUI or the driver? (hint: $ cat /dev/input/ckb0/pid should tell you if the driver's working or not - if you get "no such file or directory", it's not running)

 

If it's the GUI that doesn't work, try running /bin/ckb from a terminal and see what output it gives you.

I really appreciate the work that MSC has put into making this Linux driver...it benefits so many people, thank-you!

 

I dual-boot Windows7 & Linux Mint 17.1, but I use Linux Mint most of the time-

 

Presently I ordered a regular K70 (9000085-NA)...but I really like the look of the K70 RGB

 

Is the Linux K70 RGB 'ckb' 'ready-for-primetime' yet, or should I wait awhile?

 

I don't mind tinkering a little bit, but I use my pc mostly for work and it needs to be online, ready, and usable at a moments notice-

 

Thanks!

Edited May 10, 2015 by pizzly
update

The driver is very stable on Ubuntu/Mint in my experience. It may take some tweaking when you first set it up, but after that it shouldn't be any trouble.

That's what I need to hear :):

 

Thanks!

Thanks, I did that and it's set to permissive but I still can't run the software. I don't know what is going on. The software works perfectly on Linux Mint XFCE, but not here on Korora.

 

I have to log out and log back in as root in order to edit that file... that's such a pain, because Korora is slower than Fedora when logging in or booting up... it's horrible. But I love the Gnome Desktop so I deal with it.

I flipped over to Gnome and everything seems to be working just fine, both the ckb gui and the keyboard driver itself...

 

Running Fedora 20/gnome

 

I normally run KDE or LXDE btw.

 

Of course I may not be a good example, I have about 15 desktop env's installed and originally started at Fedora 16... Switching from FreeBSD to linux at that point so I made a lot of mistakes with repos and packages... and I was about to upgrade to Fedora 21 using 'fedup' and discovered I apparently have a ton of unresolved dependency errors along with both i686 and AMD_64 versions of QT installed.... I am going to make a backup and do a clean install... I'll install gnome on top of Fedora as one of my desktop managers and post back....

Edited May 10, 2015 by robbob2112

Notes on Fedora 21 desktop - clean install and this is the first thing I am installing (defaults to Gnome 3.14.2-2.fc21 now instead of KDE )....

 

as root

# yum install qt5-qtbase libgudev1-devel qt5-qtbase-devel zlib systemd-devel gcc gcc-c++ zlib-devel

# git clone https://github.com/ccMSC/ckb

# cd ckb/

# ./quickinstall

 

 

Finished!

Install ckb system-wide [Y/n]? y

Installed in /usr/bin

 

System service: systemd detected

Run the driver as a startup service [Y/n]? y

 

Start ckb now [Y/n]? y

 

 

Post install.... still has the hang on shutdown... boots up normally after reboot... haven't tried from reboot after windows yet...

 

keyboard and gui both work fine

 

 

and to get me back to my LXDE desktop

# yum group install 'LXDE Desktop' 'Xfce Desktop' --exclude fedora-release\*

Edited May 10, 2015 by robbob2112

That's what I need to hear :):

 

Thanks!

Awesome :D

 

I should point out, it's best to run a firmware update in Windows when you first get the keyboard, before you try to use it in Linux. The latest FW solves a lot of connection issues.

 

Notes on Fedora 21 desktop - clean install and this is the first thing I am installing (defaults to Gnome 3.14.2-2.fc21 now instead of KDE )....

 

as root

# yum install qt5-qtbase libgudev1-devel qt5-qtbase-devel zlib systemd-devel gcc gcc-c++ zlib-devel

# git clone https://github.com/ccMSC/ckb

# cd ckb/

# ./quickinstall

 

 

Finished!

Install ckb system-wide [Y/n]? y

Installed in /usr/bin

 

System service: systemd detected

Run the driver as a startup service [Y/n]? y

 

Start ckb now [Y/n]? y

 

 

Post install.... still has the hang on shutdown... boots up normally after reboot... haven't tried from reboot after windows yet...

 

keyboard and gui both work fine

 

 

and to get me back to my LXDE desktop

# yum group install 'LXDE Desktop' 'Xfce Desktop' --exclude fedora-release\*

 

Any idea what causes the shutdown hang (dmesg output maybe)?

Not really, by the time it hangs on shutdown it has already stopped writing logs and the screen has flipped to a generic background with the Fedora logo .. if I can turn that off it might print something useful to the screen.

 

Here are messages log lines since the last reboot..... not sure what it means, but seems like it might be re-initializing the keyboard periodically?

 

 

May 10 07:38:15 intrepid kernel: Linux version 3.19.5-200.fc21.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 4.9.2 20150212 (Red Hat 4.9.2-6) (GCC) ) #1 SMP Mon Apr 20 19:51:56 UTC 2015

May 10 07:38:15 intrepid kernel: hidraw: raw HID events driver © Jiri Kosina

May 10 07:38:15 intrepid kernel: usbhid: USB HID core driver

May 10 07:38:15 intrepid kernel: hid-generic 0003:1B1C:1B11.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0

May 10 07:38:15 intrepid kernel: hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0

May 10 07:38:25 intrepid kernel: hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1

May 10 07:38:35 intrepid kernel: hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2

May 10 07:38:45 intrepid kernel: hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3

May 10 13:38:46 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

May 10 13:38:48 intrepid kernel: [ 34.581158] input: ckb1 as /devices/virtual/input/input18

May 10 13:38:48 intrepid kernel: input: ckb1 as /devices/virtual/input/input18

May 10 13:38:50 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

May 10 13:38:51 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event2)

May 10 13:38:51 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11

May 10 13:38:51 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys

May 10 13:38:51 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard

May 10 13:38:51 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11)

May 10 14:44:49 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

May 10 14:44:49 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

May 10 14:45:51 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

May 10 14:45:54 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

May 10 14:52:17 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Close

May 10 14:52:17 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event2)

May 10 14:52:17 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "evdev keyboard catchall"

May 10 14:52:17 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "system-keyboard"

May 10 14:52:17 intrepid gdm-Xorg-:0: (II) Using input driver 'evdev' for 'ckb1'

May 10 14:52:17 intrepid gdm-Xorg-:0: (**) ckb1: always reports core events

May 10 14:52:17 intrepid gdm-Xorg-:0: (**) evdev: ckb1: Device: "/dev/input/event2"

May 10 14:52:17 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11

May 10 14:52:17 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys

May 10 14:52:17 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard

May 10 14:52:17 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11)

May 10 14:57:52 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Close

May 10 14:57:52 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event2)

May 10 14:57:52 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "evdev keyboard catchall"

May 10 14:57:52 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "system-keyboard"

May 10 14:57:52 intrepid gdm-Xorg-:0: (II) Using input driver 'evdev' for 'ckb1'

May 10 14:57:52 intrepid gdm-Xorg-:0: (**) ckb1: always reports core events

May 10 14:57:52 intrepid gdm-Xorg-:0: (**) evdev: ckb1: Device: "/dev/input/event2"

May 10 14:57:52 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11

May 10 14:57:52 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys

May 10 14:57:52 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard

May 10 14:57:52 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11)

May 10 15:49:21 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

May 10 16:05:45 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

 

 

 

 

 

Awesome :D

 

 

Any idea what causes the shutdown hang (dmesg output maybe)?

and here is from the last shutdown and current boot up... switched to windows and back again... no hang this time on login... It does take an additional 30~40 seconds on boot to initialize the keyboard, but doesn't require unplugging

 

shutdown -- had to unplug it...

 

May 13 08:18:14 intrepid kernel: [ 1.760973] hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0

May 13 08:18:14 intrepid kernel: [ 11.435907] hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1

May 13 08:18:14 intrepid kernel: [ 21.437228] hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2

May 13 08:18:14 intrepid kernel: [ 31.438170] hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3

May 13 07:29:38 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Close

May 13 07:29:38 intrepid kernel: hid-generic 0003:1B1C:1B11.0006: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0

May 13 07:29:46 intrepid kernel: hid-generic 0003:1B1C:1B11.0007: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1

May 13 07:29:46 intrepid kernel: usb 5-1.3: usbfs: process 910 (ckb-daemon) did not claim interface 0 before use

May 13 07:29:46 intrepid ckb-daemon: ckb Corsair Keyboard RGB driver beta-v0.1.3

May 13 07:29:46 intrepid ckb-daemon: Setting FPS to 30

May 13 07:29:46 intrepid ckb-daemon: Setting default layout: us

May 13 07:29:46 intrepid ckb-daemon: Root controller ready at /dev/input/ckb0

May 13 07:29:46 intrepid ckb-daemon: Connecting Corsair K95 RGB Gaming Keyboard (S/N: 16030013AE3B940553763B42F5001940)

May 13 07:29:46 intrepid ckb-daemon: Device ready at /dev/input/ckb1

May 13 07:29:46 intrepid ckb-daemon: Caught signal 15

May 13 07:29:46 intrepid ckb-daemon: Disconnecting Corsair K95 RGB Gaming Keyboard (S/N: 16030013AE3B940553763B42F5001940)

May 13 07:29:46 intrepid ckb-daemon: Removed device path /dev/input/ckb1

May 13 07:29:46 intrepid ckb-daemon: Removed device path /dev/input/ckb0

 

 

Bootup

 

May 13 02:17:39 intrepid kernel: Linux version 3.19.5-200.fc21.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 4.9.2 20150212 (Red Hat 4.9.2-6) (GCC) ) #1 SMP Mon Apr 20 19:51:56 UTC 2015

May 13 02:17:39 intrepid kernel: hidraw: raw HID events driver © Jiri Kosina

May 13 02:17:39 intrepid kernel: usbhid: USB HID core driver

May 13 02:17:40 intrepid kernel: hid-generic 0003:1B1C:1B11.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0

May 13 02:17:40 intrepid kernel: hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0

May 13 02:17:50 intrepid kernel: hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1

May 13 02:18:00 intrepid kernel: hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2

May 13 02:18:10 intrepid kernel: hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3

May 13 08:18:14 intrepid kernel: [ 35.428325] input: ckb1 as /devices/virtual/input/input18

May 13 08:18:14 intrepid kernel: input: ckb1 as /devices/virtual/input/input18

May 13 08:18:21 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event3)

May 13 08:18:21 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "evdev keyboard catchall"

May 13 08:18:21 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "system-keyboard"

May 13 08:18:21 intrepid gdm-Xorg-:0: (II) Using input driver 'evdev' for 'ckb1'

May 13 08:18:21 intrepid gdm-Xorg-:0: (**) ckb1: always reports core events

May 13 08:18:21 intrepid gdm-Xorg-:0: (**) evdev: ckb1: Device: "/dev/input/event3"

May 13 08:18:21 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11

May 13 08:18:21 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys

May 13 08:18:21 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard

May 13 08:18:21 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11)

 

 

 

on the boot up the clock jumps around... windows and linux seem to both want to set the bios clock... one wants to set it to UTC and the other wants to set it to local time MST... haven't ever sorted out how to tell them to stop it.

on the boot up the clock jumps around... windows and linux seem to both want to set the bios clock... one wants to set it to UTC and the other wants to set it to local time MST... haven't ever sorted out how to tell them to stop it.

 

I think you might have the same issue I had last year...this fixed it (I changed Linux [Make Linux use 'Local' time:])-->

 

Clock time is off on dual boot

Edited May 13, 2015 by pizzly

does anyone know what might be causing this.

I installed CKB on OSX and everything works fine, but when reboot CKB launches on start up but the keyboard doesn't get detected. I have to reinstall CKB then to be able to use the keyboard.

 

Thanks for any info if anyone else has experienced this before.

Try running this in a terminal:

sudo launchctl load /Library/LaunchDaemons/com.ckb.daemon.plist

 

The installer should set it up to run on boot, but maybe that's not happening for some reason?

How do I uninstall 'ckb' in Linux (Mint) if I want to install a newer version of 'ckb'?

 

I looked in Synaptic Package Manager, but could not find it...

 

Thanks!

 

I just noticed the 'uninstall' option when I right-clicked 'ckb' in the menu...hehehe...my bad :D:

Edited May 17, 2015 by pizzly

I've tried using your software with Fedora 21, and installed everything that it says must be installed, but it just won't build. The terminal gives me this: http://pastebin.com/raw.php?i=KUuYrRmR

Sounds like you're missing the zlib development headers. Anyone else with Fedora know the right package?

Sounds like you're missing the zlib development headers. Anyone else with Fedora know the right package?

 

See my post above... just did a clean install of fedora 21 and first thing this keyboard... he is missing zlib-devel... which are the headers for zlib

 

Notes on Fedora 21 desktop - clean install and this is the first thing I am installing (defaults to Gnome 3.14.2-2.fc21 now instead of KDE )....

 

as root

# yum install qt5-qtbase libgudev1-devel qt5-qtbase-devel zlib systemd-devel gcc gcc-c++ zlib-devel

# git clone https://github.com/ccMSC/ckb

# cd ckb/

# ./quickinstall

Cant still not use the volume wheel and mute button. But I can can bind the volume up and down with

other functions. That is strange. Any solutions?

Now THAT's interesting...I had assumed the problem was the input system, but if it works when you bind another key to it, it must be a USB issue instead. I'll look into it some more and see if I find anything. The keyboard isn't in BIOS mode, right?

No it is not in BIOS mode.

So here is an interesting thing.

 

If I play a stand alone video in VLC the volume and mute work perfectly inside the app, in fact all the media controls work.

 

The media controls do nothing when playing inside a browser (youtube video or streaming site)

 

So, novice question: is there something that is different/needed to make the OS/system wide controls bind up to the media controls verse apps like VLC?

 

 

 

Now THAT's interesting...I had assumed the problem was the input system, but if it works when you bind another key to it, it must be a USB issue instead. I'll look into it some more and see if I find anything. The keyboard isn't in BIOS mode, right?

As far as I know, browsers do not respond to media keys by default. I'm not sure if there's a way to make them do it or not. I've also noticed that starting VLC sometimes stops media keys from working in other apps (both with the Corsair keyboard and others), so that might be related.

Try running this in a terminal:

sudo launchctl load /Library/LaunchDaemons/com.ckb.daemon.plist

 

The installer should set it up to run on boot, but maybe that's not happening for some reason?

 

When I type this in the terminal I get the response

"Operation already in progress"

 

But CKB still says "No devices connected"

 

It used to work that I reinstall CKB everytime I boot up but now that even stopped working lol :confused:

When I type this in the terminal I get the response

"Operation already in progress"

 

But CKB still says "No devices connected"

 

It used to work that I reinstall CKB everytime I boot up but now that even stopped working lol :confused:

 

Ok, sounds like the driver is in fact running. It may be a USB communications error. Can you run the following for me (also Terminal):

 

sudo launchctl unload /Library/LaunchDaemons/com.ckb.daemon.plist
sudo /Applications/ckb.app/Contents/Resources/ckb-daemon

This will start the driver manually so that you can see its output. I'm guessing it will print some errors - copy and paste those here and I'll see what I can make of them.

Keeping getting the following messages in OS X Console

 

29/05/2015 20:34:05.876 LCore[289]: *** locationString is XX-XX-1a-12-10-00

29/05/2015 20:34:13.000 kernel[0]: com_driver_GxxxDriver::probe fails

29/05/2015 20:34:13.000 kernel[0]: com_driver_GxxxDriver::probe fails

29/05/2015 20:34:13.000 kernel[0]: com_driver_GxxxDriver::probe fails

29/05/2015 20:34:13.000 kernel[0]: com_driver_GxxxDriver::probe fails

29/05/2015 20:34:14.000 kernel[0]: IOHIDInterface unsuccessfully requested close of clients: 0xe00002c7

29/05/2015 20:34:14.000 kernel[0]: IOHIDInterface unsuccessfully requested close of clients: 0xe00002c7

 

as well as something similar to the following:

 

too many idle wake ups

.

 

The keyboard keeps alternating between on and off, sometimes reverting to previous modes saved by the previous owner of the keyboard (k95 RGB). Finally it turns off and my laptop packs up. Audio/Video works but I cannot use my keyboard or mouse or touchpad. Any ideas?