Re: libsata doesn't like bus without master

["Patrick Ale" <patrick.ale@gmail.com>]

On 2/11/07, Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> On Sun, 11 Feb 2007, Robert Hancock wrote:
> > Then in that case you should set the remaining drive as master. That's
> > just the way PATA is. A lot of BIOSes won't even detect a drive that's
> > set as slave with no master present.

> For some stupid reason, it appears that the norm around here (Brazil) is
> that "no brand" boxes get assembled with ATAPI devices in slave mode.
> Usually they attach it to the second channel using an 40-wire cable, even if
> there is nothing using the first channel.

Yes, this is actually one of the reasons i mentioned sometimes having
only a slave drive can be a "legal" way to connect drives. I've lived
in Curitiba and Rio for a while (familiar cities to you I guess) and
sometimes we just had no choice to yank the master drive out of its
bay and keep running with what we had, cause money wasnt exactly
growing in trees where I used to work.

Next to that, we had the so called "paraguay" quality assembled
hardware, which basicly means someone, somewhere put some hardware
together and if it didnt work, you had a problem since its all you
could get.

Now, I agree with Robert, people should assemble and maintain their
hardware as much as possible, following the specs. But sometimes it
just isnt possible to do that, for whatever the reason might be. And I
honestly havent found any old or new mainboard that doesnt allow you
to have only a slave drive. I did see the opposite tho. A master drive
that just refused to get detected cause the jumper wasnt set to
"master only" (hello Western Digital).

I don't know, the error i saw is nothing critical, I am just wondering
how valid the "abnormal" notation is, if you go by the specs of ATA,
yes, it is. If you go by daily practice, then in my honest opinion, it
isnt.

Then again, there are way more important things to deal with right now
than cosmetics :)


Patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/