ThinkWiki - User contributions [en]

How to protect the harddisk through APS

2010-06-02T06:03:39Z

Plaa: how to verify hdapsd is working

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page tells you how to make the [[Active Protection System]] work under Linux to protect your harddrive from damage in case of a notebook drop or other kind of impact while it is running.

Specific instructions for {{Fedora}} can be found [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]].

For {{Debian}} (Etch) have a look at [[Installing_Debian_Etch_on_a_ThinkPad_Z60m#Active_Protection_System|this]].

== How APS works in Linux ==
APS in Linux consists of four components on the software side:
* The [[HDAPS]] driver (included in recent kernels). It exports a sysfs interface providing the acceleration values.
* The <tt>hdaps_protect</tt> disk protection kernel patch, which exports a sysfs interface that enables an ide or sata disk to be protected by a userspace process. You should get the patch appropriate to your kernel version from [http://news.gmane.org/group/gmane.linux.drivers.hdaps.devel/last=/force_load=t gmane.linux.drivers.hdaps.devel].
** '''NOTE''': Starting with kernel 2.6.28 a generic disc protection feature is built into the libata driver
* The [http://sourceforge.net/projects/hdaps/ <tt>hdapsd</tt>] disk protection userspace daemon. It monitors the acceleration values through the HDAPS interface and automatically initiates disk protection through the hdaps_protect interface - given that the movement exceeds a user specified threshold.
* Optional: the [http://roy.marples.name/projects/khdaps/wiki <tt>khdapsmonitor KDE System Tray applet</tt>] or the [http://www.dresco.co.uk/hdaps/ <tt>gnome-hdaps-applet</tt>]. These applets provide a visual indication of the disk protection status and also a graphical interface for adjusting configuration options for <tt>hdapsd</tt>.
|}

==Installation==
As mentioned above, the hdaps kernel driver found in recent kernels is only responsible for reading the accelerometer data and exporting it through the sysfs interface.

In order to use this information to protect the disk, some additional steps are required.

* Download and build the latest hdaps_protect disk protection kernel patches.
* Enable the drivers in the kernel (requires kernel rebuild).
* Download, build and configure the hdapsd userspace daemon.
* Download and build one of the applets to get a real-time representation of the disk protection status.

===Getting the files===
{| border="1" cellspacing="0" cellpadding="2"
! Latest Sources
|
See [[HDAPS#Disk_head_parking|HDAPS - Disk head parking]]
|-
! {{Slackware}}
|
*<tt>hdapsd</tt> SlackBuild: http://slackbuilds.org/repository/12.2/system/hdapsd/
|-
! {{Debian}}
|
*<tt>hdapsd</tt> package: http://packages.debian.org/unstable/misc/hdapsd
|-
! {{Fedora}}
| see instructions [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]]
*kernel RPM packages including <tt>hdaps_protect</tt>: http://www.dresco.co.uk/hdaps/
*kernel RPM packages including <tt>hdaps_protect</tt> and [[Software Suspend 2]]: http://mhensler.de/swsusp/download/yum/development/fc5/ (build 2084_2 and up)
|-
! {{Gentoo}}
|
*<tt>hdapsd</tt>: [http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-laptop/hdapsd available]
*<tt>khdapsmonitor</tt>: [http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-laptop/khdapsmonitor available]
|}

=== Adding kernel support ===
A kernel patch is required for disk head parking and queue freezing.

==== Manually patching and compiling a kernel ====
As root, do:
:{{cmdroot|cd /usr/src/linux}}
:{{cmdroot|patch -p1 < ~/hdaps_protect.20060409.patch}}
:{{cmdroot|make clean}}
:{{cmdroot|make}}
:{{cmdroot|make modules_install}}

==== Zen-Sources patched kernel ====
Another way to achieve this is using zen-sources kernel.
It has hdaps patches applied. Additional it supports many other IBM futures like tp_smapi and newest thinkpad_acpi.

Download page for this kind of kernel is http://zen-sources.org/

After downloading a kernel image unpack it to ''/usr/src/linux'' with
:{{cmdroot|tar jxf zen-sources-2.6-version-zen0.tar.bz2 }}

Installation is similar to previous one.

As root, do:
:{{cmdroot|make oldconfig}}
:{{cmdroot|make clean}}
:{{cmdroot|make}}
:{{cmdroot|make modules_install}}

'''make oldconfig''' command will ask you for some information. It's required to tap '''m''' or '''y''' on "HDAPS" functionality, and on some other things connected with Thinkpad.

=== Installing hdapsd ===
==== Manual compilation from source ====
{{NOTE|1=There has been a new release of hdapsd which doesn't use sysfs anymore and therefore reduces timer interrupts. You need tp_smapi 0.32 for this. See also: http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1040 .}}
* Download the <tt>hdapsd</tt> sources (see above)
* Compile using {{cmdroot|gcc -o hdapsd hdapsd-*.c}}
* Run {{cmdroot|./hdapsd -d sda -s 12 -a}} (replace <tt>sda</tt> with your hard disk device; run {{cmdroot|./hdapsd}} without arguments for help)

==== Gentoo ====
{{NOTE|1=hdapsd was added to the official portage tree on the 26th June 2006. However the version in portage is to be considered outdated. (20060409)}}
{{Gentoo}} users can try the ebuild attached to [http://bugs.gentoo.org/show_bug.cgi?id=166166 gentoo bug 166166].
*Add hdapsd support in your kernel: device drivers -> hardware monitoring -> ... (you need it as a module if you want to use tp_smapi and hdaps, see [[Tp_smapi]])
*Download the ebuild, use same ebuild date as the kernel-patch.
*Make known the portage an extern ebuild path and add the following line to {{path|/etc/make.conf}}:
PORTDIR_OVERLAY="/usr/local/portage/" (or any other location)
*Create directory {{path|/usr/local/portage}} and {{path|/usr/local/portage/app-laptop/}}
*Copy the downloaded ebuild to {{path|/usr/local/portage/app-laptop}} ({{path|/usr/local/portage/app-laptop/hdapsd}} should now exists)
*Make portage known the new ebuild and creat digist with:
:{{cmdroot|ebuild /usr/local/portage/app-laptop/hdapsd/hdapsd-20060326.ebuild digest}}
*Optional: Copy source file to portage distfiles (if no internet connection is available):
:{{cmdroot|cp hdapsd-20060326.c /usr/portage/distfiles}}
*Accept the x86 keyword for this package: {{cmdroot|echo "app-laptop/hdapsd ~x86" >> /etc/portage/package.keywords}}
*Install hdapsd with: {{cmdroot|emerge hdapsd}}.
*Edit {{path|/etc/conf.d/hdapsd}} (change your harddrive if neccessary: mine is sda, and change the value from 5, 5 is to sensitive, 12 is a good value in my opinion).
*start deamon with: {{cmdroot|/etc/init.d/hdapsd start}}
*Optional: add to default runlevel: {{cmdroot|rc-update add hdapsd default, rc-update add hdapsd battery}}
Write an eMail to abartel[Ã¤d]htwm.de, if you want to get my hdapsd-20060326.ebuild and please upload it.

==== Ubuntu ====
hdapsd is available via synaptic for Hardy Heron (9.04) and newer versions.

=== Building an applet ===
====hdaps-gl====
*Make sure you have installed hdaps [and loaded] and ?opengl?
*Download [https://sourceforge.net/project/showfiles.php?group_id=138242 hdaps-gl-0.0.5] from the web.
*Extract files to {{path|/opt/hdaps-gl}}.
*{{cmdroot|make}}
*Start the applet: {{cmdroot|./hdaps-gl}}

==Verifying hdapsd is working==
According to instructions from the [http://sourceforge.net/mailarchive/message.php?msg_name=h5r1f4%246s8%241%40ger.gmane.org hdaps-devel mailing list]:

Start {{cmdroot|find /}} in a terminal and move your laptop. The output should stop while moving (while the heads are parked).

Alternatively, run {{cmdroot|while true; do cat /sys/block/sda/device/unload_heads; done}} (replacing <tt>sda</tt> with your device) and move the laptop. When the value is greater than zero the heads are parked.

==Troubleshooting==
See the [[Problem with APS harddisk parking]] page for troubleshooting APS issues.
{{NOTE|1=If you use [[tp_smapi]], remember to include the option <tt>HDAPS=1</tt> when [[Tp_smapi#Installation|installing tp_smapi]]. Also, you might need to build the hdaps driver as module.}}

==Further Information==
*Additonal information and support is available through the [[Mailinglists#HDAPS Developers Mailinglist|hdaps-devel]] mailinglist and its archive.

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61m]] [[Category:Z61e]] [[Category:Z61m]]

Problem with display remaining black after resume

2007-11-23T09:58:30Z

Plaa: /* Quick workaround for R61i, T23, maybe others */ correction to Gutsy instructions

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}, {{R60}}, {{R61}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}, {{Z61e}}
*ThinkPad {{X60s}}, {{X60}}, {{X61s}}

==Affected Operating Systems==
*Linux (it's a kernel issue)
*FreeBSD (6.x at least)

==Solutions==
===Quick workaround for R61i, T23, maybe others===
Try pressing CTRL+ALT+F1 to switch to text console. The backlight should come on normally. Press CTRL+ALT+F7 to return to X.

On a T23 using Ubuntu Feisty, pressing Fn+F7 (external/internal display change) once or twice brought the display back. After upgrading to Ubuntu Gutsy it doesn't work anymore, but pressing Fn+F3 (blank screen) and Fn (restore display) works.

===Quick Workaround for R61 (at least 8918-5QG) using NVidia===

Use Vesa driver instead of the proprietary NVidia driver.

=== Solution for ThinkPad Z60t ===

* '''Display controller:''' Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
* '''Distro:''' Fedora release 7 (Moonshine)
* '''Kernel:''' Linux 2.6.22.5-76.fc7

The solution is straight forward - just to add configuration parameter for the default '''pm-utils''' package. Create file <code>/etc/pm/config.d/config</code> and put there one line <code>DISPLAY_QUIRK_S3_BIOS="true"</code>, or execute following command:

echo DISPLAY_QUIRK_S3_BIOS=\"true\" >> /etc/pm/config.d/config

===Semi-Solution for ThinkPad X60 with damaged system after s2ram usage===
It happend when restarting a s2ram-session.

'''Symptom:''' Black screen with blinking "_" sign remaind. (without the ")

'''System status:''' HDD idle, fan running, everything else looks to wait for something to happen.

'''Semi-Solution:''' Booting with DVD-ROM and going through the installations menu,
where you choose "other" and "boot a installed system" (something like that). Gladly it works,
and OpenSuSE 10.1 comes up with 50% "failed" messages! I than shutdown properly, rebooted again
and had 100% "done" again, with no other things affected.

'''Further:''' Repairing with the DVD-ROM crashed massivly(!), so I selected "boot a installed system" as final
solution and it worked!

'''Unknown:''' Maybe the Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM will help,
because X60s and X60 are very familiar. (Not tested so far.)

(If this Problem is not right here, please edit and move.)

===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips and Intel 915/945GM ===

Affected models include {{X60s}}, {{R60}} and {{T60}}.

This soluton also applies to T42 with Intel 855 and ATI 9600 M10.

One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"}} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves. Also commenting POST_VIDEO may help.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. (As of FC6 these seem to be pre-commented out.) Also, the laptop, after waking up, may go back to sleep immediately or whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports certain ACPI events. This is a known problem and a simple workaround is described [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].

{{NOTE|It is possible this method will not work if the laptop is docked. It is also possible that the cited workaround for the HAL daemon bug will not work on some machines. A kludgier workaround in this event is to kill the HAL daemon on suspend. This necessitates the resuscitation of GPM upon resume.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

----

On '''T60 2007-CTO''' (Core2Duo 2Ghz, 2GB Ram, ATI X1400) the screen stayed blank after suspend-to-ram until I set '''vga=0''' in lilo.conf.

Working config:
Linux 2.6.21.5
fglrx 8.37.6
debian etch:
powersaved 0.14.0-5:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
hibernate:
SwitchToTextMode yes
lilo.conf:
vga=0

"EnableVbetool yes" and other suggestions didn't work for me.

For suspend-to-disk, don't load fglrx in initrd.

----

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
*For Debian Etch 4.0 on R50e just make following changes to /etc/default/acpi-support:
#SAVE_VBE_STATE=true
#VBESTATE=/var/lib/acpi-support/vbestate
#POST_VIDEO=true
SAVE_VIDEO_PCI_STATE=true

*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding
Option "VBERestore" "yes"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.

The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

With Ubuntu 6.10 on a [[:Category:R51|R51 (2887-32G)]] I ''just'' (as none of the other tricks above) had to add {{bootparm|fb|false}} to the kernel line in {{path|/etc/grub/menu.lst}} and edit {{path|/etc/defaults/acpi-support}} this way:

SAVE_VBE_STATE=false
POST_VIDEO=false
SAVE_VIDEO_PCI_STATE=true
USE_DPMS=false
DOUBLE_CONSOLE_SWITCH=false

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===

The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":

hw.acpi.reset_video
Reset the video adapter from real mode during the resume path.
Some systems need this help, others have display problems if it
is enabled. Default is 0 (disabled).

This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:

hw.acpi.reset_video="1"

And rebooting your machine. Hopefully, the next time you resume from a suspend, you'll see your video again. This solution doesn't appear to be specific to ATI hardware in any way, so I presume it would be helpful for video chipsets other than ATI, as well.

If this entry doesn't help you, you might consider searching in the [http://lists.freebsd.org/pipermail/freebsd-mobile/ FreeBSD-Mobile email-list archive] for more insight.

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

===Solution using s2ram for Intel 915/945GM===

Just using the "s2ram -f -p" command from the uswsusp package will work from within X, at least on a {{Z61e}}. On {{X60s}} it is enough to issue the "s2ram" command and it works.

===Solution using DOUBLE_CONSOLE_SWITCH===

By setting the following in {{path|/etc/default/acpi-support}} the display comes back on {{X61s}} using Intel chipset:

DOUBLE_CONSOLE_SWITCH=true

Problem with display remaining black after resume

2007-10-28T14:59:20Z

Plaa: /* Quick workaround for R61i, maybe others */ Quick fix for T23

There has been a problem encountered where the display stays black on resuming from suspend.

The symptom might have you think first that your system hang up, but you will realize that your ThinkPad works and you can even reset it via {{key|Ctrl}}{{key|Alt}}{{key|Del}}.

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T60}}, {{T60p}}
*Thinkpad {{T23}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}, {{R60}}, {{R61}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}, {{Z61e}}
*ThinkPad {{X60s}}, {{X60}}

==Affected Operating Systems==
*Linux (it's a kernel issue)
*FreeBSD (6.x at least)

==Solutions==
===Quick workaround for R61i, T23, maybe others===
Try pressing CTRL+ALT+F1 to switch to text console. The backlight should come on normally. Press CTRL+ALT+F7 to return to X.

On a T23 pressing Fn+F7 (external/internal display change) once or twice brought the display back on Ubuntu Feisty. After upgrading to Ubuntu Gutsy it doesn't work, but pressing Fn+F3 (blank screen) and Fn+F7 (or some sequence of them) works.

=== Solution for ThinkPad Z60t ===

* '''Display controller:''' Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
* '''Distro:''' Fedora release 7 (Moonshine)
* '''Kernel:''' Linux 2.6.22.5-76.fc7

The solution is straight forward - just to add configuration parameter for the default '''pm-utils''' package. Create file <code>/etc/pm/config.d/config</code> and put there one line <code>DISPLAY_QUIRK_S3_BIOS="true"</code>, or execute following command:

echo DISPLAY_QUIRK_S3_BIOS=\"true\" >> /etc/pm/config.d/config

===Semi-Solution for ThinkPad X60 with damaged system after s2ram usage===
It happend when restarting a s2ram-session.

'''Symptom:''' Black screen with blinking "_" sign remaind. (without the ")

'''System status:''' HDD idle, fan running, everything else looks to wait for something to happen.

'''Semi-Solution:''' Booting with DVD-ROM and going through the installations menu,
where you choose "other" and "boot a installed system" (something like that). Gladly it works,
and OpenSuSE 10.1 comes up with 50% "failed" messages! I than shutdown properly, rebooted again
and had 100% "done" again, with no other things affected.

'''Further:''' Repairing with the DVD-ROM crashed massivly(!), so I selected "boot a installed system" as final
solution and it worked!

'''Unknown:''' Maybe the Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM will help,
because X60s and X60 are very familiar. (Not tested so far.)

(If this Problem is not right here, please edit and move.)

===Solution for ThinkPads with 1400x1050 internal LCD and Intel 915GM ===
see [[1400x1050 on Intel 915GM]].
===Solution for ThinkPads with ATI graphic chips and Intel 915/945GM ===

Affected models include {{X60s}}, {{R60}} and {{T60}}.

This soluton also applies to T42 with Intel 855 and ATI 9600 M10.

One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} kernel parameter in your kernel parameter line.

For grub this would look like this:

title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

For lilo it would look like this:

image=/boot/vmlinuz
append="acpi_sleep=s3_bios"

The actual process of going to sleep is then managed through a sleep script; as a start, see the {{path|sleep.sh}} script in the Extreme Graphics 2 section below, but note the following comments:

In [[:Category:OpenSUSE|OpenSUSE]] 10.1 (at least on a T43p), it's necessary to override the default options for s2ram if you're using the newer ATI driver. This can be done putting {{bootparm|SUSPEND2RAM_FORCE|"yes"}} and {{bootparm|SUSPEND2RAM_ACPI_SLEEP|"3"}} in {{path|/etc/powersave/sleep}}.

In {{Ubuntu}} or {{Kubuntu}}, it may be necessary to modify {{path|/etc/default/acpi-support}}. In that file, make sure that {{path|ACPI_SLEEP}} is uncommented and set to true. With ATI chips, also make sure that {{path|SAVE_VBE_STATE}} is uncommented and set to true; with Intel chips, on the other hand, ensure that nothing is done with respect to VBE--no reposts, no state saves. Also commenting POST_VIDEO may help.

In {{Fedora}}, it may be necessary with the Intel chips to edit the {{path|resume_video()}} function in {{path|/etc/pm/functions-intel}} to comment out the VBE post and restore. (As of FC6 these seem to be pre-commented out.) Also, the laptop, after waking up, may go back to sleep immediately or whenever the AC adapter is disconnected. When this happens, it's caused by a bug in the HAL daemon that incorrectly reports certain ACPI events. This is a known problem and a simple workaround is described [http://live.gnome.org/GnomePowerManager/Faq#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].

{{NOTE|It is possible this method will not work if the laptop is docked. It is also possible that the cited workaround for the HAL daemon bug will not work on some machines. A kludgier workaround in this event is to kill the HAL daemon on suspend. This necessitates the resuscitation of GPM upon resume.}}

Another solution is to use vbetool. If you are using {{Debian}} with the hibernate package, uncomment "EnableVbetool yes" in {{path|/etc/hibernate/hibernate.conf}} (or {{path|/etc/hibernate/ram.conf}}).

----

On '''T60 2007-CTO''' (Core2Duo 2Ghz, 2GB Ram, ATI X1400) the screen stayed blank after suspend-to-ram until I set '''vga=0''' in lilo.conf.

Working config:
Linux 2.6.21.5
fglrx 8.37.6
debian etch:
powersaved 0.14.0-5:
UNLOAD_MODULES_BEFORE_SUSPEND2DISK="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
UNLOAD_MODULES_BEFORE_SUSPEND2RAM="usb_storage ohci_hcd uhci_hcd ehci_hcd ipw3945 pcmcia yenta_socket rsrc_nonstatic pcmcia_core"
hibernate:
SwitchToTextMode yes
lilo.conf:
vga=0

"EnableVbetool yes" and other suggestions didn't work for me.

For suspend-to-disk, don't load fglrx in initrd.

----

===Solution for ThinkPads with Intel Extreme Graphics 2===
{{NOTE|
On [[:Category:X40|X40]]s/[[:Category:X41|X41]]s - even with Intel Extreme Graphics - and for [[:Category:R52|R52]]s with Intel Graphics Media Accelerator 900 the [[Problem with display remaining black after resume#Solution for ThinkPads with ATI graphic chips|solution for ATI graphics chips]] above is reported to work. In this case, make sure no changes to VBE are made, especially no state saves and no reposts.}}

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
*For Debian Etch 4.0 on R50e just make following changes to /etc/default/acpi-support:
#SAVE_VBE_STATE=true
#VBESTATE=/var/lib/acpi-support/vbestate
#POST_VIDEO=true
SAVE_VIDEO_PCI_STATE=true

*For a R50e the only thing needed to make suspend to ram work in Ubuntu 6.06 is adding
Option "VBERestore" "yes"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}, and the example script below.

The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

# change to console 1
FGCONSOLE=`fgconsole`
chvt 6

# safe video state
cat /proc/bus/pci/00/02.0 > /tmp/video_state

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

# go to sleep
echo -n 3 > /proc/acpi/sleep

# waking up
# restore system clock
hwclock --hctosys

# restore video state
cat /tmp/video_state > /proc/bus/pci/00/02.0

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

With Ubuntu 6.10 on a [[:Category:R51|R51 (2887-32G)]] I ''just'' (as none of the other tricks above) had to add {{bootparm|fb|false}} to the kernel line in {{path|/etc/grub/menu.lst}} and edit {{path|/etc/defaults/acpi-support}} this way:

SAVE_VBE_STATE=false
POST_VIDEO=false
SAVE_VIDEO_PCI_STATE=true
USE_DPMS=false
DOUBLE_CONSOLE_SWITCH=false

===Solution for ThinkPads with Intel I830 Chipset===
The following solution worked for me on an X30 with I830M chipset with kernel >= 2.6.16.
*this works with vesafb and also with intelfb frambuffer support.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

FGCONSOLE=`fgconsole`
chvt 8
sync
hwclock --systohc

echo -n "mem" > /sys/power/state

hwclock --hctosys
vbetool post

if [ "$FGCONSOLE" -ge "7" ] ; then
chvt $FGCONSOLE
else
chvt 7
chvt $FGCONSOLE
fi
===Solution for ThinkPads with ATI graphic (and possibly other) chips and FreeBSD===

The FreeBSD acpi(4) manpage mentions a tunable parameter, "hw.acpi.reset_video":

hw.acpi.reset_video
Reset the video adapter from real mode during the resume path.
Some systems need this help, others have display problems if it
is enabled. Default is 0 (disabled).

This tunable can be set by adding the following line to your FreeBSD machine's /boot/loader.conf file:

hw.acpi.reset_video="1"

And rebooting your machine. Hopefully, the next time you resume from a suspend, you'll see your video again. This solution doesn't appear to be specific to ATI hardware in any way, so I presume it would be helpful for video chipsets other than ATI, as well.

If this entry doesn't help you, you might consider searching in the [http://lists.freebsd.org/pipermail/freebsd-mobile/ FreeBSD-Mobile email-list archive] for more insight.

{{footnotes|
#If you have this problem with R50e and the above solution doesn't work, try switching to console first. An example sleep script can be found [[How to configure acpid|here]].
}}

===Solution using s2ram for Intel 915/945GM===

Just using the "s2ram -f -p" command from the uswsusp package will work from within X, at least on a {{Z61e}}. On {{X60s}} it is enough to issue the "s2ram" command and it works.