linux-kernel - Re: SATA Drive No Longer Recognized In New 2.6.20 Kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070212163337.3af55213.randy.dunlap@oracle.com>
Date:	Mon, 12 Feb 2007 16:33:37 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	"Joseph Cosby" <jo-cosby@...mail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: SATA Drive No Longer Recognized In New 2.6.20 Kernel

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 ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/