> Dnia środa, 13 lipca 2005 18:21, Alan Stern napisał:
> Artur:
>
> Have you had a chance to try that last patch I sent?  Your symptoms are
> very much like those seen by other people, who were all helped by the
> patch.  So there's a very good chance it will fix your problem too.
>
> Alan Stern


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 :-)

Best regards
Artur Szymiec 

Attachment: 2_6_12_plus_patches.log.tar.gz
Description: application/tgz

Reply via email to