ThinkWiki - User contributions [en]

User:Fialar

2009-03-08T10:44:35Z

Fialar: Removing all content from page

User:Fialar

2007-01-18T19:04:00Z

Fialar:

I used to have a Thinkpad T23, but it died. However, my partner still uses her trusty T21 which appears to be limping along somehow.

Talk:How to make ACPI work

2007-01-18T19:02:16Z

Fialar: /* ACPI completely broken on Thinkpad T20s */

{{NOTE|Please sign and date your posts, that is much easier than trying to track down on page history who wrote what!}}

== X41 Woes ==
I have tried the referred patch (Suspend to RAM) with the latest stable kernel (2.6.12.2): Reboot after wakeup.

== T22 Woes ==

Has anyone managed to get this working with a T22? The BIOS is upgraded, but it _never_ wakes up from sleep. Neither lid nor pwr button are noticed by the system.

--Are you in suspend2ram? This works fine for me. I think you have to enable it in BIOS.

== Sound-after-suspend not working with Mandriva 2006 ==
With Mandriva 2006, suspend/resume works with ACPI, but sound quits working.
This happens with the T20 and T22. The recommended Mandriva trick of setting "RESTORE_SOUND=yes" in the "suspend" script doesn't solve this. Other suggestions? - MarkStosberg mark@summersault.com

== Solutions ==
I had 2 different issues:
- with my X21 I had to unload the alsa modules before suspend.
- with my x23 I have to change the mixer settings to get it working again.

(I hope it will help)

== CIFS ==
Hi all,

I have found out that if I use cifs to mount Samba shares, I get lots of problems with suspend/hibernate (the cifsd breaks the shutdown process). Maybe it would be good to warn about this.

Alex (alex at corcoles dot net)

== Auto-wake on lid open - how to STOP? ==

Anybody have any idea how to stop the machine (a T43p) from automatically waking up on lid open? My /etc/acpi/events only has a lm_lid file which is commented out - it should do nothing, and there is no plain 'lid' event. Is lm_lid an event only activated when in laptop-mode?

----

That's a good question, but I have the opposite problem: my T43 (2687) won't wakeup from S3 (suspend-to-RAM) when I open the lid, which is exactly what yours do, and what I wanted mine to.

-- [[User:Hmh|hmh]] 2006-03-24 11:59:00 UTC-0300

----

Yes, I have the same problem - this 'feature' is exhibited in both O/S's on my T43p... I tried everything I could think of to stop it (changing/deleting the acpi event handlers, etc). There does not seem to be any BIOS option to "wake up on lid open."

It has irritated me less over time; I find myself now using suspend if I don't want the feature, and sleep mode only if I anticipate that I will open it up and use. After all, suspend is pretty quick with 1 GB ram.

-- [[User:gsmenden|gsmenden]] 2006-03-27 19:36:55 EST
----
Just a note...the term "suspend" refers to both, suspending to RAM and suspending to disk, the counterpart to the "sleep" term is "hibernate". We should try to stay clear about this everywhere to avoid confusion.

[[User:Wyrfel|Wyrfel]] 10:24, 29 March 2006 (CEST)
----

There is a /proc/acpi/wakeup file here. (t42p). Currently shows:
Device Sleep state Status
LID 3 * enabled
SLPB 3 * enabled
PCI0 3 disabled
UART 3 disabled
PCI1 4 disabled
USB0 3 disabled
USB1 3 disabled
AC9M 4 disabled

Echoing the 4 letter code toggles that device as a wakeup device.. ie:
root# echo " LID" > /proc/acpi/wakeup
root# cat /proc/acpi/wakeup
Device Sleep state Status
LID 3 *disabled

Does that work for any of you guys?
[[User:Nirik|Nirik]] 23:15, 29 Mar 2006 (MST)

----

I encountered the same problem and echoing to /proc/acpi/wakeup made the LID, the SLPB and the UART disabled (on my T43 - no matter what I did). The syslog told me that it was due to the fact they all share the same ACPI GPE.

After reading much on ACPI and the kernel handling, I think the reason is that the kernel code activates all _PSW supporting devices (which includes the LID).

I wanted to refrain from altering kernel code so I modified the ACPI DSDT (funny).
At first I changed the GPE for the LID so it won't share it with the UART and the SLBP (which I believe is the "FN" button). Then when I saw it worked, but I had to keep echoing "LID disable" to /proc/acpi/wakeup so I erased the _PSW and _PRW entirely from the control method of the _LID device.

