(Unofficial) Linux / OSX Driver

[AkAntA]

"Operation not permitted" probably? Usually means there was a problem talking to the keyboard. Try the troubleshooting section and see if that fixes it.

 

It seemed to be the problem with talking. It works now :cool: Altough I'm not sure the troubleshoot suggestion (cmdline add) had anything to do with solving this problem. Also not sure if you had said it anywhere in the instructions but removing the keyboard from USB3.0 to USB2.0 solved the problem.

 

Edit: Oh yeah, thanks for the great work. This driver is amazing

Edited April 22, 2015 by AkAntA

[MSC]

Awesome B)

 

Yeah, I thought I had added something to the readme about USB3 ports, but I guess I forgot to. Well, it's up there now. Glad you got it working!

[LnL_]

Hi guys :)

 

Wondering if it's possible to use macros with the G-keys in the K95 RGB keyboard?

 

Thanks,

LnL_

[PlqnctoN]

Here's for you 8W7513500C383851L, to grab a beer and relax for a bit :)

Thank you for this, this is freaking awesome!

Looking forward to see other improvements, even if it already works like a charm and I'm really impressed by the GUI :)

 

Just a little thing, maybe I'm doing something wrong, but even if I check the option "start ckb at login" it won't start at login, I'm using Fedora 21 (up to date, w/ NVIDIA proprietary drivers) with GNOME environment.

 

EDIT : Nevermind, just rebooted and ckb is launching after login !

Edited April 24, 2015 by PlqnctoN

[MSC]

Hi guys :)

 

Wondering if it's possible to use macros with the G-keys in the K95 RGB keyboard?

 

Thanks,

LnL_

 

It is! The functions are somewhat limited at the moment (you can rebind them to a different key on the keyboard, or launch a custom program) but the keys are usable.

 

Here's for you 8W7513500C383851L, to grab a beer and relax for a bit :)

Thank you for this, this is freaking awesome!

Looking forward to see other improvements, even if it already works like a charm and I'm really impressed by the GUI :)

 

Just a little thing, maybe I'm doing something wrong, but even if I check the option "start ckb at login" it won't start at login, I'm using Fedora 21 (up to date, w/ NVIDIA proprietary drivers) with GNOME environment.

 

EDIT : Nevermind, just rebooted and ckb is launching after login !

 

Thanks :)

If for any reason it stops launching at login, you can add it manually (add "ckb --background" in your startup settings) and that should work as well.

 

 

Quick PSA for everyone: the new v1.20 firmware has launched. It comes with a new USB protocol which (hopefully) will fix a lot of the issues people have been experiencing with it. I've already added the necessary code to ckb and updated the firmware tables. HOWEVER,

 

Do not upgrade to firmware 1.20 unless you are running ckb beta-v0.1.2 or higher. Earlier versions are not compatible and will not work with an updated keyboard.

 

Once you've installed the latest version you can go ahead and update. :) ckb should offer to do so automatically, if you have the feature enabled. You can also update the keyboard from CUE in Windows (I recommend the latter if you've been having connection issues - don't want any bricked keyboards!) Thanks.

 

EDIT: I've uploaded a new OSX binary, so those of you who use it can upgrade your firmwares now. I made it into a pre-packaged installer so you don't have to set up the driver manually anymore - hopefully I did everything right, let me know if the installer doesn't work for any reason.

Edited April 25, 2015 by MSC

[JellyUK]

Do not upgrade to firmware 1.20 unless you are running ckb beta-v0.1.2 or higher.

 

Well, I did exactly that, noticed the update when using the keyboard in windows, updated without thinking. So impressed that you have released such an easy to install mac package, worked perfectly once installed! Also thank **** for keyboard viewer, useful if you need to complete the installation without a working keyboard.

 

What's the best way to send you a few drinking vouchers?

[CorpNewt]

The new version seems to be working just fine after the firmware upgrade... I feel like I'm blind though, I'm on Mac OS 10.10.3 and I can't for the life of me find anything that states to start at login... I had been running it with the standard launch at login option using the user settings in the system preferences application which works okay, but it always starts with the window front and center. I'm going to try and delete everything, and set it up from scratch and see if that helps.

[CorpNewt]

Hmm, got it fixed by using the quickinstall script. I had been just building ckb and switching everything out. Guess that's that!

 

Edit:

 

