linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wayne Sherman <Wayne@SystemDesignWorks.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: AHCI support on Intel chipsets (confusion?)
Date: Sat, 02 Dec 2006 02:48:29 -0800	[thread overview]
Message-ID: <457159FD.4000804@SystemDesignWorks.com> (raw)
In-Reply-To: <c384c5ea0612020232n3d33cfady627987e98957d495@mail.gmail.com>

Leon,

  Thanks for the reply.  I have enabled SATA Enhanced mode, but still 
did not see any mention of AHCI in my dmesg output.  I also did not find 
a setting for AHCI in the BIOS.  My board is a Gigabyte:

http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?&ProductID=2304

   I was about to email GigaByte and ask them about AHCI, but I decided 
to do a search first.  That is when I found the Intel page that says 
ICH7 does not support AHCI.  If that is so, then I need a different 
motherboard.  Can you confirm that ICH7 does not support AHCI?

Thanks,

Wayne


Leon Woestenberg wrote:
> Wayne,
> 
> On 12/2/06, Wayne Sherman <Wayne@systemdesignworks.com> wrote:
>> Jeff Garzik,
>> ...
>> my decision on the kernel source code.  It seems to indicate the Intel
>> ICH7 is AHCI compatible:
>>
> We (yesterday) found out that our board (a Supermicro PDSMI+, ICH7 as
> well) needs the proper BIOS setting in order for it to appear as a
> AHCI capable controller.
> 
> Precisely, we found if we enabled "SATA Enhanced Mode", then enabled
> "AHCI" in the BIOS, the chipset identifies itself as a 0x27c1 device
> rather than a 0x27c0 device.
> 
> This is probably exactly the issue you ran into. Try your BIOS settings.
> 
> Regards,
> 
> Leon Woestenberg.
> 

  reply	other threads:[~2006-12-02 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 10:20 AHCI support on Intel chipsets (confusion?) Wayne Sherman
2006-12-02 10:32 ` Leon Woestenberg
2006-12-02 10:48   ` Wayne Sherman [this message]
2006-12-02 10:53   ` Wayne Sherman
2006-12-03 13:34 ` Tejun Heo
2006-12-03 19:39   ` Wayne Sherman
2006-12-03 20:32     ` Leon Woestenberg

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=457159FD.4000804@SystemDesignWorks.com \
    --to=wayne@systemdesignworks.com \
    --cc=jgarzik@pobox.com \
    --cc=leon.woestenberg@gmail.com \
    --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).