ThinkWiki - User contributions [en]

How to reduce power consumption

2008-05-04T10:29:22Z

Aumuell: /* USB Subsystem */ move pcmcia to its own section

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, use SATA AN, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states
* Make use of every hardware devices availables power saving features (AHCI ALPM, USB autosuspend, Alsa and Wireless powersaving modes, HPET timers, ...)

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power hungry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

See also [[#Misbehaving Userland]].

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed ''enable'' them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power hungry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like [[dynticks]]).
Later, 2.6.24-rc2 brought a lot of other power efficiency improvements.
If it's not already on your distribution and you value power efficiency,
you may think about compiling a recent kernel yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_HPET_TIMER
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=3
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
CONFIG_INOTIFY

# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE and CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

=== Kernel boot and module loading options ===
If you have an Intel chipset > ICH3 (cf. lspci output), as in most modern Thinpads, you should
be using the integrated HPET timer (saves about 30 CPU wake ups per second). To see if
hpet is enabled on your laptop :

<code>
grep hpet /proc/timer_list
</code>

If this does not display "Clock Event Device: hpet", then add

<code>
hpet=force
</code>

to your kernel boot options (usualy in /boot/grub/menu.lst or lilo.conf).
Note that "hpet=force" is only available by default in 2.6.24-rc2 and above
(or as a separated patch for 2.6.22 and 2.6.23, see below).

===Useful Patches===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies). Those are
fully merged in 2.6.24-rc1 vanilla kernel.
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). Also from
Accardi, SATA Asynchronous Notification (SATA AN), alows SATA link to notify
media insertions (thus avoid hal polling the cdrom). Those patches were merged
in 2.6.24-rc2 kernel (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run a 2.6.24-rc2 or more kernel, or applied Kirsten patchset, have an Intel
AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm (beware
that "-B 1" may reduce your drive lifetime, if you have lot of intermittent
disk activity causing lots of heads load/unloads: so reduce I/O activity first,
as explained above, in order to get longer disks idling periods).
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
<code>
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

On Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend.

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive (except if you have a kernel >= 2.6.24, hal >= 0.5.10,
and SATA AN compatible devices). If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider suspending it when running on battery. Some moderns SATA buses and drivers supports a notification mechanism (SATA AN - Asynchronous Events Notifications) that obsolete the need for polling on modern hardware; support for this feature had been merged in Linux 2.6.24-rc1 and HAL 0.5.10.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

The very recent, but xorg standard way to control backlight from CLI is
using xbacklight. ie. to set backlight at half the brightness:

<code>
xbacklight -set 50
</code>

You should configure the DPMS to shutdown the screen when idle (rather than
displaying a fancy but power consuming screensaver). ie. to turn off the
display after 5mn of idling:

<code>
xset +dpms
xset dpms 0 0 300
</code>

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.
See the section above about how to enable dpms driven display power saving.

On recent xrandr/xorg versions, you can disable the TV output (or any other detected
as connected but not used outputs) when you're not using it: it's known to consume power.

<code>
xrandr # see all displays listed here, but that you don't actually use and disable them.
xrandr --output TV -off # for instance (if "xrandr" above listed a connected output named "TV" that you don't use)
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuratoin.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add this in the kernel boot options (ie. in grub's menu.lst):

<code>
usbcore.autosuspend=1
</code>

or at runtime, per device, with:

<code>
for i in /sys/bus/usb/devices/%s/power/autosuspend; do echo 1 > $i; done
</code>

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any device needing USB 1.1 (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totally avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

==PCMCIA/CardBus==
Same for PCMCIA/CardBus. Some users experiences interrupts clouds (sometime up to
several thousands interrupts/second) causing CPU wakeups, thus totally preventing
the CPU to reach lower C-states.
If you don't use PCMCIA, you may disable it the same way (unloading seems insufficient
to restore the system properly, you have to boot without it):

<code>
echo "blacklist pcmcia" >> /etc/modprobe.d/blacklist
echo "blacklist yenta_socket" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
Wireless network consume a lot of power.
To save power, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/devices/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

For drivers using the new Wi-Fi kernel framework (mac80211/cfg80211),
the canonical way to do this is now:

<code>
for i in /sys/bus/pci/devices/*/power_level ; do echo 5 > $i ; done
</code>

Most drivers, like ipw2200, that don't use the new mac80211 framework place the
interfaces in aggressive scanning mode when they are not associated with any
Access Point, even when the interface is down (more info about this on Intel's
[http://www.lesswatts.org/tips/wireless.php LessWatts] website).
This behavior consumes a lot of power, even more than when the interface
is plain active and in use. But this can disabled at module's load time :

<code>
rmmod ipw2200
modprobe ipw2200 associate=0
</code>

You can fix this setting by placing the following in /etc/modprobe.d/options
(Debian/Ubuntu) or in /etc/modprobe.conf (Red Hat/Fedora):

<code>
options ipw2200 associate=0
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save a lot of power (~1W) on most network workloads. This also reduces components temperature (e.g., [[Thermal Sensors|thermal sensor]] 0xC0 on the {{T43}} cools down by 5 degree between 1000Mbps and 100Mbps, and another 1 degree for 10Mbps).

<code>
ethtool -s eth0 autoneg off speed 100
</code>

Note, however, that if the network device on the other side has auto-negotiation enabled (which is very common) and you turn auto-negotiation off, the other side will assume half-duplex mode and you will experience a significant loss of performance.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to, in order to provide their intented functionality. Think twice before filling bugs about this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* Intel's [http://www.lesswatts.org/ LessWatts] "''Saving power on Linux''" website
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[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:T60p]] [[Category:T61]] [[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:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2008-05-04T10:26:40Z

Aumuell: /* Hard Drives */

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, use SATA AN, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states
* Make use of every hardware devices availables power saving features (AHCI ALPM, USB autosuspend, Alsa and Wireless powersaving modes, HPET timers, ...)

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power hungry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

See also [[#Misbehaving Userland]].

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed ''enable'' them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power hungry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like [[dynticks]]).
Later, 2.6.24-rc2 brought a lot of other power efficiency improvements.
If it's not already on your distribution and you value power efficiency,
you may think about compiling a recent kernel yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_HPET_TIMER
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=3
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
CONFIG_INOTIFY

# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE and CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

=== Kernel boot and module loading options ===
If you have an Intel chipset > ICH3 (cf. lspci output), as in most modern Thinpads, you should
be using the integrated HPET timer (saves about 30 CPU wake ups per second). To see if
hpet is enabled on your laptop :

<code>
grep hpet /proc/timer_list
</code>

If this does not display "Clock Event Device: hpet", then add

<code>
hpet=force
</code>

to your kernel boot options (usualy in /boot/grub/menu.lst or lilo.conf).
Note that "hpet=force" is only available by default in 2.6.24-rc2 and above
(or as a separated patch for 2.6.22 and 2.6.23, see below).

===Useful Patches===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies). Those are
fully merged in 2.6.24-rc1 vanilla kernel.
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). Also from
Accardi, SATA Asynchronous Notification (SATA AN), alows SATA link to notify
media insertions (thus avoid hal polling the cdrom). Those patches were merged
in 2.6.24-rc2 kernel (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run a 2.6.24-rc2 or more kernel, or applied Kirsten patchset, have an Intel
AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm (beware
that "-B 1" may reduce your drive lifetime, if you have lot of intermittent
disk activity causing lots of heads load/unloads: so reduce I/O activity first,
as explained above, in order to get longer disks idling periods).
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
<code>
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

On Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend.

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive (except if you have a kernel >= 2.6.24, hal >= 0.5.10,
and SATA AN compatible devices). If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider suspending it when running on battery. Some moderns SATA buses and drivers supports a notification mechanism (SATA AN - Asynchronous Events Notifications) that obsolete the need for polling on modern hardware; support for this feature had been merged in Linux 2.6.24-rc1 and HAL 0.5.10.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

The very recent, but xorg standard way to control backlight from CLI is
using xbacklight. ie. to set backlight at half the brightness:

<code>
xbacklight -set 50
</code>

You should configure the DPMS to shutdown the screen when idle (rather than
displaying a fancy but power consuming screensaver). ie. to turn off the
display after 5mn of idling:

<code>
xset +dpms
xset dpms 0 0 300
</code>

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.
See the section above about how to enable dpms driven display power saving.

On recent xrandr/xorg versions, you can disable the TV output (or any other detected
as connected but not used outputs) when you're not using it: it's known to consume power.

<code>
xrandr # see all displays listed here, but that you don't actually use and disable them.
xrandr --output TV -off # for instance (if "xrandr" above listed a connected output named "TV" that you don't use)
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuratoin.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add this in the kernel boot options (ie. in grub's menu.lst):

<code>
usbcore.autosuspend=1
</code>

or at runtime, per device, with:

<code>
for i in /sys/bus/usb/devices/%s/power/autosuspend; do echo 1 > $i; done
</code>

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any device needing USB 1.1 (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totally avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

Same for PCMCIA/Cardbus. Some users experiences interrupts clouds (sometime up to
several thousands interrupts/second) causing CPU wakeups, thus totally preventing
the CPU to reach lower C-states.
If you don't use PCMCIA, you may disable it the same way (unloading seems insufficient
to restore the system properly, you have to boot without it):

<code>
echo "blacklist pcmcia" >> /etc/modprobe.d/blacklist
echo "blacklist yenta_socket" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
Wireless network consume a lot of power.
To save power, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/devices/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

For drivers using the new Wi-Fi kernel framework (mac80211/cfg80211),
the canonical way to do this is now:

<code>
for i in /sys/bus/pci/devices/*/power_level ; do echo 5 > $i ; done
</code>

Most drivers, like ipw2200, that don't use the new mac80211 framework place the
interfaces in aggressive scanning mode when they are not associated with any
Access Point, even when the interface is down (more info about this on Intel's
[http://www.lesswatts.org/tips/wireless.php LessWatts] website).
This behavior consumes a lot of power, even more than when the interface
is plain active and in use. But this can disabled at module's load time :

<code>
rmmod ipw2200
modprobe ipw2200 associate=0
</code>

You can fix this setting by placing the following in /etc/modprobe.d/options
(Debian/Ubuntu) or in /etc/modprobe.conf (Red Hat/Fedora):

<code>
options ipw2200 associate=0
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save a lot of power (~1W) on most network workloads. This also reduces components temperature (e.g., [[Thermal Sensors|thermal sensor]] 0xC0 on the {{T43}} cools down by 5 degree between 1000Mbps and 100Mbps, and another 1 degree for 10Mbps).

<code>
ethtool -s eth0 autoneg off speed 100
</code>

Note, however, that if the network device on the other side has auto-negotiation enabled (which is very common) and you turn auto-negotiation off, the other side will assume half-duplex mode and you will experience a significant loss of performance.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to, in order to provide their intented functionality. Think twice before filling bugs about this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* Intel's [http://www.lesswatts.org/ LessWatts] "''Saving power on Linux''" website
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[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:T60p]] [[Category:T61]] [[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:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-05-04T10:01:20Z

Aumuell: /* Items that work out of the box */

== Features ==
=== Open Source Intel Wifi Driver ===
Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===
Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll. To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

=== WiFi LED ===

To active WiFi LED, install backported IWL4965 driver

sudo apt-get install linux-backports-modules-hardy

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested.

'''Wireless WAN:''' Cingular/AT&T card tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' tested

'''Webcam''' tested with cheese and skype.

'''Headphones''' out of the box

'''Microphone''' just needs to be activated, see section above

'''Keyboard Shortcuts:''' most work out of the box, some need to be activated, see section above

== Items that don't work ==

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver.

patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

See [[#WiFi_LED|above]] for the package containing the fixed driver.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-05-04T09:58:30Z

Aumuell: /* Wireless activity LED */

== Features ==
=== Open Source Intel Wifi Driver ===
Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===
Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll. To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

=== WiFi LED ===

To active WiFi LED, install backported IWL4965 driver

sudo apt-get install linux-backports-modules-hardy

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' tested

'''Webcam''' tested with cheese and skype.

'''Headphones''' out of the box

'''Microphone''' just needs to be activated, see section above

'''Keyboard Shortcuts:''' most work out of the box, some need to be activated, see section above

== Items that don't work ==

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver.

patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

See [[#WiFi_LED|above]] for the package containing the fixed driver.

[[Category: Ubuntu 8.04]]

Installing Ubuntu 8.04 (Hardy Heron) on a ThinkPad T61

2008-05-04T09:57:23Z

Aumuell: /* Wireless activity LED */

== Features ==
=== Open Source Intel Wifi Driver ===
Intel has created a new Linux Wifi driver project for Intel Wireless cards, "[[Iwlwifi]]". This driver is Open Source and no longer requires the Intel daemon to run in addition. This project will support the [[:Category:T61 | T61]]'s Wifi [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter | Intel 3945ABG network adapter]] and [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter| Intel 4965AGN network adapter]].

An automatic migration will occur when upgrading from [[Installing Ubuntu 7.10 (Gutsy Gibbon) on a ThinkPad T61|Ubuntu 7.10]] to Ubuntu 8.04. However, there is a caveat to be aware of:
* The new driver wants to name the interface wlan0 (by default -- you can rename it to anything you want), and requires a different entry in {{path|/etc/udev/rules.d/70-persistent-net.rules}}, which handles the naming of interfaces. Simply edit this file and delete your old entry for the ipw3945 driver, then unload/reload the new driver, or simply reboot. A new entry will automatically be created that is appropriate for the new driver. Here's an example of the lines to delete:
<pre>
# PCI device 0x8086:0x4227 (ipw3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1b:77:a4:0e:2f", NAME="eth1"
</pre>

If you need to perform a manual migration, the Ubuntu Help Community has written some [https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy documentation] that will make this very easy to do.

=== Compiz and XV Playback on Intel GM965/GL960 ===

With Ubuntu 7.10 (Gutsy Gibbon) you currently have to choose between using Compiz and working video playback using XV. On 8.04 (Hardy Heron) alpha 5 you can play videos using XV under compiz, it works right out of the box using the Live-CD.

=== Suspend with Nv140m ===
Suspend may not work even after editing acpi-support. Enable bluetooth (Fn+F5) may result in a successful suspend. NOTE: that although the wifi led does not change when Fn+F5 is used, the wifi is still toggled by this key.

'''Hal "S3 BIOS" parameter issue!'''

After doing the changes to the /etc/default/acpi-support file (described [http://www.thinkwiki.org/wiki/Installing_Ubuntu_7.10_(Gutsy_Gibbon)_on_a_ThinkPad_T61#How_to_Suspend_with_nVidia_140m.2F570m here]), I for one, managed to have '''stable''' suspend support by creating a new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
</match>
</device>
</deviceinfo>
</pre>
{{NOTE|The problem (after reading the HAL and pm-utils documentations) is the fact that (as far as I can tell) the T61 Lenovo doesn't allow the S3 BIOS to be called *during* suspend/resume, which HAL seems to do by default (who knows, maybe there are T61s out there that do work with this default)!

This did not seem to be necessary for previous versions of Ubuntu. Also note that I have an NVIDIA card so I have no idea what to do for Intel versions.The change should also be resistant to HAL and pm-utils upgrades.}}

'''Still no suspend with nvs140m? Got Modell 6460?'''

Fix above didn't work for me on a 15.4 wide T61 Modell 6460 with nv140m. Bios is updated to 2.14 but didn't change anything, except the usb bug is fix. Suspend seems to work fine, but resume gives me a black screen (backlight off - no reaction to brightness up) and I can hear 2 beeps. Most of the time I can reboot with ctrl+alt+delete but the screen stays dark until bios.

follow the instructions above but create the new file called: '''/etc/hal/fdi/information/lenovo.fdi''' with the following contents instead:
<pre>
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
<merge key="power_management.quirk.s3_mode" type="bool">true</merge>
<merge key="power_management.quirk.s3_bios" type="bool">false</merge>
<merge key="power_management.quirk.save_pci" type="bool">true</merge>
</match>
</device>
</deviceinfo>
</pre>

Also you want to set the following parameter in

{{path|/etc/default/acpi-support}}
<pre>
SAVE_VIDEO_PCI_STATE=true
</pre>

{{NOTE|This works for me with mode 6460, except for one problem: You may get a white screen in xorg after resume when using compiz. If you don't have a 6460 with nvidia this file may break things for you because it doesn't care about the modell and sets the parameter for any lenovo product}}
{{HELP|Anyone with more knowledge of hal and acpi-support is welcome to clean this up. I also don't know why this setting can be done via hal and in acpi-support}}

[[Category: T61]]

=== TrackPoint ===
The [[TrackPoint]] works out of the box, but does not scroll. To enable using the middle mouse button to scroll, replace the "Configured Mouse" section in
{{path|/etc/X11/xorg.conf}} with the following:
<pre>
Section "InputDevice"
Identifier "Trackpoint"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
EndSection
</pre>

=== Audio ===

Works great out of the box, just the microphone has to be activated, it is considered a generic capture source and is muted by default.

To unmute the microphone:

*Right Click on the volume icon next to the clock and click on "Open Volume Control"

*Click Edit -> Preferences. A list of devices will be displayed, you should check the following (Do not uncheck any existing items):

Input Source
Capture

*Click Close and there should be two additional tabs "Recording" and "Options". -

*Click Recording and click on the microphone under the Capture slider so that it no longer has a red line through it, and put the slider up as it may be deactivated.

*Click Options and under capture source select internal mic.

To test your mic using Sound Recorder select Capture as the sound source.

This solution has been tested with Sound Recorder and Skype.

To get the volume controls working:

*add the following line to /etc/modprobe.d/alsa-base, then reboot

options snd-hda-intel index=0 model=thinkpad

=== Multimedia Keys ===

Most Multimedia Keys work out of the box, just the play, forward and stop buttons need to be adjusted, therefore, press alt + F2 and type in gnome-keybinding-properties. Then everything works as followed:

* Fn-PgUp activates/deactivates the thinklight
* Fn-Up will trigger stop on a media player
* Fn-Down will toggle pause and play on a media player
* Fn-Left/Right go to prev/next tracks on a media player
* Fn-F2 properly locks the screen
* Fn-F3 shows remaining battery >>does not work on all machines<<
* Fn-F4 suspends (to ram)
* Fn-F9 ejects cds
* Fn-F12 hibernates (to disk)
* PrtSc opens the screenshot dialog

=== WiFi LED ===

To active WiFi LED, install backported IWL4965 driver

sudo apt-get install linux-backports-modules-hardy

== Items that work out of the box ==

'''Intel Video:''' 2D and 3D acceleration works

'''Wireless:''' Intel cards tested.

'''Network Card''' Intel 10/100/1000 tested

'''Wireless switch''' tested

'''Webcam''' tested with cheese and skype.

'''Headphones''' out of the box

'''Microphone''' just needs to be activated, see section above

'''Keyboard Shortcuts:''' most work out of the box, some need to be activated, see section above

== Items that don't work ==

=== Wireless activity LED ===

The LED is not implemented at least in the IWL4965 driver.

patch posted in this [http://bughost.org/bugzilla/show_bug.cgi?id=1209 thread] works for me on R61 with IWL4965 card.

See [[#Wifi_LED|above]] for the package containing the fixed driver.

[[Category: Ubuntu 8.04]]

Sierra Wireless HSDPA WWAN

2008-05-01T18:43:26Z

Aumuell: don´t mix information on mc8775 with other devices

North American ThinkPads have the Sierra Wireless MC8765 card.
European ThinkPads have the Sierra Wireless MC8755 card.

The only difference between the two is the frequency at which they support WCDMA. The MC8765 supports WCDMA800 and WCDMA1900, while the MC8755 supports only WCDMA2100.

Both models support GPRS and EDGE at 850, 900, 1800, and 1900MHz.

Both models are category 11/12 UMTS devices, meaning they support up to 1.8Mbps downstream using QPSK modulation. They do not support 16QAM modulation.

According to the T61 hardware maintenance manual, the T61 uses the MC8775, which is quad band EDGE (850/900/1800/1900) and tri band HSDPA (850/1900/2100).

=== Sierra Wireless MC8765 1199:6805 support ===

The model 2613-ETU T60p (and possibly others) has one of these cards which the linux <tt>sierra</tt> device driver does not automatically recognize (as of kernel 2.6.24.4, at least). While it's the same device in every other respect the PCI id isn't standard, presumably because IBM/Lenovo use their own PCI ids to restrict the use of arbitrary 3rd party cards. Using the 2.6.23+ hotplug infrastructure, we can cause the driver to claim it anyway and register serial devices in <tt>/dev</tt> for it.

To do this using the '''udev''' subsystem, edit or create the file <tt>/etc/udev/rules.d/98-local.rules</tt> file and add:

<code><pre>######
## Sierra Wireless MC8765 1199:6805 support
##
## My model 2613-ETU T60p contains a WAN device which the linux sierra
## device driver does not automatically recognize. Using the 2.6.23+
## hotplug infrastructure, we can cause the driver to claim it.
##
## The 3-port interface works with this device, but there's not much point
## in registering the 2nd and 3rd since they are used for control purposes
## that we don't currently use under linux.
######

#SUBSYSTEM=="drivers", \
# ACTION=="add", \
# ENV{DEVPATH}=="/bus/usb-serial/drivers/sierra3", \
# RUN+="/bin/sh -c 'echo 1199 6805 > /sys/bus/usb-serial/drivers/sierra3/new_id'"

SUBSYSTEM=="drivers", \
ACTION=="add", \
ENV{DEVPATH}=="/bus/usb-serial/drivers/sierra1", \
RUN+="/bin/sh -c 'echo 1199 6805 > /sys/bus/usb-serial/drivers/sierra1/new_id'"

# TODO: fix this:
# This isn't quite right for sierra3, since it will always symlink
# wan_modem to the last created device; in the 3-port case that's not the
# device we actually want to refer to for modem interaction (we want the
# first device). We could limit this using ENV{PHYSDEVDRIVER}="sierra1",
# but udev warns that this is deprecated and will be removed from a future
# kernel.
KERNEL=="ttyUSB*", \
SYSFS{manufacturer}=="Sierra Wireless*", \
SYMLINK+="wan_modem", \
GROUP="uucp", \
MODE="0666"
</pre></code>

NVidia Quadro FX 570M

2008-03-30T12:08:57Z

Aumuell:

Based on nVidia GeForce Go 8600M/8600GT.
This [http://forum.thinkpads.com/viewtopic.php?t=48287 forum thread] seems to indicate that the 128 MB version in the 14.1" T61p's only has half the memory bandwidth [http://www.nvidia.com/page/quadrofx_go.html advertised] by NVidia for the 570M.

Tp smapi

2006-08-04T08:30:05Z

Aumuell: /* X series: update X60/X60s status */

{| 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's [[SMAPI support for Linux|SMAPI]] functionality via a <tt>sysfs</tt> interface. Currently, the implemented functionality is control of battery charging, extended battery status and control of CD/DVD speed (disabled by default).

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
*Optical drive speed control (disabled by default)

===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.25.tgz}}
:{{cmdroot|cd tp_smapi-0.25}}
:{{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_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/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]].

===Optical drive control features===

To control the speed of the optical drive:
:{{cmdroot|echo 0 > /sys/devices/platform/smapi/cd_speed # slow}}
:{{cmdroot|echo 1 > /sys/devices/platform/smapi/cd_speed # medium}}
:{{cmdroot|echo 2 > /sys/devices/platform/smapi/cd_speed # fast}}
:{{cmdroot|cat /sys/devices/platform/smapi/cd_speed}}

=====Enabling this feature=====
Changing the drive speed when a disc is being accessed will hang your computer. This feature is thus '''disabled by default''', but can be enabled using by adding <tt>#define PROVIDE_CD_SPEED</tt> at the top of <tt>tp_smapi.c</tt>. The safe way to set the drive speed is using <tt>hdparm -E num</tt> or <tt>eject -x num</tt> for CD-ROM, and <tt>speedcontrol -x num</tt> (sourcecode [http://safari.iki.fi/speedcontrol.c here]) for DVD. For kernels older than 2.6.15, this may require the [[Problems_with_SATA_and_Linux#No_SMART_support libata pass-through|libata pass-through patch]].

===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.
echo 'BX=2116 CX=100 DI=0 SI=0' > /sys/devices/platform/smapi/smapi_request; cat /sys/devices/platform/smapi/smapi_request
BX=2116 CX=327 DX=b2 DI=0 SI=0 ret=0 msg=OK

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

Some new ThinkPad models are not recognized by the built-in whitelist, so you will need to add the <tt>force=1</tt> module parameter to <tt>hdaps</tt> (this option is added by the <tt>tp_smapi</tt> patch to <tt>hdaps</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_ thresh</tt>
! <tt>stop_charge_ thresh</tt>
! <tt>inhbit_charge_ minutes</tt>
! <tt>force_discharge</tt>
! battery status files
! <tt>cd_speed</tt> (see [[#Enabling_this_feature|note]] above)
! 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}} ||
|-
! 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=====
|-
! {{Z60t}}
| {{Cyes}} || {{Cyes}} || {{Cunk}} || {{Cunk}} || {{Cyes}} || {{Cunk}} ||
|-
! {{Z61m}}
| {{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

List of DMI IDs

2006-07-24T14:38:52Z

Aumuell: /* DMI ID database */

This page maintains a database of [http://en.wikipedia.org/wiki/Desktop_Management_Interface DMI] information which can be used to identify ThinkPad models. It is intended as an aid for driver development.

==DMI ID database==

{| border="1" cellspacing="0" cellpadding="2"
|-
! Model
! <tt>system- manufa cturer</tt>
! <tt>system- product-name</tt>
! <tt>system- version</tt>
! <tt>baseboard- manufa cturer</tt>
! <tt>baseboard- product-name</tt>
! <tt>baseboard- version</tt>
! <tt>chassis- manufa cturer</tt>
! <tt>chassis- version</tt>
! <tt>bios- vendor</tt>
! <tt>bios- version</tt>
! <tt>bios- release- date</tt>
! Embedded controller
! Notes
|-
! colspan=14 style="text-align:center;background:#efefef;" | R series
|-
| {{R52}} 1846AQG
|| IBM || 1846AQG || ThinkPad H || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki> ||
|
|-
| {{R52}} 1846AQG
|| IBM || 1846AQG || ThinkPad R52 || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki> ||
|
|-
| {{R51}} 18299MG
|| IBM || 18299MG || ThinkPad R51 || IBM || 18299MG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/ 27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | T series
|-
| {{T40}} 2378D2U
|| IBM || 2378D2U || ThinkPad T40 || IBM || 2378D2U || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki></nowiki> ||
|-
| {{T41}} 23732FG
|| IBM || 23732FG || ThinkPad T41 || IBM || 23732FG || Not Available || IBM || Not Available || IBM || 1RET84WW (2.11 ) || 10/30/2003
|| <nowiki></nowiki> ||
|-
| {{T43}} 2686DGU
|| IBM || 2686DGU || ThinkPad T43 || IBM || 2686DGU || Not Available || IBM || Not Available || IBM || 1YET62WW (1.27 ) || 05/18/2006
|| String 1: IBM ThinkPad Embedded Controller -[1YHT29WW-1.06 ]- ||
|-
| {{T60p}} 200783U
|| LENOVO || 200783U || ThinkPad T60p || LENOVO || 200783U || Not Available || LENOVO || Not Available || LENOVO || 79ET60WW (1.05a) || 04/18/2006 || <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT43WW-1.02 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | X series
|-
| {{X60s}} 1702-55G
|| LENOVO || 170255G || ThinkPad X60s || LENOVO || 170255G || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki> ||
|}

==Adding entries==

Edit the [[#DMI_ID_database|DMI ID database]] section above. Identify your series (or add a new one), and add an entry of the following form:
:<tt>!-</tt>
:<tt>| </tt>description of your model
:data line 1
:data line 2

where the two data lines are genereated by the following <tt>bash</tt> command:

<pre>
for X in system-{manufacturer,product-name,version} \
baseboard-{manufacturer,product-name,version} \
chassis-{manufacturer,version} bios-{vendor,version,release-date}; do \
echo -n "|| `sudo /usr/sbin/dmidecode -s $X` "; done; echo; \
echo "|| <nowiki><nowiki>`sudo /usr/sbin/dmidecode | grep -i 'embedded controller'`</nowiki></nowiki> ||"
</pre>

==Software using ThinkPad DMI IDs==
* [[HDAPS]] driver whitelist
* [[tp_smapi]] driver whitelist

List of DMI IDs

2006-07-24T14:33:19Z

Aumuell: /* DMI ID database: add X series */

This page maintains a database of [http://en.wikipedia.org/wiki/Desktop_Management_Interface DMI] information which can be used to identify ThinkPad models. It is intended as an aid for driver development.

==DMI ID database==

{| border="1" cellspacing="0" cellpadding="2"
|-
! Model
! <tt>system- manufa cturer</tt>
! <tt>system- product-name</tt>
! <tt>system- version</tt>
! <tt>baseboard- manufa cturer</tt>
! <tt>baseboard- product-name</tt>
! <tt>baseboard- version</tt>
! <tt>chassis- manufa cturer</tt>
! <tt>chassis- version</tt>
! <tt>bios- vendor</tt>
! <tt>bios- version</tt>
! <tt>bios- release- date</tt>
! Embedded controller
! Notes
|-
! colspan=14 style="text-align:center;background:#efefef;" | R series
|-
| {{R52}} 1846AQG
|| IBM || 1846AQG || ThinkPad H || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki> ||
|
|-
| {{R52}} 1846AQG
|| IBM || 1846AQG || ThinkPad R52 || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki> ||
|
|-
| {{R51}} 18299MG
|| IBM || 18299MG || ThinkPad R51 || IBM || 18299MG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/ 27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | T series
|-
| {{T40}} 2378D2U
|| IBM || 2378D2U || ThinkPad T40 || IBM || 2378D2U || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki></nowiki> ||
|-
| {{T41}} 23732FG
|| IBM || 23732FG || ThinkPad T41 || IBM || 23732FG || Not Available || IBM || Not Available || IBM || 1RET84WW (2.11 ) || 10/30/2003
|| <nowiki></nowiki> ||
|-
| {{T43}} 2686DGU
|| IBM || 2686DGU || ThinkPad T43 || IBM || 2686DGU || Not Available || IBM || Not Available || IBM || 1YET62WW (1.27 ) || 05/18/2006
|| String 1: IBM ThinkPad Embedded Controller -[1YHT29WW-1.06 ]- ||
|-
| {{T60p}} 200783U
|| LENOVO || 200783U || ThinkPad T60p || LENOVO || 200783U || Not Available || LENOVO || Not Available || LENOVO || 79ET60WW (1.05a) || 04/18/2006 || <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT43WW-1.02 ]-</nowiki> ||
|-
! colspan=14 style="text-align:center;background:#efefef;" | X series

|}

==Adding entries==

Edit the [[#DMI_ID_database|DMI ID database]] section above. Identify your series (or add a new one), and add an entry of the following form:
:<tt>!-</tt>
:<tt>| </tt>description of your model
:data line 1
:data line 2

where the two data lines are genereated by the following <tt>bash</tt> command:

<pre>
for X in system-{manufacturer,product-name,version} \
baseboard-{manufacturer,product-name,version} \
chassis-{manufacturer,version} bios-{vendor,version,release-date}; do \
echo -n "|| `sudo /usr/sbin/dmidecode -s $X` "; done; echo; \
echo "|| <nowiki><nowiki>`sudo /usr/sbin/dmidecode | grep -i 'embedded controller'`</nowiki></nowiki> ||"
</pre>

==Software using ThinkPad DMI IDs==
* [[HDAPS]] driver whitelist
* [[tp_smapi]] driver whitelist

Talk:Installing Ubuntu 6.06 Flight 6 on a ThinkPad X60s

2006-06-12T00:38:36Z

Aumuell:

In the version I downloaded of the Ubuntu 6.06 (don't know how to see what release it is more in detail, but I downloaded it the 01/06/2006) The ipw3945 driver is already included. The Wifi work out of the box.
--[[schlum]]

Have you tried undervolting to combat your noise issues?

--[[igorr]]

Switching the SATA controller from "compatibility" to "AHCI" in the BIOS settings (and thus using the ahci instead of the ata_piix driver) made suspend to ram work for me with the 2.6.15-23-686 kernel. However, it seems to draw about 1 - 2 W more power when in this mode.

3D works fine: glxgears -printfps
5057 frames in 5.0 seconds = 1011.230 FPS

Talk:Installing Ubuntu 6.06 Flight 6 on a ThinkPad X60s

2006-06-07T16:32:03Z

Aumuell: suspend to ram with ahci works

Talk:Problem with high pitch noises

2006-06-07T16:27:41Z

Aumuell: /* Discussion of "Limit ACPI CPU power states" */

==Discussion of "Limit ACPI CPU power states"==

*Stefan Baums: I raised this issue on the linux-kernel mailing list, and from there it was forwarded to the acpi-devel mailing list. See the discussion [http://sourceforge.net/mailarchive/forum.php?thread_id=7593600&forum_id=6102 here] and [http://sourceforge.net/mailarchive/forum.php?thread_id=7599419&forum_id=6102 here]. Results: The <code>idle=halt</code> kernel parameter disables ACPI C-state switching entirely (i.e., locks the processor in C1). It is preferable to pass to the ACPI processor component the option {{bootparm|max_cstate|2}}, which only disables the problematic states C3 and C4. The only way to accomplish this that worked for me was to compile the ACPI processor component permanently into the kernel (<tt>CONFIG_ACPI_PROCESSOR=y</tt>) and then enable it by adding the parameter {{bootparm|processor.max_cstate|2}} to the boot command line (and of course removing {{bootparm|idle|halt}}). Now the computer switches back and forth between C1 and C2, but avoids the noise-inducing C3 and C4, and frequency scaling works regardless. [Update: I now use the default Ubuntu kernel, with <code>processor</code> as a module, and disabled C3 and C4 by modifying {{path|/etc/init.d/acpid}} as explained on the article page.] ({{X41}})
*Simon Eggert: The {{bootparm|processor.max_cstate|3}} option worked for me on my {{T43p}} thanks.
* Adding <code>options processor max_cstate=2</code> in {{path|/etc/modprobe.conf}} (or {{path|/etc/modprobe.conf.local}} on my SuSE 9.3 installation) prevents the CPU permanently from entering into C3 and higher states. ({{X40}}, {{R52}})
* [[User:Thinker|Thinker]]: On one {{T43}}, this worked even with {{bootparm|processor.max_cstate|3}}. That is, C3 was silent and only C4 produced whining (at both HZ=100 and HZ=250).
* [[User:Thinker|Thinker]]: These options affect power consumption when the CPU is idle. Here are the figures on one 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)

* [[User:Gsmenden|gsmenden]]: On a debian system, no modprobe.conf, can use modutils to add max_cstate line. On my t43p the noise only occcurs when on battery power after suspend / resume cycle. It is definitely is still present when hard disk is spun down. Nevertheless there may be multiple sources of this (quite annoying) sound.

* [[User:Gsmenden|gsmenden]]: Update - if you don't want to use modutils, can manually load it on bootup by adding "processor max_cstate=3" in /etc/modules on a debian system. Noise still present upon resume though on my t43p though :(

* [[User:Nephiel|Nephiel]]: My {{Z60m}} also had the "screeching when on battery" problem with Ubuntu 5.10. Editing {{path|/etc/init.d/acpid}} as described worked. It needed C2: C3 was quieter but still noticeable.

* Michael Kiausch: On my {{x41}} the noise disappears on unloading uhci-hcd module (no matter which c-state), unfortunately this is not an option as this disables usb. ''edit:'' only works if HZ=100

* Just tested M. Kiausch's suggestion on a {{t43}}. The high-pitch noise is gone (HZ=100, cstate=4), but there is a low-pitch noise with about the same "beat". It is much less audible though, and I really had to keep an ear close to the exhaust to hear it. But the noise is still there.

* Michael Kiausch: You're right, same low-pitch-noise on {{x41}}, but it is really hard to hear. Does anyone know in which way the usb-uhci is related to the c-states?

* [[User:Slurm|Slurm]] The high-pitch noise occurs on my x41 only if i'm on battery and my mouse(usb, optical) is plugged in.

* Martin Aumueller: Upgrading the BIOS on my X60s from 1.04 to 1.06 solved the noise problem for me, however it seems to draw about 500 mW more power with the newer BIOS.

== Harddisk related noise ==

on my T43p the noise definitely comes from the harddisk and can be heard both in Windows and Linux. Only at boot time, before the harddisk spins up, or when I manually spin down the harddisk with

{{cmdroot|hdparm -y /dev/sda}}

the system is silent.

Hi, I don't have an IBM but Dell Latitude D410 laptop. My problem is that not only the high pitch noise is produced but the processor itself comes very busy when speedstep-centrino module is loaded. On karamba monitor (not very reliable but I can feel the difference) I get 50-100% processor occupation. Right now I'm recompiling my 2.6.14 kernel to 100Hz timer freq. (was 250) and we'll see what happens.

If you have any suggestions don't hestite since I practically can't use speedsteping because battery discharges rapidly

Cheers
Wojtek

== Noise from Wlan ==
Hi, I have a high frequency noise from my wifi modul: It occurs only with linux, only in battery mode. Disabling wifi via hardware switch disables the noise! 
Any Ideas? 
Florian 
EDIT: Giving the cpus something to calc disables the noise, too! 
EDIT2: "Turn off CPU power saving in in BIOS" seems (!!) to solve the problem! But where is the connection to the wlan?