ThinkWiki - User contributions [en]

Problem with high pitch noises

2006-12-02T05:33:25Z

Jfl: Added Z61t to the list

Information on strange high pitch, low volume noises emitted by ThinkPads.

==Problem description==
Even though ThinkPads are known as very silent notebooks, they tend to emit different, mostly high pitch noises in certain circumstances. The noises are of low volume and hence not realized by everyone or at least tolerated by most people. However, there are those with "bat like ears" that hear them and might be annoyed by that.

==Affected Models==
Noises have been experienced in the following situations:
{| border="1" cellspacing="0" cellpadding="2"
|-
! style="vertical-align:top;background-color:#DDDDDD;" | situation
! style="vertical-align:top;background-color:#DDDDDD;" | noise description
! style="vertical-align:top;background-color:#DDDDDD;" | affected models
|-
| style="vertical-align:top;" |
Plugged into AC / running at high CPU frequency
| style="vertical-align:top;" |
soft crackling, buzzing noise
| style="vertical-align:top;" |
*{{T41}}
**2379-DJU
|-
| style="vertical-align:top;" |
ThinkPad suspended to RAM
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T42p}}
|-
| style="vertical-align:top;" |
ThinkPad connected to power and switched off, with battery fully charged
| style="vertical-align:top;" |
constant high pitch noise
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
moving windows or just the mouse in xorg
| style="vertical-align:top;" |
strange noise like a rapid series of very short high pitch noises adding to a constant kind of whistling (only as long as the movement goes)
| style="vertical-align:top;" |
*{{T41p}}
**2373-GHG
|-
| style="vertical-align:top;" |
Thinkpad connected to power or working on battery, also when suspended to RAM
| style="vertical-align:top;" |
High pitch noise also when HD is powered down.
| style="vertical-align:top;" |
*{{T23}}
**2647-DG4
*{{X24}}
**2662-MWG
|-
| style="vertical-align:top;" |
Thinkpad connected to power battery charged less than 60%
| style="vertical-align:top;" |
High pitch noise till battery is charged more than 60%.
| style="vertical-align:top;" |
*{{T41p}}
**2373-GEG
|-
| style="vertical-align:top;" |
Constantly, if AC connected
| style="vertical-align:top;" |
High pitched, low volume constant noise.
| style="vertical-align:top;" |
*{{T40}}
**2373-88U
|-
| style="vertical-align:top;" |
When the CPU freq jumps up to 1Ghz or above, or when the laptop is in suspend mode
| style="vertical-align:top;" |
Constant high pitched
| style="vertical-align:top;" |
*{{R50}}
**1829-6DM
|-
| style="vertical-align:top;" |
(May come from harddisk.)
| style="vertical-align:top;" |
continuous, intermittent, low volume, high pitched
| style="vertical-align:top;" |
*{{600X}}
|-
| style="vertical-align:top;" |
ACPI puts the processor into the C3 or C4 power saving states (i.e., the system is idle).
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{X41}}
*{{T43}}
**2686-DGU
*{{T43p}}
*{{T60}}
**2007-72U
*{{T21}}
*{{T20}}
**2648-46U
|-
| style="vertical-align:top;" |
Cpufreqd (or powernowd etc.) slows down the processor, for exemple at the end of an heavy task.
| style="vertical-align:top;" |
High-pitched crackling noise.
| style="vertical-align:top;" |
*{{T42}}
|-
| style="vertical-align:top;" |
When on battery
| style="vertical-align:top;" |
Noise level varies from inaudible to clearly audible, screeching sound, or sometimes beeping (when wifi is on)
| style="vertical-align:top;" |
*{{R52}}
**1858-A11
*{{T43}}
**2686-DGU
**1871-4AG
*{{T60}}
**2007-72U
*{{x60}}
*{{x31}}
**2673-CBU
*{{Z61m}}
**9450-3HG
*{{Z61t}}
**9440-2QU

|-
| CPU is used much AND laptop is on AC power AND the TFT panel is enabled.
| Screetching high pitch noise, like a million crickets
|
* {{X41}}

|-
| Network is pluged in and networkload is ~100%.
| low volume highfreq. pitch noise from left speaker or cpu.
|
*{{Z60m}}, {{Z60t}}
*{{T40}}
*{{T43}}
**2687-DDU
|}

==Affected Operating Systems==
All, though Linux appears especially susceptible.

==Possible sources==

