mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philippe Grenard <philippe.grenard@m4x.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (Another?) Seagate / Sil3112a problem...
Date: Fri, 15 Sep 2006 09:45:25 +0200	[thread overview]
Message-ID: <200609150945.26129.philippe.grenard@m4x.org> (raw)
In-Reply-To: <45096B80.3040303@gmail.com>

Ok,

here are more informations, and i believe now this is not a software problem 
of any kind...

3 things i remarked : 

1/ when changing cables, i still had problems with ata1 : for me, this would 
sound like the controller "ata1" has maybe issues, as ata2 worked before...
2/ when swapping cables, I had problems with ata2 too : this would mean the 
cable had also some issues...
3/ maybe, (but i'm not sure...) the drive needs its own power cable : I mean, 
when the power cable , which contains a "sata plug" and a "ide plug" is 
connected to sata alone, it seems to work better than when the cable is 
connected to both a ide and a sata drive , or the graphic card and the sata 
drive....
since I got a 430 W True Power PSU from Antec, i don't really believe the 
problem is a power problem, but maybe it was too much on one cable??

I'll stop at it, since it seems to work fine, with a config like "1drive -  
ata2 - own power cable". If I go into more troubles, i will try more tests 
and if I arrive to any kind of conclusion, i will let you know about it!

thanks again for the help,

Philippe

  parent reply	other threads:[~2006-09-15  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 10:21 philippe.grenard
2006-09-14 14:47 ` Tejun Heo
2006-09-14 19:07   ` Philippe Grenard
2006-09-15  7:45   ` Philippe Grenard [this message]
     [not found] ` <20061109135956.b744a3a7.akpm@osdl.org>
     [not found]   ` <200701071704.36288.philippe.grenard@m4x.org>
2007-01-08  3:52     ` Tejun Heo

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=200609150945.26129.philippe.grenard@m4x.org \
    --to=philippe.grenard@m4x.org \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@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

Powered by JetHome