I did notice a new issue though. I use an M-Audio M-Track usb audio interface, and I can't have it plugged in to the usb port next to the one I use for the keyboard since this last update.

 

If U = Empty USB slot, K = Keyboard and M = M-Track:

 

U U

K M

U U

 

Doesn't work, but ANY combination that puts the keyboard and M-Track in different rows does. For example:

 

K U

U M

U U

 

Does work. Not sure why this might be? I have enough usb ports to get by with moving things around, but it's still kind of a weird phenomenon. Let me know if you need more info!

Edited April 25, 2015 by CorpNewt

[PlqnctoN]

Hey! Just tried to install it on a freshly installed Ubuntu 15.04 and it failed at the installation of the driver as a startup service.

 

Here's the output of the script :

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
Failed to execute operation: Not a directory

Press enter to exit.

 

So I checked the script and it appears to fail at this line (135) :

sudo systemctl enable ckb-daemon 2>$TMPFILE

 

When executed manually :

http://i.imgur.com/JB1yKtd.png

 

Here's is the file 'system' :

http://i.imgur.com/K7b942u.png

 

I don't know how systemd works so I'm not able to help you more on this :(

[MSC]

Well, I did exactly that, noticed the update when using the keyboard in windows, updated without thinking. So impressed that you have released such an easy to install mac package, worked perfectly once installed! Also thank **** for keyboard viewer, useful if you need to complete the installation without a working keyboard.

 

What's the best way to send you a few drinking vouchers?

 

There are paypal and bitcoin donations links on the github page :)

 

The new version seems to be working just fine after the firmware upgrade... I feel like I'm blind though, I'm on Mac OS 10.10.3 and I can't for the life of me find anything that states to start at login... I had been running it with the standard launch at login option using the user settings in the system preferences application which works okay, but it always starts with the window front and center. I'm going to try and delete everything, and set it up from scratch and see if that helps.

 

Hmm, got it fixed by using the quickinstall script. I had been just building ckb and switching everything out. Guess that's that!

 

Edit:

 

I did notice a new issue though. I use an M-Audio M-Track usb audio interface, and I can't have it plugged in to the usb port next to the one I use for the keyboard since this last update.

 

If U = Empty USB slot, K = Keyboard and M = M-Track:

 

U U

K M

U U

 

Doesn't work, but ANY combination that puts the keyboard and M-Track in different rows does. For example:

 

K U

U M

U U

 

Does work. Not sure why this might be? I have enough usb ports to get by with moving things around, but it's still kind of a weird phenomenon. Let me know if you need more info!

 

I should have mentioned - it only displays the "start at login" option if you've installed it system-wide (the setting doesn't work otherwise). So yeah, quickinstall is the way to go.

 

My guess would be that the USB rows are on different internal hubs, or something to that effect. Might be some kind of bandwidth/power issue with having both of them on the same slot, probably related to the new protocol.

 

Hey! Just tried to install it on a freshly installed Ubuntu 15.04 and it failed at the installation of the driver as a startup service.

 

Fixed now - see my reply here: https://github.com/ccMSC/ckb/issues/55#issuecomment-96352567

You'll need to download the latest version from the main page, then run the command I mentioned and try the quickinstall again. Should work this time.

[CorpNewt]

Cool! Thanks for the response. I'll let you know if I find anything else!

[robbob2112]

and now I am running on firmware 1.20 with your beta 1.3 software... Seems like the long delay on boot is gone

 

Here is the dmesg

$ dmesg | egrep -i 'corsair|hid'

[ 0.512391] hidraw: raw HID events driver © Jiri Kosina

[ 0.512531] usbcore: registered new interface driver usbhid

[ 0.512532] usbhid: USB HID core driver

[ 1.265361] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard

[ 1.265362] usb 5-1.3: Manufacturer: Corsair

[ 1.267223] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0001/input/input6

[ 1.317769] 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

[ 1.701007] 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

[ 11.318946] hid-generic 0003:1B1C:1B11.0002: usb_submit_urb(ctrl) failed: -1

[ 11.318962] hid-generic 0003:1B1C:1B11.0002: timeout initializing reports

[ 11.319373] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0002/input/input8

[ 11.369955] 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

[ 21.371125] hid-generic 0003:1B1C:1B11.0004: timeout initializing reports

[ 21.371371] 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