* '''CPU activity:''' On some models the noise is triggered by certain CPU power states or activity patterns (as proven [http://www.wisdom.weizmann.ac.il/~tromer/acoustic here]).
* '''Graphics processor:''' In some models from the T2x era, e.g. the {{T23}}, the problem was related to the graphics circuitry and occured especially or only while making use of DirectDraw functions. IBM was able to fix it through a BIOS upgrade.
* '''Hard disk:''' On some ThinkPads the processor and hard disk are adjacent and produce similar noise. For example, in the {{X41}} the sound generated by the hard disk is likely to be loudest at the vent.
* '''Gigabit Ethernet processor:''' In some models (e.g., {{T43}}) high ethernet activity causes a high pitch noise.

* '''Screen brightness:''' on an {{X31}}, a hissing sound is started whenever screen brightness is not full.

==Status==

The problem is highly specific to operating system, model and even individual machines. There is no universal solution, but on most machines one of the following will reduce or eliminate the noise (possibly at some cost in power consumption).

==Solutions for CPU-triggered noise==

===Limit ACPI CPU power states===

There are four ACPI CPU power states, called C1 through C4. Often only the extreme power saving modes C4 or C3 produce the noise, so the noise can be stopped by insructing the Linux ACPI code to use only lower modes.

To forbid the ACPI driver from using C4 (this fixed the problem with on some ThinkPad {{T43}}, {{T43p}} and {{T41}}):
* If the ACPI processor component is compiled as built-in (<tt>CONFIG_ACPI_PROCESSOR=y</tt>):
**Pass the {{bootparm|max_cstate|3}} kernel argument.
* If the ACPI processor component is loaded as a module (<tt>CONFIG_ACPI_PROCESSOR=m</tt> and <tt>processor</tt> shows in the output of {{cmdroot|lsmod}}), do either of:
** Pass the {{bootparm|processor.max_cstate|3}} kernel argument (this does not work in Ubuntu 5.10 with default kernel).
** Add <code>options processor max_cstate=3</code> to {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}}, or {{path|/etc/modprobe.d/...}}, depending on your system) (this does not work in Ubuntu 5.10 with default kernel).
** {{cmdroot|echo 3 > /sys/module/processor/parameters/max_cstate}} (this can be changed in runtime for experimentation). (If may need to be set again upon resume from suspend, e.g., in the wakeup script.)
** (On Ubuntu 5.10, the default kernel uses <code>processor</code> as a module. Unfortunately, the script loading it, {{path|/etc/init.d/acpid}}, ignores the <code>options processor max_cstate=3</code> setting in {{path|/etc/modprobe.d/<my file>}}. As a solution for this specific problem, add the line <code>echo 2 > /sys/module/processor/parameters/max_cstate</code> directly to {{path|/etc/init.d/acpid}}, at the end of the function <code>load_modules()</code>, immediately after the line <code>echo "$PRINTK" > /proc/sys/kernel/printk</code>.)
** On Gentoo: Configure your Thinkpad as described in the [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide]. Then as root create the files {{path|/etc/init.d/limit-sleep-states}} and {{path|/etc/conf.d/limit-sleep-states}} as below. Then just issue the command {{cmdroot|rc-update add limit-sleep-states default}} to limit the sleep states only when running on AC power, or {{cmdroot|rc-update add limit-sleep-states default battery}} to always limit the sleep states.
cat <<EOF > /etc/init.d/limit-sleep-states
#!/sbin/runscript

depend() {
need acpid
}

start() {
ebegin "Limiting CPU sleep state to C${LIMIT_CSTATE}"
echo $LIMIT_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}

stop() {
ebegin "Removing CPU sleep state limit"
echo $REMOVE_CSTATE > /sys/module/processor/parameters/max_cstate
eend $?
}
EOF

cat <<EOF > /etc/conf.d/limit-sleep-states
# limit CPU sleep state to the following value (adjust accordingly)
LIMIT_CSTATE=3
# some value which is higher than all available sleep states
REMOVE_CSTATE=8
EOF

To also forbid the C3 state, replace "<tt>3</tt>" with "<tt>2</tt>" above (this fixed the problem on some ThinkPad {{X40}}, {{X41}}, {{X60}}, {{Z61t}} and {{R52}}, as well as on {{T20}} where C4 is not supported at all):

Note that these options affect power consumption when the CPU is idle. For example, here is the [[How to measure power consumption|measured power consumption]] on a ThinkPad {{T43}}:
* {{bootparm|processor.max_cstate|4}}: 15160mW (default, noisy)
* {{bootparm|processor.max_cstate|3}}: 15770mW (660mW higher, silent)
* {{bootparm|processor.max_cstate|2}}: 16100mW (2940mW higher, silent)

See the [http://thinkwiki.org/wiki?title=Talk:Problem_with_high_pitch_noises discussion page] for further information and success reports.

*Jakob Schou Pedersen: Editing the file {{path|/etc/init.d/acpid}} as described above (the last solution) worked on my T43 :-)

