https://www.thinkwiki.org/w/api.php?action=feedcontributions&feedformat=atom&user=84.191.161.178ThinkWiki - User contributions [en]2026-04-05T17:45:35ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Graphics_Chips_Power_Management_features&diff=10933How to make use of Graphics Chips Power Management features2005-07-24T16:14:20Z<p>84.191.161.178: /* DynamicClocks in the Radeon Xorg driver */ not so severe actually</p>
<hr />
<div>==Power Saving With A Framebuffer Console==<br />
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:<br />
radeonfb: Dynamic Clock Power Management enabled<br />
<br />
==DynamicClocks in the Radeon Xorg driver==<br />
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATI Radeon Mobility M9"<br />
'''Option "DynamicClocks" "on"'''<br />
EndSection<br />
<br />
With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):<br />
<br />
(**) RADEON(0): Option "DynamicClocks" "on"<br />
(II) RADEON(0): Dynamic Clock Scaling Enabled<br />
<br />
{{NOTE|Enabling DynamicClocks crashes some models. If the CPU is entering one of the lower power states (C3 or lower) during Xorg startup the display may stay black. As a workaround disable DynamicClocks in Xorg and use [http://www.hasw.net/linux/ rovclock] instead. But it does not scale the clocks to match the workload.}}<br />
<br />
==How to use it==<br />
After enabling it, my first question was how do I control it? After reading about it, the answer is: you don't have to, it manages the power consumption for you.\<br />
<br />
==X.org on Debian==<br />
Because debian doesn't have X.org yet - [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].<br />
<br />
'''Update:''' X.org has made it into Debian. See: [http://packages.debian.org/unstable/x11/xserver-xorg]<br />
<br />
There are also sarge backports available [http://www.backports.org/ here] or [http://people.debian.org/~nobse/xorg-x11/ here].<br />
<br />
Add the following line to your repository list:<br />
deb http://people.debian.org/~nobse/xorg-x11/ sarge main<br />
<br />
==External Sources==<br />
*[http://www.ati.com/products/pdf/powerplaywp2.pdf Marketing information from ATI]<br />
<br />
<br />
[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=Active_Protection_System&diff=8420Active Protection System2005-07-24T16:13:26Z<p>84.191.161.178: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:APS.jpg|IBM Active Protection System]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== The Active Protection System ===<br />
With the new series of Thinkpads IBM introduced the Active Protection System (APS) in 2003. The APS is a protection system for the Thinkpad's internal harddrive. A sensor inside the Thinkpad recognizes when the notebook is accelerated. A software applet then is triggered to park the harddisk. This way the risk of data loss in case of when the notebook is dropped is significantly reduced since the read/write head of the harddrive is parked and hence can't crash onto the platter when the notebook drops onto the floor.<br />
<br />
The whole concept of the technology seems very advanced. For the first part, the hardware sensor is capable of not only recognizing acceleration of the notebook, but also (to a certain degree) of its whole orientation in space, relative to gravity's axis. Furthermore, having the actual control put into software, its functionality is extendable and it gives chance to implement features like the "ignore minor shocks" feature which is present in the Windows based control applet. (This feature prevents the harddrive from parking in case of minor regular shocks such as occur when in a train or car.)<br />
</div><br />
|}<br />
<br />
<br />
==Linux Support==<br />
Linux support is in early development.<br />
<br />
This feature definitely depends on software and there is no hardware or BIOS only way of making it work. A statement from IBM clearifies this:<br />
"The APS system will require APS software to be installed on the <br />
computer before it activates the harddrive parking . This means it will <br />
not work on systems preloaded with Linux."<br />
<br />
IBM made contradictory statements about their willingness to release the specifications of the hardware sensor and its API to the linux community or some developers. Although a lot of developers and other interested people from the OpenSource community actively contacted IBM to get the specs, in fact they never got them.<br />
<br />
Meanwhile, some independent projects are making progress:<br />
* Quoted from NewScientist.com: The latest Apple PowerBook laptops can be controlled with a gentle shake. Programmer Amit Singh has written code that lets him use the sensor to control software on the computer. The code is published at [http://www.kernelthread.com/software/ams/ www.kernelthread.com/software/ams/].<br />
<br />
*There is a fairly detailed article about [http://www.almaden.ibm.com/cs/people/marksmith/tpaps.html reverse engineering the APS accelerometer interface] by Mark Smith from IBM Research. Apparently they even have a prototype Linux driver working, but cannot release the full source yet.<br />
<br />
* The [http://hdaps.sourceforge.net/ HDAPS project] is dedicated to developing & testing a kernel module and a user space application. More info on this can also be optained from the [https://lists.sourceforge.net/lists/listinfo/hdaps-devel HDAPS mailinglist and its archive]. You can also find some of the coders working on this module in the #hdaps channel on irc.freenode.org.<br />
<br />
==Related Links==<br />
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=aps& IBMs ThinkVantage&trade; Technologies Flash presentation - Active Protection System]<br />
*[http://hdaps.sourceforge.net HDAPS project page]<br />
*[http://sourceforge.net/mailarchive/forum.php?forum=hdaps-devel HDAPS-devel list archive]<br />
<br />
==Models featuring this Technology==<br />
*ThinkPad {{R50}}, {{R50p}}, {{R51}}, {{R52}}<br />
*ThinkPad {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}<br />
*ThinkPad {{X40}}, {{X41}}, {{X41T}}<br />
<br />
<br />
[[Category:Glossary]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=Active_Protection_System&diff=6808Active Protection System2005-07-24T16:13:11Z<p>84.191.161.178: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:APS.jpg|IBM Active Protection System]] __NOTOC__<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== The Active Protection System ===<br />
With the new series of Thinkpads IBM introduced the Active Protection System (APS) in 2003. The APS is a protection system for the Thinkpad's internal harddrive. A sensor inside the Thinkpad recognizes when the notebook is accelerated. A software applet then is triggered to park the harddisk. This way the risk of data loss in case of when the notebook is dropped is significantly reduced since the read/write head of the harddrive is parked and hence can't crash onto the platter when the notebook drops onto the floor.<br />
<br />
The whole concept of the technology seems very advanced. For the first part, the hardware sensor is capable of not only recognizing acceleration of the notebook, but also (to a certain degree) of its whole orientation in space, relative to gravity's axis. Furthermore, having the actual control put into software, its functionality is extendable and it gives chance to implement features like the "ignore minor shocks" feature which is present in the Windows based control applet. (This feature prevents the harddrive from parking in case of minor regular shocks such as occur when in a train or car.)<br />
</div><br />
|}<br />
<br />
<br />
==Linux Support==<br />
Linux support is in early development.<br />
<br />
This feature definitely depends on software and there is no hardware or BIOS only way of making it work. A statement from IBM clearifies this:<br />
"The APS system will require APS software to be installed on the <br />
computer before it activates the harddrive parking . This means it will <br />
not work on systems preloaded with Linux."<br />
<br />
IBM made contradictory statements about their willingness to release the specifications of the hardware sensor and its API to the linux community or some developers. Although a lot of developers and other interested people from the OpenSource community actively contacted IBM to get the specs, in fact they never got them.<br />
<br />
Meanwhile, some independent projects are making progress:<br />
* Quoted from NewScientist.com: The latest Apple PowerBook laptops can be controlled with a gentle shake. Programmer Amit Singh has written code that lets him use the sensor to control software on the computer. The code is published at [http://www.kernelthread.com/software/ams/ www.kernelthread.com/software/ams/].<br />
<br />
*There is a fairly detailed article about [http://www.almaden.ibm.com/cs/people/marksmith/tpaps.html reverse engineering the APS accelerometer interface] by Mark Smith from IBM Research. Apparently they even have a prototype Linux driver working, but cannot release the full source yet.<br />
<br />
* The [http://hdaps.sourceforge.net/ HDAPS project] is dedicated to developing & testing a kernel module and a user space application. More info on this can also be optained from the [https://lists.sourceforge.net/lists/listinfo/hdaps-devel HDAPS mailinglist and its archive]. You can also find some of the coders working on this module in the #hdaps channel on irc.freenode.org.<br />
<br />
==Related Links==<br />
*[http://www.pc.ibm.com/presentations/us/thinkvantage/56/index.html?shortcut=aps& IBMs ThinkVantage&trade; Technologies Flash presentation - Active Protection System]<br />
*[http://hdaps.sourceforge.net HDAPS project page]<br />
*[http://sourceforge.net/mailarchive/forum.php?forum=hdaps-devel HDAPS-devel list archive]<br />
*[http://lemonshop.dk/ibm_hpaps/ Temporary location of current HDAPS driver]<br />
<br />
==Models featuring this Technology==<br />
*ThinkPad {{R50}}, {{R50p}}, {{R51}}, {{R52}}<br />
*ThinkPad {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}<br />
*ThinkPad {{X40}}, {{X41}}, {{X41T}}<br />
<br />
<br />
[[Category:Glossary]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_use_of_Graphics_Chips_Power_Management_features&diff=6809How to make use of Graphics Chips Power Management features2005-07-24T16:10:02Z<p>84.191.161.178: </p>
<hr />
<div>==Power Saving With A Framebuffer Console==<br />
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:<br />
radeonfb: Dynamic Clock Power Management enabled<br />
<br />
==DynamicClocks in the Radeon Xorg driver==<br />
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}<br />
<br />
Section "Device"<br />
Identifier "Videocard0"<br />
Driver "radeon"<br />
VendorName "IBM Thinkpad"<br />
BoardName "ATI Radeon Mobility M9"<br />
'''Option "DynamicClocks" "on"'''<br />
EndSection<br />
<br />
With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):<br />
<br />
(**) RADEON(0): Option "DynamicClocks" "on"<br />
(II) RADEON(0): Dynamic Clock Scaling Enabled<br />
<br />
{{WARN|Enabling DynamicClocks crashes some models. If the CPU is entering one of the lower power states (C3 or lower) during Xorg startup the display may stay black. As a workaround disable DynamicClocks in Xorg and use [http://www.hasw.net/linux/ rovclock] instead. But it does not scale the clocks to match the workload.}}<br />
<br />
<br />
==How to use it==<br />
After enabling it, my first question was how do I control it? After reading about it, the answer is: you don't have to, it manages the power consumption for you.\<br />
<br />
==X.org on Debian==<br />
Because debian doesn't have X.org yet - [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].<br />
<br />
'''Update:''' X.org has made it into Debian. See: [http://packages.debian.org/unstable/x11/xserver-xorg]<br />
<br />
There are also sarge backports available [http://www.backports.org/ here] or [http://people.debian.org/~nobse/xorg-x11/ here].<br />
<br />
Add the following line to your repository list:<br />
deb http://people.debian.org/~nobse/xorg-x11/ sarge main<br />
<br />
==External Sources==<br />
*[http://www.ati.com/products/pdf/powerplaywp2.pdf Marketing information from ATI]<br />
<br />
<br />
[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6829How to make ACPI work2005-07-24T12:06:48Z<p>84.191.161.178: /* using SoftwareSuspend2 */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
<br />
{{HINT|In general it is a good idea to read the README included with the driver.}}<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. Make sure to change the <tt>/dev/resume_partition</tt> to your swap partition, i.e. <tt>/dev/hda5</tt>.<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/resume_partition"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: <tt>resume2=swap:/dev/resume_partition</tt>. Again change <tt>/dev/resume_partition</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6798How to make ACPI work2005-07-24T12:06:23Z<p>84.191.161.178: /* using SoftwareSuspend2 */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
<br />
{{HINT|In general it is a good idea to read the README included with the driver.}}<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. Make sure to change the <tt>/dev/resume_partition</tt> to your swap partition, i.e. {{path|/dev/hda5}}.<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/resume_partition"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: <tt>resume2=swap:/dev/resume_partition</tt>. Again change <tt>/dev/resume_partition</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6797How to make ACPI work2005-07-24T12:05:24Z<p>84.191.161.178: /* using SoftwareSuspend2 */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
<br />
{{HINT|In general it is a good idea to read the README included with the driver.}}<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. You can change the <tt>/dev/resume_partition</tt> to your swap partition<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/resume_partition"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: <tt>resume2=swap:/dev/resume_partition</tt>. Again change <tt>/dev/resume_partition</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6796How to make ACPI work2005-07-24T12:05:14Z<p>84.191.161.178: /* using SoftwareSuspend2 */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
<br />
{{HINT|In general it is a good idea to read the README included with the driver.}}<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. You can change the <tt>/dev/resume_partition</tt> to your swap partition<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/resume_partition"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: <tt>resume2=swap:/dev/resume_partition/tt>. Again change <tt>/dev/resume_partition</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6795How to make ACPI work2005-07-24T12:01:39Z<p>84.191.161.178: /* Screen blanking (Standby) */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
<br />
{{HINT|In general it is a good idea to read the README included with the driver.}}<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda5"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6794How to make ACPI work2005-07-24T12:00:11Z<p>84.191.161.178: /* IBM specific ACPI driver */</p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
<br />
{{HINT|In general it is a good idea to read the README included with the driver.}}<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your XF86Config/xorg.conf.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda5"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_make_ACPI_work&diff=6793How to make ACPI work2005-07-24T11:58:44Z<p>84.191.161.178: </p>
<hr />
<div>==general==<br />
===Kernel configuration===<br />
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).<br />
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.<br />
<br />
If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:<br />
CONFIG_PM=y<br />
CONFIG_ACPI_BOOT=y<br />
CONFIG_ACPI_INTERPRETER=y<br />
CONFIG_ACPI_SLEEP=y<br />
CONFIG_ACPI_SLEEP_PROC_FS=y<br />
CONFIG_ACPI_AC=y<br />
CONFIG_ACPI_BATTERY=y<br />
CONFIG_ACPI_BUTTON=y<br />
CONFIG_ACPI_FAN=y<br />
CONFIG_ACPI_PROCESSOR=y<br />
CONFIG_ACPI_THERMAL=y<br />
CONFIG_ACPI_BUS=y<br />
CONFIG_ACPI_EC=y<br />
CONFIG_ACPI_POWER=y<br />
CONFIG_ACPI_PCI=y<br />
CONFIG_ACPI_SYSTEM=y<br />
<br />
===IBM specific ACPI driver===<br />
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10.<br /><br />
So you'll have to compile one yourself or get it as precompiled module for your kernel.<br /><br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br /><br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br /><br />
In general it is a good idea to read the README included with the driver.<br />
<br />
===ACPI daemon===<br />
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].<br />
<br />
==Screen blanking (Standby)==<br />
Make sure you have <br />
Option "DPMS"<br />
in the Monitor section of your XF86Config/xorg.conf.<br />
<br />
Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br /><br />
<br />
Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.<br />
<br />
==Suspend to RAM (Sleep)==<br />
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.<br />
<br />
The following glitches may or may not occur in relation to suspending to RAM:<br />
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.<br />
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.<br />
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].<br />
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.<br />
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.<br />
* Crash on resume<br />
** ...when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].<br />
** ...might be solved by disabling ''APIC'' (@Processor type and features) in the kernel configuration<br />
* If your suspend is failing, and a tail of {{path|/var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions<br />
* Due to the fact that Sonoma chipset based laptops (T43, T43p) utilize the SATA layer for disk access and SATA does not have power-management support yet Suspend to RAM does not work on these machines. However, Jens Axboe's patch ([http://marc.theaimsgroup.com/?l=linux-kernel&m=111504542402455&w=2] LKML posting) provides SATA power-management support and makes Suspend to RAM work on the T43 at least. (Tested on 2.6.12rc6 which the patch applies to with some offsets. T43p not tested but should work as well. X41: reboot after wake up.)<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12-rc6.diff 2.6.12-rc6 patch]<br />
** [http://shamrock.dyndns.org/~ln/linux/sata_pm.2.6.12.diff 2.6.12 patch]<br />
<br />
==Suspend to disk (Hibernate)==<br />
There are two drivers for this available:<br />
* swsusp, which is in the kernel and<br />
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself<br />
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].<br />
<br />
Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.<br />
<br />
===using swsusp===<br />
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.<br />
<br />
To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.<br />
<br />
In case you prefer to edit your config file directly, you should have the following three entries look like here...<br />
CONFIG_PM=y<br />
CONFIG_SOFTWARE_SUSPEND=y<br />
CONFIG_PM_STD_PARTITION="/dev/resume_partition"<br />
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)<br />
<br />
You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.<br />
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.<br />
<br />
To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.<br />
<br />
Ideally you would do this from a script like {{path|/etc/acpi/actions/hibernate.sh}}. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.<br />
*any running mysql server<br />
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.<br />
<br />
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.<br />
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).<br />
<br />
If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:<br />
<br />
amixer set Master mute >/dev/null 2>&1<br />
amixer set PCM mute >/dev/null 2>&1<br />
amixer set Master unmute >/dev/null 2>&1<br />
amixer set PCM unmute >/dev/null 2>&1<br />
<br />
Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.<br />
<br />
===using SoftwareSuspend2===<br />
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.<br />
<br />
Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html<br />
<br />
These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition<br />
<br />
# Software Suspend 2<br />
CONFIG_SOFTWARE_SUSPEND2=y<br />
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y<br />
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y<br />
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y<br />
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y<br />
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda5"<br />
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set<br />
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y<br />
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set<br />
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set<br />
<br />
Next, compile and install the kernel.<br />
<br />
In the meantime, add the following to the kernel parameters: <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.<br />
<br />
Install the hibernation script:<br />
*For {{Gentoo}} users: emerge hibernate-script<br /><br />
*For {{Fedora}} users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br /><br />
*For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/<br />
*{{Debian}} users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your {{path|/etc/mkinitrd/scripts}} directory before creating initrd image.<br />
<br />
Restart using the new kernel and run the script to test it: {{cmdroot|/usr/sbin/hibernate}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_configure_acpid&diff=8051How to configure acpid2005-07-24T11:49:46Z<p>84.191.161.178: </p>
<hr />
<div>Basically, acpid just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. {{cmd|man acpid}} holds detailed information on how to configure acpid.<br />
<br />
The [[ibm-acpi]] package includes example scripts in the {{path|config}} folder inside the tarball. They are a good starting point to adjust them to your needs. You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository. And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
==Example: go to sleep on lid close==<br />
<br />
To make the ThinkPad go to sleep when you close the lid, you need to add<br />
an event handler for the lid event and an action script that takes care<br />
of going to sleep and resuming.<br />
<br />
===Event Script===<br />
The event script needs to be created within {{path|/etc/acpi/events}} and can have any name you like.<br />
In this case we call it lid because it will trigger the lid event. Do {{cmdroot|vi /etc/acpi/events/lid}} and make it look like this:<br />
event=button/lid<br />
action=/etc/acpi/actions/sleep.sh %e<br />
<br />
The "event" line is a regular expression specifying the events we're<br />
interested in. You can determine what the event strings are from looking at<br />
{{path|/var/log/acpid}} after trying to suspend, close the lid, etc. .<br />
You can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
The "action" line is the command to be executed when these events are<br />
dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.<br />
<br />
{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}.<br />
<br />
===Action Script===<br />
Our example {{path|/etc/acpi/actions/sleep.sh}} script looks as follows:<br />
<br />
#!/bin/sh<br />
<br />
# if launched through a lid event and lid is open, do nothing<br />
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0<br />
<br />
# remove USB 1.1 driver<br />
rmmod uhci_hcd<br />
<br />
# sync filesystem and clock<br />
sync<br />
/sbin/hwclock --systohc<br />
<br />
# switch to console<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
/usr/sbin/radeontool light off<br />
<br />
# go to sleep<br />
echo -n "mem" > /sys/power/state<br />
<br />
# readjust the clock (it might be off a bit after suspend)<br />
/sbin/hwclock --adjust<br />
/sbin/hwclock --hctosys<br />
<br />
# reload USB 1.1 driver<br />
modprobe uhci_hcd<br />
<br />
# turn on the backlight and switch back to X<br />
radeontool light on<br />
chvt $FGCONSOLE<br />
<br />
====Explanations====<br />
*The lid generates an event for both opening and closing thus requiring that we check it's state and only act if it's closed.<br />
*There have been problems encountered with the USB devices not working properly after a resume from suspend. To circumvent those we remove the USB driver prior to suspend and reload it afterwards.<br />
*Note that the {{cmdroot|echo -n "mem" > /sys/power/state}} line does not return until we are revived. So there is only one event generated and there is no need to check the state of anything.<br />
*The console switching code in this script is a special solution for [[Problem with LCD backlight remaining on during ACPI sleep|a problem where the backlight doesn't switch off]] on the {{T30}} and some other models. Before going to sleep, these models switch to console mode which causes the backlight to come back on. So we preemptively switch to console mode and turn off the backlight using [[radeontool]] before going to sleep.<br />
{{NOTE|If your display doesn't come back on resume, look [[Problem with display remaining black after resume|here]].}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=How_to_configure_acpid&diff=6791How to configure acpid2005-07-24T11:46:22Z<p>84.191.161.178: </p>
<hr />
<div>Basically, acpid just executes scripts residing in {{path|/etc/acpi/actions}}. Which script to launch at which event is configured in several files in {{path|/etc/acpi/events}}. {{cmd|man acpid}} holds detailed information on how to configure acpid.<br />
<br />
The [[ibm-acpi]] package includes example scripts in the {{path|config}} folder inside the tarball. They are a good starting point to adjust them to your needs. You also might want to have a look at the [[Configs#ACPI | ACPI section of the Configs page]] or the [[:Category:Scripts|Scripts]] repository. And you can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
==Example: go to sleep on lid close==<br />
<br />
To make the ThinkPad go to sleep when you close the lid, you need to add<br />
an event handler for the lid event and an action script that takes care<br />
of going to sleep and resuming.<br />
<br />
The event script needs to be created within {{path|/etc/acpi/events}} and can have any name you like.<br />
In this case we call it lid because it will trigger the lid event. Do {{cmdroot|vi /etc/acpi/events/lid}} and make it look like this:<br />
event=button/lid<br />
action=/etc/acpi/actions/sleep.sh %e<br />
<br />
The "event" line is a regular expression specifying the events we're<br />
interested in. You can determine what the event strings are from looking at<br />
{{path|/var/log/acpid}} after trying to suspend, close the lid, etc. .<br />
You can find information about the event strings [[ibm-acpi]] generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].<br />
<br />
The "action" line is the command to be executed when these events are<br />
dispatched. In this example we call the {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.<br />
<br />
{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>kill -SIGHUP `pidof acpid`</tt>}}.<br />
<br />
Our example {{path|/etc/acpi/actions/sleep.sh}} script looks as follows:<br />
<br />
#!/bin/sh<br />
<br />
# if launched through a lid event and lid is open, do nothing<br />
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0<br />
<br />
# remove USB 1.1 driver<br />
rmmod uhci_hcd<br />
<br />
# sync filesystem and clock<br />
sync<br />
/sbin/hwclock --systohc<br />
<br />
# switch to console<br />
FGCONSOLE=`fgconsole`<br />
chvt 6<br />
/usr/sbin/radeontool light off<br />
<br />
# go to sleep<br />
echo -n "mem" > /sys/power/state<br />
<br />
# readjust the clock (it might be off a bit after suspend)<br />
/sbin/hwclock --adjust<br />
/sbin/hwclock --hctosys<br />
<br />
# reload USB 1.1 driver<br />
modprobe uhci_hcd<br />
<br />
# turn on the backlight and switch back to X<br />
radeontool light on<br />
chvt $FGCONSOLE<br />
<br />
The lid generates an event for both opening and closing thus requiring<br />
that we check it's state and only act if it's closed.<br />
<br />
There have been problems encountered with the USB devices not working properly after a resume from suspend.<br />
To circumvent those we remove the USB driver prior to suspend and reload it afterwards.<br />
<br />
Note that the {{cmdroot|echo -n "mem" > /sys/power/state}} line does not return until we are revived. So there is<br />
only one event generated and there is no need to check the state of anything.<br />
<br />
The console switching code in this script is a special solution for<br />
[[Problem with LCD backlight remaining on during ACPI sleep|a problem where the backlight doesn't switch off]]<br />
on the {{T30}} and some other models. Before going to sleep, these models switch to console mode which causes the<br />
backlight to come back on. So we preemptively switch to console mode and turn off the backlight using [[radeontool]]<br />
before going to sleep.<br />
{{NOTE|If your display doesn't come back on resume, look [[Problem with display remaining black after resume|here]].}}<br />
<br />
<br />
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]]</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=Problem_with_display_remaining_black_after_resume&diff=6871Problem with display remaining black after resume2005-07-24T11:38:39Z<p>84.191.161.178: </p>
<hr />
<div>There has been a problem encountered where the display stays black on resuming from suspend.<br />
<br />
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}}.<br />
<br />
==Affected Models==<br />
*ThinkPad {{T41p}}, {{T42p}}<br />
*ThinkPad {{X41}}, {{X40}}, {{X30}}, {{X31}}, {{X21}}<br />
*ThinkPad {{R50e}}{{footnote|1}}<br />
<br />
==Affected Operating Systems==<br />
*Linux (it's a kernel issue)<br />
<br />
==Solution==<br />
The Solution is to provide the <tt>acpi_sleep=s3_bios</tt> kernel parameter in your kernel parameter line.<br />
<br />
For grub this can look like this:<br />
title Linux, kernel 2.6.11-1-686<br />
root (hd0,0)<br />
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios<br />
initrd /boot/initrd.img-2.6.11-1-686<br />
savedefault<br />
boot<br />
<br />
{{footnotes|<br />
#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]].<br />
}}</div>84.191.161.178https://www.thinkwiki.org/w/index.php?title=Hardware_Specifications&diff=6815Hardware Specifications2005-07-24T09:00:02Z<p>84.191.161.178: /* Available Models */</p>
<hr />
<div>==Hardware specs and information about the specific Thinkpad Models.==<br />
* Choose a model name to to get a list of all currently available information related to this Model.<br />
* Choose a type-and-model number to get the specs of that specific model.<br />
* Compare the [[Thinkpad series]] (R, T, X, G), get an overview of the [[ThinkPad History]] or learn about the name [[ThinkPad]].<br />
** For current G, R, T and X series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tabook.pdf tabook.pdf]<br />
** For withdrawn A, G, T and X series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tawbook.pdf tawbook.pdf]<br />
** For withdrawn R series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/trwbook.pdf trwbook.pdf]<br />
** For withdrawn i series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tiwbook.pdf tiwbook.pdf]<br />
** For withdrawn 200, 300, 500, 600 and 700 series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/twbook.pdf twbook.pdf]<br><br />
** Or try searching the IBM announcements letters [http://www.ibm.com/news/usalet/ here].<br />
<br />
==Available Models==<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|- style="text-align:left;"<br />
!Numbered!!A series!!G series!!R series!!S series!!T series!!X series!!others<br />
|- style="text-align:left;vertical-align:top;"<br />
|<br />
'''[[:Category:390X | ThinkPad 390X]]'''<br />
*[[2626-L0U]]<br />
<br />
'''[[:Category:600X | ThinkPad 600X]]'''<br />
<br />
'''[[:Category:700 | ThinkPad 700]]'''<br />
<br />
'''[[:Category:760ED | ThinkPad 760ED]]'''<br />
<br />
'''[[:Category:760XD | ThinkPad 760XD]]'''<br />
<br />
'''[[:Category:770E | ThinkPad 770E]]'''<br />
*[[9548-510]]<br />
*[[9548-51U]]<br />
*[[9548-52U]]<br />
<br />
'''[[:Category:770X | ThinkPad 770X]]'''<br />
*[[9549-7AO]]<br />
'''[[:Category:770Z | ThinkPad 770Z]]'''<br />
<br />
||<br />
'''[[:Category:A20m | ThinkPad A20m]]'''<br />
<br />
'''[[:Category:A20p | ThinkPad A20p]]'''<br />
<br />
'''[[:Category:A21e | ThinkPad A21e]]'''<br />
<br />
'''[[:Category:A21m | ThinkPad A21m]]'''<br />
<br />
'''[[:Category:A21p | ThinkPad A21p]]'''<br />
<br />
'''[[:Category:A22e | ThinkPad A22e]]'''<br />
<br />
'''[[:Category:A22m | ThinkPad A22m]]'''<br />
<br />
'''[[:Category:A22p | ThinkPad A22p]]'''<br />
<br />
'''[[:Category:A30 | ThinkPad A30]]'''<br />
<br />
'''[[:Category:A30p | ThinkPad A30p]]'''<br />
<br />
'''[[:Category:A31 | ThinkPad A31]]'''<br />
<br />
'''[[:Category:A31p | ThinkPad A31p]]'''<br />
<br />
||<br />
'''[[:Category:G40 | ThinkPad G40]]'''<br />
<br />
'''[[:Category:G41 | ThinkPad G41]]'''<br />
<br />
||<br />
'''[[:Category:R30 | ThinkPad R30]]'''<br />
<br />
'''[[:Category:R31 | ThinkPad R31]]'''<br />
<br />
'''[[:Category:R32 | ThinkPad R32]]'''<br />
<br />
'''[[:Category:R40 | ThinkPad R40]]'''<br />
*[[2722-9BM]]<br />
*[[2722-DG1]]<br />
<br />
'''[[:Category:R40e | ThinkPad R40e]]'''<br />
<br />
'''[[:Category:R50 | ThinkPad R50]]'''<br />
<br />
'''[[:Category:R50p | ThinkPad R50p]]'''<br />
<br />
'''[[:Category:R50e | ThinkPad R50e]]'''<br />
<br />
'''[[:Category:R51 | ThinkPad R51]]'''<br />
*[[1829-K6G]]<br />
*[[1830-DG4]]<br />
<br />
<br />
'''[[:Category:R52 | ThinkPad R52]]'''<br />
||<br />
'''[[:Category:S30|ThinkPad S30]]'''<br />
<br />
'''[[:Category:S31|ThinkPad S31]]'''<br />
||<br />
'''[[:Category:T20|ThinkPad T20]]'''<br />
*[[2647-44G]]<br />
<br />
'''[[:Category:T21|ThinkPad T21]]'''<br />
*[[2647-97G]]<br />
<br />
'''[[:Category:T22|ThinkPad T22]]'''<br />
<br />
'''[[:Category:T23 | ThinkPad T23]]'''<br />
*[[2647-9RG]]<br />
*[[2647-7G1]]<br />
<br />
'''[[:Category:T30 | ThinkPad T30]]'''<br />
*[[2366-52U]]<br />
*[[2366-FBG]]<br />
*[[2366-JBG]]<br />
*[[2366-R7G]]<br />
<br />
'''[[:Category:T40 | ThinkPad T40]]'''<br />
<br />
'''[[:Category:T40p | ThinkPad T40p]]'''<br />
*[[2372-G1U]]<br />
<br />
'''[[:Category:T41 | ThinkPad T41]]'''<br />
<br />
'''[[:Category:T41p | ThinkPad T41p]]'''<br />
*[[2373-315]]<br />
*[[2373-GEG]]<br />
*[[2373-GGG]]<br />
*[[2373-GHG]]<br />
<br />
'''[[:Category:T42 | ThinkPad T42]]'''<br />
*[[2373-6ZG]]<br />
*[[2373-9XU]]<br />
*[[2373-F1G]]<br />
*[[2378-FVU]]<br />
*[[2373-FWG]]<br />
*[[2373-WGK]]<br />
*[[2378-RSU]]<br />
*[[2379-DXU]]<br />
<br />
'''[[:Category:T42p | ThinkPad T42p]]'''<br />
*[[2373-HTG]]<br />
*[[2373-W6M]]<br />
*[[2373-Y4M]]<br />
<br />
'''[[:Category:T43 | Thinkpad T43]]'''<br />
*[[2668-C2U]]<br />
<br />
'''[[:Category:T43p | Thinkpad T43p]]'''<br />
||<br />
'''[[:Category:X20 | ThinkPad X20]]'''<br />
<br />
'''[[:Category:X21 | ThinkPad X21]]'''<br />
*[[2662-66U]]<br />
<br />
'''[[:Category:X22 | ThinkPad X22]]'''<br />
*[[2662-95U]]<br />
*[[2662-9BU]]<br />
<br />
'''[[:Category:X23 | ThinkPad X23]]'''<br />
<br />
'''[[:Category:X24 | ThinkPad X24]]'''<br />
<br />
'''[[:Category:X30 | ThinkPad X30]]'''<br />
<br />
'''[[:Category:X31 | ThinkPad X31]]'''<br />
<br />
'''[[:Category:X40 | ThinkPad X40]]'''<br />
<br />
'''[[:Category:X41 | ThinkPad X41]]'''<br />
<br />
'''[[:Category:X41 Tablet | ThinkPad X41 Tablet]]'''<br />
||<br />
'''[[:Category:PC110 | PC110]]'''<br />
*[[PC110]]<br />
'''[[:Category:TransNote|TransNote]]'''<br />
*[[2675-61G]]<br />
|}<br />
<br />
<br />
[[Category:Models]]</div>84.191.161.178