On Tue, 13 Dec 2005, Brian Stumm wrote: > Alan Stern wrote: > > > On Mon, 12 Dec 2005, Brian Stumm wrote: > > > > > > If you really get desperate, you can use the usbmon facility to trace > > > > the > > > > URBs sent under Linux and you can use USB Snoopy to trace the URBs sent > > > > under Windows. Perhaps comparing the two will highlight a crucial > > > > difference. It's not an easy job, though. You have to understand what > > > > each URB does and you have to be able to decode the hex data. > > > > > > Having a bit of trouble getting usbmon to work in linux. I cannot seem to > > > get > > > the *.java files to compile. Also I see the driver under drivers/usb/mon > > > but I > > > cannot insert it into the kernel, I get unresolved symbol > > > usb_mon_deregister. > > > > That's the wrong usbmon! The one you want is built into the Linux kernel. > > Yea I read about that prior to that posting and that is where I run into the > usb_mon_deregister unresolved symbol mentioned before.
You need to rebuild the drivers/usb/core directory when building usbmon. That's where the missing usb_mon_deregister is. > Do the HID Driver maintainers ever read this list? I don't know. I have the impression that a lot of USB developers don't read this list. They tend to concentrate more on linux-usb-devel. > Tried e-mailing [EMAIL PROTECTED] > last week but no reply. It can be hard to attract his attention. > Who else maintains the driver? Running out of stabs in the > dark to attempt ;) Nobody else, as far as I know. However Dmitry Torokhov <[EMAIL PROTECTED]> does a lot of work on input drivers and he can be very helpful. > Enabled even more debugging today and getting much more data. I can even see > that it > is mapping the mouse stuff. If I press keyboard buttons things print to > screen but > not with mouse and obviously mouse still not working. Here is what prints: I can't help you with this; I don't know enough about how the input subsystem works. > Something else new from dmesg > > usb 1-2: new low speed USB device using uhci_hcd and address 3 > uhci_hcd 0000:00:10.0: uhci_result_control: failed with status 440000 > [c59c0240] link (059c01b2) element (03cff040) > 0: [c3cff040] link (03cff080) e0 LS Stalled CRC/Timeo Length=7 MaxLen=7 DT0 > EndPt=0 > Dev=0, PID=2d(SETUP) (buf=01292c00) > 1: [c3cff080] link (03cff0c0) e3 SPD LS Active Length=0 MaxLen=7 DT1 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd20) > 2: [c3cff0c0] link (03cff100) e3 SPD LS Active Length=0 MaxLen=7 DT0 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd28) > 3: [c3cff100] link (03cff140) e3 SPD LS Active Length=0 MaxLen=7 DT1 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd30) > 4: [c3cff140] link (03cff180) e3 SPD LS Active Length=0 MaxLen=7 DT0 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd38) > 5: [c3cff180] link (03cff1c0) e3 SPD LS Active Length=0 MaxLen=7 DT1 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd40) > 6: [c3cff1c0] link (03cff200) e3 SPD LS Active Length=0 MaxLen=7 DT0 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd48) > 7: [c3cff200] link (03cff240) e3 SPD LS Active Length=0 MaxLen=7 DT1 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd50) > 8: [c3cff240] link (03cff280) e3 SPD LS Active Length=0 MaxLen=7 DT0 > EndPt=0 Dev=0, > PID=69(IN) (buf=03d9cd58) > 9: [c3cff280] link (00000001) e3 LS IOC Active Length=0 MaxLen=7ff DT1 > EndPt=0 > Dev=0, PID=e1(OUT) (buf=00000000) This means that the device failed to respond to the SETUP packet of a control transfer. That pretty much indicates the device (or its firmware) is dead and needs to be reset or power-cycled. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