===Turn off CPU power saving in in BIOS===

Go into the BIOS and turn off the power saving processor feature that puts it into idle mode. (This worked on a ThinkPad {{T43}}, {{T21}} and {{X60s}}.)

===Disable ACPI CPU power states===

Completely disable CPU ACPI power states. Discussion:

*From Martin Steigerwald: I made the observation that I get at least less high pitch noises on my {{T23}} when I do not use the two ACPI modules "processor" and "thermal" (depends on the first one). I have no clue, why. Anyone with similar experiences?
:Omar Yasin: I've got a {{R52}} and when I load the same ACPIO modules the high pitch noises are not as loud but I can still hear them.
*Niko Ehrenfeuchter: I'm experiencing the same here on my {{X24}}. Removing the "processor" module also stops the pitch noise, which does ONLY occur when setting the CPU to maximum speed (using cpufreq). On low speed it's completely silent, even having loaded the processor module.

*Rolf Adelsberger: I can confirm this: the high pitch noise is only remarkable (at least with my ears ;-) ) if the processor speed is set to maximum frequency.

*Stefan Baums: My {{X41}} produced a high-pitched crackle from the processor vent on the left. Changing HZ did nothing, and the 'processor' module could not easily be removed from the system (Ubuntu 5.04). What solved the problem for me was adding {{bootparm|idle|halt}} to the boot command line. Unfortunately, this solution only lasts until the first hibernation or suspend - when the computer ({{X41}}) resumes, the high-pitched crackle is back.

* The {{bootparm|idle|halt}} solution combined with setting <code>#define HZ 100</code> in the kernel fixes the problem on a {{T43}}.

* jhatch: {{bootparm|idle|halt}} plus <code>#define HZ 100</code> also worked on my {{T43}}. It still reverts back to noisy after a suspend/resume though. This needs to be fixed...

===Change the timer interrupt frequency===

Change the "HZ" kernel constants to alter the frequency of timer interrupts. Discussion:

{{NOTE|The timer interrupt frequency (HZ) in current Linux kernels is directly tied to the kernel task scheduler. Lower frequencies provide larger time-slices and thus also higher latencies (which may kill latency-sensitive applications like audio processing). 100Hz ended up as the recommended "server" setting (because it increases disk/CPU throughput in a latency-insensitive environment). Higher frequencies are better for latency-sensitive applications, and improve desktop responsivity at the cost of less processor throughput. 1000Hz ended up as the recommended "desktop" setting.}}

*Andreas Karnahl: i've read in several forums it has something to do with the "idle"-state (or "C3") of the processor. There is a frequency called "timer interrupt" (or so mething like that). Since kernel 2.6x it is set to 1000 Hz by default (compared to 100 Hz in Kernel 2.4x). The exact reason i don't know, but it is safe to change this frequency to 100 Hz in kernel 2.6x (by the way, windows up to XP uses 100 Hz by default).<br />Just do the following:<br />
: In {{path|[path to kernel-sources]/include/asm-i386/param.h}} find the line
:: <code>#define HZ 1000</code>
: and change the value of HZ to 100:
:: <code>#define HZ 100</code>
:Then recompile the kernel.<br />After i changed it on my ThinkPad {{A30}} (under SuSE 9.2 and 9.3) and recompiling the kernel the high pitch noise is gone away.

* Omar Yasin: Worked on my {{R52}}, thanks.

* [[User:Thinker|Thinker]]: In modern kernels this constant is in the kernel configuration {{kernelconf|CONFIG_HZ|Processor type and features||Timer Frequency|||||}}.

===Prevent idling===

Indirectly avoid power saving states by making sure the CPU is rarely idle:

* Paul RIVIER: Here is a really simple workaround. C3 / C4 states are mainly called when the cpu freq is higher than required, for example if your cpufreqd is lazy to slow down the frequency but quick to raise it. That is why I use powernowd with the builtin "passive" mode, which is lazy for raising frequency, but quick to go back to the lowest. Now I don't hear them as often as before, as I avoid C3/C4 states at high frequency.

* The problem also occurs on my {{X41}} with 2.6.11. Setting up [[How to make use of Dynamic Frequency Scaling|frequency scaling]] with the <code>ondemand</code> governor makes things a lot better, as the processor does not stay with the maximum frequency when in idle mode. It can be still heard sometimes, though.

* On a {{T43}} the noise was gone after dropping cpufreqd and switching to the ondemand governor - maybe because of the high sampling rate? (used the default: 10ms)

===Change the processor voltage===

Reducing the processor voltage (when possible) may decrease or eliminate the noise. On one ThinkPad {{T43}}, [[Pentium M undervolting and underclocking|undervolting the Pentium M processor]] eliminated the high-pitched noise. Compared to the other solutions this has the benefit of lower power consumption, both due to the undervolting itself and because there is no need to forbid high APCI CPU power saving modes.

