Corsair K70 RGB Malfunctioning

Question

I got the new Corsair K70 RGB keyboard in early September, and I've been struggling with Linux compatibility ever since.
The keyboard usually works fine in Windows, with a couple of very irregular glitches, and it works as well in grub. My Arch setup uses dm-crypt with LUKS for an encrypted root disk, so I enter a password at boot. Typically, the keyboard isn't functioning at this point. After I select Arch linux in grub, the key backlights go black and none of the keys seem to have any effect. If I wait at the password prompt, the system throws out intermittent error messages. Once I enter the prompt and the system gets to my greeter (sddm), the keyboard may or may not be working. Some of the time, the keyboard will light up, but if I try to type my password (or, if I disable my desktop manager, my username), it starts repeating the first character I type over and over and over again. I can sometimes get it working at this point by unplugging both USB connections (yes, this keyboard has two for some reason), and plugging them back in, but that's by no means foolproof. When I reach the greeter, the keyboard might simply continue not working, in which case it starts working when I successfully authenticate.
Anecdotally, it seems like these keyboard problems manifest more often when I've just switched over from Windows, but that could just be a red herring.
I've tried removing other peripherals to isolate the issue, which has no effect on whether or not the keyboard works. I've tried moving the keyboard module to before the encrypt module in my initcpio, which only delays the encrypt prompt, and similarly has no effect on the keyboard functioning. I tried updating the keyboard firmware last night (no effect), and I've tried updating my system with pacman -Syu. I'm attaching several dmesg dumps from various boot attempts, and I can add any other logging if useful.
For dmesg log 0000: I had just rebooted from windows. The keyboard worked in grub. The keyboard backlight turned off when the encrypt password prompt came up, and they keys didn't do anything. When I reached sddm (after entering my password with my laptop keyboard), the backlight was on, but the first key I hit started repeating like crazy. After unplugging the keyboard, logging in with the laptop keyboard, and plugging the corsair keyboard back in, the keyboard still wouldn't function, even after several iterations of unplugging and plugging it back in.
For dmesg log 0001: I tried pacman -Syu, and then rebooted. The keyboard didn't work for grub, and didn't work at the encrypt prompt, but the backlight remained on. Once I reached sddm I could type correctly, including after I logged in. Below is the portion of output I saw at boot.
A password is required to access the primary volume:
Enter passphrase for /dev/sda6: [ 5.075040] usb 3-2: device descriptor read/64, error -71
[ 5.178451] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[ 5.178484] usb 3-2: hub failed to enable device, error -22
[ 8.048263] usb 3-2: device descriptor read/64, error -71
[ 8.151696] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 10.
[ 8.151731] usb 3-2: hub failed to enable device, error -22
[ 8.472083] usb 3-2: device descriptor read/64, error -71
[ 8.575564] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 11.
[ 8.575614] usb 3-2: hub failed to enable device, error -22
[ 9.142783] usb 3-2: device not accepting address 13, error -71
[ 9.710072] usb 3-2: device not accepting address 14, error -71
[ 9.710146] usb usb3-port2: unable to enumerate USB device
[ 15.446444] hid-generic 0003:1B1C:1B13.0002: usb_submit_urb(ctrl) failed: -1
For dmesg log 0002: I rebooted after 0001. The keyboard worked for grub, but didn't work at the encrypt prompt, though the backlight was still on. At sddm and beyond the keyboard worked correctly. Below is the portion of output I saw at boot.
A password is required to access the primary volume:
Enter passphrase for /dev/sda6: [ 7.799771] usb 3-2: device descriptor read/64, error -71
[ 7.903201] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 8.
[ 7.903235] usb 3-2: hub failed to enable device, error -22
[ 8.223569] usb 3-2: device descriptor read/64, error -71
[ 8.327003] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 9.
[ 8.327037] usb 3-2: hub failed to enable device, error -22
[ 8.894307] usb 3-2: device not accepting address 11, error -71
[ 9.461617] usb 3-2: device not accepting address 12, error -71
[ 9.461716] usb usb3-port2: unable to enumerate USB device
[ 15.678509] hid-generic 0003:1B1C:1B13.0002: usb_submit_urb(ctrl) failed: -1
For dmesg log 0003: I rebooted and entered a windows user session, and restarted from there. The keyboard worked from grub, and the encrypt prompt eventually showed up (as detailed in the following output), at which point the keyboard worked for entering my password (but did not function for typing with echo before the password prompt showed up).
[ 6.833134] usb 1-2: device descriptor read/64, error -71
[ 6.936577] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 7.
[ 6.936612] usb 1-2: hub failed to enable device, error -22
[ 7.550591] usb 1-2: device descriptor read/64, error -71
[ 7.654029] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 9.
[ 7.654063] usb 1-2: hub failed to enable device, error -22
[ 7.974389] usb 1-2: device descriptor read/64, error -71
[ 8.077825] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 10.
[ 8.077861] usb 1-2: hub failed to enable device, error -22
[ 8.645096] usb 1-2: device not accepting address 12, error -71
[ 9.212395] usb 1-2: device not accepting address 13, error -71
[ 9.212461] usb usb1-port2: unable to enumerate USB device
[ 15.215752] hid-generic 0003:1B1C:1B13.0002: usb_submit_urb(ctrl) failed: -1
A password is required to access the primary volume:
Enter passphrase for /dev/sda6:
/dev/mapper/primary: clean, 122766/28893184 files, 6829401/115546880 blocks
[ 64.316335] ideapad_laptop: timeout in read_ec_cmd
[ 64.439684] ideapad_laptop: timeout in read_ec_cmd
[ 67.906370] systemd-fsck[414]: fsck.fat 3.0.26 (2014-03-07)
[ 67.906549] systemd-fsck[414]: /dev/sda2: 840 files, 19997/65536 clusters
[ 73.047228] nouveau E[ PIBUS][0000:01:00.0] HUB0: 0x6013d4 0xffff573f (0x19408200)
[ 73.061732] nouveau E[ PGRAPH][0000:01:00.0] failed to load fuc409c
[ 73.061758] nouveau E[ DEVICE][0000:01:00.0] failed to create 0x18000717, -22
[ 73.061786] nouveau E[ DRM] failed to create 0x00000080, -22
Other keyboard artifacts: if I'm in bash and typing some command and then piping it through grep or something, the command will end up looking like: dmesg | |grep or dmesg | |\grep. If I type slower, the pipe character isn't repeated. Sequence of keys: space, shift down, backslash, space, shift up.
Miscellaneous system specs:
Laptop: Lenovo Y50 (59421855), less than four months old
Processor: Intel Core i7-4710HQ
Memory: 16 GB
Graphics: Intel Integrated and NVIDIA GeForce 860M 4GB
Edit: it looks like there's a thread over on Corsair's forums about this.
Edit2: also worth mentioning galen104's fix to the "timeout initializing reports" error.
Last edited by distilledchaos (2014-11-04 22:00:05)

Answer 1

Yes. From my tests I've found USB3 on Linux quite buggy (if not completely broken in some cases) and only way to get rid of the problems is to disable it. You could try blacklist xhci_hcd module, but I'm not sure if its going to change something.