Bug 357323 – Gigabyte K8100 keyboard unsupported by kernel (no response from a keyboard)

• Status: RESOLVED UPSTREAM
• Product: Gentoo Linux

[Description Dmitry Kravtsov 2011-03-04 09:45:21 UTC]

Hi,
Today I get a nice new gaming keyboard, which nicely and smoothly works in M$ Windows,on POST screen and grub loader. But when I boot up my gentoo I can't get any signal from my keyboard anymore (except for sensor panel for volume control -- surprisingly it works nice). I have a suspicious line in dmesg, here it is (with a context):


[    3.220614] usbhid 1-4.4:1.0: usb_probe_interface
[    3.220616] usbhid 1-4.4:1.0: usb_probe_interface - got id
[    3.236605] input: KB USB Keyboard as /devices/pci0000:00/0000:00:1a.7/usb1/1-4/1-4.4/1-4.4:1.0/input/input5 [    3.237209] usb 1-4.4: link qh8-3008/ffff8801b9593100 start 3 [1/2 us]
[    3.237286] generic-usb 0003:060B:2270.0006: input,hidraw4: USB HID v1.10 Keyboard [KB USB Keyboard] on usb- 0000:00:1a.7-4.4/input0
[    3.237891] usb 1-4.4: adding 1-4.4:1.1 (config #1, interface 1)
[    3.237935] usbhid 1-4.4:1.1: usb_probe_interface
[    3.237937] usbhid 1-4.4:1.1: usb_probe_interface - got id
[    3.249345] generic-usb: probe of 0003:060B:2270.0007 failed with error -22

Also I can see a bunch of new devices in lsusb:
  9 Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
...
 13 Bus 001 Device 004: ID 1044:7a02 Chu Yuen Enterprise Co., Ltd
 14 Bus 001 Device 005: ID 060b:2270 Solid Year

Reproducible: Always

Steps to Reproduce:
1. Connect a Gigabyte K8100 keyboard
2. Boot up you gentoo linux distribution
3. Enjoy

Actual Results:  
Keyboard practically not working

Expected Results:  
Keyboard nicely working

[Comment 1 Dmitry Kravtsov 2011-03-04 09:45:57 UTC]

Created attachment 264665 [details]
Full dmesg

[Comment 2 Dmitry Kravtsov 2011-03-04 09:46:39 UTC]

Created attachment 264667 [details]
Short lsusb output

[Comment 3 Dmitry Kravtsov 2011-03-04 09:47:17 UTC]

Created attachment 264669 [details]
Verbose lsusb output

[Comment 4 Jorge Manuel B. S. Vicetto (RETIRED) 2011-03-04 19:03:25 UTC]

Did you enable the CONFIG_USB_HID option in the kernel?

check bug 270983 for more details

[Comment 5 Dmitry Kravtsov 2011-03-05 01:31:11 UTC]

(In reply to comment #4)
> Did you enable the CONFIG_USB_HID option in the kernel?
> 
> check bug 270983 for more details
> 

Yes I did 

[Comment 6 Dmitry Kravtsov 2011-03-05 01:33:38 UTC]

Created attachment 264785 [details]
Kernel .config

[Comment 7 Jorge Manuel B. S. Vicetto (RETIRED) 2011-03-05 19:24:08 UTC]

Try enabling some of the CONFIG_HID_* options that are disabled and see if that fixes this issue.

[Comment 8 Dmitry Kravtsov 2011-03-06 01:54:17 UTC]

(In reply to comment #7)
> Try enabling some of the CONFIG_HID_* options that are disabled and see if that
> fixes this issue.
> 

I enabled every CONFIG_HID_* option (as a module) and still have same error. By the way, I noticed that USB hub on keyboard works. 

[Comment 9 Dmitry Kravtsov 2011-03-07 09:10:35 UTC]

So I also tried to connect this keyboard to my laptops (one with Ubuntu and one with Archlinux) and get the same error in dmesg, while other usb keyboards work fine. I'm pretty sure that it's either a bug in kernel or lack of firmware drivers (but bug is most likely, because keyboard works fine on BIOS drivers at the POST screen).

[Comment 10 Mike Pagano 2011-03-17 10:41:46 UTC]

Please post this bug upstream and post the url back here.

http://bugzilla.kernel.org

[Comment 11 Dmitry Kravtsov 2011-03-18 07:16:44 UTC]

Created bug report at bugzilla.kernel.org:
https://bugzilla.kernel.org/show_bug.cgi?id=31342

[Comment 12 Mike Pagano 2011-03-18 19:40:40 UTC]

Thanks, we'll track the upstream bug and backport and fix created