==Solutions for screen brightness related sounds==

===Disable BIOS brightness control===

The sound starts when on batteries as the BIOS automatically reduces screen brightness. To disable this, simply switch Config>Display>Brightness from
Normal to High. See also [[User:Piccobello/Hissing sound on battery|here]].

==Other solutions==

===Disable UltraBay===
*Naheed Vora: My {{T41}} (2373-268) started to give high pitch noise ocassionally, when I upgraded to 2.6.11 kernel. I tried to unload lot of modules but finally figured out that disabling bay stops the noise. If you have [[ibm-acpi]], do (need a cleaner solution): {{cmduser|echo eject >/proc/acpi/ibm/bay}} .

===Disable IrDA===
*Mike Perry: I was able to cure an intermittent high-pitched whine on both my {{X24}} and {{X40}} by disabling the Infrared port.

===Disable the Linuxant Modem Driver===
*Joern Heissler: I made another experience. I played around with linuxant conexant [[Modem Devices|modem]] drivers. After loading them I got some noise on my {{T42p}}.

===Media Player paused===
*Eilif Muller: On my {{R52}} the high-pitched noises go away if I load XMMS, play something then pause it.
*Jacob: On my {{T43}} DGU it goes away if I open mplayerc.exe and press play then pause it. This is the high-pitched noise that only shows up when I'm on battery.

''I'd guess that the above tip works as when xmms or similar is running, it is uncompressing compressed audio/video, which is a processor intensive action. Keeping this paused means that the app won't 'let go' of the processor, forcing it to stay up and running, which stops it entering the higher powersave modes.''

===Upgrade BIOS===
On a ThinkPad [[X60s]], [[BIOS_Upgrade|upgrading the BIOS]] to version 1.06 eliminated the high pitch noise when running on battery.

===Disable USB===
On one {{T43}} and one {{X60}}, (partially) disabling USB using {{cmdroot|rmmod uhci_hcd}} significantly reduced the noise.

How to make use of Dynamic Frequency Scaling

2006-12-02T03:47:47Z

Jfl:

==General==
Linux supports dynamic frequency scaling for systems with the following processors:
*[[Intel Mobile Pentium III]]
*[[Intel Mobile Pentium III-M]]
*[[Intel Mobile Pentium 4]]
*[[Intel Mobile Pentium 4-M]]
*[[Intel Pentium M (Banias)]]
*[[Intel Pentium M (Dothan)]]
*[[Intel Core Solo (Yonah)]]
*[[Intel Core Duo (Yonah)]]
*Mobile Athlon
*AMD64
*Opteron

==Configuring the Kernel==
===2.4 Kernels===
There were various frequency scaling implementations in the 2.4 series of kernels. They all were preliminary and a standard was rised with the introduction of the sysfs filesystem in 2.6 kernels. It is recommended to use a 2.6 kernel, if possible.

===2.6 Kernels===
You need to enable the cpu frequency scaling for your kernel (usually your distros kernel will have this enabled):
:{{kernelconf|CONFIG_CPU_FREQ|<*>|||||}}

You need to enable governors, if not already done in your distros default kernel:
:{{kernelconf|CONFIG_CPU_FREQ_GOV_PERFORMANCE|<*>|||||}}
:{{kernelconf|CONFIG_CPU_FREQ_GOV_POWERSAVE|<*>|||||}}
:{{kernelconf|CONFIG_CPU_FREQ_GOV_USERSPACE|<*>|||||}}

Since 2.6.10 there is the ondemand governor that does cpu frequency scaling in kernel and can be used as an alternative to powernowd etc.
It can be enabled with:
:{{kernelconf|CONFIG_CPU_FREQ_GOV_ONDEMAND|<*>|||||}}

Since 2.6.12 there is the conservative governor that works similar to the ondemand governor.
:{{kernelconf|CONFIG_CPU_FREQ_GOV_CONSERVATIVE|<*>|||||}}

ondemand and conservative differ in the way they scale up and down. The ondemand governor switches to the highest frequency immediately when there is load, while the conservative governor increases frequency step by step. Likewise they behave the other way round for stepping down frequency when the CPU is idle.

If you own a Dothan processor, you need to enable Enhanced SpeedStep functionalities.
:{{kernelconf|CONFIG_X86_SPEEDSTEP_CENTRINO|<*>|||||}}

==Using the Sys Interface==
The files in {{path|/sys/devices/system/cpu/cpu0/cpufreq/}} provide information and a means of controlling the frequency scaling subsystem.
Seed values are given in Khz. You need to be root to access the /sys filesystem.

Your max speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq}}
:{{cmdresult|700000}}
Your min speed is at {{path|/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}.
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq}}
:{{cmdresult|500000}}
If you are using the userspace governor, you can write to {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}} to change the current speed.
:{{cmdroot|echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 697.252}}
:{{cmdroot|echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed}}
:{{cmdroot|cat /proc/cpuinfo | grep "cpu MHz"}}
:{{cmdresult|cpu MHz : 976.152}}

==Using Frequency Scaling Governors==
You can compile the scaling governors into your kernel or compile it as module. You'll find the governors with 'make menuconfig' here:
:{{kernelconf||||CPU Frequency scaling|Power management options (ACPI, APM)|||}}

After booting the new kernel you can get a list of available governors with (as root):
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors}}
:{{cmdresult|conservative ondemand powersave userspace performance}}

Note: If the governors are compiled as modules, load them first:
:{{cmdroot|modprobe cpufreq_performance cpufreq_ondemand cpufreq_conservative cpufreq_powersave cpufreq_userspace}}

A Short Overview over the available governors:
:;ondemand
::This driver is a dynamic cpufreq policy governor. It changes frequency based on the processor load and may not work on older laptops without Enhanced SpeedStep due to [http://lists.debian.org/debian-powerpc/2005/05/msg00542.html latency reasons].
:;conservative
::New since 2.6.12. Similar to ''ondemand'' but has a much slower 'slew rate', remaining at high frequency for many seconds after recent processor demand. Good for battery powered environments and AMD64. Again, this governor may not work on older ThinkPads like the T21.
:;powersave
::Like the name says, your battery would choose this one ;). It sets the Frequency always to the lowest available.
:;userspace
::You have to choose this one, if you want to set the frequency manually. Some [[#Using Frequency Scaling Daemons|frequency scaling daemons]] require this governor to operate correctly. This will typically be the recommended one with older processors like A30p's pIIIm-1200.
:;performance
::This governor sets your Frequency always to the highest available.

Now we set our governor:
What is our current governor?
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|userspace}}
Set new governor and watch if it has changed
:{{cmdroot|echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdroot|cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor}}
:{{cmdresult|conservative}}

Congrats! Your governor is active.

You may set the governor in your rc.local, to make it used on every boot.

==Using Frequency Scaling Daemons==
Frequency Scaling Daemons adapt the frequency policy to different situations. A typical configuration would be to use the ondemand governor running off batteries and performance otherwise, or combining powersave with conservative on laptops with heat problems. More sophisticated setups adapt to battery level, CPU temperature or even running programs. Some daemons are able to control other power management features like hard disks or graphic cards.

