Lauwenmark

I finally found what was causing my mapping issue. There is a bug in current versions of Xorg preventing it to properly apply XkbLayout directives to keyboards recognized both as pointer and keyboard devices. This will thus happen to anyone using those keyboards with non-us layouts. Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=49950 . The patch in the bug report ( https://bugs.freedesktop.org/attachment.cgi?id=95117 ) was tested and indeed solves the issue I had with my K95 RGB. I suggest adding a reference to that patch in the ckb documentation, as this bug affects any non-us K95 Linux user (and I guess other Kxx keyboards are affected as well). On debian-based (ubuntu, etc) distributions, here's how to rebuild Xorg packages solving the bug: 1. Download the patch mentioned above, and save it into a file (for example /tmp/xorg.patch); 2. Download the source package with: apt-get source xserver-xorg-dev This will create a subdirectory in your current directory. On my system, it was called "xorg-server-1.16.4/" 3. Move into that newly created directory: cd xorg-server-1.16.4 4. Get build dependencies with: apt-get build-dep xserver-xorg-dev 5. Apply the patch with: patch -p1 < /tmp/xorg.patch 6. Install what's needed to rebuild the package: sudo apt-get install build-essential fakeroot devscripts 7. Rebuild it: debuild -b -uc -us 8. This will generate several packages on the upper directory level (cd ..). Install those you need, replacing those you had: dpkg -i xserver-common*.deb xserver-xorg-core*.deb (I only needed those two, but check if you don't use the others yourself !) And restart your X server, or reboot your system if you prefer. Hope this helps !

I do agree. Though the symptom suggests that for some reason, X is not applying the layout despite telling it is, and only does so with the K95, and not with any of the other 3 keyboards I tried, all on the same usb port. True, but my problem happens even before any DE is loaded. Any connection manager that doesn't explicitely set a layout different from the default one selected by X (this is the case for xdm, slim and others by default) uses it. Same for twm or fvwm, or even more complex ones like kde without an explicit keyboard layout defined. rules: evdev model: pc105 layout: fr variant: latin9 Yet qwerty is how the keyboard behaves! You are riht. The oss is a leftover from the many config attempts and tests I made. This should and was normally "latin9". In any case, end result was the same.

Hi, I have a Corsair K95 RGB with a French AZERTY layout. I set up a fresh Debian/Jessie installation. In the console, no problem - the keyboard is properly assigned the fr layout. But in X, it doesn't - instead, it is given a QWERTY/us one. xorg configuration file: http://paste.ubuntu.com/12962664/ /etc/default/keyboard file: http://paste.ubuntu.com/12959295/ Xorg log file: http://paste.ubuntu.com/12959220/ udevadm info reports for the two /dev/input/eventX created for K95: http://paste.ubuntu.com/12959240/ and http://paste.ubuntu.com/12959257/ . From the Xorg logfile, I can see that the keyboard event devices are indeed passed the option "xkb_layout=fr" (lines 217 and 241). Yet the keyboard is still in qwerty mode. If I plug another keyboard instead of the K95, I get the proper "fr" mapping in X. If I plug the K95 alongside another keyboard and start X, I get a qwerty layout on the K95. But if I then type even a single letter on the other keyboard, the K95 gets into an azerty layout. http://paste.ubuntu.com/12963232/ is the xev output from typing the "a" letter on the K95. The first entry is when I typed the letter before touching the other keyboard; the second is when I typed the same letter after touching the other keyboard. I don't understand anything at all. This is obviously related to the K95 itself, as it doesn't happen with other keyboards. Installing the ckb driver presented here doesn't solve the issue. So what's going on? Anyone got an idea?

I'm not using the macro keys. It freezes only when using the standard keys. It is also freezing when using the ckb driver. I've tried setting the keyboard to its min. polling rate, and it didn't solve the issue.

Yes, this is the latest firmware version available at this time of writing. I'm not using animations. This happens with the keyboard in a plain boring state with fixed keys lightning (or even with lightning turned off). I'm just trying to use it as a standard keyboard. So, I'm screwed and I bought a costly keyboard that isn't reliable enough for typing. That's bad news indeed.

Hello, See http://forum.corsair.com/v3/showthread.php?t=142504 - basically, after a random amount of time, the keyboard stops responding. Tried on USB2 and USB3 ports, with or without hub; no luck. Zero message in logs or dmesg. lsusb still shows the keyboard as connected. So far, the only way I could reactivate the keyboard was by unplugging and plugging it back. Tried both with Debian Jessie default kernel (3.16) and a vanilla 4.1.1 one. This is driving me nuts. Any idea? Help?