Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1471327

Title:
  ubuntu doesn't recognise keyboard - works fine in BIOS, stops on OS
  load

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Corsair K-50 stopped working on the 27th June, had been working
  perfectly fine for the last few months. I plugged it into another
  machine on ubuntu that has been recently updated which leads me to
  believe this is a bug.

  Furthermore the keyboard works fine in BIOS, setup and even in the
  Advanced settings - I can select recovery mode, but as soon as that
  finishes the keyboard stops working.

  I have also plugged it into a Windows machine and the keyboard works
  fine.

  Not sure if these files will help but here's what I have found:

  http://pastebin.com/uzSCh8bM - this is a log from the previous boot on
  the 25th June, on line 1185 the keyboard is registered and detected as
  the correct make and model.

  http://pastebin.com/NJEZ8YYt - this is a log from the day it stopped
  working and there is no trace of "Corsair" , instead at roughly the
  same time I find the lines on line (1133):

  Jun 27 02:53:15 jared-MS-7930 kernel: [    1.153217] usbhid 1-2:1.0: can't 
add hid device: -22
  Jun 27 02:53:15 jared-MS-7930 kernel: [    1.153221] usbhid: probe of 1-2:1.0 
failed with error -22

  This error crops up a number of times but I can find little reference
  to it on the web.

  Here is an up to date log of me removing my mouse (which works) and plugging 
the keyboard into the same port:
  Jul  3 20:08:33 jared-MS-7930 kernel: [66429.129176] usb 1-14: USB 
disconnect, device number 8
  Jul  3 20:08:53 jared-MS-7930 kernel: [66449.334761] usb 1-14: new full-speed 
USB device number 9 using xhci_hcd
  Jul  3 20:08:53 jared-MS-7930 kernel: [66449.463930] usb 1-14: New USB device 
found, idVendor=1b1c, idProduct=1b04
  Jul  3 20:08:53 jared-MS-7930 kernel: [66449.463932] usb 1-14: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
  Jul  3 20:08:53 jared-MS-7930 kernel: [66449.463933] usb 1-14: Product: KBD 
Boot Loader
  Jul  3 20:08:53 jared-MS-7930 kernel: [66449.463934] usb 1-14: Manufacturer: 
EST
  Jul  3 20:08:53 jared-MS-7930 kernel: [66449.464411] usbhid 1-14:1.0: can't 
add hid device: -22
  Jul  3 20:08:53 jared-MS-7930 kernel: [66449.464416] usbhid: probe of 
1-14:1.0 failed with error -22

  I've checked the Software Centre History and hadn't updated since the 24th 
the only packages being:
  google-chrome-stable (43.0.2357.125-1, 43.0.2357.130-1)
  flashplugin-installer (11.2.202.466ubuntu0.15.04.1, 
11.2.202.468ubuntu0.15.04.1)

  I understand that this is difficult to reproduce because you require
  the specific keyboard but I'm willing to dig and investigate if
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471327/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to