https://bugzilla.kernel.org/show_bug.cgi?id=217862 --- Comment #19 from Alan Stern (stern@xxxxxxxxxxxxxxxxxxx) --- Are you referring to the attachment in comment #16? Whatever error messages it contains are completely swamped by the usb-storage verbose debugging output; in practice it's impossible to find them. In any case, we've pretty much reached the limit of my knowledge about this driver. Everything so far has involved fixing some pretty straightforward bugs (i.e., bad interactions between the driver and the rest of the kernel), but problems involving the data sent between the driver and the device are beyond me, since I have no idea how Alauda devices are meant to work. If you want to proceed farther, there are two things you might try. One is to get in touch with the people who originally wrote the driver, to see if they still remember how it's supposed to operate and can help fix the problems. The other is to try running an older version of the Linux kernel, back from when the driver did work right (assuming it ever did -- something I'm not sure of). If you do manage to find a version of the driver that works, comparing it with the current version may indicate what needs to be fixed. One other thing: You remember that comparing the usbmon trace with the Windows Wireshark recording showed that the Linux driver was using the wrong endpoint for some of its commands. Well, in fact the recording shows that Windows uses _both_ bulk_OUT endpoints at various times. Therefore the fact that the Linux driver uses only one of them is rather suspicious. But I don't know what each endpoint is supposed to do or when they are supposed to be used. (Also, this is partly why I wonder whether the driver ever really worked, given that it has never used more than one of the bulk-OUT endpoints. Just possibly, the devices it was written for were somehow different from the device you are using now.) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
