ThinkWiki - User contributions [en]

How to make ACPI work on a ThinkPad T23

2006-03-21T06:39:55Z

Fooka: /* Frequency Scaling */

This page deals with installing and running {{Gentoo}} Linux (2005.1) on a ThinkPad {{T23}}, Model 2647-4MG.

==Basic installation==
The default kernel (2.6.12-r6) boots OK, and recognises all the devices (modem not tested).

==ACPI==
Getting software suspend working requires some tweaking.

First of all, [[BIOS Upgrade|update to the latest BIOS and Embedded Controller Program]].

{{cmdroot|dmesg}} will probably tell you that ACPI isn't enabled in the BIOS, because the T23 BIOS has no mention of ACPI. Just add {{bootparm|lapic|}} to the kernel
arguments in {{path|/etc/lilo.conf}} or {{path|/boot/grub/menu.lst}}.

After that, you will probably get a lot of ACPI error messages, generally of the form <tt>AE_NOT_EXIST</tt>. Those can be fixed by recompiling your DSTD. To do just that, get the Intel iasl compiler source from [http://developer.intel.com/technology/iapc/acpi/downloads.htm their site] and compile it. It should build without troubles. De- and re-compile the DSDT. If it gives errors or remarks, try fixing them as best as you can. Then load the new DSDT on boot with the kernel's "Custom DSDT" option.

Now {{cmdroot|dmesg}} should show that the ACPI had found the ECDT and enabled the interpreter and you should find a full set of ACPI entries under {{path|/proc}}.

Done that, verify that the [[ibm-acpi]] driver is enabled by issuing {{cmdroot|ls /proc/acpi/ibm/*}}. If you see files in this directory, everything is alright. If the directory couldn't be found, you will have to enable [[ibm-acpi]] in your kernel config (as builtin or module) and recompile your kernel.

The next step is [[How to configure acpid|configuring acpid]], which handles the ACPI buttons through scripts in {{path|/etc/acpi}}.

To try if suspend to ram workd, press {{key|Fn}}{{key|F4}} or issue a {{cmdroot|echo -n mem >/sys/power/state}}.

===Resume problem===
If your system doesn't resume from sleep after that, use the power button to switch it off and restart. To solve the issue, try disabling S3 framebuffer support in your kernel config and recompile your kernel. Should that not be enough, try unloading suspicious drivers such as USB in your suspend script and reloading them on resume.

If all that doesn't help, build a monolithic kernel having everything you need builtin and only minimal options enabled. If it works with that kernel, start reenabling other options step by step.

===Button events===
By default, ACPI seems to handle three button events only - the Power button, the Suspend key ({{key|Fn}}{{key|F4}}) and the lid event. {{key|Fn}}{{key|F3}} (Screen blank) will need [[How to make ACPI work#Screen blanking (Standby)|extra configuration]], as well as {{key|Fn}}{{key|F12}} (Suspend to disk) (look [[How to make ACPI work#Suspend to disk (Hibernate)|here}}). {{key|Fn}}{{key|F7}}, (Switch to
video) at least blanks the LCD.

{{key|Fn}}{{key|Home}} (LED brighter), {{key|Fn}}{{key|End}} (LED dimmer), {{key|Fn}}{{key|PgUp}}
(Screen light) will work without any further effords, since they are not handled by the ACPI subsystem.

When the machine is running, the lid switch blanks the screen when
pressed and restores on release, but if the machine is suspended
pressing the switch does nothing and releasing it brings the machine out
of suspend mode.

Commands echoed to eg: {{path|/proc/acpi/ibm/light}} can be mixed with the appropriate keypresses (here,
{{key|Fn}}{{key|PgUp}}) without problems.

===Frequency Scaling===
The CPU (Pentium III-M) has power management and
throttling; use the '''acpi-cpufreq''' module instead of the '''speedstep-ich''' module to change speed automatically. The CPU has
only two speeds, and with the '''cpufreq_ondemand''' & '''cpufreq_conservative''' modules, dynamic scaling will be achieved. Alternatively, with the '''speedstep-ich''' module, you can use a shell script to flip between the performance and powersave kernel governors; everything needed can be found in the {{path|/sys/devices/system/cpu/cpu0/cpufreq}} directory.

===UltraBay LED stays lid===
The Bay LED wrongly stays lit even when in suspend to ram mode, but the most recent (1.1) [[ibm-acpi]] module provides an ACPI LED device which controls most of the LEDs (the Bay LED
is 4), so you can switch it off in your suspend script.

===Resume===
With the CPU on low speed (if it matters) and the LED off the power consumption in Suspend mode is around 580mW.

It looks as if the software to control full ACPI functionality has
only stabilised within the middle of 2005, so if you
have problems, try upgrading to IBM's latest BIOS and EBIOS, and a
kernel >=2.12. With luck, the next version or so of the S3 driver will
be free of its hang problem.

Talk:Savage

2006-03-13T06:32:59Z

Fooka:

== DRM working flawless in stock debian Sid package ==
Hey, this ought to be posted. I've installed it works..
glxgears went from FPS in the high 100s to FPS in the high 400s!

the package in question is "libgl1-mesa-dri" -- install that from sid, and bam! DRM in Xorg 6.9.0.. um. probably want to add Load "drm" among the modules loading in your xorg.conf.

[http://hardware.mcse.ms/message269644.html this is the page] I found with the info.

How to configure acpid

2006-03-09T01:49:52Z

Fooka: CAN use! CAN use!

__TOC__
==Introduction==
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}}. All actions are documented in {{path|/var/log/acpid}}.

==Sources of Information==
*{{cmduser|man acpid}} holds detailed information on how to configure acpid.
*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]].

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

===Event Script===
The event script needs to be created within {{path|/etc/acpi/events}} 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
{{path|/var/log/acpid}} 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 {{path|sleep.sh}} script residing in {{path|/etc/acpi/actions}} and pass the event description text using the %e placeholder.

For the script you can use the <tt>hibernate</tt> script of [http://www.suspend2.net/ Software Suspend 2] (it is independent of the [[Software Suspend 2|suspend-to-disk]] functionality), or any of many examples available on the web, such as the one below.

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

===Action Script===
Our example {{path|/etc/acpi/actions/sleep.sh}} 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
sleep 5 && 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

====Explanations====
*The lid generates an event for both opening and closing thus requiring that we check its 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 {{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.
*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.

==Troubleshooting==
*If something doesn't work, your first action should be a {{cmdroot|tail /var/log/acpid}}. It will tell you a lot about what is going on. If it has "Permission denied" errors, check the permissions of your {{path|/etc/acpi/actions}} scripts (especially make sure that the executable bit is set). Also check the permissions for other involved files like i.e. device nodes.
*If your display doesn't come back on resume, look [[Problem with display remaining black after resume|here]].
*My X21 didn't reset the sleep LED (the small moon), it was blinking after the sleep, if you have the ibm-acpi kernel module loaded, you can switch it of after the sleep by appending this line to the script:
echo 7 off > /proc/acpi/ibm/led
{{NOTE|
The ibm-acpi module must have the experimental<math>=</math>1 parameter passed to if for /proc/acpi/ibm/led to work. You can either do this through a /etc/modprobe.d entry or manually.
}}

[[Category:770X]] [[Category:770Z]] [[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]] [[Category:TransNote]]

Talk:Problem with checking battery status

2006-03-08T06:38:19Z

Fooka: dude,

== tp_smapi ==

How about using [[tp_smapi]] to get the battery status? Does it work on the R31?

--[[User:Thinker|Thinker]] 09:21, 7 March 2006 (CET)
----

wouldn't that require a SMAPI bios? the R31 is an Acer i830 special. so no SMAPI bios. perhaps I am not well enough informed?

--Fooka
----

Why not just give it a try? What's the dmesg output when you run tp_smapi's "make load"?

--[[User:Thinker|Thinker]] 04:58, 8 March 2006 (CET)
----

== dude, ==

Mar 7 22:16:26 localhost kernel: smapi: No SMAPI BIOS header was found. :-(

yea. um. no SMAPI bios.

-Fooka

Problem with display remaining black after resume

2006-03-08T01:22:01Z

Fooka: from "The Solution is", to "One solution may be", cuz it's not The Solution always.

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

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

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43p}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)

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

==Solutions==
===Solution for ThinkPads with ATI graphic chips===
One solution may be to provide the {{bootparm|acpi_sleep|s3_bios}} 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

For lilo it can look like this:

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

Additionally, in {{Ubuntu}} or {{Kubuntu}} it might be necessary modify {{path|/etc/default/acpi-support}}. Check to make sure that ACPI_SLEEP and SAVE_VBE_STATE are both uncommented and set to true. (If you are using this trick with Intel graphics chips, as suggested below, make sure that nothing with respect to VBE state is done--don't repost the video, don't save the VBE state.)

Otherwise see the example script below.

Another one solution will be to use vbetool. If you are using Debian with hibernate package just uncomment "EnableVbetool yes" in /etc/hibernate/hibernate.conf (or /etc/hibernate/ram.conf)

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

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

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

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

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

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

# waking up
# restore system clock
hwclock --hctosys

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

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

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

Talk:Problem with checking battery status

2006-03-08T00:55:47Z

Fooka: /* re tp_smapi */

== tp_smapi ==

How about using [[tp_smapi]] to get the battery status? Does it work on the R31?

--[[User:Thinker|Thinker]] 09:21, 7 March 2006 (CET)
----

== re tp_smapi ==

wouldn't that require a SMAPI bios? the R31 is an Acer i830 special. so no SMAPI bios. perhaps I am not well enough informed?

--Fooka

Talk:Problem with checking battery status

2006-03-08T00:55:17Z

Fooka: /* re tp_smapi */

Problem with checking battery status

2006-03-07T18:46:36Z

Fooka: Changed from possible to partial, because of APM findings.

R31 laptops have a problem where anytime ACPI or APM events are polled (e.g. checking battery status), causes the mouse to jerk around the screen clicking on things. Also sometimes repeating keypresses are generated.

===Causes===
Anomaly in the way the kernel driver handles the i8042 keyboard/mouse controller in the R31.

===Related Symptoms===
These messages in dmesg seem to be related:

psmouse.c: TrackPoint at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.
psmouse.c: TrackPoint at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.

===Workarounds===
Don't query the battery. Remove any battery applets from your panel.

===Partial Solution===
Use the following kernel parameter, without quotes, at boot: "i8042.nomux=1". Add this to your "append=" line in lilo.conf or append it to the kernel line in the menu.lst of your grub configuration.

'''Make sure to use ACPI''', as this does not work if you boot with APM.

===References===
* http://kruemel.rnbhq.org/r31.html#bug_batteryquery
* http://webrum.uni-mannheim.de/math/froeser/r31_linux.html
* http://forum.kanotix.net/PNphpBB2-viewtopic-t-6424.html
* http://www.linuxquestions.org/questions/archive/25/2005/04/2/308437
* http://lists.debian.org/debian-user/2003/12/msg03632.html
* http://www.systura.com/linux/thinkpadr31.php

[[Category:R31]]

Talk:Problem with checking battery status

2006-03-07T18:44:18Z

Fooka: re tp_smapi

== tp_smapi ==

How about using [[tp_smapi]] to get the battery status? Does it work on the R31?

--[[User:Thinker|Thinker]] 09:21, 7 March 2006 (CET)
----

== re tp_smapi ==

wouldn't that require a SMAPI bios? the R31 is an Acerr i830 special. so no SMAPI bios. perhaps I am not well enough enformed?

Problem with display remaining black after resume

2006-03-07T08:51:49Z

Fooka: Added R31 to list of non-LCD-waking-up models

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

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

==Affected Models==
*ThinkPad {{T41p}}, {{T42}}, {{T42p}}, {{T43p}}
*ThinkPad {{X21}}, {{X30}}, {{X31}}, {{X40}}, {{X41}}
*ThinkPad {{R31}}, {{R50e}}{{footnote|1}}, {{R50p}}, {{R51}} (with BIOS 1.11), {{R52}}
*ThinkPad {{A30p}}
*ThinkPad {{390X}} (doesn't wake up; LCD backlight on, harddrive light remains on)

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

==Solutions==
===Solution for ThinkPads with ATI graphic chips===
The Solution is to provide the {{bootparm|acpi_sleep|s3_bios}} 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

For lilo it can look like this:

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

Additionally, in {{Ubuntu}} or {{Kubuntu}} it might be necessary modify {{path|/etc/default/acpi-support}}. Check to make sure that ACPI_SLEEP and SAVE_VBE_STATE are both uncommented and set to true. (If you are using this trick with Intel graphics chips, as suggested below, make sure that nothing with respect to VBE state is done--don't repost the video, don't save the VBE state.)

Otherwise see the example script below.

Another one solution will be to use vbetool. If you are using Debian with hibernate package just uncomment "EnableVbetool yes" in /etc/hibernate/hibernate.conf (or /etc/hibernate/ram.conf)

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

The following solution should work on 865G, 865GV, 855GM, 855GME, 852GME chipsets.
*First of all, '''do not''' use the {{bootparm|acpi_sleep|s3_bios}} kernel parameter.
*Second, completely remove framebuffer support from your kernel. If it's built as modules, it is important that they do not get loaded at all.
*Before suspending, change to a console and safe the video state with {{cmdroot|cat /proc/bus/pci/00/02.0 > /tmp/video_state}}.
*On resume, restore the video state with {{cmdroot|cat /tmp/video_state > /proc/bus/pci/00/02.0}} and change back to X.
The following example {{path|/etc/acpi/actions/sleep.sh}} script shows how to integrate the according lines.

#!/bin/bash

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

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

# sync filesystem
sync

# sync hardware clock with system time
hwclock --systohc

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

# waking up
# restore system clock
hwclock --hctosys

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

# change back to X
chvt $FGCONSOLE

# clean up behind us
rm /tmp/video_state

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

Problem with checking battery status

2006-03-07T08:18:32Z

Fooka: Jerky mouse on ThinkPad R31

R31 laptops have a problem where anytime ACPI or APM events are polled (e.g. checking battery status), causes the mouse to jerk around the screen clicking on things. Also sometimes repeating keypresses are generated.

===Causes===
Anomaly in the way the kernel driver handles the i8042 keyboard/mouse controller in the R31.

===Related Symptoms===
These messages in dmesg seem to be related:

psmouse.c: TrackPoint at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.
psmouse.c: TrackPoint at isa0060/serio4/input0 lost synchronization, throwing 2 bytes away.

===Workarounds===
Don't query the battery. Remove any battery applets from your panel.

===Possible Solution===
Use the following kernel parameter, without quotes, at boot: "i8042.nomux=1". Add this to your "append=" line in lilo.conf or append it to the kernel line in the menu.lst of your grub configuration.

===References===
* http://kruemel.rnbhq.org/r31.html#bug_batteryquery
* http://webrum.uni-mannheim.de/math/froeser/r31_linux.html
* http://forum.kanotix.net/PNphpBB2-viewtopic-t-6424.html
* http://www.linuxquestions.org/questions/archive/25/2005/04/2/308437
* http://lists.debian.org/debian-user/2003/12/msg03632.html
* http://www.systura.com/linux/thinkpadr31.php

[[Category:R31]]