Comment 28 for bug 1678477

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.