Now my laptop only wakes up when "FN" is pressed. I can post the DSDT modification or elaborate on my solution if you please.

[[User:mr.dnme|Mr DNME]] 11:00 3 May 2006 (UTC+0300)

----

== R50e - suspend to ram with DRI on ==

Does anyone got this working? After resume the X do not refresh properly applications (the panel, application content and background).

== ACPI completely broken on Thinkpad T20s ==

I removed T20 and T21 from the recommended list, since, their BIOS's don't support ACPI
properly. In the Linux 2.6 kernels, multiple kacpid processes create a race condition, eating
up CPU time until the machine eventually has to be rebooted.

For more information see [[Talk:Ibm-acpi|Ibm-acpi discussion page]]

--[[User:Fialar|Fialar]] 20:02, 18 January 2007 (CET)

How to make ACPI work

2007-01-18T19:00:46Z

Fialar: Removed T20 and T21 thinkpads from Recommended list. ACPI has been known to cause problems on these machines, including race conditions eating up resources. (kacpi) See Talk page for more information.

==General==
===Kernel configuration===
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).
To do this open your kernel config and enable ACPI Power Management:
:{{kernelconf|CONFIG_PM|<*>|Power Management support|Power management options|||}}
:{{kernelconf|CONFIG_ACPI_SLEEP|<*>|ACPI|Power management options|||}}

You'd most likely want to enable the following ACPI options:
:{{kernelconf|CONFIG_ACPI_SLEEP|<*>|Sleep States|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_AC|<*>|AC Adapter|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_BATTERY|<*>|Battery|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_FAN|<*>|Fan|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_PROCESSOR|<*>|Processor|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_THERMAL|<*>|Thermal Zone|ACPI|Power management options||}}

If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:
CONFIG_PM=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y

Then recompile your kernel.

