robbob2112

Will take a lot more info to be useful. 1. Os used both linux flavor and version 2. Did you try in windows? I.E are you sure the hardware is not defective? 3. Assuming you are using linux, tail the messages log as you plug it in and post the results. 4. Assuming linux, post the results of 'lsusb' while you are root... somewhere in the many pages there is a list of things to try, but those are mostly the gist of it. Robert

I had an 'oops' moment last night with 'sgdisk' trying to copy a partition table.. Why the folks that wrote sgdisk thought it would be smart to switch the expected order or arguments I'll never know.... ever unix copy command I know does .... COMMAND src dest ... but sgdisk does ... sgdisk /dev/sd(dest) /dev/sd(src) .... so I managed to wipe my partition table out ...... That said, after I mucked around with it for an hour or so and decided the simplest and cleanest cure would be a re-install and restore the critical stuff from backup... .. Much to my surprise the k95-RGB functions with the native drivers under Fedora 22 .... there is no way to adjust the colors or any of the other great stuff, but it does work now... I will re-install ckb simply because it is a great utility.... and thanks again for writing and maintaining it... But thought you should know they seem to be rolling support into the newer kernels now. Linux intrepid 4.0.4-301.fc22.x86_64 #1 SMP Thu May 21 13:10:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Also note: they integrated support for the volume and mute buttons into it. Robert

Here is an interesting side effect of trying the change in /etc/default/grub It caused my second monitor to go to sleep and stay that way until power cycled... as in physically pulled power... just the on/off button had no effect.. Intel i7 3770k/intel HD4000 graphics built in... connecting monitor 1 via DVI and monitor 2 via displayport->hdmi cable boot time also increased by several seconds No idea how that interaction worked... so took it out and will wait on your fix to try it... Thought it was strange enough to report and it is repeatable... I'll try out the modprob part tonight to see if it does the same thing.. Robert

Seems like the 10 second delay on boot is tied up in the kernel and should be fixable via adding a 'hid.quirks' entry to /etc/default/grub and running grub2-mkconfig ... I haven't figured out the proper syntax yet to make it work but find many entries referring to a bug in 2013 when I google for "hid-generic timeout initializing reports" ... there are many posts about disabling the reports function to fix, but none are clear. Has anyone fiddled with this enough to make it work? If so, can you post your /etc/defaults/grub and 'dmesg | grep -i hid' please? Thanks Robert

