On Fri, 11 Feb 2011, Jiri Kosina wrote: > On Wed, 9 Feb 2011, Alan Stern wrote: > > > > > The trace shows nothing at all -- just the constant probing of the card > > > > reader. It looks like you didn't even plug in the keyboard while > > > > running usbmon. > > > > > > > >> Keyboard produce nothing when I typed it in text editor, in web > > > >> browser, in shell, etc. Indeed, no character appear on screen at all. > > > > > > > > That's a new problem. Maybe Jiri has some ideas that can help. > > > > > > > Yeah. its very strange. Because the keyboard is works well in Windows > > > (XP/Vista/7), Solaris 11 Express and FreeBSD 8.1 > > > > > > > One thing you might try: As root, do "lsusb -v" while the keyboard is > > > > plugged in normally. > > > > > > > Here is the "lsusb -v" output. http://pastebin.com/wCACHY7h . The > > > keyboard is on: > > > Bus 002 Device 007: ID 0926:3333 > > > Bus 002 Device 006: ID 04cc:1521 ST-Ericsson USB 2.0 Hub > > > > At this point I'm out of ideas. Let's see what Jiri suggests. > > Sorry, I am somehow not seeing the complete thread. Has the problem with > -EPIPE during probe been solved or not? The whole thread is here: http://marc.info/?t=129610043500002&r=1&w=2 Yes, the patch I sent to kholis fixes the -EPIPE error. Now the device appears to be working correctly, judging by the usbmon trace. But the system still ignores any typing on the keyboard. > I understand that /dev/input/eventX device node is created for the > keyboard, right? (/proc/bus/input/devices will tell). kholis? 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
