From: "Matheus Izvekov" <mizvekov@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Eric D. Mudama" <edmudama@gmail.com>,
linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: AHCI + ST3160023AS + NCQ problems
Date: Tue, 30 Oct 2007 22:28:56 -0200 [thread overview]
Message-ID: <305c16960710301728j557689a5rbec52a11ec606963@mail.gmail.com> (raw)
In-Reply-To: <472788F4.60300@msgid.tls.msk.ru>
On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
> Eric D. Mudama wrote:
> > On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
> >> By the way, did you forget to remove a jumper on the drive
> >> (the only jumper installed by default) that limits drive
> >> usage to SATAI?
> > ...
> >> ..etc. Try again without the jumper? Note that NCQ is NOT supported
> >> in SATAI mode, or there were some pre-standard implementations of it.
> >> In SATAII, NCQ is standard (well... more or less anyway ;)
> >
> > Huh?
> >
> > To my knowledge, the jumper should only limit the bus rate to
> > 1.5Gbit/s, for compatibility with one or more chipsets. It shouldn't
> > affect the command set supported by the device.
>
> The thing is that I don't know. I had some other probs with seagate
> sata drives when the jumper was there. So I learned a lesson -
> always remove the jumper before using their drives. I don't want
> to test which other restrictions this and other drive families
> apply when jumpered... ;)
>
> /mjt
>
Indeed removing the jumper of sdb made it be recognised as SATA2. But
sdc, what the problem is really about, is neither SATA2, not has any
jumper whatsoever. but both the manufacturer and libata claim it
supports NCQ.
next prev parent reply other threads:[~2007-10-31 0:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 0:13 AHCI + ST3160023AS + NCQ problems Matheus Izvekov
2007-10-30 10:52 ` Michael Tokarev
2007-10-30 13:15 ` Eric D. Mudama
2007-10-30 19:41 ` Michael Tokarev
2007-10-31 0:28 ` Matheus Izvekov [this message]
2007-11-07 6:21 ` Matheus Izvekov
2007-11-12 3:04 ` Tejun Heo
2007-12-07 20:54 ` Matheus Izvekov
2007-12-07 23:51 ` Tejun Heo
2007-12-08 0:39 ` Matheus Izvekov
2007-12-09 10:39 ` 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=305c16960710301728j557689a5rbec52a11ec606963@mail.gmail.com \
--to=mizvekov@gmail.com \
--cc=edmudama@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).