Nothing Special   »   [go: up one dir, main page]

Advanced Host Controller Interface: Difference between revisions

Content deleted Content added
→‎Operating system support: add link + reference for ArcaOS
Citation bot (talk | contribs)
Alter: template type. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_webform 24/3850
 
(17 intermediate revisions by 16 users not shown)
Line 1:
{{Short description|Computer standard for SATA host controllers}}
{{refimprove|date=August 2012}}
{{redirect-distinguish|AHCI|Arts and Humanities Citation Index}}
{{Infobox technology standard
| title = AHCI
Line 25 ⟶ 26:
| website = {{URL|https://www.intel.com/content/www/us/en/io/serial-ata/ahci.html}}
}}
The '''Advanced Host Controller Interface''' ('''AHCI''') is a technical standard defined by [[Intel]] that specifies the operation[[Hardware register|register-level interface]] of [[Serial ATA]] (SATA) [[host controller]]s in a non-implementation-specific manner in its [[Intel chips|motherboard chipsets]].<ref name=":0" />
 
The specification describes a system memory structure for computer hardware vendors to exchange data between host system [[computer memory|memory]] and attached [[computer storage device|storage devices]]. AHCI gives software developers and hardware designers a standard method for detecting, configuring, and programming SATA/AHCI adapters. AHCI is separate from the SATA 3&nbsp;Gbit/s standard, although it exposes SATA's advanced capabilities (such as [[hot swapping]] and [[Native Command Queuing|native command queuing]]) such that host systems can utilize them. For modern [[Solid-state drive|solid state drives]], the interface has been superseded by [[NVM Express|NVMe]].<ref>{{citationCite web|title=NVMe vs. SATA: Which SSD Technology Is Faster?|url=https://www.howtogeek.com/657972/nvme-neededvs.-sata-which-ssd-technology-is-faster/|access-date=October 20192020-10-10|website=www.howtogeek.com}}</ref>
 
{{As of|December 2019}}, theThe current version of the specification is 1.3.1.
 
== Operating modes ==
Many SATA controllers offer selectable modes of operation: legacy [[AT Attachment|Parallel ATA]] emulation (more commonly called IDE Mode), standard AHCI mode (also known as Native Mode), or vendor-specific [[RAID]] (which generally enables AHCI in order to take advantage of its capabilities). Intel recommends choosing RAID mode on their [[motherboard]]s (which also enables AHCI) rather than AHCI/SATA mode for maximum flexibility.<ref name="intel">{{cite web |url=http://www.intel.com/support/chipsets/imsm/sb/CS-015988.htm |title=Intel Matrix Storage Technology - Changing and/or choosing Serial ATA Modes |publisher=Intel |accessdateaccess-date=2007-09-30}}</ref> Legacy mode is a software [[Backward compatibility|backward-compatibility]] mechanism intended to allow the SATA controller to run in legacy operating systems which are not SATA-aware or where a driver does not exist to make the operating system SATA-aware.
 
When a SATA controller is configured to operate in LegacyIDE Mode, the number of storage devices per controller is usually limited to four (two IDE channels, master device and slave, device with up to two devices per channel), compared to the maximum of 32 devices/ports when configured in AHCI mode.<ref>{{cite web |url=http://www.bswd.com/pciide.pdf |title=PCI IDE Controller Specification 1.0 |publisher=Berg Software Design |accessdateaccess-date=2015-05-03}}</ref><ref name=":0">{{cite web |url=http://www.intel.com/content/www/us/en/io/serial-ata/serial-ata-ahci-spec-rev1-3-1.html |title=Serial ATA AHCI: Specification, Rev. 1.3.1 |publisher=Intel Corp. |accessdateaccess-date=2015-05-03}}</ref> But the [[chipset]] SATA interfaces may emulate more than one "IDE controller" when configured in IDE Mode.
 
== Operating system support ==
AHCI is supported out of the box on [[Windows Vista]] and later, [[Linux]]-based operating systems (since version 2.6.19 of the [[Linux kernel|kernel]]), [[OpenBSD]] (since version 4.1), [[NetBSD]] (since version 4.0), [[FreeBSD]] (since version 8.0),<ref>{{Cite web|url=https://www.freebsd.org/cgi/man.cgi?ahci(4)|title = Ahci(4)}}</ref>, [[macOS]], [[GNU Mach]], [[ArcaOS]],<ref>{{cite web|url=https://www.arcanoae.com/wp-content/uploads/wiki/ArcaOS-changes.txt|title=ArcaOS Changelog|access-date=2020-08-24}}</ref> [[eComStation]] (since version 2.1), and [[Solaris 10]] (since version 8/07).<ref>{{cite web|url=http://docs.sun.com/app/docs/doc/817-0547/gevhg?a=view |title=What's New in the Solaris 10 8/07 Release - Driver Enhancements |publisher=Oracle |accessdateaccess-date=2010-10-20 }}{{dead link|datearchive-url=June 2017https://web.archive.org/web/20071025053159/http://docs.sun.com/app/docs/doc/817-0547/gevhg |bot=InternetArchiveBot |fixarchive-attempteddate=yes 2007-10-25}}</ref> [[DragonFlyBSD]] based its AHCI implementation on OpenBSD's and added extended features such as port multiplier support. Older versions of operating systems require hardware-specific drivers in order to support AHCI. [[Windows XP]] and older do not provide AHCI support out of the box.
 
=== System drive boot issues ===
Some operating systems, notably [[Windows Vista]], [[Windows 7]], [[Windows 8]], [[Windows 8.1]] and [[Windows 10]], do not configure themselves to load the AHCI driver upon boot if the SATA controller was not in AHCI mode at the time the operating system was installed. Although this is an easily rectifiable condition, it remains an ongoing issue with the AHCI standard.
 
The most prevalent symptom for an operating system (or systems) that are installed in IDE mode (in some BIOS firmware implementations otherwise called 'Combined IDE mode'), is that the system drive typically fails to boot, with an ensuing error message, if the SATA controller (in BIOS) is inadvertently switched to AHCI mode after OS installation. In Microsoft Windows the symptom is a boot loop which begins with a Blue Screen error, if not rectified - and through no fault of Microsoft Windows.
 
Technically speaking, this is an implementation bug with AHCI that can be avoided, but it has not been fixed yet. As an interim resolution, Intel recommends changing the drive controller to AHCI or RAID before installing an operating system.<ref name="intel"/> (It may also be necessary to load chipset-specific AHCI or RAID drivers at installation time, for example from a USB flash drive).
 
On Windows Vista and Windows 7, this can be fixed by configuring the <code>msahci</code> device driver to start at boot time (rather than on-demand). Setting non-AHCI mode (i.e. IDE or Combined mode) in the [[BIOS]] will allow the user to boot into Windows, and thereby the required [[Windows registry|registry]] change can be performed. Consequently, the user then has the option of continuing to use the system in Combined mode or switching to AHCI mode.<ref>{{cite web |url=http://support.microsoft.com/kb/922976 |title=Error Message when you start a Windows 7 or Windows Vista-based computer after you change the SATA mode of the boot drive: "STOP 0x0000007B INACCESSABLE_BOOT_DEVICE" |publisher=Microsoft |accessdateaccess-date=2011-04-20 |archiveurlarchive-url=https://web.archive.org/web/20110524021238/http://support.microsoft.com/kb/922976 |archivedatearchive-date=24 May 2011 |url-status=live}}</ref>
WithInter alia with Windows 10 and 8, this can be fixed by forcing the correct drivers to reload during [[Safe Mode]].<ref>{{cite webnews |url=http://www.tenforums.com/performance-maintenance/15006-attn-ssd-owners-enabling-ahci-mode-after-windows-10-installation.html |title=Enabling AHCI mode AFTER Windows 10 installation |publisher=tenforums.com user Toobad |accessdateaccess-date=2015-12-19}}</ref>
 
In Windows 8, Windows 8.1 and [[Windows Server 2012]], the controller driver has changed from <code>msahci</code> to <code>storahci</code>,<ref>{{cite web |url=http://msdn.microsoft.com/en-us/library/windows/desktop/hh848066%28v=vs.85%29.aspx |title=StorAHCI replaces MSAHCI (Windows) |publisher=Microsoft}}</ref> and the procedures to upgrade to the AHCI controller is similar to that of Windows 7.<ref>{{cite web |url=http://www.happysysadm.com/2012/12/intel-g530-nas-performance-part-3.html |title=Improving performance of SATA drives on Windows 2012}}</ref> On Windows 8, 8.1 and Windows Server 2012, changing from SATAIDE mode to AHCI mode without first updating the registry will make the boot drive inaccessible (i.e. resulting in a recurring boot loop, which begins with a Blue Screen error).
 
In Windows 10, after changing the controller to AHCI mode, if the OS is allowed to reboot a couple of times after the start of the boot loop, which starts with an INACCESSIBLE_BOOT_DEVICE BSOD, Windows presents recovery options. Out of the Advanced options, if Startup Repair option is selected, Windows attempts to fix the issue and the PC begins to function normally.
 
A similar problem can occur on Linux systems if the AHCI driver is compiled as a [[kernel module]] rather than built into the [[kernel image]], as it may not be included in the [[initrd]] (initial RAM disk) created when the controller is configured to run in Legacy Mode. The solution is either to build a new initrd containing the AHCI module, or to build the AHCI driver into the kernel image.<ref>{{cite web|url=http://www.novell.com/support/kb/doc.php?id=3744228 |title=Support &#124; How to enable AHCI support after install |publisher=Novell.com |accessdateaccess-date=2014-05-11}}</ref>
 
== Power management ==