[ 31.372099] hid-generic 0003:1B1C:1B11.0005: usb_submit_urb(ctrl) failed: -1

[ 31.372127] hid-generic 0003:1B1C:1B11.0005: timeout initializing reports

[ 31.372340] 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

[MSC]

Awesome! Let me know if you find any other developments :)

[dr_rgb]

Awesome! Let me know if you find any other developments :)

MSC sorry for the ignorance, maybe this subject has been touched but way to many posts. Is there any software i can use for the m65 rgb mouse so i can change the colors etc.. Runing on Macbook pro 2014

[MSC]

I'm actually working on M65 RGB support...it's going to be a few weeks before it gets into the stable version, but it's coming! I'll post an update once I have a testing version for it.

[svanheulen]

I'm having an issue getting usbhid quirks working. I have both the K70 and the M65. Here's my modprobe config file:

options usbhid quirks=0x1B1C:0x1B12:0x20000000
options usbhid quirks=0x1B1C:0x1B13:0x20000000

 

So with this config, the M65 (0x1B12) still gets the error on boot but the K70 (0x1B13) does not. And if I swap the order in the config, then the opposite happens.

 

So I'm guessing that setting the option twice just overwrites the previous option. Does anyone know how to set the quirk on both devices properly?

[MSC]

Correct, the second will overwrite the first. You have to use commas, like so:

 

options usbhid quirks=0x1b1c:0x1b12:0x20000000,0x1b1c:0x1b13:0x20000000

[svanheulen]

Correct, the second will overwrite the first. You have to use commas, like so:

 

options usbhid quirks=0x1b1c:0x1b12:0x20000000,0x1b1c:0x1b13:0x20000000

 

Excellent, that worked. Thanks!

[MSC]

Hey everyone, I'm rolling out M65 support in the [testing] repo right now! It's Linux-only at the moment and VERY incomplete, but give it a try if you're feeling brave. I'll be updating it with new features over the next few weeks and I'll merge the changes into [master] once they're production-ready.

[robbob2112]

Something new...weird, so of course windows is involved...

 

If I boot into window everything there works fine... then when I boot back into Linux the keyboard hang on boot is back... but only on the first boot back from windows... reboots after that have the typical forever hang until the keyboard is unplugged on shutdown, but boots straight back up with no issues... So, seems to me the 'new' windows driver is leaving the keyboard with something gimped up and once it loads things are corrected..

 

~ $ dmesg | egrep -i 'hid|corsair'

[ 0.512458] hidraw: raw HID events driver © Jiri Kosina

[ 0.512595] usbcore: registered new interface driver usbhid

[ 0.512597] usbhid: USB HID core driver

[ 1.266869] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard

[ 1.266870] usb 5-1.3: Manufacturer: Corsair

[ 1.268431] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0001/input/input6

[ 1.319045] 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

[ 1.705072] 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

[ 11.320232] hid-generic 0003:1B1C:1B11.0002: usb_submit_urb(ctrl) failed: -1

[ 11.320258] hid-generic 0003:1B1C:1B11.0002: timeout initializing reports

[ 11.320669] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0002/input/input8

[ 11.371105] 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

[ 21.372281] hid-generic 0003:1B1C:1B11.0004: timeout initializing reports

[ 21.372679] 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

[ 28.359134] 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

[ 31.981245] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard

[ 31.981247] usb 5-1.3: Manufacturer: Corsair

[ 31.983113] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0006/input/input18

[ 32.034462] 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

[ 42.035455] hid-generic 0003:1B1C:1B11.0007: usb_submit_urb(ctrl) failed: -1

[ 42.035477] hid-generic 0003:1B1C:1B11.0007: timeout initializing reports

[ 42.035918] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0007/input/input19

[ 42.086790] 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

[ 52.087609] hid-generic 0003:1B1C:1B11.0008: timeout initializing reports

[ 52.087970] hid-generic 0003:1B1C:1B11.0008: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2

[ 62.088738] hid-generic 0003:1B1C:1B11.0009: usb_submit_urb(ctrl) failed: -1

[ 62.088762] hid-generic 0003:1B1C:1B11.0009: timeout initializing reports

[ 62.089097] hid-generic 0003:1B1C:1B11.0009: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3

[pcb]

Hey MSC,

 

