Advanced Host Controller Interface

From Wikipedia, the free encyclopedia

Jump to: navigation, search
 This article or section is missing information about: AHCI and other operating systems.
This concern has been noted on the talk page where it may be discussed whether or not to include such information. (December 2007)
This article may require cleanup to meet Wikipedia's quality standards. Please improve this article if you can. (March 2009)
This article contains instructions, advice, or how-to content. The purpose of Wikipedia is to present facts, not to train. Please help improve this article either by rewriting the how-to content or by moving it to Wikiversity or Wikibooks.

The Advanced Host Controller Interface (AHCI) is a programming-specification which defines the operation of Serial ATA host-controllers (also known as host bus adapters) in a non implementation-specific manner. The specification describes a system memory structure for computer hardware vendors in order to exchange data between host system memory and the attached storage-devices. As of June 2008, the current version of the specification is v. 1.3.[1] AHCI offers software developers and hardware designers a standard method for detecting, configuring, and programming SATA/AHCI adapters. AHCI is separate from the Serial ATA-II standard, although it exposes SATA's advanced capabilities (such as hot-plugging and native command queuing) such that host-systems can utilize them.

Many SATA controllers offer selectable modes of operation: legacy Parallel ATA, standard AHCI-mode, or vendor-specific RAID. Intel recommends choosing RAID mode on their motherboards (which also enables AHCI) rather than the plain AHCI/SATA mode for maximum flexibility, due to the issues caused when the mode is switched once an operating system has already been installed.[2] Legacy-mode is a software backward-compatibility mechanism intended to allow the SATA-controller to run in legacy operating-systems which are not SATA-aware.

AHCI is fully supported out of the box for Microsoft Windows Vista and the Linux operating system from kernel 2.6.19.[3] NetBSD also supports drivers in AHCI mode out of the box in certain versions. OpenBSD has had an ahci driver since OpenBSD 4.1. FreeBSD supports AHCI as well. AHCI support for Solaris 10 has been introduced in the 8/07 release [4]. Older operating systems require drivers written by the host bus adapter vendor in order to support AHCI.

Contents

[edit] Common problems switching to AHCI under Windows

  • Enabling AHCI in a system's BIOS will cause a 0x7B Blue Screen of Death STOP error (INACCESSIBLE_BOOT_DEVICE) on installations of Windows XP and Windows Vista where AHCI/RAID drivers for that system's chipset are not installed; i.e., boot failure.[5] Switching the chipset to AHCI mode involves changing the BIOS settings and will not work. Usually, manual installation of new drivers is required before enabling AHCI in BIOS.[6] Alternatively, a "Repair" installation with the appropriate driver loaded during the setup process usually corrects the problem. For motherboards with more than one Sata controller (for example, some boards have Intel and Jmicron Sata controllers) another alternative is possible. The sata cable for the boot drive can be inserted into a port on one controller (which can be configured in IDE mode), allowing the machine to boot successfully with the other controller configured for AHCI mode. The AHCI drivers can then be installed in windows without difficulty before swapping the cable back.
  • For Intel chipsets (for example, Intel ICH9) drivers are available from either an OEM motherboard or computer manufacturer. For the Intel versions, the driver must be loaded before loading the OS (by pressing F6 as setup starts, then using the floppy disk when prompted). The Intel drivers will work for both XP and Vista. Also, in the case of ICH9, an unsupported method to enable AHCI on ICH9 is available.
  • When attempting to install Windows XP or a previous version on an AHCI-enabled system, setup will fail with the error message "setup could not detect hard disk drive..." since no drivers will be found for accessing the SATA controller/s. This problem can be corrected by either using a floppy disk or by slipstreaming the appropriate drivers into the Windows XP installation CD, or by turning on IDE emulation in the BIOS settings if it's available (usually labelled COMPATIBILITY or ACPI).
  • Enabling AHCI in a system with Windows Vista already installed will result in a BSoD if SATA was configured in IDE mode during Vista's installation. Before enabling AHCI in the BIOS, users must first follow the instructions found at Microsoft Knowledge Base article 922976. This fix also works with the Windows 7 Beta.
  • Enabling AHCI in a system BIOS on installations of Windows XP or Windows Vista will cause SATA Optical drives to disappear. A Hotfix for Windows Vista is available under the title: "SATA optical drives are not available after you start a Windows Vista-based computer."[7] This problem was fixed in Vista SP1.
  • Windows Vista installation process may take several hours on a system that uses an AMD/ATI SB600 Series chipset operating in AHCI mode.[8]

[edit] Common problems switching to AHCI under Linux

  • The AHCI controller does not work on AMD/ATI RS400-200, and RS480 HBA; and Nvidia nForce 560 chipset[citation needed] when MSI is enabled due to a hardware error. In order for AHCI to work users must provide the "pci=nomsi" kernel boot parameter. With MSI disabled in this way, the PCIe bus can only act as a faster PCI bus with hotplug capabilities.
  • The AHCI controller on AMD/ATI SB600 HBA can't do 64-bit DMA transfers. 64-bit addressing is optional in AHCI 1.1 and the chip claims it can do them, but, in reality, it can't so it is disabled. After that it will be forced to do 32-bit DMA transfers. Thus DMA transfers will occur in the lower 4 GB region of the memory, and bounce buffers must be used sometimes if there is more than 4 GB of RAM.[9]
  • The VIA VT8251 South bridge suffers the same fate but it can be circumvented with the "pci=nomsi" option to force detection of the chip. This has been tested to work on 2.6.26, 2.6.24 and 2.6.20 kernels.
  • Under RHEL, CentOS and similar, if you change your BIOS to AHCI mode and do not have the ahci drivers in your initrd then you will not be able to boot. To solve this
    • Set your BIOS to IDE/ATA/Original setting mode
    • boot into linux
    • edit /etc/modprobe.conf and add the line alias scsi_hostadapter2 ahci
    • run mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`
    • reboot in to you BIOS and set to AHCI/RAID mode
    • boot into linux
    • check your vendors manual for more details

[edit] References

  1. ^ Serial ATA Advanced Host Controller Interface (AHCI) homepage. Intel, Inc. Retrieved on 2008-08-20.
  2. ^ Intel Matrix Storage Technology - Changing and/or choosing Serial ATA Modes. Intel, Inc. Retrieved on 2007-09-30.
  3. ^ Serial ATA (SATA) Linux hardware/driver status report - Dunvegan Media
  4. ^ What's New in the Solaris 10 8/07 Release
  5. ^ Microsoft KB article 922976
  6. ^ How to Install Ahci Support for Ati Sb600 Sata Controllers on Existing Windows Installations
  7. ^ SATA optical drives are not available after you start a Windows Vista-based computer. Microsoft KB article 928253, revision 1.5. Retrieved on 2007-07-27.
  8. ^ Microsoft KB article 931369
  9. ^ ahci: disable 64bit dma on sb600

[edit] External links

Retrieved from "http://en.wikipedia.org/wiki/Advanced_Host_Controller_Interface"
Personal tools