ThinkWiki - User contributions [en]

X301 Power Savings

2009-04-04T18:19:26Z

Gfbarros: added category

[[Category: X301]]
== x301 Power Savings ==

The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W to around 7W. powertop is an invaluable tool in figuring out how much power is being drawn by each component, not to mention seeing your progress. A lot of this information is covered in other pages, but this is specific to the x301. Note that these settings were tested on an x301 running a fresh Fedora 11 Beta install.
 

*I don't use bluetooth on a regular day... 
<code>
echo disabled > /proc/acpi/ibm/bluetooth
</code>
 

*The video system keeps one or more of the external connectors powered up at all times.
Anything with a '*' next to the mode is powered on:

<code>
[root@x301 ~]# xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm
1440x900 60.0*+ 50.0
DVI1 disconnected (normal left inverted right x axis y axis)
DVI2 connected (normal left inverted right x axis y axis)
1024x768 60.0*
800x600 60.3
640x480 59.9
</code>

So disable them with
<code>
xrandr --output DVI2 --off
</code>
 

*By default, the wifi driver keeps the card at the maximum power setting for better performance. If you are just browsing the web or not using a lot of bandwidth significant savings can be had by reducing this setting.{{footnote|1}}
<code>
echo 5 > /sys/class/net/wlan0/device/power_level
</code>
 

*Newer kernels are much smarter about how they load the cores on a CPU, this setting tells it to be more power efficient rather than performance oriented.{{footnote|2}}
<code>
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
</code>
 

*Hal will constantly poll the cdrom to see if a disk has been inserted and if it should mount and open it for you in X. Disabling this allows the cpu to sleep longer.
<code>
hal-disable-polling --device /dev/cdrom
</code>
 

*New features in the SATA driver allows it to power down the link when not utilized, make sure to enable on all paths with{{footnote|3}}
<code>
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo min_power > $foo;
done
</code>
 

*Similar savings can be had by setting the pcie bus to a more power-friendly mode
<code>
echo powersave > /sys/module/pcie_aspm/parameters/policy
</code>
 

*The sound hardware also has power savings settings
<code>
echo 5 > /sys/module/snd_hda_intel/parameters/power_save
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>
 

*Turning off Wake-On-Lan will save some power while your system is suspended or hibernated
<code>
ethtool -s eth0 wol d
</code>
 

*Powering down the usb bus while not in use is also beneficial
<code>
usbcore.autosuspend=1
</code>

{{footnotes|
#[http://www.lesswatts.org/tips/wireless.php#pm WiFi power saving mode (Power Save Poll, PS-Poll)]
#[http://www.lesswatts.org/tips/cpu.php#smpsched Scheduler tunables for multi-socket systems]
#[http://www.lesswatts.org/tips/disks.php#alpm SATA Aggressive Link Power Management]

}}

==External Resources==
* [http://itgen.blogspot.com/2009/03/energy-management-in-linux.html Energy management in Linux]
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.lesswatts.org/tips/index.php Less Watts Tips & Tricks]

X301 Power Savings

2009-04-04T18:18:06Z

Gfbarros: footnotes

== x301 Power Savings ==

The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W to around 7W. powertop is an invaluable tool in figuring out how much power is being drawn by each component, not to mention seeing your progress. A lot of this information is covered in other pages, but this is specific to the x301. Note that these settings were tested on an x301 running a fresh Fedora 11 Beta install.
 

*I don't use bluetooth on a regular day... 
<code>
echo disabled > /proc/acpi/ibm/bluetooth
</code>
 

*The video system keeps one or more of the external connectors powered up at all times.
Anything with a '*' next to the mode is powered on:

<code>
[root@x301 ~]# xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm
1440x900 60.0*+ 50.0
DVI1 disconnected (normal left inverted right x axis y axis)
DVI2 connected (normal left inverted right x axis y axis)
1024x768 60.0*
800x600 60.3
640x480 59.9
</code>

So disable them with
<code>
xrandr --output DVI2 --off
</code>
 

*By default, the wifi driver keeps the card at the maximum power setting for better performance. If you are just browsing the web or not using a lot of bandwidth significant savings can be had by reducing this setting.{{footnote|1}}
<code>
echo 5 > /sys/class/net/wlan0/device/power_level
</code>
 

*Newer kernels are much smarter about how they load the cores on a CPU, this setting tells it to be more power efficient rather than performance oriented.{{footnote|2}}
<code>
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
</code>
 

*Hal will constantly poll the cdrom to see if a disk has been inserted and if it should mount and open it for you in X. Disabling this allows the cpu to sleep longer.
<code>
hal-disable-polling --device /dev/cdrom
</code>
 

*New features in the SATA driver allows it to power down the link when not utilized, make sure to enable on all paths with{{footnote|3}}
<code>
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo min_power > $foo;
done
</code>
 

*Similar savings can be had by setting the pcie bus to a more power-friendly mode
<code>
echo powersave > /sys/module/pcie_aspm/parameters/policy
</code>
 

*The sound hardware also has power savings settings
<code>
echo 5 > /sys/module/snd_hda_intel/parameters/power_save
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>
 

*Turning off Wake-On-Lan will save some power while your system is suspended or hibernated
<code>
ethtool -s eth0 wol d
</code>
 

*Powering down the usb bus while not in use is also beneficial
<code>
usbcore.autosuspend=1
</code>

{{footnotes|
#[http://www.lesswatts.org/tips/wireless.php#pm WiFi power saving mode (Power Save Poll, PS-Poll)]
#[http://www.lesswatts.org/tips/cpu.php#smpsched Scheduler tunables for multi-socket systems]
#[http://www.lesswatts.org/tips/disks.php#alpm SATA Aggressive Link Power Management]

}}

==External Resources==
* [http://itgen.blogspot.com/2009/03/energy-management-in-linux.html Energy management in Linux]
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.lesswatts.org/tips/index.php Less Watts Tips & Tricks]

X301 Power Savings

2009-04-04T18:11:02Z

Gfbarros: formating

== x301 Power Savings ==