Just installed your 1.4 version of the driver. Also turned off all the Fedora splash screens so I could watch and see where it hangs up. Wanted to report that when shutting down the forever pause until the keyboard is unplugged is gone now. On boot the keyboard functions as a standard keyboard during the grub menu... i.e. I can edit kernel options if I want or need to. There is still a pause on boot... dmesg below... the ' timeout initializing reports' lines are where it pauses for maybe 10 second each (*didn't time it, just guessing*) [ 1.782534] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 1.785924] input: Kensington Kensington Expert Mouse as /devices/pci0000:00/0000:00:1c.7/0000:04:00.0/usb3/3-2/3-2:1.0/0003:047D:1020.0003/input/input7 [ 1.786329] hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0 [ 2.471032] Switched to clocksource tsc [ 11.406291] hid-generic 0003:1B1C:1B11.0002: usb_submit_urb(ctrl) failed: -1 [ 11.406376] hid-generic 0003:1B1C:1B11.0002: timeout initializing reports [ 11.406841] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0002/input/input8 [ 11.457239] hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 [ 21.458465] hid-generic 0003:1B1C:1B11.0004: timeout initializing reports [ 21.458758] hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2 [ 31.459566] hid-generic 0003:1B1C:1B11.0005: usb_submit_urb(ctrl) failed: -1 [ 31.459845] hid-generic 0003:1B1C:1B11.0005: timeout initializing reports [ 31.460068] hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3 [ 31.522442] usb 5-1.5: new full-speed USB device number 4 using ehci-pci [ 31.611784] usb 5-1.5: New USB device found, idVendor=8087, idProduct=07da [ 31.611813] usb 5-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0

So here is an interesting thing. If I play a stand alone video in VLC the volume and mute work perfectly inside the app, in fact all the media controls work. The media controls do nothing when playing inside a browser (youtube video or streaming site) So, novice question: is there something that is different/needed to make the OS/system wide controls bind up to the media controls verse apps like VLC?

See my post above... just did a clean install of fedora 21 and first thing this keyboard... he is missing zlib-devel... which are the headers for zlib Notes on Fedora 21 desktop - clean install and this is the first thing I am installing (defaults to Gnome 3.14.2-2.fc21 now instead of KDE ).... as root # yum install qt5-qtbase libgudev1-devel qt5-qtbase-devel zlib systemd-devel gcc gcc-c++ zlib-devel # git clone https://github.com/ccMSC/ckb # cd ckb/ # ./quickinstall

and here is from the last shutdown and current boot up... switched to windows and back again... no hang this time on login... It does take an additional 30~40 seconds on boot to initialize the keyboard, but doesn't require unplugging shutdown -- had to unplug it... May 13 08:18:14 intrepid kernel: [ 1.760973] hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0 May 13 08:18:14 intrepid kernel: [ 11.435907] hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 May 13 08:18:14 intrepid kernel: [ 21.437228] hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2 May 13 08:18:14 intrepid kernel: [ 31.438170] hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3 May 13 07:29:38 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Close May 13 07:29:38 intrepid kernel: hid-generic 0003:1B1C:1B11.0006: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0 May 13 07:29:46 intrepid kernel: hid-generic 0003:1B1C:1B11.0007: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 May 13 07:29:46 intrepid kernel: usb 5-1.3: usbfs: process 910 (ckb-daemon) did not claim interface 0 before use May 13 07:29:46 intrepid ckb-daemon: ckb Corsair Keyboard RGB driver beta-v0.1.3 May 13 07:29:46 intrepid ckb-daemon: Setting FPS to 30 May 13 07:29:46 intrepid ckb-daemon: Setting default layout: us May 13 07:29:46 intrepid ckb-daemon: Root controller ready at /dev/input/ckb0 May 13 07:29:46 intrepid ckb-daemon: Connecting Corsair K95 RGB Gaming Keyboard (S/N: 16030013AE3B940553763B42F5001940) May 13 07:29:46 intrepid ckb-daemon: Device ready at /dev/input/ckb1 May 13 07:29:46 intrepid ckb-daemon: Caught signal 15 May 13 07:29:46 intrepid ckb-daemon: Disconnecting Corsair K95 RGB Gaming Keyboard (S/N: 16030013AE3B940553763B42F5001940) May 13 07:29:46 intrepid ckb-daemon: Removed device path /dev/input/ckb1 May 13 07:29:46 intrepid ckb-daemon: Removed device path /dev/input/ckb0 Bootup May 13 02:17:39 intrepid kernel: Linux version 3.19.5-200.fc21.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 4.9.2 20150212 (Red Hat 4.9.2-6) (GCC) ) #1 SMP Mon Apr 20 19:51:56 UTC 2015 May 13 02:17:39 intrepid kernel: hidraw: raw HID events driver © Jiri Kosina May 13 02:17:39 intrepid kernel: usbhid: USB HID core driver May 13 02:17:40 intrepid kernel: hid-generic 0003:1B1C:1B11.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0 May 13 02:17:40 intrepid kernel: hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0 May 13 02:17:50 intrepid kernel: hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 May 13 02:18:00 intrepid kernel: hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2 May 13 02:18:10 intrepid kernel: hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3 May 13 08:18:14 intrepid kernel: [ 35.428325] input: ckb1 as /devices/virtual/input/input18 May 13 08:18:14 intrepid kernel: input: ckb1 as /devices/virtual/input/input18 May 13 08:18:21 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event3) May 13 08:18:21 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "evdev keyboard catchall" May 13 08:18:21 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "system-keyboard" May 13 08:18:21 intrepid gdm-Xorg-:0: (II) Using input driver 'evdev' for 'ckb1' May 13 08:18:21 intrepid gdm-Xorg-:0: (**) ckb1: always reports core events May 13 08:18:21 intrepid gdm-Xorg-:0: (**) evdev: ckb1: Device: "/dev/input/event3" May 13 08:18:21 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11 May 13 08:18:21 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys May 13 08:18:21 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard May 13 08:18:21 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11) on the boot up the clock jumps around... windows and linux seem to both want to set the bios clock... one wants to set it to UTC and the other wants to set it to local time MST... haven't ever sorted out how to tell them to stop it.

Not really, by the time it hangs on shutdown it has already stopped writing logs and the screen has flipped to a generic background with the Fedora logo .. if I can turn that off it might print something useful to the screen. Here are messages log lines since the last reboot..... not sure what it means, but seems like it might be re-initializing the keyboard periodically? May 10 07:38:15 intrepid kernel: Linux version 3.19.5-200.fc21.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 4.9.2 20150212 (Red Hat 4.9.2-6) (GCC) ) #1 SMP Mon Apr 20 19:51:56 UTC 2015 May 10 07:38:15 intrepid kernel: hidraw: raw HID events driver © Jiri Kosina May 10 07:38:15 intrepid kernel: usbhid: USB HID core driver May 10 07:38:15 intrepid kernel: hid-generic 0003:1B1C:1B11.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0 May 10 07:38:15 intrepid kernel: hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0 May 10 07:38:25 intrepid kernel: hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 May 10 07:38:35 intrepid kernel: hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2 May 10 07:38:45 intrepid kernel: hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3 May 10 13:38:46 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway. May 10 13:38:48 intrepid kernel: [ 34.581158] input: ckb1 as /devices/virtual/input/input18 May 10 13:38:48 intrepid kernel: input: ckb1 as /devices/virtual/input/input18 May 10 13:38:50 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway. May 10 13:38:51 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event2) May 10 13:38:51 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11 May 10 13:38:51 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys May 10 13:38:51 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard May 10 13:38:51 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11) May 10 14:44:49 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway. May 10 14:44:49 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway. May 10 14:45:51 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway. May 10 14:45:54 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway. May 10 14:52:17 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Close May 10 14:52:17 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event2) May 10 14:52:17 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "evdev keyboard catchall" May 10 14:52:17 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "system-keyboard" May 10 14:52:17 intrepid gdm-Xorg-:0: (II) Using input driver 'evdev' for 'ckb1' May 10 14:52:17 intrepid gdm-Xorg-:0: (**) ckb1: always reports core events May 10 14:52:17 intrepid gdm-Xorg-:0: (**) evdev: ckb1: Device: "/dev/input/event2" May 10 14:52:17 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11 May 10 14:52:17 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys May 10 14:52:17 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard May 10 14:52:17 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11) May 10 14:57:52 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Close May 10 14:57:52 intrepid gdm-Xorg-:0: (II) config/udev: Adding input device ckb1 (/dev/input/event2) May 10 14:57:52 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "evdev keyboard catchall" May 10 14:57:52 intrepid gdm-Xorg-:0: (**) ckb1: Applying InputClass "system-keyboard" May 10 14:57:52 intrepid gdm-Xorg-:0: (II) Using input driver 'evdev' for 'ckb1' May 10 14:57:52 intrepid gdm-Xorg-:0: (**) ckb1: always reports core events May 10 14:57:52 intrepid gdm-Xorg-:0: (**) evdev: ckb1: Device: "/dev/input/event2" May 10 14:57:52 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Vendor 0x1b1c Product 0x1b11 May 10 14:57:52 intrepid gdm-Xorg-:0: (--) evdev: ckb1: Found keys May 10 14:57:52 intrepid gdm-Xorg-:0: (II) evdev: ckb1: Configuring as keyboard May 10 14:57:52 intrepid gdm-Xorg-:0: (II) XINPUT: Adding extended input device "ckb1" (type: KEYBOARD, id 11) May 10 15:49:21 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway. May 10 16:05:45 intrepid systemd: Configuration file /usr/lib/systemd/system/ckb-daemon.service is marked executable. Please remove executable permission bits. Proceeding anyway.

