2.04 is why I'm trying fw2kb in the first place.) (Might have a go with firmware 2.04 later, and see if that fixes my disconnect issue. input: ckb1: Corsair K95 RGB Gaming Keyboard as /devices/virtual/input/input249 input: ckb1: Corsair K95 RGB Gaming Keyboard as /devices/virtual/input/input248 usb 3-1.3: new full-speed USB device number 102 using xhci_hcd usb 3-1.3: USB disconnect, device number 101 input: ckb1: Corsair K95 RGB Gaming Keyboard as /devices/virtual/input/input245 input: ckb1: Corsair K95 RGB Gaming Keyboard as /devices/virtual/input/input244 usb 3-1.3: Product: Corsair K95 RGB Gaming Keyboard usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1.3: New USB device found, idVendor=1b1c, idProduct=1b11 usb 3-1.3: new full-speed USB device number 101 using xhci_hcd usb 3-1.3: USB disconnect, device number 100 usb 3-1.3: usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon rqt 161 rq 1 len 64 ret -110 Trying beta-v0.2.5 on the working system currently running beta-v0.2.4+t02.Slightly older (tribal logo) K95 RGB running Ubuntu Studio with a 3.13.0-85-lowlatency kernel and ckb beta-v0.2.4+t02. I also have another system, which works perfectly fine. input: ckb1: Corsair K95 RGB Gaming Keyboard as /devices/virtual/input/input219 input: ckb1: Corsair K95 RGB Gaming Keyboard as /devices/virtual/input/input218 usb 3-1: Product: Corsair K95 RGB Gaming Keyboard usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1: New USB device found, idVendor=1b1c, idProduct=1b11 usb 3-1: new full-speed USB device number 54 using xhci_hcd Usb 3-1: USB disconnect, device number 53