The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W to around 7W. powertop is an invaluable tool in figuring out how much power is being drawn by each component, not to mention seeing your progress. A lot of this information is covered in other pages, but this is specific to the x301. Note that these settings were tested on an x301 running a fresh Fedora 11 Beta install.
 

*I don't use bluetooth on a regular day... 
<code>
echo disabled > /proc/acpi/ibm/bluetooth
</code>
 

*The video system keeps one or more of the external connectors powered up at all times.
Anything with a '*' next to the mode is powered on:

<code>
[root@x301 ~]# xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm
1440x900 60.0*+ 50.0
DVI1 disconnected (normal left inverted right x axis y axis)
DVI2 connected (normal left inverted right x axis y axis)
1024x768 60.0*
800x600 60.3
640x480 59.9
</code>

So disable them with
<code>
xrandr --output DVI2 --off
</code>
 

*By default, the wifi driver keeps the card at the maximum power setting for better performance. If you are just browsing the web or not using a lot of bandwidth significant savings can be had by reducing this setting.
<code>
echo 5 > /sys/class/net/wlan0/device/power_level
</code>
 

*Newer kernels are much smarter about how they load the cores on a CPU, this setting tells it to be more power efficient rather than performance oriented.
<code>
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
</code>
 

*Hal will constantly poll the cdrom to see if a disk has been inserted and if it should mount and open it for you in X. Disabling this allows the cpu to sleep longer.
<code>
hal-disable-polling --device /dev/cdrom
</code>
 

*New features in the SATA driver allows it to power down the link when not utilized, make sure to enable on all paths with
<code>
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo min_power > $foo;
done
</code>
 

*Similar savings can be had by setting the pcie bus to a more power-friendly mode
<code>
echo powersave > /sys/module/pcie_aspm/parameters/policy
</code>
 

*The sound hardware also has power savings settings
<code>
echo 5 > /sys/module/snd_hda_intel/parameters/power_save
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>
 

*Turning off Wake-On-Lan will save some power while your system is suspended or hibernated
<code>
ethtool -s eth0 wol d
</code>
 

*Powering down the usb bus while not in use is also beneficial
<code>
usbcore.autosuspend=1
</code>

==External Resources==
* [http://itgen.blogspot.com/2009/03/energy-management-in-linux.html Energy management in Linux]
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.lesswatts.org/tips/index.php Less Watts Tips & Tricks]

X301 Power Savings

2009-04-04T18:08:29Z

Gfbarros: typo fix

== x301 Power Savings ==

The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W to around 7W. powertop is an invaluable tool in figuring out how much power is being drawn by each component, not to mention seeing your progress. A lot of this information is covered in other pages, but this is specific to the x301. Note that these settings were tested on an x301 running a fresh Fedora 11 Beta install.

*I don't use bluetooth on a regular day... 
<code>
echo disabled > /proc/acpi/ibm/bluetooth
</code>

*The video system keeps one or more of the external connectors powered up at all times.
Anything wish a '*' next to the mode is powered on:

<code>
[root@x301 ~]# xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm
1440x900 60.0*+ 50.0
DVI1 disconnected (normal left inverted right x axis y axis)
DVI2 connected (normal left inverted right x axis y axis)
1024x768 60.0*
800x600 60.3
640x480 59.9
</code>

So disable them with
<code>
xrandr --output DVI2 --off
</code>

*By default, the wifi driver keeps the card at the maximum power setting for better performance. If you are just browsing the web or not using a lot of bandwidth significant savings can be had by reducing this setting.
<code>
echo 5 > /sys/class/net/wlan0/device/power_level
</code>

*Newer kernels are much smarter about how they load the cores on a CPU, this setting tells it to be more power efficient rather than performance oriented.
<code>
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
</code>

*Hal will constantly poll the cdrom to see if a disk has been inserted and if it should mount and open it for you in X. Disabling this allows the cpu to sleep longer.
<code>
hal-disable-polling --device /dev/cdrom
</code>

*New features in the SATA driver allows it to power down the link when not utilized, make sure to enable on all paths with
<code>
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo min_power > $foo;
done
</code>

*Similar savings can be had by setting the pcie bus to a more power-friendly mode
<code>
echo powersave > /sys/module/pcie_aspm/parameters/policy
</code>

*The sound hardware also has power savings settings
<code>
echo 5 > /sys/module/snd_hda_intel/parameters/power_save
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>

*Turning off Wake-On-Lan will save some power while your system is suspended or hibernated
<code>
ethtool -s eth0 wol d
</code>

*Powering down the usb bus while not in use is also beneficial
<code>
usbcore.autosuspend=1
</code>

==External Resources==
* [http://itgen.blogspot.com/2009/03/energy-management-in-linux.html Energy management in Linux]
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.lesswatts.org/tips/index.php Less Watts Tips & Tricks]

X301 Power Savings

2009-04-04T18:07:45Z

Gfbarros: mentioned fedora version used

== x301 Power Savings ==

The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W to around 7W. powertop is an invaluable tool in figuring out how much power is being drawn by each component, not to mention seeing your progress. A lot of this information is covered in other pages, but this is specific to the x301. Note that these settings were tested on an x301 running a fresh Fedora 11 Beta install.

*I don't use bluetooth on a regular day... 
<code>
echo disabled > /proc/acpi/ibm/bluetooth
</code>

*The video system keeps one or more of the external connectors powered up at all times.
Anything wish a '*' next to the mode is powered on:

<code>
[root@x301 ~]# xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm
1440x900 60.0*+ 50.0
DVI1 disconnected (normal left inverted right x axis y axis)
DVI2 connected (normal left inverted right x axis y axis)
1024x768 60.0*
800x600 60.3
640x480 59.9
</code>

So disable them with
<code>
xrandr --output DVI2 --off
</code>

*By default, the wifi driver keeps the card at the maximum power setting for better performance. If you are just browsing the web or not using a lot of bandwidth significant savings can be had by reducing this setting.
<code>
echo 5 > /sys/class/net/wlan0/device/power_level
</code>

