Jump to content
Corsair Logo Corsair Logo
Corsair Community
CORSAIR COMMUNITY Survey, we want to hear your feedback!

Vengeance K90 & Linux

romeodelight

By romeodelight
in Keyboards and Mice

Recommended Posts

SpeedFreak01

SpeedFreak01

Posted
Posted

+1 for linux support, urgently needed.

 

Cant seem to get the k95 RGB to work in linux.

Linux recognises the device, lights turn on, but but none of the keys work.

 

Maybe someone else might have some clues on how to fix this...

Kernal logs, i did a bit of googling but wasnt able to find anything helpful.

 

Oct 28 22:01:48 kernel: [ 2568.488979] usb 5-2: new full-speed USB device number 3 using uhci_hcd
Oct 28 22:01:49 kernel: [ 2569.365029] usb 5-2: New USB device found, idVendor=1b1c, idProduct=1b11
Oct 28 22:01:49 kernel: [ 2569.365034] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 28 22:01:49 kernel: [ 2569.365037] usb 5-2: Product: Corsair K95 RGB Gaming Keyboard
Oct 28 22:01:49 kernel: [ 2569.365040] usb 5-2: Manufacturer: Corsair
Oct 28 22:01:49 kernel: [ 2569.365042] usb 5-2: SerialNumber: <removed>
Oct 28 22:01:49 kernel: [ 2569.574136] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.2/usb5/5-2/5-2:1.0/input/input23
Oct 28 22:01:49 kernel: [ 2569.574482] hid-generic 0003:1B1C:1B11.0007: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard] on usb-0000:00:1a.2-2/input0
Oct 28 22:02:24 kernel: [ 2604.537451] usbhid 5-2:1.1: can't add hid device: -110
Oct 28 22:02:24 kernel: [ 2604.537468] usbhid: probe of 5-2:1.1 failed with error -110
Oct 28 22:02:59 kernel: [ 2639.502083] usbhid 5-2:1.2: can't add hid device: -110
Oct 28 22:02:59 kernel: [ 2639.502099] usbhid: probe of 5-2:1.2 failed with error -110
Oct 28 22:03:34 kernel: [ 2674.466703] usbhid 5-2:1.3: can't add hid device: -110
Oct 28 22:03:34 kernel: [ 2674.466720] usbhid: probe of 5-2:1.3 failed with error -110

 

 

I did manage to build the code located here: https://github.com/jupiter126/Linux_Custom_Control_Device

 

To build it, i had to delete getscancodes.o and edit getscancodes.c to specify the full path to /home/username/path/to/LCCD_core.sh on line 97.

After getscancodes compiled, i was able to detect key presses made on the keyboard.

Even though you cant actually see any of the letters you type appearing in a note pad etc, the getscancodes program was able to detect actual key presses.. translating to unknown numbers.

 

Confirmed the keyboard works fine under windows 7 (i had a spare pc to test with), no real issues at all. Just wish it had nix support.

Link to comment
Share on other sites
  • Replies 86
  • Created
  • Last Reply
CalcProgrammer1

CalcProgrammer1

Posted
Posted
Try a different USB port. My K70 RGB works with Linux on my desktop, but only in a USB 3.0 port. It works fine on my laptop and server for some reason. In all cases it takes 30 seconds or so before it starts providing input as it registers 4 input events according to dmesg. Once it is up you can set the LEDs with the code I wrote on Reddit.
Link to comment
Share on other sites
SpeedFreak01

SpeedFreak01

Posted
Posted
Try a different USB port. My K70 RGB works with Linux on my desktop, but only in a USB 3.0 port. It works fine on my laptop and server for some reason. In all cases it takes 30 seconds or so before it starts providing input as it registers 4 input events according to dmesg. Once it is up you can set the LEDs with the code I wrote on Reddit.

 

My motherboard only supports USB 2.0 so maybe thats part of the problem?

I have tried all available USB ports, tried shutting the PC down and booting from scratch with the keyboard plugged in.

The keyboard seems to work fine in bios, but as soon as linux takes over and starts to boot it takes ages to get past the initial loading stage, and when it does the keyboard still doesnt function correctly.

Other USB keyboards work with no issues.

Link to comment
Share on other sites
SpeedFreak01

SpeedFreak01

Posted
Posted
Did you plug in both plugs or just one? For me it works with just one, but not all ports are the same. It worked on my laptop's USB2.0 port as well as 3.0 and my server's front USB port is 2.0 as well so that alone isn't the issue. What motherboard/computer?

 

I tried plugging in just one port, lights on the keyboard turn on but that's it. Almost seems like it would work but something else is causing an issue. Tried front USB as well.

 

I compiled and tested MSC's unofficial linux driver, but whenever i run the daemon it halts at the exception "Failed to get device info".

 

PC specs

