Miralinux Blog

  • Home
  • Linux
    • Scripts
    • CentOS
  • Apple
  • Microsoft
    • Features
    • Office
    • Windows
  • Learning
  • Games
  • Multimedia
    • XBMC
  • Other
    • About WordPress
  • Links
    • General
    • Software
      • Autocad
    • Hardware
      • BIOS
    • Linux
    • WiKieS

Posted on 2010/10/10 by arno Posted in Uncategorized

Source: http://www.techsupportforum.com/hardware-support/motherboards-bios-cpu/45869-alpe-asp-sata-setting-p5ad2.html

ALPE and ASP:
According to Intel SATA documents, ALPE means “Aggressive Link Power Management Enable”, and ASP means “Aggressive Slumber/Partial”. The two bits work together. ALPE is like an enable; when ALPE is off, ASP is ignored. When ALPE is on, ASP is also enabled, and allows controlling certain power-related aspects of the SATA ports: basically it allows your ICH6R Southbridge chip to power some stuff down if something figures out it’s not needed.

Asus doesn’t let you control ALPE and ASP separately, and it’s probably unnecessary anyway. Instead they give you the one BIOS field that turns on some [fixed] combination of these two bits.

Staggered Spinup Support:
This is one of the features available when ASP is on. According to Maxtor documents, this is a feature that lets hard disks that have gone to sleep (“slumber”) or are otherwise starting from a stopped condition, to power up sequentially instead of all at once. Because a drive draws most of its power during spinup, systems with many drives in them can strain the power supply. With staggered spinup active, the idea is that you can have more drives in the system on a smaller power supply. Your DiamondMax 10 is one of the newer drives that supports this feature, although it may be dependent on your supply’s wiring harness… I can’t quite tell, this being the first time I’ve seen this new feature. If your drives and cabling support this feature, I think it would be safe to set it to Enabled.

AHCI Port 3 Interlock Switch:
This is another new feature available when ASP is on. I think that this has something to do with hot-swapping disk drives; Intel documents refer to this as “Hot Plug Support”. It has something to do with being able to detect if a disk drive has been removed from the system. The ICH6R Port Control Register has bits for four ports, numbered 0 to 3. Because Asus’ BIOS only refers to Port 3, I suspect they may only be attempting to provide Hot Plug Support on Port 3 (probably the “SATA4” port on most mobo models, unless they numbered it backwards in which case it’s “SATA1”, or unless if by “Port 3” they really mean “SATA3”… I can’t tell for sure).

This would be considered a fairly Advanced usage of this motherboard. Unless you plan to hot-swap one (and only one) Intel SATA drive, you can probably leave this feature Disabled.

Regarding 32-bit data transfer,
this is a standard field in all the AMIBIOS’ IDE configuration, not just SATA ports, and not just your mobo model. If I recall, it is here because a lot of legacy O/S’s, drivers, and disk controllers weren’t fully 32-bit compliant. Particularly if you are attaching, say, an older CDROM device or something like that. Also if you usually transfer small random chunks of data, being forced to transfer 32 bits all the time could hurt performance instead of helping it… though I think this unlikely.

I think Disabled is the usual setting, and I think this means to use the lowest common denominator, which is 16-bit transfers. This makes sense, because mobo manufacturers don’t want you to have a DOA experience just because you happened to hook up a very old piece of hardware. I have never found a need to enable it, and my systems all run fine. But since all peripherals are newer now, maybe I should try the 32 bits sometime.

« DNS Transfer / Reload from master, what is what ?
Apache – ‘content-negotiation’ aka ‘Extentionless URLs’ »
  • Login
  • Mother of all Portals
  • .Handy .Handig
  • Links – wikis – wikies

Archives

  • June 2022
  • October 2021
  • June 2021
  • September 2016
  • April 2016
  • March 2016
  • November 2014
  • September 2014
  • August 2014
  • July 2014
  • April 2014
  • March 2014
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • February 2013
  • December 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
CyberChimps ©2025