I just got a K95 for my iMac, and I'm looking forward to it supporting the assignment of modified keys (like CMD-H) to one of the keyboard's G keys. Kudos to you for this pretty amazing driver -- I just sent you five bucks on Github to show my appreciation. Please keep up the great work!

 

P.

[MSC]

Something new...weird, so of course windows is involved...

 

If I boot into window everything there works fine... then when I boot back into Linux the keyboard hang on boot is back... but only on the first boot back from windows... reboots after that have the typical forever hang until the keyboard is unplugged on shutdown, but boots straight back up with no issues... So, seems to me the 'new' windows driver is leaving the keyboard with something gimped up and once it loads things are corrected..

 

~ $ dmesg | egrep -i 'hid|corsair'

[ 0.512458] hidraw: raw HID events driver © Jiri Kosina

[ 0.512595] usbcore: registered new interface driver usbhid

[ 0.512597] usbhid: USB HID core driver

[ 1.266869] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard

[ 1.266870] usb 5-1.3: Manufacturer: Corsair

[ 1.268431] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0001/input/input6

[ 1.319045] 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

[ 1.705072] 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

[ 11.320232] hid-generic 0003:1B1C:1B11.0002: usb_submit_urb(ctrl) failed: -1

[ 11.320258] hid-generic 0003:1B1C:1B11.0002: timeout initializing reports

[ 11.320669] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0002/input/input8

[ 11.371105] 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

[ 21.372281] hid-generic 0003:1B1C:1B11.0004: timeout initializing reports

[ 21.372679] 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

[ 28.359134] 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

[ 31.981245] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard

[ 31.981247] usb 5-1.3: Manufacturer: Corsair

[ 31.983113] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0006/input/input18

[ 32.034462] 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

[ 42.035455] hid-generic 0003:1B1C:1B11.0007: usb_submit_urb(ctrl) failed: -1

[ 42.035477] hid-generic 0003:1B1C:1B11.0007: timeout initializing reports

[ 42.035918] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0007/input/input19

[ 42.086790] 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

[ 52.087609] hid-generic 0003:1B1C:1B11.0008: timeout initializing reports

[ 52.087970] hid-generic 0003:1B1C:1B11.0008: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2

[ 62.088738] hid-generic 0003:1B1C:1B11.0009: usb_submit_urb(ctrl) failed: -1

[ 62.088762] hid-generic 0003:1B1C:1B11.0009: timeout initializing reports

[ 62.089097] hid-generic 0003:1B1C:1B11.0009: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3

 

Unfortunately I've noticed this with the Linux driver too - it seems to be fine after a cold boot, but a warm restart sometimes makes it act up. I'm hoping it can be solved by a firmware update.

 

Hey MSC,

 

I just got a K95 for my iMac, and I'm looking forward to it supporting the assignment of modified keys (like CMD-H) to one of the keyboard's G keys. Kudos to you for this pretty amazing driver -- I just sent you five bucks on Github to show my appreciation. Please keep up the great work!

 

P.

Thanks :)

 

Macros are my next priority after the M65. After that I'll be doing CUE profiles and then I'll probably call the driver done. I'll post updates here as I'm working on them.

[iamtheram]

Hello,

 

First of all, thank you for this driver. If it wasn't for this, I wouldn't be able to use my new k95 I bought recently. I have been able to use it on Linux Mint and Ubuntu based systems quite well, but it requires USB3.0 not USB2.0 to work on my computer for some reason, luckily I have both.

 

I am commenting about using it on Korora, a spin of Fedora, however. I'm having a really hard time getting the software to even run. It just tells me there was a problem trying to run it.

 

I installed it via the quickinstall option that comes inside the folder after I extract the zip. I have all dependencies installed properly, it took a few times (I broke the partition a few times while doing it before, but I figured out what I did and reinstalled and tried again).

 

Any idea why it won't run the software for this? I can't get it to run at all, just errors on me. I love the Gnome Desktop but there is no Linux Mint edition with Gnome 3.14-16 available... so I'm stuck with using something that has it, like Fedora/Korora. I chose Korora because it's essentially Fedora but with all the essential software I'd want to use to make installing things a little easier.

 

If you could find the time to assist me with this, I'd very much appreciate it. If there is anything I need to, or could do in return I'm willing if I'm capable. I just want it to work on RPM based systems as well. I would definitely try a Gnome version of Linux Mint if it was available, because it works very well there and I really like Mint, but I prefer the Gnome desktop and when I try to install that desktop there I get nothing but problems, because it's not integrated into it.

 