Notes on Fedora 21 desktop - clean install and this is the first thing I am installing (defaults to Gnome 3.14.2-2.fc21 now instead of KDE ).... as root # yum install qt5-qtbase libgudev1-devel qt5-qtbase-devel zlib systemd-devel gcc gcc-c++ zlib-devel # git clone https://github.com/ccMSC/ckb # cd ckb/ # ./quickinstall Finished! Install ckb system-wide [Y/n]? y Installed in /usr/bin System service: systemd detected Run the driver as a startup service [Y/n]? y Start ckb now [Y/n]? y Post install.... still has the hang on shutdown... boots up normally after reboot... haven't tried from reboot after windows yet... keyboard and gui both work fine and to get me back to my LXDE desktop # yum group install 'LXDE Desktop' 'Xfce Desktop' --exclude fedora-release\*

I flipped over to Gnome and everything seems to be working just fine, both the ckb gui and the keyboard driver itself... Running Fedora 20/gnome I normally run KDE or LXDE btw. Of course I may not be a good example, I have about 15 desktop env's installed and originally started at Fedora 16... Switching from FreeBSD to linux at that point so I made a lot of mistakes with repos and packages... and I was about to upgrade to Fedora 21 using 'fedup' and discovered I apparently have a ton of unresolved dependency errors along with both i686 and AMD_64 versions of QT installed.... I am going to make a backup and do a clean install... I'll install gnome on top of Fedora as one of my desktop managers and post back....