{{HINT| ACPI SLEEP States option did only show up for me after patching [[Software Suspend 2]] into the kernel. With a vanilla 2.6.17 kernel, one must enable CONFIG_SMP and CONFIG_HOTPLUG_CPU for the option to appear, cf. [http://bugs.debian.org/383059 Debian bug #383059] .}}

===Kernel boot parameters===
Many ThinkPads have been hit by a recent (kernel 2.6.16) change to ACPI4Linux that changed the default means of accessing the ACPI Embedded Controller as a way to shake out underlying bugs in the EC access code. If your ThinkPad fails to resume properly (a blinking Sleep light on resume that doesn't go away, or a hang when trying to suspend/standby a second time), adding {{bootparm|ec_intr|0}} to your kernel command line may help.

===IBM specific ACPI driver===
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.

You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.

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.

{{HINT|Generally it is a good idea to read the README included with the driver.}}

===ACPI daemon===
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]].

==Screen blanking (Standby)==
Make sure you have
Option "DPMS"
in the Monitor section of your {{path|/etc/X11/XF86Config}} or {{path|/etc/X11/xorg.conf}}.

Running {{cmduser|xset +dpms}} and then {{cmduser|xset dpms force off}} will turn off the backlight on a laptop screen.<br />

Note that this may not work in combination with {{cmduser|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.

==Suspend to RAM (Sleep)==
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.

For Troubleshooting, look at the [[Problems with ACPI suspend-to-ram|Problems with ACPI suspend-to-ram page]].

==Suspend to disk (Hibernate)==
There are two drivers for this available:
* [[swsusp]], which is in the kernel and
* [[Software Suspend 2]] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself.

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].

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.

See the according drivers page for instructions.

==ThinkPads on which it is recommended to use ACPI==
*ThinkPad {{770X}}, {{770Z}}
*ThinkPad {{A20m}}, {{A20p}}, {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
*ThinkPad {{G40}}, {{G41}}
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R40e}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}
*ThinkPad {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}
*ThinkPad {{Z60t}}, {{Z60m}}
*ThinkPad {{X60s}}
*ThinkPad {{TransNote}}

Talk:How to make ACPI work

2006-10-24T14:10:58Z

Fialar: /* ACPI completely broken on Thinkpad T20s */

{{NOTE|Please sign and date your posts, that is much easier than trying to track down on page history who wrote what!}}

== X41 Woes ==
I have tried the referred patch (Suspend to RAM) with the latest stable kernel (2.6.12.2): Reboot after wakeup.

== T22 Woes ==

Has anyone managed to get this working with a T22? The BIOS is upgraded, but it _never_ wakes up from sleep. Neither lid nor pwr button are noticed by the system.

--Are you in suspend2ram? This works fine for me. I think you have to enable it in BIOS.

== Sound-after-suspend not working with Mandriva 2006 ==
With Mandriva 2006, suspend/resume works with ACPI, but sound quits working.
This happens with the T20 and T22. The recommended Mandriva trick of setting "RESTORE_SOUND=yes" in the "suspend" script doesn't solve this. Other suggestions? - MarkStosberg mark@summersault.com

== Solutions ==
I had 2 different issues:
- with my X21 I had to unload the alsa modules before suspend.
- with my x23 I have to change the mixer settings to get it working again.

(I hope it will help)

== CIFS ==
Hi all,

I have found out that if I use cifs to mount Samba shares, I get lots of problems with suspend/hibernate (the cifsd breaks the shutdown process). Maybe it would be good to warn about this.

Alex (alex at corcoles dot net)

== Auto-wake on lid open - how to STOP? ==

Anybody have any idea how to stop the machine (a T43p) from automatically waking up on lid open? My /etc/acpi/events only has a lm_lid file which is commented out - it should do nothing, and there is no plain 'lid' event. Is lm_lid an event only activated when in laptop-mode?

----

That's a good question, but I have the opposite problem: my T43 (2687) won't wakeup from S3 (suspend-to-RAM) when I open the lid, which is exactly what yours do, and what I wanted mine to.

-- [[User:Hmh|hmh]] 2006-03-24 11:59:00 UTC-0300

----

Yes, I have the same problem - this 'feature' is exhibited in both O/S's on my T43p... I tried everything I could think of to stop it (changing/deleting the acpi event handlers, etc). There does not seem to be any BIOS option to "wake up on lid open."

It has irritated me less over time; I find myself now using suspend if I don't want the feature, and sleep mode only if I anticipate that I will open it up and use. After all, suspend is pretty quick with 1 GB ram.

-- [[User:gsmenden|gsmenden]] 2006-03-27 19:36:55 EST
----
Just a note...the term "suspend" refers to both, suspending to RAM and suspending to disk, the counterpart to the "sleep" term is "hibernate". We should try to stay clear about this everywhere to avoid confusion.

[[User:Wyrfel|Wyrfel]] 10:24, 29 March 2006 (CEST)
----

There is a /proc/acpi/wakeup file here. (t42p). Currently shows:
Device Sleep state Status
LID 3 * enabled
SLPB 3 * enabled
PCI0 3 disabled
UART 3 disabled
PCI1 4 disabled
USB0 3 disabled
USB1 3 disabled
AC9M 4 disabled

Echoing the 4 letter code toggles that device as a wakeup device.. ie:
root# echo " LID" > /proc/acpi/wakeup
root# cat /proc/acpi/wakeup
Device Sleep state Status
LID 3 *disabled

Does that work for any of you guys?
[[User:Nirik|Nirik]] 23:15, 29 Mar 2006 (MST)

----

I encountered the same problem and echoing to /proc/acpi/wakeup made the LID, the SLPB and the UART disabled (on my T43 - no matter what I did). The syslog told me that it was due to the fact they all share the same ACPI GPE.

After reading much on ACPI and the kernel handling, I think the reason is that the kernel code activates all _PSW supporting devices (which includes the LID).

I wanted to refrain from altering kernel code so I modified the ACPI DSDT (funny).
At first I changed the GPE for the LID so it won't share it with the UART and the SLBP (which I believe is the "FN" button). Then when I saw it worked, but I had to keep echoing "LID disable" to /proc/acpi/wakeup so I erased the _PSW and _PRW entirely from the control method of the _LID device.

Now my laptop only wakes up when "FN" is pressed. I can post the DSDT modification or elaborate on my solution if you please.

[[User:mr.dnme|Mr DNME]] 11:00 3 May 2006 (UTC+0300)

----

== R50e - suspend to ram with DRI on ==

Does anyone got this working? After resume the X do not refresh properly applications (the panel, application content and background).

== ACPI completely broken on Thinkpad T20s ==

Suggest to remove T20 from the "ThinkPads on which it is recommended to use ACPI" category.
For more information see [[Talk:Ibm-acpi|Ibm-acpi discussion page]]

-- [[User:Fialar|fialar]] 2006-10-23 09:14:00 UTC+0100

User:Fialar

2006-10-23T09:16:15Z

Fialar:

I used to have a Thinkpad T23, but it died. However, my partner still uses her trusty T20 which appears to be limping along somehow.

Talk:How to make ACPI work

2006-10-23T09:14:06Z

Fialar:

{{NOTE|Please sign and date your posts, that is much easier than trying to track down on page history who wrote what!}}

== X41 Woes ==
I have tried the referred patch (Suspend to RAM) with the latest stable kernel (2.6.12.2): Reboot after wakeup.

== T22 Woes ==

Has anyone managed to get this working with a T22? The BIOS is upgraded, but it _never_ wakes up from sleep. Neither lid nor pwr button are noticed by the system.

--Are you in suspend2ram? This works fine for me. I think you have to enable it in BIOS.

== Sound-after-suspend not working with Mandriva 2006 ==
With Mandriva 2006, suspend/resume works with ACPI, but sound quits working.
This happens with the T20 and T22. The recommended Mandriva trick of setting "RESTORE_SOUND=yes" in the "suspend" script doesn't solve this. Other suggestions? - MarkStosberg mark@summersault.com

== Solutions ==
I had 2 different issues:
- with my X21 I had to unload the alsa modules before suspend.
- with my x23 I have to change the mixer settings to get it working again.

(I hope it will help)

== CIFS ==
Hi all,

I have found out that if I use cifs to mount Samba shares, I get lots of problems with suspend/hibernate (the cifsd breaks the shutdown process). Maybe it would be good to warn about this.

Alex (alex at corcoles dot net)

== Auto-wake on lid open - how to STOP? ==

Anybody have any idea how to stop the machine (a T43p) from automatically waking up on lid open? My /etc/acpi/events only has a lm_lid file which is commented out - it should do nothing, and there is no plain 'lid' event. Is lm_lid an event only activated when in laptop-mode?

----

That's a good question, but I have the opposite problem: my T43 (2687) won't wakeup from S3 (suspend-to-RAM) when I open the lid, which is exactly what yours do, and what I wanted mine to.

-- [[User:Hmh|hmh]] 2006-03-24 11:59:00 UTC-0300

----

Yes, I have the same problem - this 'feature' is exhibited in both O/S's on my T43p... I tried everything I could think of to stop it (changing/deleting the acpi event handlers, etc). There does not seem to be any BIOS option to "wake up on lid open."

It has irritated me less over time; I find myself now using suspend if I don't want the feature, and sleep mode only if I anticipate that I will open it up and use. After all, suspend is pretty quick with 1 GB ram.

-- [[User:gsmenden|gsmenden]] 2006-03-27 19:36:55 EST
----
Just a note...the term "suspend" refers to both, suspending to RAM and suspending to disk, the counterpart to the "sleep" term is "hibernate". We should try to stay clear about this everywhere to avoid confusion.

[[User:Wyrfel|Wyrfel]] 10:24, 29 March 2006 (CEST)
----

There is a /proc/acpi/wakeup file here. (t42p). Currently shows:
Device Sleep state Status
LID 3 * enabled
SLPB 3 * enabled
PCI0 3 disabled
UART 3 disabled
PCI1 4 disabled
USB0 3 disabled
USB1 3 disabled
AC9M 4 disabled

Echoing the 4 letter code toggles that device as a wakeup device.. ie:
root# echo " LID" > /proc/acpi/wakeup
root# cat /proc/acpi/wakeup
Device Sleep state Status
LID 3 *disabled

Does that work for any of you guys?
[[User:Nirik|Nirik]] 23:15, 29 Mar 2006 (MST)

----

I encountered the same problem and echoing to /proc/acpi/wakeup made the LID, the SLPB and the UART disabled (on my T43 - no matter what I did). The syslog told me that it was due to the fact they all share the same ACPI GPE.

After reading much on ACPI and the kernel handling, I think the reason is that the kernel code activates all _PSW supporting devices (which includes the LID).

I wanted to refrain from altering kernel code so I modified the ACPI DSDT (funny).
At first I changed the GPE for the LID so it won't share it with the UART and the SLBP (which I believe is the "FN" button). Then when I saw it worked, but I had to keep echoing "LID disable" to /proc/acpi/wakeup so I erased the _PSW and _PRW entirely from the control method of the _LID device.

Now my laptop only wakes up when "FN" is pressed. I can post the DSDT modification or elaborate on my solution if you please.

[[User:mr.dnme|Mr DNME]] 11:00 3 May 2006 (UTC+0300)

----

== R50e - suspend to ram with DRI on ==

Does anyone got this working? After resume the X do not refresh properly applications (the panel, application content and background).

== ACPI completely broken on Thinkpad T20s ==

Suggest to remove T20 from the "ThinkPads on which it is recommended to use ACPI" category.
For more information see [[Talk:Ibm-acpi|Ibm-acpi discussion page]]