From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jan De Luyck <lkml@kcore.org>,
USB Storage list <usb-storage@lists.one-eyed-alien.net>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Genesys USB 2.0 enclosures
Date: Sun, 4 Sep 2005 14:04:46 -0700 [thread overview]
Message-ID: <20050904210446.GA16290@one-eyed-alien.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509032151040.5675-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On Sat, Sep 03, 2005 at 09:53:19PM -0400, Alan Stern wrote:
> On Sat, 3 Sep 2005, Jan De Luyck wrote:
>
> > I've posted in the past about problems with these enclosures - increasing the
> > delay seems to fix it, albeit temporarily. The further you go in using the
> > disk in such an enclosure, the higher the udelay() had to be - atleast that's
> > what I'm seeing here (I've got two of these now :/ )
> >
> > One permanent fix is adding a powered USB-hub in between the drive enclosures
> > and the computer. Since I've done that, I've no longer seen any of the
> > problems (i've attached the 'fault' log). Weird but true, since the drives
> > come with their own powersupply.
> >
> > Hope this helps anyone in the future running into the same problem.
>
> This one certainly goes into the Bizarro file.
>
> Just out of curiosity -- when you use the powered hub, does the drive work
> even if you remove that delay completely?
Aren't USB 2.0 hubs more "intelligent" as part of the requirement to
support 1.1 and 2.0 devices? I wonder if it's really a 2.0 drive, and if
the timing is different enough with the hub to make a difference.
Matt
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
THEY CASTRATED MY QUAKE BITS! I WANT THEM BACK!!!!
-- Greg
User Friendly, 3/27/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-04 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0412151627350.2419-100000@ida.rowland.org>
[not found] ` <200503291344.42951.lkml@kcore.org>
[not found] ` <42499406.7090406@ipom.com>
2005-09-03 16:12 ` Genesys USB 2.0 enclosures Jan De Luyck
2005-09-04 1:53 ` [linux-usb-devel] " Alan Stern
2005-09-04 8:46 ` Jan De Luyck
2005-09-04 21:04 ` Matthew Dharm [this message]
2005-09-04 22:10 ` Grant Coady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050904210446.GA16290@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=lkml@kcore.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox