Re: not supported hardware: Gigabyte K8100 Aivia USB Gaming Keyboard
From: zitev <hidden>
Date: 2012-02-01 19:39:55
Possibly related (same subject, not in this thread)
- 2012-03-10 · Re: not supported hardware: Gigabyte K8100 Aivia USB Gaming Keyboard · zitev <hidden>
- 2012-03-09 · Re: not supported hardware: Gigabyte K8100 Aivia USB Gaming Keyboard · Jonathan Nieder <hidden>
- 2012-02-11 · Re: not supported hardware: Gigabyte K8100 Aivia USB Gaming Keyboard · zitev <hidden>
i attached the detail of syslog: "Feb 1 20:26:40 player kernel: [ 1247.275287] usb 1-1.1: new high-speed USB device number 6 using ehci_hcd Feb 1 20:26:40 player kernel: [ 1247.444488] usb 1-1.1: New USB device found, idVendor=05e3, idProduct=0608 Feb 1 20:26:40 player kernel: [ 1247.520511] usb 1-1.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Feb 1 20:26:40 player kernel: [ 1247.596369] usb 1-1.1: Product: USB2.0 Hub Feb 1 20:26:40 player kernel: [ 1247.672160] hub 1-1.1:1.0: USB hub found Feb 1 20:26:40 player kernel: [ 1247.736605] hub 1-1.1:1.0: 4 ports detected Feb 1 20:26:41 player kernel: [ 1248.074036] usb 1-1.1.2: new full-speed USB device number 7 using ehci_hcd Feb 1 20:26:41 player kernel: [ 1248.240627] usb 1-1.1.2: New USB device found, idVendor=1044, idProduct=7a02 Feb 1 20:26:41 player kernel: [ 1248.314881] usb 1-1.1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Feb 1 20:26:41 player mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2" Feb 1 20:26:41 player kernel: [ 1248.391648] generic-usb: probe of 0003:1044:7A02.0006 failed with error -22 Feb 1 20:26:41 player kernel: [ 1248.459226] input: HID 1044:7a02 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/input/input7 Feb 1 20:26:41 player kernel: [ 1248.523851] generic-usb 0003:1044:7A02.0007: input,hiddev0,hidraw0: USB HID v1.11 Mouse [HID 1044:7a02] on usb-0000:00:1a.0-1.1.2/input1 Feb 1 20:26:41 player kernel: [ 1248.592068] generic-usb 0003:1044:7A02.0008: input,hidraw1: USB HID v1.11 Device [HID 1044:7a02] on usb-0000:00:1a.0-1.1.2/input2 Feb 1 20:26:41 player mtp-probe: bus: 1, device: 7 was not an MTP device Feb 1 20:26:41 player kernel: [ 1248.729040] usb 1-1.1.4: new low-speed USB device number 8 using ehci_hcd Feb 1 20:26:42 player kernel: [ 1248.917065] usb 1-1.1.4: New USB device found, idVendor=060b, idProduct=2270 Feb 1 20:26:42 player kernel: [ 1248.990757] usb 1-1.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 1 20:26:42 player kernel: [ 1249.063713] usb 1-1.1.4: Product: USB Keyboard Feb 1 20:26:42 player kernel: [ 1249.136990] usb 1-1.1.4: Manufacturer: KB Feb 1 20:26:42 player kernel: [ 1249.219263] input: KB USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/input/input8 Feb 1 20:26:42 player kernel: [ 1249.293903] generic-usb 0003:060B:2270.0009: input,hidraw2: USB HID v1.10 Keyboard [KB USB Keyboard] on usb-0000:00:1a.0-1.1.4/input0 Feb 1 20:26:42 player kernel: [ 1249.380643] generic-usb: probe of 0003:060B:2270.000A failed with error -22 Feb 1 20:26:42 player mtp-probe: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.4" Feb 1 20:26:42 player mtp-probe: bus: 1, device: 8 was not an MTP device" 2012-01-28 08:12 keltezéssel, Jonathan Nieder írta:
zitev wrote:quoted
I attached the lsusb output!Perfect, thanks.quoted
Bus 001 Device 004: ID 1044:7a02 Chu Yuen Enterprise Co., Ltd[...]quoted
bNumInterfaces 3[...]quoted
Interface Descriptor: bInterfaceClass 3 Human Interface Device iInterface 2 KB[...]quoted
Interface Descriptor: bInterfaceClass 3 Human Interface Device iInterface 3 Mouse[...]quoted
Interface Descriptor: bInterfaceClass 3 Human Interface Device iInterface 4 K8100 InterfaceCan you set up usbmon and get a trace of e.g., pressing, holding, then releasing the "a" key? See Documentation/usb/usbmon.txt in the Linux source or the doc directory of the linux-doc-3.2 package for details. It works roughly like this: 1. Mount debugfs and load the usbmon module: mount -t debugfs debugfs /sys/kernel/debug modprobe usbmon 2. Start tracing: { sleep 1; # one second of quiet cat /sys/kernel/debug/usb/usbmon/1u>/tmp/mon.out& sleep 20; # twenty seconds or so to run the test kill $!; # and then stop collecting data } 3. Somehow summarize the output. If it is fairly small, an attachment is fine; otherwise, excerpts and maybe a link to a copy that can be downloaded online might work. Hope that helps, Jonathan
-- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html