From: "Dieter Stüken" <stueken@conterra.de>
To: linux-ide@vger.kernel.org
Subject: Re: IDENTIFY DEVICE not working any more?
Date: Mon, 15 Aug 2005 15:54:13 +0200 [thread overview]
Message-ID: <43009E85.40606@conterra.de> (raw)
In-Reply-To: <4300998D.6000205@dtbb.net>
Tyler wrote:
> Were the 2.6.11 kernels you have included with a distribution such as
> ubuntu, fedora, etc? If it was, there's a good chance that it has the
> passthru libata patch, that allows you to access drives using smartctl,
> with the special ata flag.
That may be the explanation: I used prebuild kernels from SuSE and got the
illusion the SMART enabled libata went into the recent kernels since 2.6.9
by default. So I'll try with the libata patch explicitely again.
Thanks for the tip.
Dieter.
--
Dieter Stüken, con terra GmbH, Münster
stueken@conterra.de
http://www.conterra.de/
(0)251-7474-501
prev parent reply other threads:[~2005-08-15 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 9:07 IDENTIFY DEVICE not working any more? Dieter Stüken
2005-08-15 10:34 ` Erik Slagter
2005-08-15 13:18 ` Dieter Stüken
2005-08-15 13:33 ` Tyler
2005-08-15 13:54 ` Dieter Stüken [this message]
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=43009E85.40606@conterra.de \
--to=stueken@conterra.de \
--cc=linux-ide@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).