Difference between revisions of "Problems with SATA and Linux"

From ThinkWiki
Jump to: navigation, search
(No DMA on system hard disk)
(No disk power management)
Line 92: Line 92:
 
The Linux SATA system currently does not support power management commands. This is under development.
 
The Linux SATA system currently does not support power management commands. This is under development.
  
The above patches for SMART support resolves this by enabling the {{cmdroot|hdparm -y}} command (spin down) and the {{cmdroot|hdparm -S}} command (automatic spin down timeout). The {{cmdroot|hdparm -M}} command (acoustic management) is still rejected. (Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)
+
The above patches for SMART support resolves this, as it also enables the following commands:
 +
* {{cmdroot|hdparm -y}} (spin down)
 +
* {{cmdroot|hdparm -S num}} (automatic spin down timeout)
 +
* {{cmdroot|hdparm -B num}} (advanced power management level)
 +
Note that this command is still rejected:
 +
* {{cmdroot|hdparm -M num}} (acoustic management)
 +
(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)
  
Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up.
+
Note that even when [[Laptop-mode]] is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the {{path|/proc/sys/vm/block_dump}} facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the {{T43}}, none of the {{path|/proc/acpi/ibm/thermal}} values corresponds to the disk's built-in temperature sensor).
  
 
==No disk information==
 
==No disk information==

Revision as of 12:37, 2 October 2005

Some ThinkPad models use a SATA controller for the system hard disk. This causes several complications for Linux installation. The following lists these problems and known workarounds. Note that the details are often version- and distribution-specific.

Models using a SATA disk interface

Models using a SATA controller and a SATA system disk:

Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:

Hang on resume from suspend to RAM

Linux kernels (as of 2.6.14-rc2) do not support suspend and resume for SATA devices. As a result, the machine hangs upon the first disk access after resume. A kernel patch LKML posting) is available that provides SATA power-management support and makes Suspend to RAM work on the T43 and X41 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. (On the T43p the patch has not been tested so far but should work as well. The R52 uses SATA and sleep doesn't work, so it is probably affected too.)

Patches

Some distributions already include this patch (e.g., Ubuntu Breezy), but some don't (e.g., Fedora 4).

Failed resume from suspend to disk

Suspend to disk (using swsusp or swsusp2) needs to load the memory image from the SATA disk. For this to work, you either need an initrd with all the necessary SATA modules, or the SATA drivers compiled into the kernel.

DVD drive not recognized

The ata_piix SATA driver grabs ownership over the IDE ports when it is loaded, but (by default) does not support PATA ATAPI devices such as the Ultrabay optical drives. Thus, if IDE support is compiled as a module and loaded after ata_piix, the DVD drive will not be recognized by either driver.

The following configurations do work:

  • Compile IDE into the kernel (non-module).
  • Compile both IDE and SATA as modules and make sure IDE is loaded first.
  • Pass the hdc=noprobe kernel/module argument, which tells the IDE system to ignore the drive.
  • Enable PATA ATAPI support in the SATA system (experimental; see below).

Note that the optical drive must be in the Ultrabay during system boot (Ultrabay device swapping is currently unsupported).

No DMA on DVD drive

Using the IDE driver, DMA support cannot be enabled on an Ultrabay optical drive:

# hdparm -d1 /dev/hdc

/dev/hdc:
 setting using_dma to 1 (on)
 HDIO_SET_DMA failed: Operation not permitted
 using_dma    =  0 (off)

As a result, the optical drive is slow, and in particular, too slow to play video DVDs.

One workaround is to use employ the SATA driver (instead of the IDE driver) for the optical drive. This requires enabling two featues of the SATA driver, namely ATAPI support and PATA support, which are both in active development and far from stable. Using this will probably devour all your data and go on to eat all the food in your fridge. But if you have full backups and an empty fridge, do the following:

  • Grab the latest kernel, since these feature are under active development (these instructions where tested with 2.6.14-rc2).
  • Configure the IDE system as modules, to get it out of the way (maybe it can be completely removed).
  • Configure the SATA system (and in particular the ata_piix driver) as built-in.
  • In include/linux/libata.h, set
#define ATA_ENABLE_PATA
  • In drivers/scsi/libata-core.c, set
int atapi_enabled = 1

(An untested alternative to the last step is to compile the SATA system as modules, make sure it is loaded before the IDE modules, and pass the "atapi_enabled=1" module parameter.)

There have been reports that DVD burning doesn't work under this configuration, but it seems to work with kernel 2.6.14-rc2 (tested on a ThinkPad T43 with a UltraBay Slim DVD Multi-Burner Plus).

NOTE!
If you are aware of a more reliable solution to this issue, please update this page.

No DMA on system hard disk

In some Linux kernels, both the SATA driver and the IDE driver can handle the system hard disk. With the SATA driver, it shows as /dev/sda and DMA is enabled. With the IDE driver, it shows as /dev/hda and DMA is disabled.

The simplest way to enable DMA is to force the IDE driver to ignore the system hard disk by passing the hda=noprobe kernel argument. The driver will then be handled by the SATA driver. Note that this will change its device name to /dev/sda (which may require changes in /etc/fstab and the boot loader) and may cause other problems as listed above.

(Observed on a ThinkPad T43 with Fedora Core kernel 2.6.13-1.1526_FC4.)

No SMART support

The Linux SATA system currently does not support SMART commands (e.g., via smartctl). This is under development.

A patch is available:

After applying the patch, run smartctl with the "-d ata" parameter:

# smartctl -d ata -a /dev/sda

(Tested on ThinkPad T43 with kernel 2.6.13.1.)

No disk power management

The Linux SATA system currently does not support power management commands. This is under development.

The above patches for SMART support resolves this, as it also enables the following commands:

  • # hdparm -y (spin down)
  • # hdparm -S num (automatic spin down timeout)
  • # hdparm -B num (advanced power management level)

Note that this command is still rejected:

  • # hdparm -M num (acoustic management)

(Tested with patched kernels 2.6.13.1 and 2.6.12-4 and a 60GB 7200RPM disk model HTS726060M9AT00.)

Note that even when Laptop-mode is used, the "hddtemp" daemon (as shipped with Fedora Core 4) will wake up the disk every minute, and must thus be disabled for power management to be effective. Its accesses are not visibile through the /proc/sys/vm/block_dump facility. It is unclear whether disk temperature can be monitored without causing the disk to spin up (on the T43, none of the /proc/acpi/ibm/thermal values corresponds to the disk's built-in temperature sensor).

No disk information

With mainline kernels (as of 2.6.14-rc2), the disk information cannot be read via either of:

  • # hdparm -i /dev/sda
  • # hdparm -I /dev/sda

The latter is fixed by the above patch for SMART support.

BIOS error 2010 on user-installed hard disk

While not a Linux issue, note that there is an issue with installing alternative PATA (IDE) hard disks as the system drive. Unless the disk is one of the few approved disks listed inside the BIOS, you will get an BIOS error 2010 during system boot, and the disk may operate unreliably. This seems to be enforced due to limitations (bugs?) of the SATA-to-PATA bridge, and currently the only reliably way to avoid it seems to be to use only drives sold by IBM specifically for use in these ThinkPad models.

There are no such limitations for disks used in the UltraBay Slim 2nd Hard Drive Adapter. It is not known whether any limitations apply to the models, listed at the top of this page, that use a SATA system drive (i.e., no SATA-to-PATA bridge).