I see similar results. Tho, sometimes it does work (the error & reset recovery eventuall get us back to a working state).
This is an interesting failure, because I don't think we're really doing anything different here than under 2.4.x -- it's just an INQUIRY command. One problem (it looks like) is that usb_device_reset() isn't returning when we request that the device get reset. That's pretty messed up, in and of itself. Doing a quick test, my Zip250 (self-powered) works just fine. So does my Zip750. Doing some tests with my Zip100, I can see that the system gets into a state where I can send a CBW, but not get a CSW. It almost looks like the data toggles are screwed up or something, but those sorts of HCD bugs were purged a long time ago. As Ged points out, I am pretty busy. So if you could generate a log similar to what you gave, but for a working 2.4 kernel, that would be helpful. Actually, send both as I'm also CC'ing the usb-storage development list on this. Matt On Sun, Mar 14, 2004 at 11:59:34AM +0000, Ged Haywood wrote: > Hi there, > > According to > > http://www2.one-eyed-alien.net/~mdharm/linux-usb/ > > your drive is one of those that M. Dharm has available to him, so I > guess he'll be looking at it. You might have to be patient, this USB > stuff keeps him pretty busy when he's not otherwise occupied. :) > > On Fri, 12 Mar 2004, [iso-8859-15] Andr� Welter wrote: > > > I'm trying to get my USB Zip100 working with kernel 2.6. It works just fine > > under 2.4. > > 73, > Ged. -- Matthew Dharm Home: [EMAIL PROTECTED] Maintainer, Linux USB Mass Storage Driver NYET! The evil stops here! -- Pitr User Friendly, 6/22/1998
pgp00000.pgp
Description: PGP signature
