K90 issues on Linux (64-bit)

[jupiter]

Re, the script is going forward well, I just hit a few unexpected issues, nothing to worry about. I hope... I will be able to post a half-decent version (with comments and examples) tomorrow.

For your questions:

- Is it possible somehow to use the G-keys for binds in games?

As my script is a level below, it should be possible to simulate a combination of keystrokes (up, up, down, left, a, wait 3 seconds, space, space, p, ...), although this is at system level, so I'm not sure (I didn't try it). Again, here you might give xmacro or xsendkeycode a try for a small shellscript.

- Is there a keycode for the 'disable windows-key'-key, or is it handled internally in the keyboard?

xev reports a keycode 115, so this is a native keyboard key (not on the same event interface as the g keys).

- How do you estimate the chance of getting to control the keyboards backlight and other features?

Here the backlight works as expected with the backlight key. For what I see, this is controlled internally by the keyboard (thus no controlling trough the OS).

- Did you adjust swm's xorg.conf much to fix the ALT issue (switching terminals)? If so, could you post your edits please?

I adjusted my xorg.conf with swm's fix, but my xorg.conf is completely handcrafted, so few are the chances that it's compatible with your setup. Note that there is still one extra issue I need to solve there too, as smv's fix broke my mouse's 'next' and 'previous' buttons. Anyway, it's here: xorg.conf

- Do you experience any other out of the ordinary issues on Linux?

The G9, G17 and G18 buttons send signal on the 2 channels, making them quite buggy (ex: G17 is like play/pause and G18 is like stop). This means I won't use them in my script - we're left with a total of 21 signals to customize from :)

EDIT:
I just found out that cron only allows per minute granularity, this will make it hard to use this script for gaming purposes (unless if you can wait one minute per executer command). It is possible to attain more granularity by combining multiple cron jobs & sleep, but there is no clean way to do it that way.
Live use should be possible by taking the input from an alternate way, I might look into this for a further version. (I tried to get a bit of modularity in the script)

[jupiter]

Re,

So far so good, RC3 run quite smootly, tell me what you think about.

https://github.com/jupiter126/k90-test

Looking forward for some feedback ;)

[Hell4You]

I will respond to your answers on my questions and review your script this week-end. Quick peek: nice job.

Edit:

About your answers to my questions:

Here the backlight works as expected with the backlight key. For what I see, this is controlled internally by the keyboard (thus no controlling through the OS).

The backlight actually works as expected, sure, but I know the windows drivers can control the intensity by using the official Corsair software. I suppose they are not prepared to just hand over the protocol so it's a (low priority) possibility to sniff the usb traffic and figure it out on our own

I adjusted my xorg.conf with swm's fix, but my xorg.conf is completely handcrafted, so few are the chances that it's compatible with your setup. Note that there is still one extra issue I need to solve there too, as smv's fix broke my mouse's 'next' and 'previous' buttons. Anyway, it's here: xorg.conf

Doesn't your Xorg work out of the box? The latest versions should, but you'll need customizations when using proprietary drivers. I'll try the fix at a later time.

(ex: G17 is like play/pause and G18 is like stop)

This behaviour is exactly the same here, but somehow Corsair managed to keep them apart. Maybe worth looking into when the rest is finished ;)

I reviewed your script:

• The script also depends on x11-apps/xhost
• Line 148: You should use $(dirname $0) to determine the directory
• Line 182: You could use user=${USER} or possibly ${SUDO_USER}
• It would be better if all the parameters where on top, or where in a config file. Remember most people are lazy and they just want a quick start. When it doesn't work, most will abandon it and only some of them will actually read what you typed. Nonetheless, good documentation is essential.
• Personally, I would figure that there must be some way in linux to directly listen to the events and immediately take action, instead of waiting for a while. In my opinion, cronjobs are not the way to tackle this issue. Maybe this would help: http://stackoverflow.com/questions/1...le-application As you can simulate keypresses of keys that aren't actually on the keyboard (F13, F14 ..), or maybe there actually are events for Gxx keys!? Could possibly also help with the bind keys in games issue. Don't take this as the only solution: There may be even better ways to solve this!
• You even managed to add some of the questions I had to the script! Great!

Finally I must say I really appreciate your efforts and your doing the open source community and of course also Corsair a great favor. They should be grateful. Thanks!

[jupiter]

Sent from my mobile on holliday, i'll be brief.

Tnx for the feedback,

1. I'll update the code with proposed changes as soon as back from holliday, tnx for the code review.

2. I agree getting the usb codes wiretapping windows usb would indeed be the easiest way of getting the low level control codes, unfortunately I don't know the fragile OS well enoigh to do so.

3. I have some trouble with parameter order as some require functions to be initialised.. I'll try to work on conf file when I'm back.

4. Just before leaving, I tested to solve the cron issue. It should be easy to replace with a tail function, but I'm planning to leave the cron possibility as well, as it is usefullto be able to cancel for sysadmin.

5. For the G9 17 18 issues, I believe the solution woud require multiplexing events, but also to disable X listening for some inputs on its keyboard event.

6. My xorg works on default, but does not function with dual display by default.

Tnx again for feedback, I'll be back next week.

[MadMax1963]

I'm about to order a K60 does anyone know if this keyboard has any issues with Linux??? I'm using Zorin OS 6 but might switch to Mint 13.

[Hell4You]

The basic functions probably do work as advertised, but you will most likely also experience (some) issues discussed in the topic start.

Edit:
As the K60 does not have G-keys, you dont have to worry about that so I guess you're good to go.

[MadMax1963]

Originally Posted by Hell4You

The basic functions probably do work as advertised, but you will most likely also experience (some) issues discussed in the topic start.

Edit:
As the K60 does not have G-keys, you dont have to worry about that so I guess you're good to go.

Thanks for your heads up !!! Was actually thinking of ordering the K90 mostly cause of the blue back lights since I don't use the G keys (mostly play FPS games) but then again I would be paying for features that I don't use, in the end I think the k60 is a better buy in my case(no blue lights though ).

[jupiter]

I've changed the variables you pointed me and did a separate conf file.

I'm working towards gaming mode support, although this implies some major changes in the code...
I thus pushed the actual changes as version 1.0 (check github) and just started working on version 1.5 with.

In this version I'm trying to get a separate file for each layout, as well as the said real time mode implemented.

edit:
just pushed 1.6 ... code has been heavily reflifted, it's a dev release and is still a bit incomplete

[jupiter]

Hi, I recently stumbled across the exact same issue with my mouse (razer imperator), and as expected, this scripts allows me to catch the clicks that go on another /dev/eventxx than the usual mouse clicks.

I thus decided to rename the git repo to be more general than just K90 bound.
Please update your links to
https://github.com/jupiter126/Linux_...Control_Device

[vaughnd]

Has anyone found a solution to the "|\" issue? I also run into problems typing | followed by a space, I end up with "|| |" or something random if I type too quickly. No problems in windows of course.

[gnarlium]

I too have the "|\" issue - I thought this was just me but I have the exact same behavior as described by Hell4You. I also am experiencing the sticking keys issue across the board.

[subraizada3]

|\ issue present for me too, in Ubuntu 12.04, 13.04, Mint 13/14, Backtrack 5r3, and Arch.