I'm still kind of new to GNU/Linux. I've only been using distros for maybe 6 months now. I've hopped around trying to find the one for me and I love Mint, but can't get Gnome to work well with it, so I'm just going to keep using something with Gnome like Korora/Fedora.

 

EDIT: I ran it in the terminal just now instead to see what it will report to me and it spit this out: bash: /home/Russ/Documents/ckb-master/usr/ckb.desktop: Permission denied

 

I do not know why it's basically telling me 'I'm not allowed'... I am administrator, and I ran it through root in the terminal.

 

Thank you for your time.

Edited May 8, 2015 by iamtheram
Tried it in the terminal and wanted to report what it spit out afterwards.

[robbob2112]

Did you check if you have SElinux enabled? (hint all flavors of Fedora come with it enabled by default)

 

as root

# getenforce

Enforcing

 

 

if it is enabled try switching it to permissive mode

# setenforce permissive

 

# getenforce

Permissive

 

 

There is a whole debate about leaving SELinux on or off... I tend to leave it on and make modules as needed... lots of people turn it off... Best bet _if_ the above works and this is just a desktop and behind firewalls and such is leave it in permissive mode...

 

to leave it permanently in permissive mode edit /etc/selinux/config and change from enforcing to permissive and reboot.... if you just disable it (same file) it can be painful to go back so permissive is better...

 

If you want instructions on making modules and leave it on, google for it or ask and I can post a down and dirty crib sheet for you.

 

Robert

 

Hello,

 

First of all, thank you for this driver. If it wasn't for this, I wouldn't be able to use my new k95 I bought recently. I have been able to use it on Linux Mint and Ubuntu based systems quite well, but it requires USB3.0 not USB2.0 to work on my computer for some reason, luckily I have both.

 

I am commenting about using it on Korora, a spin of Fedora, however. I'm having a really hard time getting the software to even run. It just tells me there was a problem trying to run it.

 

I installed it via the quickinstall option that comes inside the folder after I extract the zip. I have all dependencies installed properly, it took a few times (I broke the partition a few times while doing it before, but I figured out what I did and reinstalled and tried again).

 

Any idea why it won't run the software for this? I can't get it to run at all, just errors on me. I love the Gnome Desktop but there is no Linux Mint edition with Gnome 3.14-16 available... so I'm stuck with using something that has it, like Fedora/Korora. I chose Korora because it's essentially Fedora but with all the essential software I'd want to use to make installing things a little easier.

 

If you could find the time to assist me with this, I'd very much appreciate it. If there is anything I need to, or could do in return I'm willing if I'm capable. I just want it to work on RPM based systems as well. I would definitely try a Gnome version of Linux Mint if it was available, because it works very well there and I really like Mint, but I prefer the Gnome desktop and when I try to install that desktop there I get nothing but problems, because it's not integrated into it.

 

I'm still kind of new to GNU/Linux. I've only been using distros for maybe 6 months now. I've hopped around trying to find the one for me and I love Mint, but can't get Gnome to work well with it, so I'm just going to keep using something with Gnome like Korora/Fedora.

 

EDIT: I ran it in the terminal just now instead to see what it will report to me and it spit this out: bash: /home/Russ/Documents/ckb-master/usr/ckb.desktop: Permission denied

 

I do not know why it's basically telling me 'I'm not allowed'... I am administrator, and I ran it through root in the terminal.

 

Thank you for your time.

Edited May 8, 2015 by robbob2112

[iamtheram]

Did you check if you have SElinux enabled? (hint all flavors of Fedora come with it enabled by default)

 

as root

# getenforce

Enforcing

 

 

if it is enabled try switching it to permissive mode

# setenforce permissive

 

# getenforce

Permissive

 

 

There is a whole debate about leaving SELinux on or off... I tend to leave it on and make modules as needed... lots of people turn it off... Best bet _if_ the above works and this is just a desktop and behind firewalls and such is leave it in permissive mode...

 

to leave it permanently in permissive mode edit /etc/selinux/config and change from enforcing to permissive and reboot.... if you just disable it (same file) it can be painful to go back so permissive is better...

 

If you want instructions on making modules and leave it on, google for it or ask and I can post a down and dirty crib sheet for you.

 

Robert

 

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.