System:    Kernel: 3.17.0-031700-generic x86_64 (64 bit, gcc: 4.8.2) Desktop: N/A Distro: Linux Mint 17 Qiana
Machine:   Mobo: Gigabyte model: EX58-UD5 version: x.x Bios: Award version: F12 date: 03/11/2010
CPU:       Quad core Intel Core i7 CPU 930 (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 22670 
          Clock Speeds: 1: 1596.00 MHz 2: 1596.00 MHz 3: 1596.00 MHz 4: 1596.00 MHz 5: 1596.00 MHz 6: 1596.00 MHz 7: 1596.00 MHz 8: 1596.00 MHz
Graphics:  Card: NVIDIA GF100 [GeForce GTX 480] bus-ID: 02:00.0 
          X.org: 1.15.1 driver: nvidia tty size: 195x57 Advanced Data: N/A for root

Previously i was using a Logitech G19 keyboard with no issues at all.

 

I updated the keyboards firmware using a windows pc, still doesnt work properly.

Short of a re-install of mint, i cant think of much else to try.

 

Appreciate the help.

 

Edit: Xorg logs dont seem to indicate any issues either.

 

[   109.039] (II) config/udev: Adding input device Corsair Corsair K95 RGB Gaming Keyboard (/dev/input/event6)
[   109.039] (**) Corsair Corsair K95 RGB Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
[   109.039] (II) Using input driver 'evdev' for 'Corsair Corsair K95 RGB Gaming Keyboard'
[   109.039] (**) Corsair Corsair K95 RGB Gaming Keyboard: always reports core events
[   109.039] (**) evdev: Corsair Corsair K95 RGB Gaming Keyboard: Device: "/dev/input/event6"
[   109.039] (--) evdev: Corsair Corsair K95 RGB Gaming Keyboard: Vendor 0x1b1c Product 0x1b11
[   109.039] (--) evdev: Corsair Corsair K95 RGB Gaming Keyboard: Found keys
[   109.039] (II) evdev: Corsair Corsair K95 RGB Gaming Keyboard: Configuring as keyboard
[   109.039] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input9/event6"
[   109.040] (II) XINPUT: Adding extended input device "Corsair Corsair K95 RGB Gaming Keyboard" (type: KEYBOARD, id 12)
[   109.040] (**) Option "xkb_rules" "evdev"
[   109.040] (**) Option "xkb_model" "pc105"
[   109.040] (**) Option "xkb_layout" "us"

 

Any idea what version of evdev you are running? Im using version: 1:2.8.2-1ubuntu2, seems there are later builds out but im not sure how i would go about configuring those for my current setup. Not sure if it would make a difference either.

Link to comment
Share on other sites
SpeedFreak01

SpeedFreak01

Posted
Posted

So.. bit of an update.

 

Tried updating my kernel, still didnt work.

Tried a few suggestions from people who had usb hotplug issues on linux, still no dice.

Downloaded a linux mint installation iso and booted into that, keyboard still didn't work.

 

Out of sheer desperation to get this working i remembered reading somewhere in this forum some guy had to unplug everything from his pc, power cord etc. give it a few secs, then plug everything back in.

 

Funnily enough, that seems to have done the trick. :(

 

Cant say how long this will work though, very hesitant to touch the G keys in case i cant get basic functionality back.

Link to comment
Share on other sites
  • 5 months later...
Clément

Clément

Posted
Posted

Hello everyone.

 

I would like what is the state of Linux support for the K90. Is there anyone working on drivers or documentations?

 

I have been doing some input device hacking recently and I feel like I could help.

 

I had a quick look at the HID reports from the keyboard and I saw that the main problem is that the special keys are sending weird keyboard usage and the generic linux driver misused them. I guess this could be fixed with a simple specific HID driver but I would not know to what to bind them.

Link to comment
Share on other sites
  • 4 months later...
b.wehan

b.wehan

Posted
Posted

Ummm, this is my third attempt at bumping this thread. i am slightly upset that my 1.5 hours of writing have gone into a black hole of bad server/code organization.

 

+1 for linux support, it is worth it read previous posts that give very good level headed arguments

 

Subrazaiden3

Xaeros

eeg

Link to comment
Share on other sites
Clément

Clément

Posted
Posted
There is a driver for linux is the two posts just above yours. You can choose in patch form (post from 08-29-2015) or as an independent kernel module (post from 04-18-2015, git repo is up to date). The independent module cannot automatically replace the hid-generic driver, so you have to unbind it yourself.
Link to comment
Share on other sites
Clément

Clément

Posted
Posted

I have posted a new patch to the kernel mailing list: http://www.spinics.net/lists/kernel/msg2070218.html.

 

This version remove the ABI for writing profiles. It was bad anyway and I wrote a userspace program for sending them: https://github.com/cvuchener/k90-send-profile. It does not rely on any special driver, it just sends some control packet through libusb.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...