Bug 621498 – Corsair RGB Keyboard Fails to Properly Initialize (fix)

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description jonathanmartin6 2017-06-11 11:38:24 UTC]

To the meat of it.

I have the R70 series Corsair RGB keyboard, which typically does not initialize properly under the Gentoo live or install media. I have found a way to do this without Choosing The Impossible, though its fairly ridiculous. 

The procedure is as follows.

Set the polling slider to furthest from "BIOS." Plug in both USB endpoints. Unplug the power-only endpoint. Unplug the data/peripheral endpoint, and reinsert with a bit of repose. If successful, the numlock will register as active after a few seconds.

A few facts. 

The initialization of this keyboard under windos requires that its microcontroller be reset three times because it reports three devices and seemingly does not discriminate on which one takes over the USB channel. Under UBUNTU, I often need to restart three times to get the keyboard itself to register. The kernel-software workaround instead of the PEBKAC rework is not typically possible in systems where this re-cycle does not have an impact. The keyboard retains enough power during erroneous resets that it can retain the pattern broadcast by CUE during the POST, so this fix probably works because it manually triggers the keyboard hardware to reset and become properly detected. I do not know if it is necessary to use USB 2.0 slots to perform this feat, but I did so, and somewhat strangely, it did not affect the keyboard's features as expected. Since this weird hackey-sack-of-cherryMX-trampolines is also a weak implicit keylogger, I can't say I would recommend using it in the first place under a systems culture composed of skilled programmers.

As my other devices are also in strange configurations, the only evidence I have that this procedure is effective is that I am using said keyboard to type this report.

[Comment 1 Jonas Stein 2017-06-11 12:03:53 UTC]

I read your report twice, but did not understand which ebuild is affected and what you exactly report. 

Could you elaborate the report a bit, so that we can hand it over to the corresponding maintainer? Please try to avoid any chitchat, but provide all required facts. 
Please write category/package-version in the beginning of the subject.
https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide