ThinkWiki - User contributions [en]

How to configure acpid

2005-05-19T09:10:52Z

217.231.122.13:

Basically, acpid just executes scripts residing in <tt>/etc/acpi/actions</tt>. Which script to launch at which event is configured in several files in <tt>/etc/acpi/events</tt>. {{cmd|man acpid}} holds detailed information on how to configure acpid.

The [[ibm-acpi]] package includes example scripts in the <tt>config</tt> 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]].

==Example: go to sleep on lid close==

To make the ThinkPad go to sleep when you close the lid, you need to add
an event handler for the lid event and an action script that takes care
of going to sleep and resuming.

The event script needs to be created within <tt>/etc/acpi/events</tt> and can have any name you like.
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:
event=button/lid
action=/etc/acpi/actions/sleep.sh %e

The "event" line is a regular expression specifying the events we're
interested in. You can determine what the event strings are from looking at
<tt>/var/log/acpid</tt> after trying to suspend, close the lid, etc. .
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]].

The "action" line is the command to be executed when these events are
dispatched. In this example we call the <tt>sleep.sh</tt> script residing in <tt>/etc/acpi/actions</tt> and pass the event description text using the %e placeholder.

{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>'''kill -SIGHUP `pidof acpid`'''</tt>}}.

Our example <tt>/etc/acpi/actions/sleep.sh</tt> script looks as follows:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6
/usr/sbin/radeontool light off

# go to sleep
echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd

# turn on the backlight and switch back to X
radeontool light on
chvt $FGCONSOLE

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.

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.

Note that the <code>echo -n "mem" > /sys/power/state
</code> 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.

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.
{{NOTE|If your display doesn't come back on resume, look [[Problem with display remaining black after resume|here]].}}

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

Problem with display remaining black after resume

2005-05-19T09:08:45Z

217.231.122.13:

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

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

===Affected Models===
*ThinkPad {{T41p}}, {{T42p}}
*ThinkPad {{X40}}

===Affected Operating Systems===
*Linux (it's a kernel issue)

===Solution===
The Solution is to provide the <tt>acpi_sleep=s3_bios</tt> kernel parameter in your kernel parameter line.

For grub this can look like this:
title Linux, kernel 2.6.11-1-686
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1-686 root=/dev/hda1 ro acpi_sleep=s3_bios
initrd /boot/initrd.img-2.6.11-1-686
savedefault
boot

How to configure acpid

2005-05-19T09:05:47Z

217.231.122.13:

Basically, acpid just executes scripts residing in <tt>/etc/acpi/actions</tt>. Which script to launch at which event is configured in several files in <tt>/etc/acpi/events</tt>. {{cmd|man acpid}} holds detailed information on how to configure acpid.

The [[ibm-acpi]] package includes example scripts in the <tt>config</tt> 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]].

==Example: go to sleep on lid close==

To make the ThinkPad go to sleep when you close the lid, you need to add
an event handler for the lid event and an action script that takes care
of going to sleep and resuming.

The event script needs to be created within <tt>/etc/acpi/events</tt> and can have any name you like.
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:
event=button/lid
action=/etc/acpi/actions/sleep.sh %e

The "event" line is a regular expression specifying the events we're
interested in. You can determine what the event strings are from looking at
<tt>/var/log/acpid</tt> after trying to suspend, close the lid, etc. .
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]].

The "action" line is the command to be executed when these events are
dispatched. In this example we call the <tt>sleep.sh</tt> script residing in <tt>/etc/acpi/actions</tt> and pass the event description text using the %e placeholder.

{{NOTE|To make your changes take effect after adding or modifying the events files you must do a <tt>'''kill -SIGHUP `pidof acpid`'''</tt>}}.

Our example <tt>/etc/acpi/actions/sleep.sh</tt> script looks as follows:

#!/bin/sh

# if launched through a lid event and lid is open, do nothing
echo "$1" | grep "button/lid" && grep -q open /proc/acpi/button/lid/LID/state && exit 0

# remove USB 1.1 driver
rmmod uhci_hcd

# sync filesystem and clock
sync
/sbin/hwclock --systohc

# switch to console
FGCONSOLE=`fgconsole`
chvt 6
/usr/sbin/radeontool light off

# go to sleep
echo -n "mem" > /sys/power/state

# readjust the clock (it might be off a bit after suspend)
/sbin/hwclock --adjust
/sbin/hwclock --hctosys

# reload USB 1.1 driver
modprobe uhci_hcd

# turn on the backlight and switch back to X
radeontool light on
chvt $FGCONSOLE

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.

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.

Note that the <code>echo -n "mem" > /sys/power/state
</code> 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.

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.

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

Known Problems

2005-05-19T09:01:46Z

217.231.122.13:

Information on known problems with certain Thinkpad models.

Choose (or create) a problem:

===Display Problems===
*[[Problem with red tinted display | Red tint problem]] (TP 23)

*[[Problem with red display shadow | Red shadow problem]] (TP T41p)

*[[Problem with DVI throughput | Problem with DVI throughput on port replicators and docks]] (models from 2000-2004)

*[[Problem with garbled screen | Garbled screen problem]]

*[[Problem with video related system lockup | Video-related system lockups]] (TP T2x)

*[[Problem with black X | Unmovable square black X in X]] (TP T2x)

===Network Problems===
*[[Problem with 3Com 10/100 Ethernet card not being recognized]] (models with that card)

===Power Management and Battery Problems===
*[[Problem with Thinkpad 600 batteries | Battery problem]] (TP 600/E/X)

*[[Problem with fan noise | Fan noise problem]] (TP T4x/p, TP R5x/p)

*[[Problem with high power drain in ACPI sleep | High power drain in ACPI sleep]] (various models)

*[[Problem with LCD backlight remaining on during ACPI sleep | LCD backlight remaining on during ACPI sleep]] (various models)

*[[Problem with display remaining black after resume|Blank display after resume]] (various models)

===Sound Problems===
*[[Problem with broken sound on ThinkPad 600 | Broken sound on ThinkPad 600/E]] (TP 600/E/X, 770Z)

===Misc Problems===
*[[Problem with lm-sensors | Problem with lm_sensors]] (TP 570E, 770X/Z, 600E/X, 240, X20)
*[[Problem with high pitch noises | High pitch noises]] (several models)
*[[Problem with hard drive clicking | Clicking Hard Drive]] (T4x models and other models which ship with Hitachi's 5k80 hard drive)
*[[Problem with Dock USB Ports | Dock USB Ports]] (T30)
*[[Problem with USB 2.0 | USB 2.0 problems]] (T4x)

[[de:Bekannte_Probleme]]