Did you check if you have SElinux enabled? (hint all flavors of Fedora come with it enabled by default) as root # getenforce Enforcing if it is enabled try switching it to permissive mode # setenforce permissive # getenforce Permissive There is a whole debate about leaving SELinux on or off... I tend to leave it on and make modules as needed... lots of people turn it off... Best bet _if_ the above works and this is just a desktop and behind firewalls and such is leave it in permissive mode... to leave it permanently in permissive mode edit /etc/selinux/config and change from enforcing to permissive and reboot.... if you just disable it (same file) it can be painful to go back so permissive is better... If you want instructions on making modules and leave it on, google for it or ask and I can post a down and dirty crib sheet for you. Robert

Something new...weird, so of course windows is involved... If I boot into window everything there works fine... then when I boot back into Linux the keyboard hang on boot is back... but only on the first boot back from windows... reboots after that have the typical forever hang until the keyboard is unplugged on shutdown, but boots straight back up with no issues... So, seems to me the 'new' windows driver is leaving the keyboard with something gimped up and once it loads things are corrected.. ~ $ dmesg | egrep -i 'hid|corsair' [ 0.512458] hidraw: raw HID events driver © Jiri Kosina [ 0.512595] usbcore: registered new interface driver usbhid [ 0.512597] usbhid: USB HID core driver [ 1.266869] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard [ 1.266870] usb 5-1.3: Manufacturer: Corsair [ 1.268431] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0001/input/input6 [ 1.319045] hid-generic 0003:1B1C:1B11.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0 [ 1.705072] hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0 [ 11.320232] hid-generic 0003:1B1C:1B11.0002: usb_submit_urb(ctrl) failed: -1 [ 11.320258] hid-generic 0003:1B1C:1B11.0002: timeout initializing reports [ 11.320669] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0002/input/input8 [ 11.371105] hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 [ 21.372281] hid-generic 0003:1B1C:1B11.0004: timeout initializing reports [ 21.372679] hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2 [ 28.359134] hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3 [ 31.981245] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard [ 31.981247] usb 5-1.3: Manufacturer: Corsair [ 31.983113] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0006/input/input18 [ 32.034462] hid-generic 0003:1B1C:1B11.0006: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0 [ 42.035455] hid-generic 0003:1B1C:1B11.0007: usb_submit_urb(ctrl) failed: -1 [ 42.035477] hid-generic 0003:1B1C:1B11.0007: timeout initializing reports [ 42.035918] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0007/input/input19 [ 42.086790] hid-generic 0003:1B1C:1B11.0007: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 [ 52.087609] hid-generic 0003:1B1C:1B11.0008: timeout initializing reports [ 52.087970] hid-generic 0003:1B1C:1B11.0008: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2 [ 62.088738] hid-generic 0003:1B1C:1B11.0009: usb_submit_urb(ctrl) failed: -1 [ 62.088762] hid-generic 0003:1B1C:1B11.0009: timeout initializing reports [ 62.089097] hid-generic 0003:1B1C:1B11.0009: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3

