On Fri, 28 Jan 2011, kholis wrote: > > The best thing would be for you to collect a usbmon trace showing what > > happens when this device is plugged in. Instructions are in the kernel > > source file Documentation/usb/usbmon.txt. > > > > root@kalau:~# ls /sys/kernel/debug/usb/usbmon > 0s 0u 1s 1t 1u 2s 2t 2u > > "cat /proc/bus/input/devices" not display anything about this > keyboard. http://pastebin.com/0ZE73huZ > > kholis@kalau:~$ lsusb > Bus 002 Device 013: ID 0926:3333 > Bus 002 Device 012: ID 04cc:1521 ST-Ericsson USB 2.0 Hub > Bus 002 Device 005: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse > Bus 002 Device 004: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 > multicard reader > Bus 002 Device 003: ID 04f2:b1c1 Chicony Electronics Co., Ltd > Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > since lsusb mention it in Bus 002 Device 013. i try to to catch debug > message on bus 2 then unplugged and plugged it again. > # cat /sys/kernel/debug/usb/usbmon/2u > /tmp/1.mon.out > here is the output. http://pastebin.com/PpwME8hQ . I try to grep to > display bus 002 device 013 only. http://pastebin.com/MXymDKjK The log shows that the device was working until you unplugged it. Then when you plugged it back in again, it didn't work -- it crashed when it received a Get-String-Descriptor request. Is that what usually happens? Does the keyboard sometimes work okay and sometimes not? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
