From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Joseph Cosby" <jo-cosby@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA Drive No Longer Recognized In New 2.6.20 Kernel
Date: Mon, 12 Feb 2007 16:33:37 -0800 [thread overview]
Message-ID: <20070212163337.3af55213.randy.dunlap@oracle.com> (raw)
In-Reply-To: <BAY120-F15C225BC4817C7D84BC43E83900@phx.gbl>
On Mon, 12 Feb 2007 17:30:38 -0700 Joseph Cosby wrote:
> Hi,
> Until recently I was using the 2.6.18 kernel. I have a SATA hard drive
> that was detected by the kernel, using the PIIX driver. But after
> updating to 2.6.20, the hard drive is no longer detected by the kernel.
> I used make oldconfig to create the 2.6.20 config file, and I noticed a
> new option CONFIG_ATA. I did not use this, because as I understand it is
> not necessary and is experimental. Do I need to use this or is there
> something else in the new kernel that needs to be enabled for this
> driver?
Yes, you need CONFIG_ATA for SATA after 2.6.18.
(prod) == production level code, not experimental (that only
applies to the PATA drivers)
> My 2.6.20 config file follows.
> The hard drive has vendor ID 8086 and device ID 27c0. It is listed in the
> modules.pcilist file of 2.6.18 but not 2.6.20.
>
> If anybody can share any advice please CC me in response.
>
> #
> # Serial ATA (prod) and Parallel ATA (experimental) drivers
> #
> # CONFIG_ATA is not set
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-02-13 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jh6bEu1Gx0021e119@bay0-omc3-s26.bay0.hotmail.com>
2007-02-13 0:30 ` Joseph Cosby
2007-02-13 0:33 ` Randy Dunlap [this message]
[not found] <fa.N6er7HcCs0nD4LsKNkIdtRxShpk@ifi.uio.no>
[not found] ` <fa.TnmEtAvuWo/QaHolplJ1wxgmx8A@ifi.uio.no>
2007-02-13 0:43 ` Robert Hancock
[not found] <BAY120-F18A42FB31328FBBDDFC8B183900@phx.gbl>
2007-02-13 1:34 ` Randy Dunlap
2007-02-13 18:55 ` Joseph Cosby
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=20070212163337.3af55213.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jo-cosby@hotmail.com \
--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
all inboxes | Powered by JetHome®