*Newer kernels are much smarter about how they load the cores on a CPU, this setting tells it to be more power efficient rather than performance oriented.
<code>
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
</code>

*Hal will constantly poll the cdrom to see if a disk has been inserted and if it should mount and open it for you in X. Disabling this allows the cpu to sleep longer.
<code>
hal-disable-polling --device /dev/cdrom
</code>

*New features in the SATA driver allows it to power down the link when not utilized, make sure to enable on all paths with
<code>
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo min_power > $foo;
done
</code>

*Similar savings can be had by setting the pcie bus to a more power-friendly mode
<code>
echo powersave > /sys/module/pcie_aspm/parameters/policy
</code>

*The douns hardware also has power savings settings
<code>
echo 5 > /sys/module/snd_hda_intel/parameters/power_save
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>

*Turning off Wake-On-Lan will save some power while your system is suspended or hibernated
<code>
ethtool -s eth0 wol d
</code>

*Powering down the usb bus while not in use is also beneficial
<code>
usbcore.autosuspend=1
</code>

==External Resources==
* [http://itgen.blogspot.com/2009/03/energy-management-in-linux.html Energy management in Linux]
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.lesswatts.org/tips/index.php Less Watts Tips & Tricks]

X301 Power Savings

2009-04-04T18:06:49Z

Gfbarros: added external resources

== x301 Power Savings ==

The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W to around 7W. powertop is an invaluable tool in figuring out how much power is being drawn by each component, not to mention seeing your progress. A lot of this information is covered in other pages, but this is specific to the x301.

*I don't use bluetooth on a regular day... 
<code>
echo disabled > /proc/acpi/ibm/bluetooth
</code>

*The video system keeps one or more of the external connectors powered up at all times.
Anything wish a '*' next to the mode is powered on:

<code>
[root@x301 ~]# xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm
1440x900 60.0*+ 50.0
DVI1 disconnected (normal left inverted right x axis y axis)
DVI2 connected (normal left inverted right x axis y axis)
1024x768 60.0*
800x600 60.3
640x480 59.9
</code>

So disable them with
<code>
xrandr --output DVI2 --off
</code>

*By default, the wifi driver keeps the card at the maximum power setting for better performance. If you are just browsing the web or not using a lot of bandwidth significant savings can be had by reducing this setting.
<code>
echo 5 > /sys/class/net/wlan0/device/power_level
</code>

*Newer kernels are much smarter about how they load the cores on a CPU, this setting tells it to be more power efficient rather than performance oriented.
<code>
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
</code>

*Hal will constantly poll the cdrom to see if a disk has been inserted and if it should mount and open it for you in X. Disabling this allows the cpu to sleep longer.
<code>
hal-disable-polling --device /dev/cdrom
</code>

*New features in the SATA driver allows it to power down the link when not utilized, make sure to enable on all paths with
<code>
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo min_power > $foo;
done
</code>

*Similar savings can be had by setting the pcie bus to a more power-friendly mode
<code>
echo powersave > /sys/module/pcie_aspm/parameters/policy
</code>

*The douns hardware also has power savings settings
<code>
echo 5 > /sys/module/snd_hda_intel/parameters/power_save
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>

*Turning off Wake-On-Lan will save some power while your system is suspended or hibernated
<code>
ethtool -s eth0 wol d
</code>

*Powering down the usb bus while not in use is also beneficial
<code>
usbcore.autosuspend=1
</code>

==External Resources==
* [http://itgen.blogspot.com/2009/03/energy-management-in-linux.html Energy management in Linux]
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.lesswatts.org/tips/index.php Less Watts Tips & Tricks]

X301 Power Savings

2009-04-04T18:00:37Z

Gfbarros: â†Created page with '== x301 Power Savings == The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W t...'

== x301 Power Savings ==

The standard Fedora configuration provides for a lot of leeway in power savings. Here are the items I have modified that got me from around 11W to around 7W. powertop is an invaluable tool in figuring out how much power is being drawn by each component, not to mention seeing your progress. A lot of this information is covered in other pages, but this is specific to the x301.

*I don't use bluetooth on a regular day... 
<code>
echo disabled > /proc/acpi/ibm/bluetooth
</code>

*The video system keeps one or more of the external connectors powered up at all times.
Anything wish a '*' next to the mode is powered on:

<code>
[root@x301 ~]# xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm
1440x900 60.0*+ 50.0
DVI1 disconnected (normal left inverted right x axis y axis)
DVI2 connected (normal left inverted right x axis y axis)
1024x768 60.0*
800x600 60.3
640x480 59.9
</code>

So disable them with
<code>
xrandr --output DVI2 --off
</code>

*By default, the wifi driver keeps the card at the maximum power setting for better performance. If you are just browsing the web or not using a lot of bandwidth significant savings can be had by reducing this setting.
<code>
echo 5 > /sys/class/net/wlan0/device/power_level
</code>

*Newer kernels are much smarter about how they load the cores on a CPU, this setting tells it to be more power efficient rather than performance oriented.
<code>
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
</code>

*Hal will constantly poll the cdrom to see if a disk has been inserted and if it should mount and open it for you in X. Disabling this allows the cpu to sleep longer.
<code>
hal-disable-polling --device /dev/cdrom
</code>

*New features in the SATA driver allows it to power down the link when not utilized, make sure to enable on all paths with
<code>
for foo in /sys/class/scsi_host/host*/link_power_management_policy;
do echo min_power > $foo;
done
</code>

*Similar savings can be had by setting the pcie bus to a more power-friendly mode
<code>
echo powersave > /sys/module/pcie_aspm/parameters/policy
</code>

*The douns hardware also has power savings settings
<code>
echo 5 > /sys/module/snd_hda_intel/parameters/power_save
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>

*Turning off Wake-On-Lan will save some power while your system is suspended or hibernated
<code>
ethtool -s eth0 wol d
</code>

*Powering down the usb bus while not in use is also beneficial
<code>
usbcore.autosuspend=1
</code>

Category:X301

2009-04-04T17:31:19Z

Gfbarros: typo fix