{{NOTE|Daemons are optional. If you don't plan to change policies depending on the situation, you don't need one and you can stick to the <tt>ondemand</tt> or <tt>conservative</tt> frequency scaling governors, available in kernels after 2.6.10 or 2.6.12 respectively. See [[#Using Frequency Scaling Governors|above]]. They require less configuration and have generally been experienced to flawlessly adapt to the situations at hand.}}

Some daemons use the kernel governors (see above), others implement the functionality on their own. In the latter case you have to enable the userspace governor. If it is built as module, load it as <tt>cpufreq-userspace</tt>.

There are plenty of userspace frequency scaling daemons available:

*[[How to configure cpudynd | cpudynd]]
*[[How to configure cpufreqd | cpufreqd]]
*[[How to use cpufrequtils | cpufrequtils]]
*[[How to configure powernowd | powernowd]]
*[[How to configure powersaved | powersaved]]
*[[How to configure speedfreqd | speedfreqd]]

==Debian notes==
Instead of compiling your own kernel, you can use the {{Debian}} "stock" kernel. In Unstable/SID the 2.6.12 kernel image with an {{path|/etc/modules}} file that includes:

battery
ac
thermal
processor
acpi-cpufreq
cpufreq-userspace

With the powernowd package and you should be setup.

{{Debian}} has no {{path|rc.local}}, so read [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-custombootscripts this] and [http://www.debian.org/doc/FAQ/ch-customizing.en.html#s-booting this].

A better alternative for Debian than modifying bootscripts, is to install the [http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&version=all&exact=1&keywords=sysfsutils sysfsutils package]. Then edit {{path|/etc/sysfs.conf}} (as root), where you can setup values to sysfs entries that you want to be modified automatically on boot.

==Troubleshooting==
*If you have a Coppermine-piix-smi based ThinkPads like from the A2x, X2x and T2x series you need to enable the <tt>speedstep-smi</tt> driver in the kernel and load it if it's built as module. You might want to look at [[How to get SpeedStep working on Coppermine-piix4-smi based ThinkPads | this page]].

*If you have a p4-class celeron based ThinkPad like the R40e you might want to look at [[How to get SpeedStep working on P4-class-Celeron based ThinkPads | this page]]

*You may need to set your BIOS to "maximum performance" if you are using Linux to set the CPU speed. This is necessary to prevent odd behaviour (cpufreq 'freezing' at certain frequencies) with the T4x series.

==Finetuning voltages and available frequencies==
See [[Pentium M undervolting and underclocking]].

==A note about CPU throttling==

Throttling the CPU through ACPI "T" states is generally useless for power consumption reduction. It does not decrease clock frequency at all, and it can even increase power consumption in a modern CPU capable of ACPI "C" states, as it can interfere with the CPU reaching the higher C states (such as C2).

On a T43, setting a CPU to a ACPI Throttle state different than T0 (no throttling) can cause it to draw more than 100mW extra power, as it will reach C2 less often.

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[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:T60]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:TransNote]]

Tp smapi

2006-12-02T03:46:58Z

Jfl:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
The <tt>tp_smapi</tt> kernel module exposes some features of the ThinkPad hardware/firmware via a <tt>sysfs</tt> interface. Currently, the main implemented functionality is control of battery charging and extended battery status. The underlfying hardware interfaces are [[SMAPI support for Linux|SMAPI]] and direct access to the embedded controller.

For older ThinkPad models, see also [[tpctl]].

{{WARN|This driver uses undocumented features and direct hardware access. It thus cannot be guaranteed to work and could conceivably damage your computer (though so far no incidents have been reported).}}

|}

===Features===
*Battery charge/discharge control
*Battery status information
*PCI bus power saving control

===Project Homepage / Availability===
* Project page: http://tpctl.sourceforge.net/
* You need to [http://sourceforge.net/project/showfiles.php?group_id=1212&package_id=171579 download] only the <tt>tp_smapi</tt> package. Versions containing <tt>-test</tt> are experimental, others are stable.

===Installation===
====Installation from source====
You will need the kernel headers and makefiles corresponding to your current kernel version. On {{Fedora}}, this means {{cmdroot|yum install kernel-devel-$(uname -r)}} .

For testing, you can simply compile and load the driver within the current
working directory:
:{{cmdroot|tar xzvf tp_smapi-0.30.tgz}}
:{{cmdroot|cd tp_smapi-0.30}}
:{{cmdroot|make load}}

To compile and install into the kernel's module path:
:{{cmdroot|make install}}

If you use the [[HDAPS]] driver, add <tt>HDAPS=1</tt> to also patch the <tt>hdaps</tt> for compatibility with <tt>tp_smapi</tt> (this requires a kernel source tree matching the current kernel):
:{{cmdroot|1=make load HDAPS=1}}
or, to compile and install into the kernel's module path:
:{{cmdroot|1=make install HDAPS=1}}

To prepare a stand-alone patch against the current kernel tree (including
a patch against <tt>hdaps</tt> and new <tt>Kconfig</tt> entries):
:{{cmdroot|make patch}}

To delete all autogenerated files:
:{{cmdroot|make clean}}

The original kernel tree is never modified by any these commands.
The {{path|/lib/modules}} directory is modified only by {{cmdroot|make install}}.

====Installation in Gentoo====
The {{Gentoo}} portage system carries a [http://packages.gentoo.org/packages/?category=app-laptop;name=tp_smapi tp_smapi package], which follows the latest version pretty closely. On a Gentoo system, you can install and load as follows.

If you use the [[HDAPS]] driver, do this first:

* Configure <tt>hdaps</tt> as module in your kernel
* Add the <tt>HDAPS</tt> use flag in {{path|/etc/make.conf}}
* {{cmdroot|rmmod hdaps}}

Then:

* {{cmdroot|emerge tp_smapi}} (or install tp_smapi with hdaps support manually, as above)
* {{cmdroot|echo "tp_smapi" >> /etc/modules.autoload.d/kernel-2.6}}
* {{cmdroot|echo "hdaps" >> /etc/modules.autoload.d/kernel-2.6}}

Then reboot, or run:
* {{cmdroot|modprobe tp_smapi}}
* {{cmdroot|modprobe hdaps}}

====Installation on Debian/Ubuntu====

<pre>
deb http://www.oakcourt.dyndns.org/debian/ ./
deb-src http://www.oakcourt.dyndns.org/debian/ ./
</pre>

This repository has kernel-patch packages for tp_smapi. This will not only integrate tp_smapi into your kernel build but will patch the hdaps driver for you. It is available for kernel 2.6.15 and later. Also available is an init script to automatically set SMAPI paramaters at boot--this is in package tpsmapi-utils. Please report any bugs to [[User:Ajbarr]]

===Battery charge control features===
To set the thresholds for starting and stopping battery charging (in percent of current full charge capacity):
:{{cmdroot|echo 40 > /sys/devices/platform/smapi/BAT0/start_charge_thresh}}
:{{cmdroot|echo 70 > /sys/devices/platform/smapi/BAT0/stop_charge_thresh}}
:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/*_charge_thresh}}
{{HINT|Battery charging thresholds can be used to keep Li-Ion ad Li-Polymer batteries partially charged, in order to [[Maintenance#Battery_treatment|increase their lifetime]].}}
To unconditionally inhibit charging for 17 minutes:
:{{cmdroot|echo 17 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}
{{HINT|Charge inhibiting can be used to reduce the power draw of the laptop, in order to use a an under-spec power supply that can't handle the combined power draw of running and charging. It can also be used to control which battery is charged when [[How to use UltraBay batteries|using an Ultrabay battery]].}}

To cancel charge inhibiting:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/inhibit_charge_minutes}}

To force battery discharging even if connected to AC, use one of these:
:{{cmdroot|echo 1 > /sys/devices/platform/smapi/BAT0/force_discharge}}
{{HINT|This can be used to choose which battery is discharged when [[How to use UltraBay batteries|using an UltraBay battery]].}}

To cancel forced discharge:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/BAT0/force_discharge}}

===Battery status features===
To view extended battery status such as charging state, voltage, current, capacity, cycle count and model information:

<pre>
# cat /sys/devices/platform/smapi/BAT0/installed
# cat /sys/devices/platform/smapi/BAT0/state # idle/charging/discharging
# cat /sys/devices/platform/smapi/BAT0/cycle_count
# cat /sys/devices/platform/smapi/BAT0/current_now # instantaneous current
# cat /sys/devices/platform/smapi/BAT0/current_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/power_now # instantaneous power
# cat /sys/devices/platform/smapi/BAT0/power_avg # last minute average
# cat /sys/devices/platform/smapi/BAT0/last_full_capacity
# cat /sys/devices/platform/smapi/BAT0/remaining_percent
# cat /sys/devices/platform/smapi/BAT0/remaining_running_time
# cat /sys/devices/platform/smapi/BAT0/remaining_charging_time
# cat /sys/devices/platform/smapi/BAT0/remaining_capacity
# cat /sys/devices/platform/smapi/BAT0/design_capacity
# cat /sys/devices/platform/smapi/BAT0/voltage
# cat /sys/devices/platform/smapi/BAT0/design_voltage
# cat /sys/devices/platform/smapi/BAT0/manufacturer
# cat /sys/devices/platform/smapi/BAT0/model
# cat /sys/devices/platform/smapi/BAT0/barcoding
# cat /sys/devices/platform/smapi/BAT0/chemistry
# cat /sys/devices/platform/smapi/BAT0/serial
# cat /sys/devices/platform/smapi/BAT0/manufacture_date
# cat /sys/devices/platform/smapi/BAT0/first_use_date
# cat /sys/devices/platform/smapi/BAT0/temperature # in milli-Celsius
# cat /sys/devices/platform/smapi/ac_connected
</pre>

The raw status data is also available, including some fields not listed above (in case you can figure them out):

:{{cmdroot|cat /sys/devices/platform/smapi/BAT0/dump}}

In all of the above, replace <tt>BAT0</tt> with <tt>BAT1</tt> to address the 2nd battery.

Note that the battery status readout conflicts with the stock [[HDAPS|hdaps]] driver, so if you use <tt>hdaps</tt> you will need to load <tt>tp_smapi</tt> using {{cmdroot|1=make load HDAPS=1}} (see [[#Conflict_with_hdaps|Conflict with hdaps]] below).

On [[ACPI]]-enabled systems, most of above information is also available through the files under {{path|/proc/acpi/battery}}. However, the ACPI interface does not include the instantaneous power and cycle count readouts, and does not work well when [[How to use UltraBay batteries|hotswapping UltraBay batteries]].

===Other features===

This controls the "PCI bus power saving" option in the BIOS, and takes effect at the next boot. On a ThinkPad {{T43}} turning this off increases idle power consumption by about 350mW. Out-of-the-box default is 1.
# cat /sys/devices/platform/smapi/enable_pci_power_saving_on_boot
# echo 1 > /sys/devices/platform/smapi/enable_pci_power_saving_on_boot # on
# echo 0 > /sys/devices/platform/smapi/enable_pci_power_saving_on_boot # off

There is also [[sysfs]] attribute for making direct SMAPI requests to the SM BIOS firmware. Don't touch it unless you really know what you're doing. Example:
# echo '211a 100 0 0 > /sys/devices/platform/smapi/smapi_request; cat /sys/devices/platform/smapi/smapi_request
211a 34b b2 0 0 0 'OK'
The 4b" in the 2nd value, converted to decimal is 75: the current charge stop threshold.

===Conflict with <tt>hdaps</tt>===
The extended battery status function conflicts with the [[HDAPS|hdaps]] kernel module (they use the same IO ports). The <tt>tp_smapi</tt> package includes a patch against <tt>hdaps</tt> to make it compatible with <tt>tp_smapi</tt>, and also to fix many problems in the original driver.

To build the patched version, simply append the <tt>HDAPS=1</tt> parameter to the <tt>make</tt> command, for example: {{cmdroot|1=make load HDAPS=1}} (see [[#Installation|Installation]] above).

If you don't do that, you will not be able tp load <tt>tp_smapi</tt> (and its support module <tt>tp_base</tt>) when <tt>hdaps</tt> is loaded, and vice versa. You can use <tt>rmmod</tt> to switch between these modules.

Note that some of the battery status is also visible through ACPI ({{path|/proc/acpi/battery/*}}), independently of <tt>tp_smapi</tt>.

===Model-specific status===

<div style="font-size: 92%">
{| border="1" cellspacing="0" cellpadding="2"
|+<tt>tp_smapi</tt> feature support matrix
|-
! ×
! <tt>start_charge_<br />thresh</tt>
! <tt>stop_charge_<br />thresh</tt>
! <tt>inhbit_charge_<br />minutes</tt>
! <tt>force_discharge</tt>
! battery status files
! <tt>cd_speed</tt><br \><span style="font-size: 90%">(removed)</span>
! Notes
|-
! colspan=8 style="text-align:center;background:#efefef;" |
=====A series=====
|-
! {{A22p}} 2629-USG
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} ||
|-
! {{A30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} ||
|-
! colspan=8 style="text-align:center;background:#efefef;" |
=====G series=====
|-
! {{G41}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||
|-
! colspan=8 style="text-align:center;background:#efefef;" |
=====R series=====
|-
! [[:Category:R31|R31]]
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || No SMAPI BIOS
|-
! {{R40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} ||
|-
! {{R50}}
| {{Cunk}} || {{Cno}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! {{R50p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} ||
|-
! {{R51}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! {{R52}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} ||
|-
! {{R60}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} ||
|-

! colspan=8 style="text-align:center;background:#efefef;" |

=====T series=====
|-
! {{T20}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T22}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || Has SMAPI BIOS but no function is supported. EC LPC3 protocol fails.
|-
! {{T23}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} ||
|-
! {{T30}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} ||
|-
! {{T40}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cyes}} ||
|-
! {{T40p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} ||
|-
! {{T41}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} ||
|-
! {{T41p}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cyes}} ||
|-
! {{T42}}
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||
|-
! {{T42p}} 2373-KUU
| {{Cyes}} || {{Cno}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! {{T43}} 2686-DGU
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||
|-
! {{T43p}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||
|-
! {{T60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cyes}} || {{Cunk}} ||
|-
! colspan=8 style="text-align:center;background:#efefef;" |

=====X series=====
|-
! {{X20}} 2662-31G
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || tp_smapi 0.20
|-
! {{X24}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! {{X31}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! {{X32}}
| {{Cno}} || {{Cno}} || {{Cno}} || {{Cno}} || {{Cyes}} || {{Cunk}} ||
|-
! {{X40}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cyes}} || {{Cunk}} || BIOS v2.03, EC v1.60
|-
! {{X41}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} ||
|-
! {{X60}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! colspan=8 style="text-align:center;background:#efefef;" |

=====Z series=====
|-
! {{Z60m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cunk}} ||
|-
! {{Z60t}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! {{Z61m}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||
|-
! {{Z61t}}
| {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} || {{Cyes}} ||
|}
</div>

Please update the above and report your experience on the [[Talk:tp_smapi|discussion]] page. If the module loads but gives a "<tt>not supported</tt>" or "<tt>not implementeded</tt>" when you try to use some specific file in {{path|/sys/devices/platform/smapi/}}, please report the <tt>dmesg</tt> output and whether the corresponding functionality is available under Windows - maybe your ThinkPad just can't do that.

While at it, you may also want to add your laptop to the [[list of DMI IDs]].

[[Category:Drivers]] [[Category:Patches]]

===Tools using this driver===

The driver's interface can be accessed directly through the files under {{path|/sys/devices/platform/smapi}}, or via the following tools:
* [[KThinkBat]] - display battery status on the KDE <tt>kicker</tt> panel.
* [[gkrellm-ThinkBat]] - battery status plugin for Gkrellm2