> Dear Alan,
>
> thank You very much for interest :-).
> I see this problem is interesting :-).
>
> Yes obviously I tried this patches but here is full story of mean time
> activities:
> I have a motherboard with 4 USB ports on the back and additional 2 on
> the pin's to connect the front USB ports in my tower.
> Then I found that the cables for front motherboards aren't shielded
> properly - I tried to use the backports again.
> I tried it before - just at the beginning of our discussion - but somehow
> maybe
> I've done something wrong, stupid etc. - at that time it didn't work.
> Now I tried it again - and oops ! - Even on my current Kernel 2.6.11 the
> system recognized the device and mounted it !!!
> I would like to say flawless victory .... but I can't .........here are
> details:
>
> 1) The copy to the USB player is OK in 80% - sometimes it hangs up in the
> middle and the device become "dead" - I need to plug it in again. The
> successfully copied files are 100% OK.
> 2) The copy from the device is OK in 25% - very often it hangs up in some
> place - same dead as above ..... successfully copied files are 100% OK.
>
> The above phenomenas seems do not depend from file count - It can hang up on
> the 1 big file or even first small file ... no rule at all.
>
> Regarding cables to the front ports - I've changed them to proper ones that
> the results are now same on the back ports and the front ones.
>
> I'm sending You the latest log from 2.6.12-2 kernel with your latest 2
> patches.
> Tomorrow I'll try this player on one more different hardware platform -
> I'll let You know the result - this can be good point cause on this "test"
> platform
> with Win 2K the player works correctly - let us see what will happen with
> Knoppix on the same machine.
>
> I suspect that from this log You'll say that the device itself is a problem -
> cause
> other devices worked well on the front ports even before shielding
> (Creative,HP) -
> then maybe this device is a bit "shit" on hardware level and Your great
> driver has nothing to it ?
> But still the point is how Win can handle it ... more flexible timings ?
>
> but let us hope that You'll find something :-)
Interesting. It looks like shielding may still be a problem, although
a smaller problem than before...
Is it possible for you to try this test using 2.6.13-rc2? Those patches
probably won't apply correctly, or at least, the second one won't. You
may have to add by hand a line saying
sdev->scsi_level = SCSI_2;
to the slave_configure() routine in drivers/usb/storage/scsiglue.c.
My reason for asking is because 2.6.13-rc2 includes improved error
recovery in usb-storage compared to 2.6.11 or 2.6.12. In fact it's the
same scheme as Windows uses. (Although I still don't understand why there
didn't appear any examples where Windows got these same sorts of errors in
the usb-snoop log you sent.)
Alan Stern
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
