Public bug reported:
Related to bug:
https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477
Support for Corsair Strafe RGB was added, but the Corsair Strafe
monochrome keyboard has a different device ID and isn't covered by the
RGB fix.
Quote from other user:
"I'm using a slightly different variant of this keyboard - Corsair Strafe
(without RGB; product ID is 1b15). I had more or less the same problem (error
-110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every
time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and
after applying this change it worked 10 out of 10 reboots (I also get this new
message during boot, like others did before - "couldn't find an input interrupt
endpoint").
As this keyboard has a different product ID (but the same vendor ID), it
will probably require additional entry in the drivers/usb/core/quirks.c
Please let me know if you need any additional info or tests from me."
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718703
Title:
Kernel support for Corsair Strafe monochrome keyboard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
