From: Paulo da Silva <psdasilva@esoterica.pt>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Strange behaviour with SATA disks. Light always ON
Date: Tue, 27 Sep 2005 21:54:45 +0000 [thread overview]
Message-ID: <4339BFA5.6070000@esoterica.pt> (raw)
In-Reply-To: <43376FD1.2020306@shaw.ca>
Robert Hancock wrote:
> Paulo da Silva wrote:
>
>> Hi!
>> I don't know if this is the right place to ask
>> about this, or even if this is a problem at all.
>>
>> Anyway I didn't find relevant information on
>> this ...
>>
>> I have just bought a new PC with two SATA drives.
>> I had no problems to have them working,
>> apparently fine except for one thing:
>> After reading the kernel, the driver access light (led?)
>> is always on!
>> Is this normal? Why?
>
>
> I don't know if this is considered "normal" but I know that the
> Silicon Image chips do have a strange way of handling the access light
> - it has to be specifically turned on and off by a GPIO pin in the
> driver, the chip doesn't seem to handle it itself..
>
Is there any intention to correct this?
Should I file a bug?
I think this should be trivial for those
who know the driver ...
BTW, the kernel configuration has a specific "option" for
Silicon Image SATA, but if I choose it without "ahci"
the system does not boot! Why?
Thanks
next prev parent reply other threads:[~2005-09-27 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4QP2K-4ML-7@gated-at.bofh.it>
2005-09-26 3:49 ` Strange behaviour with SATA disks. Light always ON Robert Hancock
2005-09-27 21:54 ` Paulo da Silva [this message]
[not found] <4QSjW-N8-7@gated-at.bofh.it>
[not found] ` <4QSjW-N8-5@gated-at.bofh.it>
[not found] ` <4RuIM-7uQ-39@gated-at.bofh.it>
2005-09-28 0:45 ` Robert Hancock
2005-09-26 1:24 Paulo da Silva
2005-09-28 6:46 ` Jens Axboe
2005-09-28 20:14 ` Paulo da Silva
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=4339BFA5.6070000@esoterica.pt \
--to=psdasilva@esoterica.pt \
--cc=hancockr@shaw.ca \
--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;
as well as URLs for NNTP newsgroup(s).