and now I am running on firmware 1.20 with your beta 1.3 software... Seems like the long delay on boot is gone Here is the dmesg $ dmesg | egrep -i 'corsair|hid' [ 0.512391] hidraw: raw HID events driver © Jiri Kosina [ 0.512531] usbcore: registered new interface driver usbhid [ 0.512532] usbhid: USB HID core driver [ 1.265361] usb 5-1.3: Product: Corsair K95 RGB Gaming Keyboard [ 1.265362] usb 5-1.3: Manufacturer: Corsair [ 1.267223] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:1B1C:1B11.0001/input/input6 [ 1.317769] hid-generic 0003:1B1C:1B11.0001: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input0 [ 1.701007] hid-generic 0003:047D:1020.0003: input,hidraw1: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0 [ 11.318946] hid-generic 0003:1B1C:1B11.0002: usb_submit_urb(ctrl) failed: -1 [ 11.318962] hid-generic 0003:1B1C:1B11.0002: timeout initializing reports [ 11.319373] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:1B1C:1B11.0002/input/input8 [ 11.369955] hid-generic 0003:1B1C:1B11.0002: input,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input1 [ 21.371125] hid-generic 0003:1B1C:1B11.0004: timeout initializing reports [ 21.371371] hid-generic 0003:1B1C:1B11.0004: hiddev0,hidraw3: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input2 [ 31.372099] hid-generic 0003:1B1C:1B11.0005: usb_submit_urb(ctrl) failed: -1 [ 31.372127] hid-generic 0003:1B1C:1B11.0005: timeout initializing reports [ 31.372340] hid-generic 0003:1B1C:1B11.0005: hiddev0,hidraw4: USB HID v1.11 Device [Corsair Corsair K95 RGB Gaming Keyboard ] on usb-0000:00:1a.0-1.3/input3

[ 0.526307] hidraw: raw HID events driver © Jiri Kosina [ 0.526440] usbcore: registered new interface driver usbhid [ 0.526442] usbhid: USB HID core driver [ 2.099795] hid-generic 0003:047D:1020.0001: input,hidraw0: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:04:00.0-2/input0 [ 2.320081] usb 1-1.3: Product: Corsair K95 RGB Gaming Keyboard [ 2.320084] usb 1-1.3: Manufacturer: Corsair [ 2.324441] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:1B1C:1B11.0002/input/input7 [ 2.324554] hid-generic 0003:1B1C:1B11.0002: input,hidraw1: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard] on usb-0000:00:1a.0-1.3/input0 [ 20.441224] usbhid 1-1.3:1.1: can't add hid device: -32 [ 20.441240] usbhid: probe of 1-1.3:1.1 failed with error -32 [ 20.445436] usbhid 1-1.3:1.2: can't add hid device: -32 [ 20.445449] usbhid: probe of 1-1.3:1.2 failed with error -32 [ 20.449560] usbhid 1-1.3:1.3: can't add hid device: -32 [ 20.449568] usbhid: probe of 1-1.3:1.3 failed with error -32 [ 25.330008] usb 1-1.3: Product: Corsair K95 RGB Gaming Keyboard [ 25.330010] usb 1-1.3: Manufacturer: Corsair [ 25.334989] input: Corsair Corsair K95 RGB Gaming Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:1B1C:1B11.0003/input/input17 [ 25.335368] hid-generic 0003:1B1C:1B11.0003: input,hidraw1: USB HID v1.11 Keyboard [Corsair Corsair K95 RGB Gaming Keyboard] on usb-0000:00:1a.0-1.3/input0 [ 60.337497] usbhid 1-1.3:1.1: can't add hid device: -110 [ 60.337526] usbhid: probe of 1-1.3:1.1 failed with error -110 [ 95.337879] usbhid 1-1.3:1.2: can't add hid device: -110 [ 95.337898] usbhid: probe of 1-1.3:1.2 failed with error -110 [ 130.338277] usbhid 1-1.3:1.3: can't add hid device: -110 [ 130.338295] usbhid: probe of 1-1.3:1.3 failed with error -110