>> I tested the device driver at two other PCs (a single and a quad CPU >> Intel processor) with three different kernels (i.e. distributions >> SuSE SLES 9, openSuSE 11.0, openSuSE 11.1) and it worked just fine. >> >> At the System which shows the problem we first used libusb 0.1.12 to communicate with the device, >> and the problem did not show up there. >> >> Then we began to develop our own device driver for some reason. >> Maybe the problem was not triggered with libusb, because with the kernel device driver the data throughput is now three times faster. >> >> I don't know if it gets lost by hardware or software. > > You should be able to find out by running those SuSE kernels on the > "bad" computer. If the problem persists then it isn't caused by > software. > > Alan Stern I just did that. The "bad" computer also shows the same error with openSuSE 11.0 the same error. This may point to a hardware problem? But why does the problem not show up whith libusb? Guenter Gebhardt -- 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
