From: Tim Small <tim@seoss.co.uk>
To: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: WRITE DMA EXT failures with JM20330 based sata2ide
Date: Thu, 09 Jun 2011 20:38:25 +0100 [thread overview]
Message-ID: <4DF12131.1070507@seoss.co.uk> (raw)
In-Reply-To: <BANLkTimuGOGxJgKJsxUc6ACzEcZwgQuTWw@mail.gmail.com>
On 09/06/11 15:31, Tejun Heo wrote:
> Hello,
>
> On Mon, Jun 6, 2011 at 8:51 PM, Manuel Reimer
> <Manuel.Spam@nurfuerspam.de> wrote:
>
>> I've converted a 1,5TB SATA drive to IDE to run it on a UDMA100 IDE
>> controller.
>>
> You're having a genuine transmission problem and I think
> fixing the underlying hardware issue would be the better choice than
> mucking with EH behaviors.
>
FWIW, I've played with three different makes and models of SATA<->PATA
bridges at one time or another, and only one of them actually worked
reliably with hard drives - all seemed to be OK with optical drives, but
I assume that was down to their lower transmission speeds / throughput.
If you have any PCI or PCIe slots available, then you may be better off
buying a cheap add-in SATA controller instead (e.g. Silicon Image 3132,
or second-hand 3124, or Marvell 88SExxxx).
Cheers,
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
prev parent reply other threads:[~2011-06-09 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 18:51 WRITE DMA EXT failures with JM20330 based sata2ide Manuel Reimer
2011-06-09 14:31 ` Tejun Heo
2011-06-09 19:38 ` Tim Small [this message]
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=4DF12131.1070507@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=Manuel.Spam@nurfuerspam.de \
--cc=linux-ide@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).