On Mon, 19 Sep 2011, netdevil77 wrote: > >On Sun, Sep 18, 2011 at 11:17:45AM -0500, Malcolm wrote: > >> Hi > >> I'm a helper on the openSUSE forums and a user has an issue with a > >> njytouch USB touchscreen device ( Thread is here > >> http://forums.opensuse.org/showthread.php?t=465251 ) > >> > >> The output from dmesg shows the following error; > >> > >> [16691.882588] usb 3-3: Product: Љ > >> [16691.882591] usb 3-3: Manufacturer: Љ > >> [16691.903041] generic-usb: probe of 0003:0EEF:0001.0004 failed with error -32 > >> > >> Then in the lsusb info it shows; > >> > >> iManufacturer 1 ? > >> iProduct 2 ? > >> > >> Would this be causing the usbtouchscreen to fail? If so, would a > >> modified quirks.c help? > > > >I don't think those two things have any correlation, as the i* fields > >are just strings, and something else above caused the probe error. > > > >It would be good to get a usbmon dump of what happens when the device is > >plugged in in order to properly determine what is going on > >here. > > > >thanks, > > > >greg k-h > > Hi, > > I am the user having the issue with the njytouch USB touchscreen > device. I have created the usbmon output (see attachment). I hope the > output is long enough, I really have no idea how much you need. This is fine. The usbmon output shows that the touchscreen is buggy. It fails to send its report descriptor to the computer. And this has nothing to do with the bizarre Manufacturer and Product strings that the device sends -- those are simply bugs. Instead of sending the actual string contents, the device sends the Language Code for English. Has this device ever worked on any system? If so, can you send a similar usbmon log for that system? The only thing I can think of that might help is to get rid of the Set-Idle request. But that's far from guaranteed, and in any case, there's no quirk setting to do it. One would have to be written. 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
