On Fri, 11 Aug 2006, Christian Axelsson wrote: > >>> I guess the hub is built directly into the X-pad. > >>> > >>> This may or may not help... If you build a kernel with CONFIG_USB_DEBUG > >>> set, the dmesg log will then contain more detailed information about what > >>> happens when you plug in the X-pad. > >> Said and done. The result, snipped from my kern.log (dmesg buffer got > >> flooded) is attached... I dont really know what to make out of it except > >> that it seems to verify that it the pad has it's own hub.
Yes, you're right. Well, the log shows a bunch of problems but it doesn't indicate how they might be fixed. Basically, the computer fails to receive several replies from the device -- or else the device fails to send the replies, hard to say which. And oddly enough, the X-pad's internal hub disables the internal port connecting the main device. I have no idea why any of these things is happening. My only guess would be some sort of hardware incompatibility, but you said that the same device attached to the same computer worked when the computer ran Windows. So the guess appears pretty unlikely. The fact that it worked with a different Linux computer suggests that there's very nothing wrong with the drivers. But it doesn't suggest any scheme for getting the device to work where you want it. Does the behavior change if you plug the USB cable into any of the other ports? Alan Stern ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
