On 10/30/07, Matheus Izvekov <mizvekov@xxxxxxxxx> wrote: > On 10/30/07, Michael Tokarev <mjt@xxxxxxxxxx> wrote: > > Eric D. Mudama wrote: > > > On 10/30/07, Michael Tokarev <mjt@xxxxxxxxxx> 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. > Anything i could do to help debug this? or perhaps it makes more sense to just blacklist NCQ for this particular drive? - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