{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad X301 ===
This page gives an overview of all ThinkPad X301 related topics.
==== Standard Features ====
* [[Intel Core 2 Duo SU9400]] 1.4 GHz
* Mobile Intel GM45 Express Chipset
* 256 MB [[Intel GMA X4500HD]] onboard graphics
** 13,3" LED Backlight WXGA+ 1440 x 900, 128 DPI
* 1-4 GB DDR3-RAM [[PC3-8500]]
* Solid State 64 or 128 GB SSD
* Ultraslim DVD burner
* [[MiniPCI Express slot]] 1 with one of the following:
** [[Intel WiFi Link 5100/5300 WLAN controller]]
* [[MiniPCI Express slot]] 2 with one of the following:
** none (empty)
** [[Ericsson F3507g Mobile Broadband Module]] (AT&T)
* [[Integrated camera]]
* [[Bluetooth]]
* AuthenTec Fingerprint scanner

* Size: 318 x 231 x 18.6 – 23.4 mm
* Weight: 1.33 kg to 1.42 kg

</div>
|style="vertical-align:top" |
[[image:x301.jpg|ThinkPad X301]]
|}

* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/43y9441.pdf Hardware Maintenance Manual Thinkpad X301] (5,503,105 Bytes)
* [http://redmonk.com/sogrady/2008/09/24/apone/ Ubuntu Hardy on an X301]
* [http://web.mit.edu/eefi/www/debian-thinkpad-x301/ Debian unstable on an X301]
* [http://binaryground.com/install-debian-lenny-thinkpad-x301 Install Debian Lenny (testing) on a ThinkPad X301]
* [http://www.linux-community.de/Internal/User-Blogs/Daniel-Gultsch/Lenovo-Thinkpad-X301-im-Test#Test Thinkpad X301 Test (German)]
* [[x301 Power Savings]]
[[Category:X Series]]

Category:X301

2009-04-04T17:30:24Z

Gfbarros: Added x301-specific power info

Talk:Problems with SATA and Linux

2006-06-27T18:38:35Z

Gfbarros: /* Patch against SATA-resume problem with T60 */

__TOC__

I'm running gentoo on my T43; I had problems with X11 (opensource radeon driver) and a SATA-patched kernel (I tried both 2.6.14 and 2.6.15-gentoo). Suspend to RAM worked nicely, but starting X freezed the machine after a short time. I tried removing radeonfb from the kernel; with vesafb, everything seems to work.

-- Stefan, 10 Jan 2006

--------
That's strange - with the libata passthrough (IDE driver not in kernel) as set up in the text, my t43p DVD drive also will not record as hinted in the wikipage... DMA works fine, so DVD playing / ripping is smooth and quick. CD record functions also are absent. I have PATA enabled, and the suspend + SMART patches applied over 2.6.14.2.
--------
I can confirm this with 2.6.14.4, however with 2.6.15/15.1 with sata_pm patch it works.

-- Rasto, 24 Jan 2006

--------
regarding the "BIOS error 2010 on user-installed hard disk":
the text says that corruption occurs if you use a harddisk without the specific ibm bios. would be interesting if it is possible to fix this problem in the kernel so that you can use any disk and the kernel doesn't use specific ATA commands which are known to cause problems.

in the tabook i didn't find any specification of the SATA bridge. it would be interesting:
1) what type it is
2) if it is fixed on the mainboard or if it is possible to solder in a new one

----

Another interesting question is whether these ThinkPads can be hacked to accept a real SATA system disk, by bypassing the SATA-to-PATA bridge (this would probably involve some soldering and cutting). If the BIOS can also handle that then it may come in handy, since some new high-capacity 2.5" disks have only SATA versions.
--[[User:Thinker|Thinker]] 02:56, 8 Oct 2005 (CEST)

----

'''Z series'''

Since the Z series uses a SATA controller and disk, without the bridge, would it be possible to make SATA ATAPI support as a module that you could load only when using the optical drive? Then, for everyday use, the experimental options of PATA and ATAPI with ata_piix would not be needed, moving you one step further in the direction of stability.

----

I have an R52 with Ubuntu Breezy and no problems with SATA (I personally asked the developers to include the needed patches).

However, I'd like to know wheter there are any advantages with this configuration. Future proof? Power saving? Speed?

Anybody cares to comment?

-- [[User:Micampe|Michele]]

Straight SATA, like in the Z60m/t, will provide better upgrade options in the long run (the hard disk industry is slowly but surely moving to SATA), and maybe a small performance increase if your drive, controller and OS support command queueing (they probably don't). However, with the hybrid ThinkPad models that use a SATA-to-PATA bridge, like your R52, you get all the drawbacks and none of the benefits; plus there's the horrible issue with [[Problem with non-ThinkPad hard disks|drive compatibility]]. My impression is that Lenovo did this just as a convenient (for them!) transition path, in order to use new chipsets without comitting to (temporarily) scarcer and more expensive drives. In any case, they didn't even have the decency to make the UltraBay Slim accept SATA drives.

--[[User:Thinker|Thinker]] 18:10, 3 Nov 2005 (CET)
----
There is a [[UltraBay Slim SATA HDD Adapter]], but only compatible with the Z series (at least for the moment).

--[[User:Tonko|Tonko]] 03:12, 4 Nov 2005 (CET)

== updated libata_passthru.patch ==

FYI: when using the Suspend-to-RAM patch from http://lkml.org/lkml/2005/9/23/97 against 2.6.14 the libata_passthru.patch from the article doesn't apply any more, so I've put up an updated version at http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

I give no warranties whatsoever whether it works or kills your hardware, but since I just removed duplicate parts already in the Suspend-to-RAM patch it should be ok.

--[[User:spiney|spiney]] 19:04, 4 Nov 2005 (CET)

Hi

Running 2.6.16-rc4 and I'm running into scsci errors and Input/output
errrors when resuming from suspend to ram. The suspend patch is
supposed to be in 2.6.16-rc1 and I'm booting with

title= 2.6.16-rc4
root (hd0,0)
kernel /boot/kernel-2.6.16-rc4 root=/dev/sda3 ro combined_mode=libata
libata.atapi_enabled=1 acpi_sleep=s3_bios processor.max_cstate=2
elevator=cfq ide1=noprobe

Thanks.

----

Don't know about -rc4, but -rc3 worked without problems, could you try that one instead? Maybe there was some bug introduced between these two versions. What's combined_mode=libata BTW?

--[[User:Spiney|spiney]] 08:28, 23 February 2006 (CET)
----

== ATA_ENABLE_PATA PCI IDs ==

Spiney, could you extend the article to explain what and why are the PCI IDs in the footnote about ATA_ENABLE_PATA?

--[[User:Thinker|Thinker]] 21:59, 4 Nov 2005 (CET)
----

Ok, done, feel free to fix the table because I'm a bit struggling with Wiki-style editing. ;) As for the why, those PCI IDs are the only ones affected by the ATA_ENABLE_PATA, as seen in {{path|drivers/scsi/ata_piix.c}} in the kernel source.

--[[User:spiney|spiney]] 11:19, 5 Nov 2005 (CET)
----

Will other cards work without ATA_ENABLE_PATA, or just fail? In the former case your instructions are right, but in the latter case we should tell the user to check the list of IDs in his ''current'' kernel and, if there's no match, to give up in the first place instead of following the rest of the instructions.

--[[User:Thinker|Thinker]] 12:48, 5 Nov 2005 (CET)
----

AFAICT if the chipset is supported by libata it will work, regardless of what low-level driver is used. Of course if there is no low-level driver for the chipset then even using the harddisk via libata will fail, but that's a different story. At least ATA_ENABLE_PATA will then make no difference since it's Intel PIIX (and compatible) only.

--[[User:spiney|spiney]] 13:24, 5 Nov 2005 (CET)
----

Not sure I got you. Is there any case where the instructions will work without ATA_ENABLE_PATA, given that all ThinkPad optical drives are PATA?

--[[User:Thinker|Thinker]] 13:41, 5 Nov 2005 (CET)
----

The instructions will work without ATA_ENABLE_PATA unless the Thinkpad uses one of the three chipsets listed in the article, as long as libata works at all, i.e. the system drive shows up as /dev/sda. The #define doesn't change the behaviour of libata for any other chipset, it's [http://linux.yyz.us/sata/sata-status.html#ich5 ata_piix] only.

Since I don't have a machine with one of the three chipsets (anyone?), I can't tell whether those work at all with libata, but I guess there's a reason why they're not enabled by default. It's just that defining ATA_ENABLE_PATA is only making sense for these three chipsets.

Any clearer now? If not, just run {{cmd|grep -r ATA_ENABLE_PATA /path/to/kernelsource|}} and see how seldom and where the #define is used.

--[[User:spiney|spiney]] 14:55, 5 Nov 2005 (CET)
----

All clear now. I thought it will work only if you have these chipsets ''and'' ATA_ENABLE_PATA=1. Thanks for the explanation!

--[[User:Thinker|Thinker]] 15:12, 5 Nov 2005 (CET)
----

Does any of the relevant ThinkPad models (listed in the article) use these chips? They look too old to be found on the SATA models.

--[[User:Thinker|Thinker]] 23:35, 9 Nov 2005 (CET)
----

I don't think so, I was about to add "in the unlikely event that you own one of these chipsets" or something.

--[[User:Spiney|spiney]] 07:56, 10 Nov 2005 (CET)
----

== DVD DMA with ide/sata as module ==

Did anyone get DVD DMA to work with either the IDE or SATA drivers compiled as modules? If so, please fill in the missing details in that section. I have it working only with both IDE and SATA built-in.

--[[User:Thinker|Thinker]] 17:58, 16 Nov 2005 (CET)
----

Basically using a Live-CD with a recent kernel (is there one with 2.6.14 already?) would be sufficient, since they usually use an initrd or something similar, don't they? I'll give the Debian distribution kernel a try when I get around to it (bit busy atm), after all there's 2.6.14 in sid.

But for people using their own kernel compiled from source I see no point in doing the module+initrd thing anyway, unless you want LVM for the root filesystem or other funky stuff.

--[[User:Spiney|spiney]] 19:22, 16 Nov 2005 (CET)
----

Hi

Can anyone tell me how those modules are called?

Thomas
--[[User:Thomas|thomas]] 19:48, 23 Jan 2006 (CET)
----

Where the hell do I find the libata module?

--[[User:squashball|squashball]] 09:09, 11 June 2006 (CET)

The relevant driver is called ata_piix. The ata_piix driver uses a chunk of shared kernel code called libata.

--[[User:Thinker|Thinker]] 09:33, 11 June 2006 (CEST)

Ok, Thanks. Nevertheless I am not able to get my drive working. It's a T60...

--[[User:squashball|squashball]] 12:29, 12 June 2006 (CET)

Your T60 uses AHCI by default. You have to change the BIOS settings to "compatibility mode" to use the HDD and DVD drive with ata_piix. Then, you're also able to hotswap your ultrabay. But for this, a patch for ibm_acpi is needed.

--[[User:Whoopie|Whoopie]] 14:57, 12 June 2006 (CEST)

Yeah, thanks, it's working now! Where was I supposed to find this info?
EDIT: But DMA is still off and can't be enabled.

--[[User:squashball|squashball]] 07:58, 13 June 2006 (CET)

DMA is enabled by default with libata. Do a "dmesg |grep DMA" and you'll see. You can't use hdparm to see the settings for your hdd. BTW, if you have more questions, you could join IRC ##ibmthinkpad.

--[[User:Whoopie|Whoopie]] 11:04, 13 June 2006 (CEST)
----

== occasional hang upon resume with various kernels ==

I keep having trouble with resume after suspend to ram. Occasionally, it takes longer to wake up and then is in a semi-hanged
state, i.e. nothing having to do with actual reading from the disk works. (what was running, as aterm
is still running, ls works, when the listing is buffered, but hangs if it is not).
Kernel is 2.6.15 with sata-pm patch. Later 2.6.15 kernels hang always and it's the same with 2.6.16.
Could perhaps somebody, for whom it works without problems post his .config somewhere?
I'm out of ideas.

--[[User:Rasto|Rasto]] 14:46, 20 March 2006 (CET)

I have the same problem with my x41 and 2.6.16 or 2.6.16-r1 running on Gentoo. Sometimes resume is ok and sometimes the disk doesn't resume. I can't see any log because the disk is unwritable after resume. The logs on F12 is full of io error.
I tested many different kernel configs, unloading modules before suspend, stopping services...
Like Rasto, I'm out of ideas...

--[[User:Pplr|Pplr]] 19:21, 8 April 2006 (CEST)

You could try http://rtr.ca/dell_i9300/kernel/kernel-2.6.16/02_libata_resume_fix.patch
This patch worked for me.

--[[User:Whoopie|Whoopie]] 21:21, 8 April 2006 (CEST)

Hello, according to the first lines of the article, resume does not work prior to kernel 2.6.16, i.e. the computer hangs up just a second after it comes back. I just switched from 2.6.15 to 2.6.16 but the problem still remains. I have a Z60M thinkpad. So this has obviously the same problem as the T60.

-- [[User:Bjoern.thalheim|BjÃ¶rn]] 14:37, 10 April 2006 (CEST)

Increasing the timeouts seems to do the trick. I applied it about two weeks ago, and it works since.

-- [[User:Rasto|Rasto]] 09:59, 11 April 2006 (CEST)

Ubuntu Dapper with 2.6.15-23 is also exhibiting this problem even though the sata_pm patch is applied. Bjorn, which timeout are you referring to?

-- [[User:nmuntz|nmuntz]] 09:08, 13 June 2006 (MDT)

== Suspend to RAM on X41 not working with Debian-packaged 2.6.16 ==

I just tried the Debian package of the Linux 2.6.16 kernel on my [[X41]] to see if suspend-to-RAM would work. Unfortunately, it didn't. The laptop suspends just fine, but when it's turned back on, the backlight remains off, there is a lot of disk activity for a while, and then the computer just shuts off. When turned on again, it boots normally. Suspend-to-disk works fine, just like before.

On a different note, CPU throttling broke on my system with the new kernel. I can no longer modprobe acpi-cpufreq. [[User:Ehn|Ehn]] 04:28, 22 March 2006 (CET)

:The latter issue was solved by using speedstep-centrino instead of acpi-cpufreq. [[User:Ehn|Ehn]] 23:25, 9 April 2006 (CEST)
----

Neither problem is related to this article, so it's unlikely to be answered here.

--[[User:Thinker|Thinker]] 17:37, 22 March 2006 (CET)
----

Hm. It seems to be a problem with sata power management for me, so I guess this could be one of the places.

[[User:Rasto|Rasto]] 17:45, 22 March 2006 (CET)
---

Ehn, by "disk activity" do you mean a constantly on HDD LED and no disk movement noises, or ''real'' disk activity with the LED flashing and disk noise? The former is likely to be the SATA problem, the latter rules out the SATA problem.

--[[User:Thinker|Thinker]] 18:44, 22 March 2006 (CET)

:The latter. There is real disk activity, indicated by LED flashing and disk movement noise, for about 30 seconds, before the machine gives up and shuts down. If this is not SATA-related, what might it be? [[User:Ehn|Ehn]] 23:23, 9 April 2006 (CEST)

----

Sorry, I didn't realize Ehn has two problems, and I considered your post as aimed at my and Ehn's. Never mind then.

[[User:Rasto|Rasto]] 10:47, 23 March 2006 (CET)

== Problem with 2.6.16 ==

ok, seems like we have a new problem:
After upgrading from 2.6.15 to 2.6.16 my DVD device is not recognised anymore by libsata.
The only way to get working is by using the ide layer - without DMA of course.
Can anyone confirm this?

--[[User:Defiant|Erik]] 17:49, 23 Mar 2006 (CET)
--------

Try the kernel parameter '''combined_mode=libata''', does this help? Also, have you enabled libata's ATAPI support as described in the article?

--[[User:Thinker|Thinker]] 20:31, 23 March 2006 (CET)
----

Yes, I'm using the command line parameter libata.atapi_enable=1 - up to 2.6.15 it works fine.
About the combined_mode parameter: Also tried it, though the Author of this patch mentioned that the default behavior did not changed.
I will continue hungting this problem when I find some time.

--[[User:Defiant|Erik]] 7:12, 24 Mar 2006 (CET)
-----

I can confirm Eriks problem. After updating to 2.6.16 I have it, too. libata.atapi_enable=1 is still on kernel command line. With some help of Michael Ott I figured out that this only happens if you have the current suspend2 patches applied.
Using a vanilla 2.6.16 works as expected.

--[[User:Mobst|mobst]] 14:30, 24 Mar 2006 (CET)
-----

Ahh thanks. Finding the problem in the suspend2 patch should be an easy task.
I just hope for some free time this weekend!

--[[User:Defiant|Erik]] 18:31, 24 Mar 2006 (CET)
-----

Uhm, looks like [[ZolnOtt|ZolnOtt]] was faster, he added the note to
http://thinkwiki.org/wiki/Problems_with_SATA_and_Linux#No_DMA_on_DVD_drive

--[[User:Defiant|Erik]] 20:02, 24 Mar 2006 (CET)

== Patch against SATA-resume problem with T60 ==

I only have a Fujitsu-Siemens C1320, but I had the same problem with resuming from suspend with a SATA disk and kernel 2.6.16 as mentioned for the T60. I solved the problem for me by merging several patches (patches.fixes/libata-increase-timeout-for-resume, patches.fixes/ahci-suspend, patches.fixes/ahci-atapi-sense-request, patches.drivers/libata-acpi-suspend, patches.fixes/libata-resume-drive_port-mode, patches.fixes/ahci-init-on-resume, patches.drivers/libata-device-spindown)
from the OpenSuSE kernel 2.6.16-12 to vanilla 2.6.16.5. You'll find my patch at http://www.spinnaker.de/linux/c1320/sata-resume-2.6.16.5.patch. I expect this to solve the T60 problem, so I provide the patch here, as this wiki helped me so much with my laptop.

--[[User:Rrosenfeld|Rrosenfeld]] 23:12, 16 April 2006 (CEST)

I just want to let you know that I managed to get Suspend-to-RAM working on the T60. I'm using Gentoo's suspend2-sources-2.6.16-r2 as base and applied the above patches from Rrosenfeld (thanks!) and additionally this [https://bugzilla.novell.com/attachment.cgi?id=75844&action=view one] (here the corresponding [https://bugzilla.novell.com/show_bug.cgi?id=162090 bug]).

--[[User:Sts|sts]] 22:52, 17 April 2006 (CEST)

same here. applied both patches to gentoo suspend-sources-2.6.16-r5 --- working. sweet.

--[[User:Husemann|dr who]] 21:51, 3 May 2006 (CEST)

however: powersave (powersaved) is a spoiler: it will cause the resume operation to get stuck at "reading back caches" and eventually result in a kernel panic. stopping powersaved before hibernating does not prevent it: it seems that running powersaved just once will screw things up. interesting and nasty. but not a show stopper (IMHO).

--[[User:Husemann|dr who]] 17:14, 10 May 2006 (CEST)

that's not powersaved's fault. kernel panics are always kernel (or hardware) bugs. i experienced this kind of lockups when using different cpufreq governors at once (that's probaly something one shoudln't do?). i'm now using only cpufreq_userspace and don't have any problems.

--[[User:Sts|sts]] 15:11, 11 May 2006 (CEST)

Having exactly the same SATA wakeup problem on my Z60t, using FC5. Can the patch from rosenfeld be applied also to the FC5 kernelsource?

--[[User:SzentivÃ¡nyi|szenti]] 21:29, 11 May 2006 (CEST)

Latest fedora (FC5) 2.6.17-1.2139_FC5smp kernel solved the problem on my T60p. I have successfully resumed a number of times now.

--[[User:Gfbarros|Guil]] 20:38, 27 June 2006 (CEST)

Problems with SATA and Linux

2006-06-27T18:35:05Z

Gfbarros: /* Hang on resume from suspend to RAM */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPad models use an [[Intel ICH6-M]] SATA/PATA 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:
*ThinkPad {{T60}}, {{T60p}}
*ThinkPad {{X60}}, {{X60s}}
*ThinkPad {{Z60t}}, {{Z60m}}
*ThinkPad {{Z61t}}, {{Z61m}}
Models using a SATA controller and a PATA (IDE) system disk with a SATA-to-PATA bridge:
*ThinkPad {{T43}}, {{T43p}}
*ThinkPad {{R52}}
*ThinkPad {{X41}}, {{X41T}}

{{NOTE|Some of these problems (namely SMART support, power management and disk information) are solved in Linux 2.6.15 with the inclusion of libata pass-through. See the SATA driver [http://linux-ata.org/features.html features], [http://linux-ata.org/software-status.html software status] and [http://linux-ata.org/sata-status.html hardware status].}}
|}

==Hang on resume from suspend to RAM==

Linux kernels prior to 2.6.16 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 ([http://lkml.org/lkml/2005/5/2/46 LKML posting]) fixes this by adding SATA power management support.

Kernel 2.6.16 and later fixes this problem for most systems. The Thinkpad T60 and X60s still need some patches to get resume working using 2.6.16, see [[Talk:Problems with SATA and Linux#Patch against SATA-resume problem with T60|here]]. The T60p resumes properly with 2.6.17-rc6, the T60 and X60 should also. You need to enable ata_piix and disable AHCI in the bios. The latest fedora (FC5) 2.6.17 kernel seems to have fixed the resume problem on the T60p, still need to disable AHCI though.

===Patches===
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff Patch for kernel 2.6.12]
* [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.13-rc5.diff Patch for kernel 2.6.13-rc5]
* [http://lkml.org/lkml/2005/9/23/97 Patch for kernel 2.6.14]
* [http://www.xenotime.net/linux/SATA/2.6.15-rc/libata_suspend.patch Patch for kernel 2.6.15-rc4]
* [http://tpctl.sourceforge.net/tmp/sata_pm.2.6.15-rc6.patch Patch for kernels 2.6.15-rc6 through 2.6.15]

Some distributions already include this patch (e.g., {{Ubuntu}} Breezy, {{Gentoo}}'s gentoo-sources 2.6.15-r1), but some don't (e.g., {{Fedora}} 4). If your distribution doesn't include the patch, you will need to compile your own kernel with this patch included.

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169201 bug 169201: "SATA drives fail on laptop suspend"]
* [http://lkml.org/lkml/2005/11/15/385 Fix to libata.h recommended on LKML] in case you get "ata: abnormal state 0x80 on port 0x1F7"
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183138 bug 183138": "SATA failure after pm-suspend/resume ata1: handling error/timeout"]

==Failed resume from suspend to disk==

Suspend to disk (using [[swsusp]] or [[Software Suspend 2]]) 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 <tt>ata_piix</tt> 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 the <tt>ide</tt> driver is compiled as a module and loaded after <tt>ata_piix</tt>, the DVD drive will not be recognized by either driver.

Either of the following configurations will work:
* For kernel 2.6.14 and newer: enable ATAPI support in the SATA system using {{bootparm|libata.atapi_enabled|1}} (see below; this is experimental).
* Compile IDE into the kernel (non-module).
* Compile both IDE and SATA as modules and make sure IDE is loaded first (the module is called 'ide_generic').

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 <tt>ata_piix</tt> driver (instead of the IDE driver) for the optical drive. This requires enabling the ATAPI support of the <tt>ata_piix</tt> driver, which is under active development and not yet 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 (must be 2.6.14 or newer; the relevant code is under active development).
* Do one of the following:
** Enable the <tt>ata_piix</tt> and <tt>libata</tt>) drivers as built-in, and add {{bootparm|libata.atapi_enabled|1}} to your kernel command line (e.g., in in {{path|/boot/grub/menu.lst}}).
** Enable <tt>ata_piix</tt> and <tt>libata</tt>) as modules (this is often the default) and add "<tt>options libata atapi_enabled=1</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
*** Note : if you are using a ''Debian Sid'' system, and want to use Debian precompiled kernels, then type the following command in a ''root'' shell :
'''# echo options libata atapi_enabled=1>/etc/modprobe.d/atapienable && update-initramfs -u'''
* Do one of the following:
** Disable the IDE system.
** Build the IDE driver as built-in (this is often the default) and add the {{bootparm|hdc|noprobe}} kernel argument (e.g., in in {{path|/boot/grub/menu.lst}}).
** Build the IDE driver as module and add "<tt>options ide hdc=noprobe</tt>" to your {{path|/etc/modprobe.conf}} (or the equivalent in your distribution).
* If you chose to use modules above, regenerate your <tt>initrd</tt> file.

If this doesn't work, use {{cmd|lspci -vn|}} to check whether one of the following chipsets is used in the Thinkpad:
{| border="1" cellspacing="0" cellpadding="2"
|-
!PCI ID
!Name
|-
|8086:7111
|Intel 82371AB/EB/MB PIIX4 IDE
|-
|8086:24db
|Intel 82801EB/ER (ICH5/ICH5R) IDE Controller
|-
|8086:25a2
|Intel 6300ESB PATA Storage Controller
|}
If yes, enable support for these chipsets has to be enabled by setting
#define ATA_ENABLE_PATA
in {{path|include/linux/libata.h}} (and report your ThinkPad model in the discussion page).

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

===Problem with kernel 2.6.16 kernel and suspend2 2.2.1===
DVD access fails with kernel 2.6.16.* and [[Software Suspend 2|suspend2]] 2.2.1. Thia is fixed by later versions of suspend2, or by deleting the 4000-libata-rollup-2616-rc3.patch (see
[http://lists.suspend2.net/lurker/message/20060322.082452.873dc526.en.html this post notice] by Alexander E. Patrakov).

===Links===
* RedHat Bugzilla [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163418 bug 163418: "can't enable DMA on DVD drive"]

==No DMA on system hard disk==

In recent Linux kernels, there are two modules capable of handling the ICH6 disk controller:
* <tt>ata_piix</tt>: the disk shows as {{path|/dev/sda}} and DMA is enabled.
* Generic IDE driver (<tt>ide-disk</tt>): the disk shows as {{path|/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 {{bootparm|hda|noprobe}} kernel argument. The driver will then be handled by the <tt>ata_piix</tt> driver. Note that this will change its device name to {{path|/dev/sda}} (which may require changes in {{path|/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==

Prior to kernel 2.6.15, the Linux SATA system did not support SMART commands (e.g., via smartctl).

The necessary capability is "libata pass-through", which was incorporated into Linux 2.6.15-rc1 and later. A patch is available for older kernels:
* Kernel 2.6.12: http://rtr.ca/dell_i9300/kernel/kernel-2.6.12/03_libata_passthru.patch
* Kernel 2.6.13: http://rtr.ca/dell_i9300/kernel/kernel-2.6.13/02_libata_passthru.patch
* Kernel 2.6.14: http://www.foo.fh-furtwangen.de/~koenigr/02_libata_passthru.fixed.again.patch
* Kernel 2.6.14 with the above suspend-to-RAM patch: http://linux.spiney.org/system/files?file=02_libata_passthru.fixed.patch

After applying the patch, run smartctl with the "-d ata" parameter:
:{{cmdroot|smartctl -d ata -a /dev/sda}}

==No disk power management==

Prior to kernel 2.6.15, the Linux SATA system did not support power management commands on these models.

The above patches for SMART support resolves this, and in particular 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.)

Refer to [[How to make use of Harddisk Power Management features]] for details about using
HD power management. Refer to [[Laptop-mode]] if you are interested into spinning down your HD.

==No disk information==

Prior to kernel 2.6.15, on these models the disk information could not be read by the standard commands such as:
*{{cmdroot|hdparm -i /dev/sda}}
*{{cmdroot|hdparm -I /dev/sda}}
The latter is fixed by the above patch for SMART support.

==No swapping of UltraBay device==

The <tt>ata_piix</tt> driver in mainline kernels does not yet support hot-swapping (or warm-swapping) of PATA devices. If you use a DVD or 2nd PATA HDD via the <tt>ata_piix</tt> driver, to swap them in or out you must power down the machine. This is scheduled to be fixed in Linux 2.6.18.

See [[How_to_hotswap_UltraBay_devices#When_using_the_ata_piix_driver|How_to_hotswap_UltraBay_devices]] for further information and a pending solution.

If you use the <tt>ide</tt> driver for a PATA UltraBay device, hot-swapping might work using [[lt_hotswap]], <tt>hdparm</tt>, <tt>idectl</tt> or <tt>hotswap</tt> (please report). However, since you use the <tt>ide</tt> driver, DMA will be disabled (see above).

Swapping of the [[UltraBay Slim Battery]] does work.

==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. See [[Problem with non-ThinkPad hard disks]].

==RHEL3.0 Update 7 on T60p==

RHEL3.0 Update 7 will install on a {{T60p}}, but you need to make an adjustment. Both uni-processor and SMP kernels get installed, with the SMP kerrnel the default. However, the SMP kernel can't seem to find the disk drive. You can work around this by use "e" at the GRUB kernel prompt, then on the "kernel" line appending " noapic". After the system boots, you'll want to edit /boot/grub/grub.conf to add the " noapic" option to the kernel line as well.

==Mandriva 2006 on T60==

Mandriva 2006.0 has a problem with SATA on a {{T60}}, to fix this you need to make an adjustment. The install procedure can't seem to find the SATA disk drive, you can work around this by adding the "noapic" kernel option during CD/DVD boot. You *might* need to add this to lilo or GRUB for normal operations, after install completes. The problem with not using apic during normal operations is that you might have problems with power management, please see article on [[Software Suspend 2]]