ThinkWiki - User contributions [en]

WWAN Slot

2022-04-29T16:35:32Z

WilliamPoetra: â†Created page with '===Overview=== Most ThinkPads have a WWAN slot. In older ThinkPads, the WWAN slot is a mini-PCI or mini-PCIe slot. In newer ThinkPads, the WWAN slot is a 2242 M.2 slot...'

===Overview===

Most ThinkPads have a WWAN slot. In older ThinkPads, the WWAN slot is a mini-PCI or mini-PCIe slot. In newer ThinkPads, the WWAN slot is a 2242 M.2 slot.

On some models, the WWAN slot has PCIe lines, on others only USB is available. This page aims to clear things up and provide a central source of truth.

===SSD in WWAN Slot===

Some models can accept an SSD installed into the WWAN slot.



These models only have USB signals on the WWAN slot:
* {{X60}}, {{X60s}}

These models may be able to accept a mini-PCIe SSD in the WWAN slot: (need confirmation)
* {{X61}}, {{X61s}}, {{X61 Tablet}}

For these models, the SSD installed in the WWAN slot has to be SATA, because there are no PCIe signals on the slot. The WWAN card communicates via USB.
* {{T440p}}, {{T440s}}, {{T450s}}

For these models, the WWAN slot can actually accept a 2242 M.2 NVMe SSD:
* {{T14}}

Problem with LCD brightness buttons

2019-04-07T12:07:57Z

WilliamPoetra: /* Change permissions on the brightness file */

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{X61s}}
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

'''Note for T420s users:''' Using the workarounds listed below (except the chmod workaround) in Linux Mint 19.1 MATE introduces a weird bug, whereby the brightness is reset every time the power cord is plugged or unplugged. It also disables the brightness keys when we are at the login screen. This does not occur on Linux Mint 19.1 Cinnamon and Ubuntu 18.04.1 Desktop. In fact, for those distros we do not need to apply any of the workarounds below at all.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
# rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

# echo options video brightness_switch_enabled=0 | tee /etc/modprobe.d/video-br.conf

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

# echo N | tee /sys/module/video/parameters/brightness_switch_enabled

=== Update Grub loading ===

From https://bbs.archlinux.org/viewtopic.php?id=184949&p=2

Add to GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub
video.use_native_backlight=0

=== Change permissions on the brightness file ===

Find the raw brightness control method:

$ grep -qs raw /sys/class/backlight/*/type
/sys/class/backlight/intel_backlight/type:raw

Then chmod the brightness file so the power manager can't write to it.

# chmod 444 /sys/class/backlight/intel_backlight/brightness

Incidentally, this also fixes the brightness reset upon plug or unplug of the power cable.

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

Problem with LCD brightness buttons

2019-04-07T11:38:28Z

WilliamPoetra: /* Modify the parameter for video.ko at runtime */

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{X61s}}
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

'''Note for T420s users:''' Using the workarounds listed below (except the chmod workaround) in Linux Mint 19.1 MATE introduces a weird bug, whereby the brightness is reset every time the power cord is plugged or unplugged. It also disables the brightness keys when we are at the login screen. This does not occur on Linux Mint 19.1 Cinnamon and Ubuntu 18.04.1 Desktop. In fact, for those distros we do not need to apply any of the workarounds below at all.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
# rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

# echo options video brightness_switch_enabled=0 | tee /etc/modprobe.d/video-br.conf

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

# echo N | tee /sys/module/video/parameters/brightness_switch_enabled

=== Update Grub loading ===

From https://bbs.archlinux.org/viewtopic.php?id=184949&p=2

Add to GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub
video.use_native_backlight=0

=== Change permissions on the brightness file ===

Find the raw brightness control method:

$ grep -qs raw /sys/class/backlight/*/type
/sys/class/backlight/intel_backlight/type:raw

Then chmod the brightness file so the power manager can't write to it.

# chmod 444 /sys/class/backlight/intel_backlight/type

Incidentally, this also fixes the brightness reset upon plug or unplug of the power cable.

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

Problem with LCD brightness buttons

2019-04-07T11:36:54Z

WilliamPoetra: /* Workaround */

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{X61s}}
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

'''Note for T420s users:''' Using the workarounds listed below (except the chmod workaround) in Linux Mint 19.1 MATE introduces a weird bug, whereby the brightness is reset every time the power cord is plugged or unplugged. It also disables the brightness keys when we are at the login screen. This does not occur on Linux Mint 19.1 Cinnamon and Ubuntu 18.04.1 Desktop. In fact, for those distros we do not need to apply any of the workarounds below at all.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
# rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

# echo options video brightness_switch_enabled=0 | tee /etc/modprobe.d/video-br.conf

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

echo N > /sys/module/video/parameters/brightness_switch_enabled

=== Update Grub loading ===

From https://bbs.archlinux.org/viewtopic.php?id=184949&p=2

Add to GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub
video.use_native_backlight=0

=== Change permissions on the brightness file ===

Find the raw brightness control method:

$ grep -qs raw /sys/class/backlight/*/type
/sys/class/backlight/intel_backlight/type:raw

Then chmod the brightness file so the power manager can't write to it.

# chmod 444 /sys/class/backlight/intel_backlight/type

Incidentally, this also fixes the brightness reset upon plug or unplug of the power cable.

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

Problem with LCD brightness buttons

2019-04-06T09:22:31Z

WilliamPoetra: /* Workaround */

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{X61s}}
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

'''Note for T420s users:''' Using the workarounds listed below in Linux Mint 19.1 MATE introduces a weird bug, whereby the brightness is reset every time the power cord is plugged or unplugged. It also disables the brightness keys when we are at the login screen. This does not occur on Linux Mint 19.1 Cinnamon and Ubuntu 18.04.1 Desktop. In fact, for those distros we do not need to apply any of the workarounds below at all.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
{{cmdroot|rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko }}

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

{{cmdroot|1=echo options video brightness_switch_enabled=0 {{!}} tee /etc/modprobe.d/video-br.conf}}

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

echo N > /sys/module/video/parameters/brightness_switch_enabled

=== Update Grub loading ===

From https://bbs.archlinux.org/viewtopic.php?id=184949&p=2

Add to GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub
video.use_native_backlight=0

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

Problem with LCD brightness buttons

2019-04-06T09:21:46Z

WilliamPoetra: /* Workaround */

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{X61s}}
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

'''Note for T420s users:''' Using the workarounds listed below in Linux Mint 19.1 MATE introduces a weird bug, whereby the brightness is reset every time the power cord is plugged or unplugged. It also disables the brightness keys when we are at the login screen. This does not occur on Linux Mint 19.1 Cinnamon and Ubuntu 18.04.1 Desktop.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
{{cmdroot|rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko }}

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

{{cmdroot|1=echo options video brightness_switch_enabled=0 {{!}} tee /etc/modprobe.d/video-br.conf}}

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

echo N > /sys/module/video/parameters/brightness_switch_enabled

=== Update Grub loading ===

From https://bbs.archlinux.org/viewtopic.php?id=184949&p=2

Add to GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub
video.use_native_backlight=0

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

Problem with LCD brightness buttons

2019-04-05T19:26:36Z

WilliamPoetra: /* Workaround */

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{X61s}}
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

'''Note for T420s users:''' Using the workarounds listed below in Linux Mint 19.1 introduces a weird bug, whereby the brightness is reset every time the power cord is plugged or unplugged. It also disables the brightness keys when we are at the login screen.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
{{cmdroot|rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko }}

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

{{cmdroot|1=echo options video brightness_switch_enabled=0 {{!}} tee /etc/modprobe.d/video-br.conf}}

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

echo N > /sys/module/video/parameters/brightness_switch_enabled

=== Update Grub loading ===

From https://bbs.archlinux.org/viewtopic.php?id=184949&p=2

Add to GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub
video.use_native_backlight=0

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

Category:X1 Tablet

2019-02-05T18:34:43Z

WilliamPoetra: /* ThinkPad X1 Tablet */

=== ThinkPad X1 Tablet ===
This page gives an overview of the ThinkPad X1 Tablet (2016).

The following generations of ThinkPad X1 Tablet exist:
* [[:Category:X1 Tablet|X1 Tablet]]: ThinkPad X1 Tablet (Type 20GG, 20GH), 1st generation (2016)
* [[:Category:X1 Tablet (2nd Gen)|X1 Tablet (2nd Gen)]]: Thinkpad X1 Tablet 2nd generation (2017)
* [[:Category:X1 Tablet (3rd Gen)|X1 Tablet (3rd Gen)]]: Thinkpad X1 Tablet 3rd generation (2018) (Type 20KJ)

==== Details ====
* '''Machine type:''' 20GG, 20GH

* '''Processor:''' One of the following 6th Generation Intel Core M processors:
** Intel® Core™-M m3-6Y30 (2 cores, 4 threads, 0.9-2.2GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y54 (2 cores, 4 threads, 1.1-2.7GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y57 (2 cores, 4 threads, 1.1-2.8GHz, 4MB L3 cache) with vPro™
** Intel® Core™-M m7-6Y75 (2 cores, 4 threads, 1.2-3.1GHz, 4MB L3 cache) with vPro™

* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 515]]

* '''Display:'''
** 12.0" FHD+ glossy screen (2160x1440) with Corning ® Gorilla ® Glass and 10-point multi-touch

* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1866 MHz
** 8GB DDR3L SDRAM 1866 MHz
** 16GB DDR3L SDRAM 1866 MHz

* '''Disk:'''
** M.2 SATA 256GB SSD
** M.2 NVMe 256GB SSD

* '''WLAN:'''
** Intel Dual Band Wireless-AC 8260 + Bluetooth Combo Adapter
** Intel Tri-Band Wireless-AC 18260 + Bluetooth Combo Adapter

* '''WWAN:'''
** Sierra Wireless EM7455
** HUAWEI ME906S

* '''Bluetooth:''' Bluetooth Combo Adapter with the WLAN card

* '''Keyboard:''' Detachable pogo keyboard with TrackPoint® and buttonless TrackPad®

* '''I/O Ports:'''
** 1 x USB 3.0
** 1 x USB Type-C
** Mini DisplayPort
** Headphone / Microphone combo jack
** Nano-SIM Slot

* '''Power:'''
** 37Wh battery for 10-hour video playback
** 45W USB Type-C adapter

* '''Camera:'''
** 2.0MP front camera
** 8.0MP rear camera with autofocus and LED flash

* '''Audio:'''
** Realtek® ALC3268 codec
** Stereo speakers

* '''Dimensions'''
** Tablet only: 11.48in x 8.25in x 0.34in (291.5mm x 209.5mm x 8.75mm)

* '''Weight'''
** Tablet only: 1.69 lb (767 g)
** Tablet+keyboard: 2.35 lb (1.07 kg)

[[Category:X_Series]]

Category:X1 Tablet

2019-02-05T18:33:35Z

WilliamPoetra: /* ThinkPad X1 Tablet */

=== ThinkPad X1 Tablet ===
This page gives an overview of the ThinkPad X1 Tablet (2016).

The following generations of ThinkPad X1 Tablet exist:
* [[:Category:X1 Tablet]]: ThinkPad X1 Tablet (Type 20GG, 20GH), 1st generation (2016)
* [[:Category:X1 Tablet (2nd Gen)]]: Thinkpad X1 Tablet 2nd generation (2017)
* [[:Category:X1 Tablet (3rd Gen)]]: Thinkpad X1 Tablet 3rd generation (2018) (Type 20KJ)

==== Details ====
* '''Machine type:''' 20GG, 20GH

* '''Processor:''' One of the following 6th Generation Intel Core M processors:
** Intel® Core™-M m3-6Y30 (2 cores, 4 threads, 0.9-2.2GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y54 (2 cores, 4 threads, 1.1-2.7GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y57 (2 cores, 4 threads, 1.1-2.8GHz, 4MB L3 cache) with vPro™
** Intel® Core™-M m7-6Y75 (2 cores, 4 threads, 1.2-3.1GHz, 4MB L3 cache) with vPro™

* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 515]]

* '''Display:'''
** 12.0" FHD+ glossy screen (2160x1440) with Corning ® Gorilla ® Glass and 10-point multi-touch

* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1866 MHz
** 8GB DDR3L SDRAM 1866 MHz
** 16GB DDR3L SDRAM 1866 MHz

* '''Disk:'''
** M.2 SATA 256GB SSD
** M.2 NVMe 256GB SSD

* '''WLAN:'''
** Intel Dual Band Wireless-AC 8260 + Bluetooth Combo Adapter
** Intel Tri-Band Wireless-AC 18260 + Bluetooth Combo Adapter

* '''WWAN:'''
** Sierra Wireless EM7455
** HUAWEI ME906S

* '''Bluetooth:''' Bluetooth Combo Adapter with the WLAN card

* '''Keyboard:''' Detachable pogo keyboard with TrackPoint® and buttonless TrackPad®

* '''I/O Ports:'''
** 1 x USB 3.0
** 1 x USB Type-C
** Mini DisplayPort
** Headphone / Microphone combo jack
** Nano-SIM Slot

* '''Power:'''
** 37Wh battery for 10-hour video playback
** 45W USB Type-C adapter

* '''Camera:'''
** 2.0MP front camera
** 8.0MP rear camera with autofocus and LED flash

* '''Audio:'''
** Realtek® ALC3268 codec
** Stereo speakers

* Dimensions
** Tablet only: 11.48in x 8.25in x 0.34in (291.5mm x 209.5mm x 8.75mm)

* Weight
** Tablet only: 1.69 lb (767 g)
** Tablet+keyboard: 2.35 lb (1.07 kg)

[[Category:X_Series]]

Category:X1 Tablet

2019-02-05T18:26:13Z

WilliamPoetra:

=== ThinkPad X1 Tablet ===
This page gives an overview of the ThinkPad {{X1 Tablet}} (2016).

==== Details ====
* '''Machine type:''' 20GG, 20GH

* '''Processor:''' One of the following 6th Generation Intel Core M processors:
** Intel® Core™-M m3-6Y30 (2 cores, 4 threads, 0.9-2.2GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y54 (2 cores, 4 threads, 1.1-2.7GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y57 (2 cores, 4 threads, 1.1-2.8GHz, 4MB L3 cache) with vPro™
** Intel® Core™-M m7-6Y75 (2 cores, 4 threads, 1.2-3.1GHz, 4MB L3 cache) with vPro™

* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 515]]

* '''Display:'''
** 12.0" FHD+ glossy screen (2160x1440) with Corning ® Gorilla ® Glass and 10-point multi-touch

* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1866 MHz
** 8GB DDR3L SDRAM 1866 MHz
** 16GB DDR3L SDRAM 1866 MHz

* '''Disk:'''
** M.2 SATA 256GB SSD
** M.2 NVMe 256GB SSD

* '''WLAN:'''
** Intel Dual Band Wireless-AC 8260 + Bluetooth Combo Adapter
** Intel Tri-Band Wireless-AC 18260 + Bluetooth Combo Adapter

* '''WWAN:'''
** Sierra Wireless EM7455
** HUAWEI ME906S

* '''Bluetooth:''' Bluetooth Combo Adapter with the WLAN card

* '''Keyboard:''' Detachable pogo keyboard with TrackPoint® and buttonless TrackPad®

* '''I/O Ports:'''
** 1 x USB 3.0
** 1 x USB Type-C
** Mini DisplayPort
** Headphone / Microphone combo jack
** Nano-SIM Slot

* '''Power:'''
** 37Wh battery for 10-hour video playback
** 45W USB Type-C adapter

* '''Camera:'''
** 2.0MP front camera
** 8.0MP rear camera with autofocus and LED flash

* '''Audio:'''
** Realtek® ALC3268 codec
** Stereo speakers

* Dimensions
** Tablet only: 11.48in x 8.25in x 0.34in (291.5mm x 209.5mm x 8.75mm)

* Weight
** Tablet only: 1.69 lb (767 g)
** Tablet+keyboard: 2.35 lb (1.07 kg)

[[Category:X_Series]]

Category:X1 Tablet

2019-02-05T18:25:35Z

WilliamPoetra: â†Created page with '=== ThinkPad X1 Tablet === This page gives an overview of the ThinkPad {{X1 Tablet}} (2016). ==== Details ==== * '''Machine type:''' 20GG, 20GH * '''Processor:''' One...'

=== ThinkPad X1 Tablet ===
This page gives an overview of the ThinkPad {{X1 Tablet}} (2016).

==== Details ====
* '''Machine type:''' 20GG, 20GH

* '''Processor:''' One of the following 6th Generation Intel Core M processors:
** Intel® Core™-M m3-6Y30 (2 cores, 4 threads, 0.9-2.2GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y54 (2 cores, 4 threads, 1.1-2.7GHz, 4MB L3 cache)
** Intel® Core™-M m5-6Y57 (2 cores, 4 threads, 1.1-2.8GHz, 4MB L3 cache) with vPro™
** Intel® Core™-M m7-6Y75 (2 cores, 4 threads, 1.2-3.1GHz, 4MB L3 cache) with vPro™

* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 515]]

* '''Display:'''
** 12.0" FHD+ glossy screen (2160x1440) with Corning ® Gorilla ® Glass and 10-point multi-touch

* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1866 MHz
** 8GB DDR3L SDRAM 1866 MHz
** 16GB DDR3L SDRAM 1866 MHz

* '''Disk:'''
** M.2 SATA 256GB SSD
** M.2 NVMe 256GB SSD

* '''WLAN:'''
** Intel Dual Band Wireless-AC 8260 + Bluetooth Combo Adapter
** Intel Tri-Band Wireless-AC 18260 + Bluetooth Combo Adapter

* '''WWAN:'''
** Wireless WAN, Sierra Wireless EM7455
** Wireless WAN, HUAWEI ME906S

* '''Bluetooth:''' Bluetooth Combo Adapter with the WLAN card

* '''Keyboard:''' Detachable pogo keyboard with TrackPoint® and buttonless TrackPad®

* '''I/O Ports:'''
** 1 x USB 3.0
** 1 x USB Type-C
** Mini DisplayPort
** Headphone / Microphone combo jack
** Nano-SIM Slot

* '''Power:'''
** 37Wh battery for 10-hour video playback
** 45W USB Type-C adapter

* '''Camera:'''
** 2.0MP front camera
** 8.0MP rear camera with autofocus and LED flash

* '''Audio:'''
** Realtek® ALC3268 codec
** Stereo speakers

* Dimensions
** Tablet only: 11.48in x 8.25in x 0.34in (291.5mm x 209.5mm x 8.75mm)

* Weight
** Tablet only: 1.69 lb (767 g)
** Tablet+keyboard: 2.35 lb (1.07 kg)

[[Category:X_Series]]

Category:X1 Carbon (6th Gen)

2019-02-05T17:12:31Z

WilliamPoetra: /* Details */

The Thinkpad X1 Carbon 6th Generation is based on the Intel Kaby Lake R microarchitecture and released in January 2018. It comes in black and silver.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]], [[:Category:X1 Carbon (5th Gen)|2017]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}

* '''Machine type:''' 20KG*, 20KH*

* '''Processor:'''
** One of the following 8th generation ULV [[Intel Core]] processors (code name: "Kaby Lake R", 14nm)
*** Intel® Core™ i5-8250U (1.6-3.4GHz, 6MB L3 cache)
*** Intel® Core™ vPro™ i5-8350U (1.7-3.6GHz, 6MB L3 cache)
*** Intel® Core™ i7-8550U (1.8-4.0GHz, 8MB L3 cache)
*** Intel® Core™ vPro™ i7-8650U (1.9-4.2GHz, 8MB L3 cache)
** One of the following ULV 7th generation Intel Core processors (code name: "Kaby Lake", 14nm)
*** Intel® Core™ vPro™ i5-7300U (2.6-3.5GHz, 3MB L3 cache)

* '''Graphics:''' [[Intel HD Graphics|Intel® UHD Graphics 620]]

* '''Display:''' IPS screen with
** Matte 14.0" FHD (1920x1080), 300 nits
** Matte 14.0" FHD (1920x1080), 300 nits with touchscreen
** Matte 14.0" WQHD (2560x1440), 300 nits
** Glossy 14.0" WQHD (2560x1440), 500 nits with Dolby Vision™ HDR

* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 8GB LPDDR3-2133 (PC3L-17000)
** 16GB LPDDR3-2133 (PC3L-17000)

* '''Storage:''' One of the following connected to the M.2 port
** 256GB M.2 SSD
** 512GB M.2 SSD
** 1TB TLC NVMe SSD with OPAL 2.0

* '''WLAN:''' Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2

* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module

* '''WWAN:''' Fibocom L850-GL LTE-A

* '''Keyboard:''' 6-row with TrackPoint and ClickPad, illuminated keyboard keys

* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4
** Mini Ethernet jack with dongle for full-size Ethernet port
** 3.5mm Audio/Mic TRRS combo jack
** microSD card slot
** Micro SIM slot

* '''Camera options'''
** 720p HD webcam with noise-cancelling microphone and ThinkShutter webcam cover (selected models only)
** IR camera for Windows Hello (selected models only)

* '''Audio:''' Dolby® Audio™ Premium

* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader
** Kensington® lock slot

* '''Power'''
** USB Type-C charger
** 57Wh Li-ion battery with RapidCharge technology, up to 15 hours

* '''Physical Dimensions'''
** Size: 12.7in x 8.54in x 0.63in (324 x 217mm x 16.0mm)
** Weight: 2.49 lb (1.13 kg) / 3.30lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon (5th Gen)

2019-02-05T16:55:50Z

WilliamPoetra: /* Details */

The Thinkpad X1 Carbon 5th Generation is based on the Intel Kaby Lake microarchitecture and released in early 2017.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}

* '''Machine type:'''
** Kaby Lake: 20HQ, 20HR
** Skylake: 20K3, 20K4

* '''Processor:'''
** 20HQ, 20HR: one of the following ULV 7th generation Intel Core processors (code name: "Kaby Lake", 14nm)
*** Intel® Core™ i5-7200U (2.5-3.1GHz, 3MB L3 cache)
*** Intel® Core™ vPro™ i5-7300U (2.6-3.5GHz, 3MB L3 cache)
*** Intel® Core™ i7-7500U (2.7-3.5GHz, 4MB L3 cache)
*** Intel® Core™ vPro™ i7-7600U (2.8-3.9GHz, 4MB L3 cache)
** 20K3, 20K4: one of the following ULV 6th generation Intel Core processors (code name: "Skylake", 14nm)
*** Intel® Core™ i5-6200U (2.3-2.8GHz, 3MB L3 cache)
*** Intel® Core™ vPro™ i5-6300U (2.4-3.0GHz, 3MB L3 cache)
*** Intel® Core™ i7-6500U (2.5-3.1GHz, 4MB L3 cache)
*** Intel® Core™ vPro™ i7-6600U (2.6-3.4GHz, 4MB L3 cache)

* '''Graphics:'''
** 20HQ, 20HR: [[Intel HD Graphics|Intel® HD Graphics 620]]
** 20K3, 20K4: [[Intel HD Graphics|Intel® HD Graphics 520]]

* '''Display:''' Matte anti-glare IPS screen with 700:1 contrast ratio and 170° viewing angle
** 14.0" FHD (1920x1080), 300 nits
** 14.0" WQHD (2560x1440), 300 nits (available from mid-2017)

* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 8GB LPDDR3-1866 (PC3L-14900)
** 16GB LPDDR3-1866 (PC3L-14900)

* '''Storage:''' One of the following connected to the M.2 port
** 128GB M.2 SATA SSD (SanDisk X400, maybe others)
** 256GB NVMe SSD with OPAL 2.0
** 512GB Samsung PM961 NVMe SSD with OPAL 2.0
** 1TB NVMe SSD with OPAL 2.0

* '''WLAN:''' One of the following cards
** Intel® Dual Band Wireless-AC 8260 2x2 with Bluetooth 4.2
** Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2
** Intel® Tri-Band Wireless-AC 18265 2x2 with WiGig 802.11ad and Bluetooth 4.2

* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module

* '''WWAN:''' Qualcomm® Snapdragon™ X7 LTE-A / Sierra Wireless EM7455 (WWAN is available but must be configured at purchase, otherwise there is no WWAN antenna provided)

* '''Keyboard:''' 6-row with TrackPoint and ClickPad, illuminated keyboard keys

* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support, external monitor up to 4096x2304@60Hz
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4b, supports up to 4096x2160@24Hz
** Mini Ethernet jack
** 3.5mm Audio/Mic combo jack
** microSD card slot
** Micro-SIM slot

* '''Battery:''' 3-cell Li-Poly battery (57Wh), up to 15.5 hours

* '''AC Adapter:'''
** 45W USB Type-C AC adapter
** 65W USB Type-C AC adapter with RapidCharge support (80% in 1 hr, 100% in 2.5 hrs)

* '''Webcam:''' 720p HD webcam with microphone

* '''Audio:''' Dolby® Audio™ Premium

* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader

* '''Physical Dimensions'''
** Size: 12.7in x 8.54in x 0.63in (324 x 217mm x 16.0mm)
** Weight: 2.49 lb (1.13 kg) / 3.30lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon

2019-02-05T16:50:51Z

WilliamPoetra: /* ThinkPad X1 Carbon */

=== ThinkPad X1 Carbon ===
This page gives an overview of the ThinkPad {{X1 Carbon}} (2012).

The following generations of ThinkPad X1 Carbon exist:
* {{X1 Carbon}}: ThinkPad X1 Carbon (Type 34xx), 1st generation, appeared in 2012
* {{X1 Carbon 2nd}}: ThinkPad X1 Carbon 2nd generation (Type 20A7, 20A8), appeared in 2014, also known as "Lenovo New Thinkpad X1 Carbon".
* [[:Category:X1 Carbon (3rd Gen) | X1 Carbon (3rd Gen)]]: ThinkPad X1 Carbon 3rd generation (Type 20BS, 20BT), released in 2015.
* [[:Category:X1 Carbon (4th Gen) | X1 Carbon (4th Gen)]]: ThinkPad X1 Carbon 4th generation (Type 20FB, 20FC), released in 2016.
* [[:Category:X1 Carbon (5th Gen) | X1 Carbon (5th Gen)]]: ThinkPad X1 Carbon 5th generation (Type 20HQ, 20HR), released in 2017.
* [[:Category:X1 Carbon (6th Gen) | X1 Carbon (6th Gen)]]: ThinkPad X1 Carbon 6th generation (Type 20KG, 20KH), released in 2018.
* [[:Category:X1 Carbon (7th Gen) | X1 Carbon (7th Gen)]]: ThinkPad X1 Carbon 7th generation (Type 20??), released in 2019.

==== Details ====
* '''Machine type:''' 34xx
* '''Processor:''' One of the following ULV 3rd generation Intel Core processors (code name: "Ivy Bridge"):
** Intel® Core™ i5-3317U (1.7-2.6GHz, 3MB L3 cache)
** Intel® Core™ i5-3337U (1.8-2.7GHz, 3MB L3 cache)
** Intel® Core™ i5-3427U (1.8-2.8GHz, 3MB L3 cache)
** Intel® Core™ i7-3667U (2.0-3.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 4000]]
* '''Display:'''
** 14.0" HD+ Matte screen (1600x900)
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1600 MHz
** 8GB DDR3L SDRAM 1600 MHz
* '''Disk:'''
** 128GB SSD
** 250GB SSD
** 256GB SSD
* '''WLAN:'''
** Intel 801.11b/g/n
* '''WWAN:''' TODO
* '''Bluetooth:''' TODO
* '''Keyboard:''' TODO
* '''I/O Ports:'''
** 1 x USB 2.0, 1 x USB 3.0
** Mini DisplayPort
** SD Card Slot
* '''Battery:''' Up to 6.3 hours
* '''Webcam:''' [[Integrated camera]] 1.3MP (720p)
* '''Audio:'''
* Size: 13.03in x 8.90in x 0.74in (331mm x 226mm x 19mm)
* Weight: 3.00 lb (1.36 kg)

[[Category:X_Series]]

Category:T480s

2018-12-21T18:30:58Z

WilliamPoetra: /* Standard Features */

=== Machine Type ===

xxx

=== Standard Features ===

Dimensions:
* Size: 331mm x 227mm x 18.5mm (13.0" x 8.93" x 0.72")
* Weight: 1.32kg (2.9 lbs)

Color:
* Black
* Silver

Features:
* CPU: one of the following ULV 8th-gen Intel Core processors
** Intel Core i5-7300U
** Intel Core i5-8250U
** Intel Core i5-8350U
** Intel Core i7-8550U
** Intel Core i7-8650U with vPro, 1.9 - 4.2 GHz, 8MB Cache

* RAM:
** 4GB or 8GB DDR4-2133 (PC4-17000) soldered to the systemboard
** One free socket supporting up to 16GB DDR4 SO-DIMM

* GPU:
** Intel UHD Graphics 620 integrated into CPU
** Nvidia MX150 with 2GB GDDR5 (optional)

* Maximum supported resolution on external monitor:
** 4096x2304@60Hz via USB Type-C
** 4096x2160@24Hz via HDMI

* Display: one of the following IPS anti-glare displays with LED backlight, 700:1 contrast ratio and 160° viewing angle
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1 with multitouch
** 14.0" 2560x1440 ("WQHD") FlexView, 300 nits, 700:1

* Storage: one of the following installed in the M.2 slot
** SATA 3 SSD
** 256GB PCIe NVMe SSD
** 512GB PCIe NVMe SSD
** 1TB PCIe NVMe SSD

* M.2-2230 slot with one of the following, no SATA lanes:
** Intel Dual Band Wireless-AC 8260: 2x2 Wi-Fi 802.11ac, Bluetooth 4.1
** Intel Dual Band Wireless-AC 8265: 2x2 Wi-Fi 802.11ac with MU-MIMO, Bluetooth 4.1
** Intel Tri-Band Wireless-AC 18265: 2x2 Wi-Fi 802.11ac, WiGig 802.11ad, Bluetooth 4.1

* M.2-2242 slot with one of the following, no SATA lanes:
** Empty slot, if WiGig is available
** Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455), LTE-Advanced/DC-HSPA+/HSPA+/HSPA/UMTS/GNSS

* Ethernet chip: Intel I219-LM (vPro), Intel I219-V (non vPro)

* 720p HD [[Integrated camera]] with ThinkShutter

* Battery: 57Wh

* Power adapter: one of the following
** 45W AC adapter with USB Type-C
** 65W AC adapter with USB Type-C

* Security features
** Kensington lock slot
** dTPM 2.0
** [[Integrated Fingerprint Reader]] (optional)

* Pointing devices
** TrackPoint (with 3 physical buttons)
** UltraNav touch pad

* I/O ports
** Intel Thunderbolt 3 (compatible with USB Type-C)
** USB Type-C (doubles as charging port)
** 2x USB 3.0
** MicroSD card reader
** TRRS headphone/microphone combo jack
** HDMI
** RJ45 Ethernet port
** Micro-SIM card slot

[[Category:T Series]]

Category:X1 Carbon 2nd

2018-04-25T03:23:00Z

WilliamPoetra:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad X1 Carbon 2nd ===
This page gives an overview of the ThinkPad {{X1 Carbon 2nd}} (2014),<br />
also it's referred as New ThinkPad X1 Carbon.<br />
NOTE: This generation of ThinkPad X1 Carbon has no physical Trackpoint buttons.<br />
Link to the previous model: {{X1 Carbon}} (2012)

==== Details ====
* '''Machine type:''' 20A7*, 20A8*
* '''Processor:''' one of the following processors on new 4th Gen Intel [[Haswell]] architecture:
** [[Intel Core i7]] 4600U (3.30GHz 1600MHz 4MB)
** [[Intel Core i5]] 4300U (2.90GHz 1600MHz 3MB)
** [[Intel Core i5]] 4200U (2.60GHz 1600MHz 3MB)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 4400]]
* '''Display:'''
** 14.0" WQHD (2560x1440), 260nit, IPS with or without 10-point multitouch
** 14.0" HD+ (1600x900), 260nit
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1600 MHz
** 8GB DDR3L SDRAM 1600 MHz
* '''Disk:'''
** 128GB SSD M.2
** Intel 180GB Opal SSD
** 256GB SSD M.2 eDrive Capable
** Intel 240GB Opal SSD
** 512GB SSD M.2
* '''WLAN:'''
** Intel Centrino 7260 (Wilkins Peak 2 BN) 2x2 AC + Bluetooth 4.0
** Intel Centrino 7260 (Wilkins Peak 2 AC) 2x2 AC + Bluetooth 4.0
* '''WWAN:''' Sierra Wireless EM7355 - Gobi 5000
* '''Bluetooth:''' Bluetooth 4.0 supported by WLAN module
* '''Keyboard:''' 5-row with Trackpoint (Island style, Under mount) plus Adaptive backlit Keyboard keys
* '''I/O Ports:'''
** 2 x USB 3.0 (1 with AOU)
** Audio/Mic Combo OneLink Dock
** HDMI
** MiniDP
* '''Battery:''' Up to 8.6 hours (about 4 hours working mode)
* '''Webcam:''' [[Integrated camera]] 1.3MP - 720P with mute function
* '''Audio:''' Dolby® Home Theater® v4 with Digital Dual Array microphone certified for Microsoft Lync

</div>
|style="vertical-align:top" |
[[Image:X1Carbon2nd-face.png|thumb|ThinkPad X1 Carbon 2nd]]
[[Image:X1Carbon2nd-top.png|thumb|ThinkPad X1 Carbon 2nd - Top view]]
|}
* [http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-carbon-type-20a7-20a8 Download and support page for ThinkPad X1 Carbon Gen2]
* [http://download.lenovo.com/pccbbs/mobiles_pdf/x1carbon_2_hmm_sp40a26110.pdf Hardware Maintenance Manual Thinkpad X1 Carbon 2] (58,331,257 bytes)

==== Reviews ====
{{Todo|add reviews}}
[[Gentoo on ThinkPad X1 Carbon 2nd]]

==== Memory ====
{{Todo|add specification on memory and other components}}

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon 2nd

2018-04-25T03:22:47Z

WilliamPoetra:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad X1 Carbon 2nd ===
This page gives an overview of the ThinkPad {{X1 Carbon 2nd}} (2014),<br />
also it's referred as New ThinkPad X1 Carbon.<br />
NOTE: This generation of ThinkPad X1 Carbon has no physical Trackpoint buttons.
Link to the previous model: {{X1 Carbon}} (2012)

==== Details ====
* '''Machine type:''' 20A7*, 20A8*
* '''Processor:''' one of the following processors on new 4th Gen Intel [[Haswell]] architecture:
** [[Intel Core i7]] 4600U (3.30GHz 1600MHz 4MB)
** [[Intel Core i5]] 4300U (2.90GHz 1600MHz 3MB)
** [[Intel Core i5]] 4200U (2.60GHz 1600MHz 3MB)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 4400]]
* '''Display:'''
** 14.0" WQHD (2560x1440), 260nit, IPS with or without 10-point multitouch
** 14.0" HD+ (1600x900), 260nit
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1600 MHz
** 8GB DDR3L SDRAM 1600 MHz
* '''Disk:'''
** 128GB SSD M.2
** Intel 180GB Opal SSD
** 256GB SSD M.2 eDrive Capable
** Intel 240GB Opal SSD
** 512GB SSD M.2
* '''WLAN:'''
** Intel Centrino 7260 (Wilkins Peak 2 BN) 2x2 AC + Bluetooth 4.0
** Intel Centrino 7260 (Wilkins Peak 2 AC) 2x2 AC + Bluetooth 4.0
* '''WWAN:''' Sierra Wireless EM7355 - Gobi 5000
* '''Bluetooth:''' Bluetooth 4.0 supported by WLAN module
* '''Keyboard:''' 5-row with Trackpoint (Island style, Under mount) plus Adaptive backlit Keyboard keys
* '''I/O Ports:'''
** 2 x USB 3.0 (1 with AOU)
** Audio/Mic Combo OneLink Dock
** HDMI
** MiniDP
* '''Battery:''' Up to 8.6 hours (about 4 hours working mode)
* '''Webcam:''' [[Integrated camera]] 1.3MP - 720P with mute function
* '''Audio:''' Dolby® Home Theater® v4 with Digital Dual Array microphone certified for Microsoft Lync

</div>
|style="vertical-align:top" |
[[Image:X1Carbon2nd-face.png|thumb|ThinkPad X1 Carbon 2nd]]
[[Image:X1Carbon2nd-top.png|thumb|ThinkPad X1 Carbon 2nd - Top view]]
|}
* [http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-carbon-type-20a7-20a8 Download and support page for ThinkPad X1 Carbon Gen2]
* [http://download.lenovo.com/pccbbs/mobiles_pdf/x1carbon_2_hmm_sp40a26110.pdf Hardware Maintenance Manual Thinkpad X1 Carbon 2] (58,331,257 bytes)

==== Reviews ====
{{Todo|add reviews}}
[[Gentoo on ThinkPad X1 Carbon 2nd]]

==== Memory ====
{{Todo|add specification on memory and other components}}

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon

2018-02-25T02:05:01Z

WilliamPoetra: /* ThinkPad X1 Carbon */

=== ThinkPad X1 Carbon ===
This page gives an overview of the ThinkPad {{X1 Carbon}} (2012).

The following generations of ThinkPad X1 Carbon exist:
* {{X1 Carbon}}: ThinkPad X1 Carbon (Type 34xx), 1st generation, appeared in 2012
* {{X1 Carbon 2nd}}: ThinkPad X1 Carbon 2nd generation (Type 20A7, 20A8), appeared in 2014, also known as "Lenovo New Thinkpad X1 Carbon".
* [[:Category:X1 Carbon (3rd Gen) | X1 Carbon (3rd Gen)]]: ThinkPad X1 Carbon 3rd generation (Type 20BS, 20BT), released in 2015.
* [[:Category:X1 Carbon (4th Gen) | X1 Carbon (4th Gen)]]: ThinkPad X1 Carbon 4th generation (Type 20FB, 20FC), released in 2016.
* [[:Category:X1 Carbon (5th Gen) | X1 Carbon (5th Gen)]]: ThinkPad X1 Carbon 5th generation (Type 20HQ, 20HR), released in 2017.
* [[:Category:X1 Carbon (6th Gen) | X1 Carbon (6th Gen)]]: ThinkPad X1 Carbon 6th generation (Type 20KG, 20KH), released in 2018.

==== Details ====
* '''Machine type:''' 34xx
* '''Processor:''' One of the following ULV 3rd generation Intel Core processors (code name: "Ivy Bridge"):
** Intel® Core™ i5-3317U (1.7-2.6GHz, 3MB L3 cache)
** Intel® Core™ i5-3337U (1.8-2.7GHz, 3MB L3 cache)
** Intel® Core™ i5-3427U (1.8-2.8GHz, 3MB L3 cache)
** Intel® Core™ i7-3667U (2.0-3.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 4000]]
* '''Display:'''
** 14.0" HD+ Matte screen (1600x900)
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1600 MHz
** 8GB DDR3L SDRAM 1600 MHz
* '''Disk:'''
** 128GB SSD
** 250GB SSD
** 256GB SSD
* '''WLAN:'''
** Intel 801.11b/g/n
* '''WWAN:''' TODO
* '''Bluetooth:''' TODO
* '''Keyboard:''' TODO
* '''I/O Ports:'''
** 1 x USB 2.0, 1 x USB 3.0
** Mini DisplayPort
** SD Card Slot
* '''Battery:''' Up to 6.3 hours
* '''Webcam:''' [[Integrated camera]] 1.3MP (720p)
* '''Audio:'''
* Size: 13.03in x 8.90in x 0.74in (331mm x 226mm x 19mm)
* Weight: 3.00 lb (1.36 kg)

[[Category:X_Series]]

Category:X1 Carbon (6th Gen)

2018-02-25T02:03:31Z

WilliamPoetra:

The Thinkpad X1 Carbon 6th Generation is based on the Intel Kaby Lake R microarchitecture and released in January 2018. It comes in black and silver.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]], [[:Category:X1 Carbon (5th Gen)|2017]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}

* '''Machine type:''' 20KG*, 20KH*

* '''Processor:''' One of the following 8th generation ULV [[Intel Core]] processors (code name: "Kaby Lake R", 14nm)
** Intel® Core™ i7-8650U (1.9-4.2GHz, 4MB L3 cache)

* '''Graphics:''' [[Intel HD Graphics|Intel® UHD Graphics 620]]

* '''Display:''' IPS screen with
** Matte 14.0" FHD (1920x1080), 300 nits
** Matte 14.0" FHD (1920x1080), 300 nits with touchscreen
** Matte 14.0" WQHD (2560x1440), 300 nits
** Glossy 14.0" WQHD (2560x1440), 500 nits with Dolby Vision™ HDR

* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 16GB LPDDR3-2133 (PC3L-17000)

* '''Storage:''' One of the following connected to the M.2 port
** 1TB TLC NVMe SSD with OPAL 2.0

* '''WLAN:''' Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2

* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module

* '''WWAN:''' Fibocom L850-GL LTE-A

* '''Keyboard:''' 6-row with TrackPoint and ClickPad, illuminated keyboard keys

* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4
** Mini Ethernet jack with dongle for full-size Ethernet port
** 3.5mm Audio/Mic TRRS combo jack
** microSD card slot
** Micro SIM slot

* '''Camera options'''
** 720p HD webcam with noise-cancelling microphone and ThinkShutter webcam cover (selected models only)
** IR camera for Windows Hello (selected models only)

* '''Audio:''' Dolby® Audio™ Premium

* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader
** Kensington® lock slot

* '''Power'''
** USB Type-C charger
** 57Wh Li-ion battery with RapidCharge technology, up to 15 hours

* '''Physical Dimensions'''
** Size: 12.7in x 8.54in x 0.63in (324 x 217mm x 16.0mm)
** Weight: 2.49 lb (1.13 kg) / 3.30lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:T450s

2018-01-14T01:59:41Z

WilliamPoetra: â†Created page with '=== Machine Type === * Broadwell: 20BW, 20BX === Standard Features === Dimensions: * Size: ** Models without touchscreen: 331mm x 226mm x 20.6mm (13.0" x 8.90" x 0.8...'

=== Machine Type ===

* Broadwell: 20BW, 20BX

=== Standard Features ===

Dimensions:
* Size:
** Models without touchscreen: 331mm x 226mm x 20.6mm (13.0" x 8.90" x 0.81")
** Models with touchscreen: 331mm x 226mm x 22.9mm (13.0" x 8.90" x 0.90")
* Weight:
** Starts from 1.32kg (2.9lbs) with only external 3-cell Li-ion battery (23Wh)
** Discrete GPU option adds 0.24kg (0.53lbs)
** Internal battery option (3-cell Li-polymer, 23Wh) adds 0.11kg (0.24lbs)
** 6-cell external battery option (Li-ion, 48Wh) adds 0.18kg (0.40lbs)
** 6-cell external battery option (Li-ion, 72Wh) adds 0.18kg (0.40lbs)

Color:
* Black

Features:
* CPU: one of the following ULV processors
** Intel Core i5-5200U, 2.2 - 2.7 GHz, 3MB Cache
** Intel Core i5-5300U, 2.3 - 2.9 GHz, 3MB Cache
** Intel Core i7-5600U with vPro, 2.6 - 3.2 GHz, 4MB Cache

* RAM:
** 4GB DDR3L-1600 (PC3L-12800) soldered to the systemboard
** One free socket supporting up to 8GB DDR3L SO-DIMM

* GPU:
** Intel HD Graphics 5500 integrated into CPU

* Maximum supported resolution on external monitor:
** 3840x2160@60Hz via mDP
** 1920x1200@60Hz via VGA

* Display: one of the following IPS anti-glare displays with LED backlight, 700:1 contrast ratio and 160° viewing angle
** 14.0" 1600x900 ("HD+"), 250 nits, 400:1 contrast ratio
** 14.0" 1920x1080 ("FHD"), 300 nits, 700:1 contrast ratio
** Multitouch option available

* Storage: one of the following
** SATA 3 SSD, 7mm high
** SATA 3 HDD, 7mm / 9mm high
** SATA 3 SSHD
** Optional M.2 SSD

* M.2 slot with one of the following
** Thinkpad 11b/g/n 2x2 Wi-Fi + Bluetooth combo adapter
** Intel Wireless-N 7265 2x2 Wi-Fi + Bluetooth card
** Intel Dual Band Wireless-N 7265 2x2 Wi-Fi + Bluetooth card
** Intel Dual Band Wireless-N 7265 2x2 Wi-Fi + Bluetooth card

* M.2 slot with one of the following options
** Ericsson® N5321 WWAN card with HSPA+ 21Mbps/GSM/GPRS/EDGE and GPS
** Sierra Wireless EM7345 WWAN card with 4G LTE/HSPA/GSM/GPRS/EDGE and GPS

** Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455), LTE-Advanced/DC-HSPA+/HSPA+/HSPA/UMTS/GNSS

* SIM card slot

* Ethernet: one of the following
** Intel I219-V
** Intel I219-LM (vPro models)

* 720p HD [[Integrated camera]]

* Batteries:
** 3-cell internal Li-ion battery, 23Wh (option)
** 3-cell external Li-ion battery, 23Wh
** 6-cell external Li-ion battery, 48Wh (option)
** 6-cell external Li-ion battery, 72Wh (option)

* Power adapter: one of the following with slim Lenovo charging port
** 45W AC adapter
** 65W Slim AC adapter
** 65W AC adapter

* Security features
** Kensington lock slot
** TPM module
** [[Integrated Fingerprint Reader]] (optional)

* Pointing devices
** TrackPoint (with 3 physical buttons)
** UltraNav touch pad

=== Resources ===

* [http://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad%20T450s/ThinkPad_T450s_Platform_Specifications.pdf ThinkPad T450s Platform Specifications]

[[Category:T Series]]

Category:T470s

2018-01-13T18:20:34Z

WilliamPoetra: /* Resources */

=== Machine Type ===

* Kaby Lake: 20HF, 20HG
* Skylake: 20JS, 20JT

=== Standard Features ===

Dimensions:
* Size: 331mm x 227mm x 16.9-18.8mm (13.0" x 8.93" x 0.67-0.74")
* Weight: 1.32kg (2.9 lbs)

Color:
* Black
* Silver

Features:
* CPU: one of the following ULV processors
** Kaby Lake (20HF, 20HG)
*** Intel Core i5-7200U, 2.5 - 3.1 GHz, 3MB Cache
*** Intel Core i5-7300U, 2.6 - 3.5 GHz, 3MB Cache
*** Intel Core i7-7500U, 2.7 - 3.5 GHz, 4MB Cache
*** Intel Core i7-7600U, 2.8 - 3.9 GHz, 4MB Cache
** Skylake (20JS, 20JT)
*** Intel Core i5-6200U, 2.3 - 2.8 GHz, 3MB Cache
*** Intel Core i5-6300U, 2.4 - 3.0 GHz, 3MB Cache
*** Intel Core i7-6600U, 2.6 - 3.4 GHz, 4MB Cache

* RAM:
** 4GB or 8GB DDR4-2133 (PC4-17000) soldered to the systemboard
** One free socket supporting up to 16GB DDR4 SO-DIMM

* GPU:
** Kaby Lake-based: [[Intel HD620 Graphics]] integrated into CPU
** Skylake-based: [[Intel HD520 Graphics]] integrated into CPU

* Maximum supported resolution on external monitor:
** 4096x2304@60Hz via USB Type-C
** 4096x2160@24Hz via HDMI

* Display: one of the following IPS anti-glare displays with LED backlight, 700:1 contrast ratio and 160° viewing angle
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1 with multitouch
** 14.0" 2560x1440 ("WQHD"), 300 nits, 700:1

* Storage: one of the following installed in the M.2 slot
** SATA 3 SSD
** PCIe NVMe SSD

* M.2-2230 slot with one of the following, no SATA lanes:
** Intel Dual Band Wireless-AC 8260: 2x2 Wi-Fi 802.11ac, Bluetooth 4.1
** Intel Dual Band Wireless-AC 8265: 2x2 Wi-Fi 802.11ac with MU-MIMO, Bluetooth 4.1
** Intel Tri-Band Wireless-AC 18265: 2x2 Wi-Fi 802.11ac, WiGig 802.11ad, Bluetooth 4.1

* M.2-2242 slot with one of the following, no SATA lanes:
** Empty slot, if WiGig is available
** Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455), LTE-Advanced/DC-HSPA+/HSPA+/HSPA/UMTS/GNSS

* Micro-SIM card slot

* Ethernet: Intel I219-LM (vPro), Intel I219-V (non vPro)

* 720p HD [[Integrated camera]]

* Batteries: non-removable integrated batteries, total up to 10.5 hr
** Front: 23Wh 3-cell Li-Polymer
** Rear: 26Wh 3-cell Li-ion

* Power adapter: one of the following
** 45W AC adapter with USB Type-C
** 65W AC adapter with USB Type-C

* Security features
** Kensington lock slot
** dTPM 2.0
** [[Integrated Fingerprint Reader]] (optional)

* Pointing devices
** TrackPoint (with 3 physical buttons)
** UltraNav touch pad

=== Resources ===

* [http://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad%20T470s/ThinkPad_T470s_Platform_Specifications.pdf ThinkPad T470s Platform Specifications]

[[Category:T Series]]

Category:T480s

2018-01-13T18:20:18Z

WilliamPoetra:

=== Machine Type ===

xxx

=== Standard Features ===

Dimensions:
* Size: 331mm x 227mm x 18.5mm (13.0" x 8.93" x 0.72")
* Weight: 1.32kg (2.9 lbs)

Color:
* Black
* Silver

Features:
* CPU: one of the following ULV 8th-gen Intel Core processors
** Intel Core i7-8650U with vPro, 1.9 - 4.2 GHz, 8MB Cache

* RAM:
** 4GB or 8GB DDR4-2133 (PC4-17000) soldered to the systemboard
** One free socket supporting up to 16GB DDR4 SO-DIMM

* GPU:
** Intel UHD Graphics 620 integrated into CPU
** Nvidia MX150 with 2GB GDDR5 (optional)

* Maximum supported resolution on external monitor:
** 4096x2304@60Hz via USB Type-C
** 4096x2160@24Hz via HDMI

* Display: one of the following IPS anti-glare displays with LED backlight, 700:1 contrast ratio and 160° viewing angle
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1 with multitouch
** 14.0" 2560x1440 ("WQHD") FlexView, 300 nits, 700:1

* Storage: one of the following installed in the M.2 slot
** SATA 3 SSD
** PCIe NVMe SSD

* M.2-2230 slot with one of the following, no SATA lanes:
** Intel Dual Band Wireless-AC 8260: 2x2 Wi-Fi 802.11ac, Bluetooth 4.1
** Intel Dual Band Wireless-AC 8265: 2x2 Wi-Fi 802.11ac with MU-MIMO, Bluetooth 4.1
** Intel Tri-Band Wireless-AC 18265: 2x2 Wi-Fi 802.11ac, WiGig 802.11ad, Bluetooth 4.1

* M.2-2242 slot with one of the following, no SATA lanes:
** Empty slot, if WiGig is available
** Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455), LTE-Advanced/DC-HSPA+/HSPA+/HSPA/UMTS/GNSS

* Ethernet chip: Intel I219-LM (vPro), Intel I219-V (non vPro)

* 720p HD [[Integrated camera]] with ThinkShutter

* Battery: 57Wh

* Power adapter: one of the following
** 45W AC adapter with USB Type-C
** 65W AC adapter with USB Type-C

* Security features
** Kensington lock slot
** dTPM 2.0
** [[Integrated Fingerprint Reader]] (optional)

* Pointing devices
** TrackPoint (with 3 physical buttons)
** UltraNav touch pad

* I/O ports
** Intel Thunderbolt 3 (compatible with USB Type-C)
** USB Type-C (doubles as charging port)
** 2x USB 3.0
** MicroSD card reader
** TRRS headphone/microphone combo jack
** HDMI
** RJ45 Ethernet port
** Micro-SIM card slot

[[Category:T Series]]

Category:T480s

2018-01-13T18:19:29Z

WilliamPoetra: â†Created page with '=== Machine Type === xxx === Standard Features === Dimensions: * Size: 331mm x 227mm x 18.5mm (13.0" x 8.93" x 0.72") * Weight: 1.32kg (2.9 lbs) Color: * Black * S...'

=== Machine Type ===

xxx

=== Standard Features ===

Dimensions:
* Size: 331mm x 227mm x 18.5mm (13.0" x 8.93" x 0.72")
* Weight: 1.32kg (2.9 lbs)

Color:
* Black
* Silver

Features:
* CPU: one of the following ULV 8th-gen Intel Core processors
** Intel Core i7-8650U with vPro, 1.9 - 4.2 GHz, 8MB Cache

* RAM:
** 4GB or 8GB DDR4-2133 (PC4-17000) soldered to the systemboard
** One free socket supporting up to 16GB DDR4 SO-DIMM

* GPU:
** Intel UHD Graphics 620 integrated into CPU
** Nvidia MX150 with 2GB GDDR5 (optional)

* Maximum supported resolution on external monitor:
** 4096x2304@60Hz via USB Type-C
** 4096x2160@24Hz via HDMI

* Display: one of the following IPS anti-glare displays with LED backlight, 700:1 contrast ratio and 160° viewing angle
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1 with multitouch
** 14.0" 2560x1440 ("WQHD") FlexView, 300 nits, 700:1

* Storage: one of the following installed in the M.2 slot
** SATA 3 SSD
** PCIe NVMe SSD

* M.2-2230 slot with one of the following, no SATA lanes:
** Intel Dual Band Wireless-AC 8260: 2x2 Wi-Fi 802.11ac, Bluetooth 4.1
** Intel Dual Band Wireless-AC 8265: 2x2 Wi-Fi 802.11ac with MU-MIMO, Bluetooth 4.1
** Intel Tri-Band Wireless-AC 18265: 2x2 Wi-Fi 802.11ac, WiGig 802.11ad, Bluetooth 4.1

* M.2-2242 slot with one of the following, no SATA lanes:
** Empty slot, if WiGig is available
** Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455), LTE-Advanced/DC-HSPA+/HSPA+/HSPA/UMTS/GNSS

* Ethernet chip: Intel I219-LM (vPro), Intel I219-V (non vPro)

* 720p HD [[Integrated camera]] with ThinkShutter

* Battery: 57Wh

* Power adapter: one of the following
** 45W AC adapter with USB Type-C
** 65W AC adapter with USB Type-C

* Security features
** Kensington lock slot
** dTPM 2.0
** [[Integrated Fingerprint Reader]] (optional)

* Pointing devices
** TrackPoint (with 3 physical buttons)
** UltraNav touch pad

* I/O ports
** Intel Thunderbolt 3 (compatible with USB Type-C)
** USB Type-C (doubles as charging port)
** 2x USB 3.0
** MicroSD card reader
** TRRS headphone/microphone combo jack
** HDMI
** RJ45 Ethernet port
** Micro-SIM card slot

=== Resources ===

* [http://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad%20T470s/ThinkPad_T470s_Platform_Specifications.pdf ThinkPad T460s Platform Specifications]

[[Category:T Series]]

Category:X1 Carbon (6th Gen)

2018-01-13T17:23:58Z

WilliamPoetra:

The Thinkpad X1 Carbon 6th Generation is based on the Intel Kaby Lake R microarchitecture and released in January 2018. It comes in black and silver.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]], [[:Category:X1 Carbon (5th Gen)|2017]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}

* '''Machine type:'''

* '''Processor:''' One of the following 8th generation ULV [[Intel Core]] processors (code name: "Kaby Lake R", 14nm)
** Intel® Core™ i7-8650U (1.9-4.2GHz, 4MB L3 cache)

* '''Graphics:''' [[Intel HD Graphics|Intel® UHD Graphics 620]]

* '''Display:''' Matte IPS screen with
** 14.0" FHD (1920x1080), 300 nits
** 14.0" FHD (1920x1080), 300 nits with touchscreen
** 14.0" WQHD (2560x1440), 300 nits
** 14.0" WQHD (2560x1440), 500 nits with Dolby Vision™ HDR

* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 16GB LPDDR3-2133 (PC3L-17000)

* '''Storage:''' One of the following connected to the M.2 port
** 1TB TLC NVMe SSD with OPAL 2.0

* '''WLAN:''' Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2

* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module

* '''WWAN:''' Fibocom L850-GL LTE-A

* '''Keyboard:''' 6-row with TrackPoint and ClickPad, illuminated keyboard keys

* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4
** Mini Ethernet jack with dongle for full-size Ethernet port
** 3.5mm Audio/Mic TRRS combo jack
** microSD card slot
** Micro SIM slot

* '''Camera options'''
** 720p HD webcam with noise-cancelling microphone and ThinkShutter webcam cover (selected models only)
** IR camera for Windows Hello (selected models only)

* '''Audio:''' Dolby® Audio™ Premium

* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader
** Kensington® lock slot

* '''Power'''
** USB Type-C charger
** 57Wh Li-ion battery with RapidCharge technology, up to 15 hours

* '''Physical Dimensions'''
** Size: 12.7in x 8.54in x 0.63in (324 x 217mm x 16.0mm)
** Weight: 2.49 lb (1.13 kg) / 3.30lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon (5th Gen)

2018-01-13T17:22:15Z

WilliamPoetra:

The Thinkpad X1 Carbon 5th Generation is based on the Intel Kaby Lake microarchitecture and released in early 2017.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}

* '''Machine type:'''
** Kaby Lake: 20HQ, 20HR
** Skylake: 20K3, 20K4

* '''Processor:'''
** 20HQ, 20HR: one of the following ULV 7th generation Intel Core processors (code name: "Kaby Lake", 14nm)
*** Intel® Core™ i5-7200U (2.5-3.1GHz, 3MB L3 cache)
*** Intel® Core™ i5-7300U (2.6-3.5GHz, 3MB L3 cache)
*** Intel® Core™ i7-7500U (2.7-3.5GHz, 4MB L3 cache)
*** Intel® Core™ vPro™ i7-7600U (2.8-3.9GHz, 4MB L3 cache)
** 20K3, 20K4: one of the following ULV 6th generation Intel Core processors (code name: "Skylake", 14nm)
*** Intel® Core™ i5-6200U (2.3-2.8GHz, 3MB L3 cache)
*** Intel® Core™ i5-6300U (2.4-3.0GHz, 3MB L3 cache)
*** Intel® Core™ i7-6500U (2.5-3.1GHz, 4MB L3 cache)
*** Intel® Core™ vPro™ i7-6600U (2.6-3.4GHz, 4MB L3 cache)

* '''Graphics:'''
** 20HQ, 20HR: [[Intel HD Graphics|Intel® HD Graphics 620]]
** 20K3, 20K4: [[Intel HD Graphics|Intel® HD Graphics 520]]

* '''Display:''' Matte anti-glare IPS screen with 700:1 contrast ratio and 170° viewing angle
** 14.0" FHD (1920x1080), 300 nits
** 14.0" WQHD (2560x1440), 300 nits (available from mid-2017)

* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 8GB LPDDR3-1866 (PC3L-14900)
** 16GB LPDDR3-1866 (PC3L-14900)

* '''Storage:''' One of the following connected to the M.2 port
** 128GB M.2 SATA SSD (SanDisk X400, maybe others)
** 256GB NVMe SSD with OPAL 2.0
** 512GB Samsung PM961 NVMe SSD with OPAL 2.0
** 1TB NVMe SSD with OPAL 2.0

* '''WLAN:''' One of the following cards
** Intel® Dual Band Wireless-AC 8260 2x2 with Bluetooth 4.2
** Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2
** Intel® Tri-Band Wireless-AC 18265 2x2 with WiGig 802.11ad and Bluetooth 4.2

* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module

* '''WWAN:''' Qualcomm® Snapdragon™ X7 LTE-A / Sierra Wireless EM7455 (WWAN is available but must be configured at purchase, otherwise there is no WWAN antenna provided)

* '''Keyboard:''' 6-row with TrackPoint and ClickPad, illuminated keyboard keys

* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support, external monitor up to 4096x2304@60Hz
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4b, supports up to 4096x2160@24Hz
** Mini Ethernet jack
** 3.5mm Audio/Mic combo jack
** microSD card slot
** Micro-SIM slot

* '''Battery:''' 3-cell Li-Poly battery (57Wh), up to 15.5 hours

* '''AC Adapter:'''
** 45W USB Type-C AC adapter
** 65W USB Type-C AC adapter with RapidCharge support (80% in 1 hr, 100% in 2.5 hrs)

* '''Webcam:''' 720p HD webcam with microphone

* '''Audio:''' Dolby® Audio™ Premium

* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader

* '''Physical Dimensions'''
** Size: 12.7in x 8.54in x 0.63in (324 x 217mm x 16.0mm)
** Weight: 2.49 lb (1.13 kg) / 3.30lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:T470s

2018-01-13T17:05:50Z

WilliamPoetra:

=== Machine Type ===

* Kaby Lake: 20HF, 20HG
* Skylake: 20JS, 20JT

=== Standard Features ===

Dimensions:
* Size: 331mm x 227mm x 16.9-18.8mm (13.0" x 8.93" x 0.67-0.74")
* Weight: 1.32kg (2.9 lbs)

Color:
* Black
* Silver

Features:
* CPU: one of the following ULV processors
** Kaby Lake (20HF, 20HG)
*** Intel Core i5-7200U, 2.5 - 3.1 GHz, 3MB Cache
*** Intel Core i5-7300U, 2.6 - 3.5 GHz, 3MB Cache
*** Intel Core i7-7500U, 2.7 - 3.5 GHz, 4MB Cache
*** Intel Core i7-7600U, 2.8 - 3.9 GHz, 4MB Cache
** Skylake (20JS, 20JT)
*** Intel Core i5-6200U, 2.3 - 2.8 GHz, 3MB Cache
*** Intel Core i5-6300U, 2.4 - 3.0 GHz, 3MB Cache
*** Intel Core i7-6600U, 2.6 - 3.4 GHz, 4MB Cache

* RAM:
** 4GB or 8GB DDR4-2133 (PC4-17000) soldered to the systemboard
** One free socket supporting up to 16GB DDR4 SO-DIMM

* GPU:
** Kaby Lake-based: [[Intel HD620 Graphics]] integrated into CPU
** Skylake-based: [[Intel HD520 Graphics]] integrated into CPU

* Maximum supported resolution on external monitor:
** 4096x2304@60Hz via USB Type-C
** 4096x2160@24Hz via HDMI

* Display: one of the following IPS anti-glare displays with LED backlight, 700:1 contrast ratio and 160° viewing angle
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1 with multitouch
** 14.0" 2560x1440 ("WQHD"), 300 nits, 700:1

* Storage: one of the following installed in the M.2 slot
** SATA 3 SSD
** PCIe NVMe SSD

* M.2-2230 slot with one of the following, no SATA lanes:
** Intel Dual Band Wireless-AC 8260: 2x2 Wi-Fi 802.11ac, Bluetooth 4.1
** Intel Dual Band Wireless-AC 8265: 2x2 Wi-Fi 802.11ac with MU-MIMO, Bluetooth 4.1
** Intel Tri-Band Wireless-AC 18265: 2x2 Wi-Fi 802.11ac, WiGig 802.11ad, Bluetooth 4.1

* M.2-2242 slot with one of the following, no SATA lanes:
** Empty slot, if WiGig is available
** Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455), LTE-Advanced/DC-HSPA+/HSPA+/HSPA/UMTS/GNSS

* Micro-SIM card slot

* Ethernet: Intel I219-LM (vPro), Intel I219-V (non vPro)

* 720p HD [[Integrated camera]]

* Batteries: non-removable integrated batteries, total up to 10.5 hr
** Front: 23Wh 3-cell Li-Polymer
** Rear: 26Wh 3-cell Li-ion

* Power adapter: one of the following
** 45W AC adapter with USB Type-C
** 65W AC adapter with USB Type-C

* Security features
** Kensington lock slot
** dTPM 2.0
** [[Integrated Fingerprint Reader]] (optional)

* Pointing devices
** TrackPoint (with 3 physical buttons)
** UltraNav touch pad

=== Resources ===

* [http://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad%20T470s/ThinkPad_T470s_Platform_Specifications.pdf ThinkPad T460s Platform Specifications]

[[Category:T Series]]

Category:T470s

2018-01-13T17:02:31Z

WilliamPoetra: â†Created page with '=== Machine Type === * 20HF, 20HG, 20JS, 20JT === Standard Features === Dimensions: * Size: 331mm x 227mm x 16.9-18.8mm (13.0" x 8.93" x 0.67-0.74") * Weight: 1.32kg...'

=== Machine Type ===
* 20HF, 20HG, 20JS, 20JT

=== Standard Features ===

Dimensions:
* Size: 331mm x 227mm x 16.9-18.8mm (13.0" x 8.93" x 0.67-0.74")
* Weight: 1.32kg (2.9 lbs)

Color:
* Black
* Silver

Features:
* CPU: One of the following ULV processors:
** Kaby Lake (20HF, 20HG)
*** Intel Core i5-7200U, 2.5 - 3.1 GHz, 3MB Cache
*** Intel Core i5-7300U, 2.6 - 3.5 GHz, 3MB Cache
*** Intel Core i7-7500U, 2.7 - 3.5 GHz, 4MB Cache
*** Intel Core i7-7600U, 2.8 - 3.9 GHz, 4MB Cache
** Skylake (20JS, 20JT)
*** Intel Core i5-6200U, 2.3 - 2.8 GHz, 3MB Cache
*** Intel Core i5-6300U, 2.4 - 3.0 GHz, 3MB Cache
*** Intel Core i7-6600U, 2.6 - 3.4 GHz, 4MB Cache

* RAM:
** 4GB or 8GB DDR4-2133 (PC4-17000) soldered to the systemboard
** One free socket supporting up to 16GB DDR4 SO-DIMM

* GPU:
** Kaby Lake-based: [[Intel HD620 Graphics]] integrated into CPU
** Skylake-based: [[Intel HD520 Graphics]] integrated into CPU

* Maximum supported resolution on external monitor:
** 4096x2304@60Hz via USB Type-C
** 4096x2160@24Hz via HDMI

* One of the following IPS anti-glare displays with LED backlight, 700:1 contrast ratio and 160° viewing angle:
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1
** 14.0" 1920x1080 ("FHD"), 250 nits, 700:1 with multitouch
** 14.0" 2560x1440 ("WQHD"), 300 nits, 700:1

* Storage: one of the following installed in the M.2 slot
** SATA 3 SSD
** PCIe NVMe SSD

* M.2-2230 slot with one of the following, no SATA lanes:
** Intel Dual Band Wireless-AC 8260: 2x2 Wi-Fi 802.11ac, Bluetooth 4.1
** Intel Dual Band Wireless-AC 8265: 2x2 Wi-Fi 802.11ac with MU-MIMO, Bluetooth 4.1
** Intel Tri-Band Wireless-AC 18265: 2x2 Wi-Fi 802.11ac, WiGig 802.11ad, Bluetooth 4.1

* M.2-2242 slot with one of the following, no SATA lanes:
** Empty Slot, if WiGig is available
** Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455), LTE-Advanced/DC-HSPA+/HSPA+/HSPA/UMTS/GNSS

* Micro-SIM card slot

* Ethernet: Intel I219-LM (vPro), Intel I219-V (non vPro)

* 720p HD [[Integrated camera]]

* Batteries: non-removable integrated batteries, total up to 10.5 hr
** Front: 23Wh 3-cell Li-Polymer
** Rear: 26Wh 3-cell Li-ion

* Power adapter: one of the following
** 45W AC adapter with USB Type-C
** 65W AC adapter with USB Type-C

* Security features
** Kensington lock slot
** dTPM 2.0
** [[Integrated Fingerprint Reader]] (optional)

* Pointing devices
** TrackPoint (with 3 physical buttons)
** UltraNav touch pad

=== Resources ===

* [http://psref.lenovo.com/syspool/Sys/PDF/ThinkPad/ThinkPad%20T470s/ThinkPad_T470s_Platform_Specifications.pdf ThinkPad T460s Platform Specifications]

[[Category:T Series]]

Category:X1 Carbon (6th Gen)

2018-01-13T16:23:55Z

WilliamPoetra: â†Created page with 'The Thinkpad X1 Carbon 6th Generation is based on the Intel Kaby Lake R microarchitecture and released in January 2018. It comes in black and silver. Previous generati...'

The Thinkpad X1 Carbon 6th Generation is based on the Intel Kaby Lake R microarchitecture and released in January 2018. It comes in black and silver.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]], [[:Category:X1 Carbon (5th Gen)|2017]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}
* '''Machine type:'''
* '''Processor:''' One of the following 8th generation ULV [[Intel Core]] processors (code name: "Kaby Lake R", 14nm)
** Intel® Core™ i7-8650U (1.9-4.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel® UHD Graphics 620]]
* '''Display:''' Matte IPS screen with
** 14.0" FHD (1920x1080), 300 nits
** 14.0" FHD (1920x1080), 300 nits with touchscreen
** 14.0" WQHD (2560x1440), 300 nits
** 14.0" WQHD (2560x1440), 500 nits with Dolby Vision™ HDR
* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 16GB LPDDR3-2133 (PC3L-17000)
* '''Storage:''' One of the following connected to the M.2 port
** 1TB TLC NVMe SSD with OPAL 2.0
* '''WLAN:''' Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2
* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module
* '''WWAN:''' Fibocom L850-GL LTE-A
* '''Keyboard:''' 5-row with TrackPoint and ClickPad, illuminated keyboard keys
* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4
** Mini Ethernet jack with dongle for full-size Ethernet port
** 3.5mm Audio/Mic TRRS combo jack
** microSD card slot
** Micro SIM slot
* '''Camera options'''
** 720p HD webcam with noise-cancelling microphone and ThinkShutter webcam cover (selected models only)
** IR camera for Windows Hello (selected models only)
* '''Audio:''' Dolby® Audio™ Premium
* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader
** Kensington® lock slot
* '''Power'''
** USB Type-C charger
** 57Wh Li-ion battery with RapidCharge technology, up to 15 hours
* '''Physical Dimensions'''
** Size: 12.7in x 8.54in x 0.63in (324 x 217mm x 16.0mm)
** Weight: 2.49 lb (1.13 kg) / 3.30lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon

2018-01-13T15:41:29Z

WilliamPoetra:

=== ThinkPad X1 Carbon ===
This page gives an overview of the ThinkPad {{X1 Carbon}} (2012).

The following generations of ThinkPad X1 Carbon exist:
* {{X1 Carbon}}: ThinkPad X1 Carbon (Type 34xx), 1st generation, appeared in 2012
* {{X1 Carbon 2nd}}: ThinkPad X1 Carbon 2nd (Type 20A7, 20A8), 2nd generation, appeared in 2014, known also as "Lenovo New Thinkpad X1 Carbon".
* [[:Category:X1 Carbon (3rd Gen) | X1 Carbon (3rd Gen)]]: ThinkPad X1 Carbon 3rd (Type 20BS, 20BT), 3rd generation, released in 2015.
* [[:Category:X1 Carbon (4th Gen) | X1 Carbon (4th Gen)]]: ThinkPad X1 Carbon 4th (Type 20FB, 20FC), 4th generation, released in 2016.
* [[:Category:X1 Carbon (5th Gen) | X1 Carbon (5th Gen)]]: ThinkPad X1 Carbon 5th (Type 20HQ, 20HR), 5th generation, released in 2017.
* [[:Category:X1 Carbon (6th Gen) | X1 Carbon (6th Gen)]]: ThinkPad X1 Carbon 6th generation, released in 2018.

==== Details ====
* '''Machine type:''' 34xx
* '''Processor:''' One of the following ULV 3rd generation Intel Core processors (code name: "Ivy Bridge"):
** Intel® Core™ i5-3317U (1.7-2.6GHz, 3MB L3 cache)
** Intel® Core™ i5-3337U (1.8-2.7GHz, 3MB L3 cache)
** Intel® Core™ i5-3427U (1.8-2.8GHz, 3MB L3 cache)
** Intel® Core™ i7-3667U (2.0-3.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 4000]]
* '''Display:'''
** 14.0" HD+ Matte screen (1600x900)
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1600 MHz
** 8GB DDR3L SDRAM 1600 MHz
* '''Disk:'''
** 128GB SSD
** 250GB SSD
** 256GB SSD
* '''WLAN:'''
** Intel 801.11b/g/n
* '''WWAN:''' TODO
* '''Bluetooth:''' TODO
* '''Keyboard:''' TODO
* '''I/O Ports:'''
** 1 x USB 2.0, 1 x USB 3.0
** Mini DisplayPort
** SD Card Slot
* '''Battery:''' Up to 6.3 hours
* '''Webcam:''' [[Integrated camera]] 1.3MP (720p)
* '''Audio:'''
* Size: 13.03in x 8.90in x 0.74in (331mm x 226mm x 19mm)
* Weight: 3.00 lb (1.36 kg)

[[Category:X_Series]]

Category:X230

2017-08-08T16:41:46Z

WilliamPoetra:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

=== ThinkPad X230 ===
This page gives an overview of the ThinkPad X230.

==== Features ====
*One of the following [[Ivy Bridge]] processors (third generation Intel Core series):
** Intel Core i7-3520M (2.90 GHz, 4MB L3, 1600MHz FSB)
** Intel Core i5-3360M (2.80 GHz, 3MB L3, 1600MHz FSB)
** Intel Core i5-3320M (2.60 GHz, 3MB L3, 1600MHz FSB)

* [[Intel HD Graphics]] 3000 or 4000
* Up to 16GB [[PC3-10600]] DDR3 memory at 1600MHz

* One of the following [[TFT display|TFT displays]]:
** 12.5" TN TFT display with 1366x768 resolution with LED backlight
** 12.5" extra bright wide-viewing IPS TFT display with 1366x768 resolution with LED backlight
* 2.5" × [[7mm hard drive bay]] with one of the following hard drives:
** 500GB (5400rpm) SATA
** 320GB/500GB (7200rpm) SATA
** 128GB SSD SATA3
** Intel® 180GB SSD SATA3

* [[MiniPCI Express slot]] 1 with zero or one of the following:
** 10/100/1000 Ethernet
** ThinkPad b/g/n Wireless (1×1 BGN)
** Intel Centrino Wireless-N 2200 (2×2 BGN)
** Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) (2×2 AGN)

* [[MiniPCI Express slot]] 2 with zero or one of the following:
**Qualcomm® Gobi™ 4k LTE VzW/HSPA
**Qualcomm® Gobi™ 3K 14.4Mbps/HSPA
**[[Ericsson H5321 gw Mobile Broadband Module]] HSPA+ WWAN Minicard

* [[ExpressCard slot|ExpressCard/54 slot]]
* [[SD Card slot]]
* Three USB ports:
** Two on the left are [[USB 3.0]]
** One on the right is [[USB 2.0]], powered (BIOS-selectable: on even when system off, on when suspended, off)

* 720p HD [[Integrated camera]] (04f2:b2eb Chicony Electronics Co., Ltd) or 3x3 Antenna Grid
* Stereo digital microphones
* Stereo speakers
* Combined headphone and microphone jack

* [[UltraNav]] ([[Trackpoint]] and [[Buttonless Touchpad]])
* Optional [[Integrated Fingerprint Reader]] (UPEK, model ID 147e:2020, not yet supported [Dec 2012])
* Comes with 65W AC Adapter (0.5lb / 230g)
* Supports [[ThinkPad UltraBase Series 3]], [[ThinkPad Mini Dock Series 3]], etc.

* Size: 12.0in x 8.1in x 0.75-1.05in (305mm x 207mm x 19-27mm)
* Weight: 2.98 lb (1.35 kg) with 6-cell battery
</div>
|style="vertical-align:top" |
[[Image:ThinkPadX230.png|ThinkPad X230|300px]]
|}

=== Resources ===
* [https://support.lenovo.com/en_US/detail.page?DocID=UM014928 X230 Hardware maintenance manual]

* It's possible to use a [[7mm_hard_drive_bay#mSata_SSD| mSATA SSD within the second MiniPCI Express slot]]:
** The device will show up at /dev/sdb and can be booted from
** Keep in mind the Hardware maintenance manual includes this warning: "If the computer is equipped with both a hard disk drive and an mSATA solid-state drive, do not use the mSATA solid-state drive as a bootable device. The mSATA solid-state drive is used for the “cache” function only."

[[Category:X Series]]

Category:X61s

2017-04-23T11:53:16Z

WilliamPoetra:

{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

=== ThinkPad X61s ===
This page gives an overview of the ThinkPad X61s.

==== Standard Features ====
* '''Machine type:''' 7668, 7669
* '''Processor:''' One of the following low-voltage processors:
** [[Intel Core 2 Duo]] CPU L7300 @ 1.40 GHz
** [[Intel Core 2 Duo]] CPU L7500 @ 1.60 GHz
** [[Intel Core 2 Duo]] CPU L7700 @ 1.80 GHz
* '''Graphics:''' [[Intel Graphics Media Accelerator X3100]]
* '''Display:''' Matte 12.1" TFT display with 1024x768 resolution, 180 nits
* '''Memory:''' 2 slots upgradable to 4GB, with the following standard choices
** 1GB DDR2 [[PC2-5300]]
** 2GB DDR2 [[PC2-5300]]
* '''Storage:''' One of the following SATA HDDs
** 100GB 7k100 Hitachi 7200 RPM
** 120GB, [..] SATA HDD
* [[Active Protection System]]
* '''Audio:''' Intel HD Audio with [[AD1984]] codec
* '''Ethernet:''' [[Intel Gigabit Ethernet (10/100/1000) PCI-Express]]
* '''WLAN:'''
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** [[Intel PRO/Wireless 4965AGN Mini-PCI Express Adapter]]
* '''Security:'''
** [[Embedded Security Subsystem|Trusted Computing Group TPM 1.2]]
** [[Integrated Fingerprint Reader]] in some models
* '''I/O Ports:'''
** 3x USB 2.0 Ports
** VGA port
** RJ-45 Ethernet jack
** RJ-11 Modem jack
** 3.5mm Headphone jack
** 3.5mm Microphone jack
** [[SD Card slot]] with IO support
** [[CardBus slot]] (Type 2)
** 4-pin [[Firewire Port|Firewire 400]] (IEEE1394a) port
* '''Dimensions:''' 268 x 211 x 20-28 mm (10.5 x 8.3 x 0.8-1.1")
* '''Weight:'''
** with 4-cell prismatic:
** with 4-cell cylindrical: 1.41 kg (3.11 lb)
** with 8-cell cylindrical: 1.63 kg (3.56 lb)
</div>
|style="vertical-align:top" |
[[Image:X61s.jpg|ThinkPad X61s|300px]]
|}

==== Resources ====
* [https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42x3550_03.pdf X61s Tablet Hardware Maintenance Manual]

[[Category:X Series]]

Category:X1 Carbon (4th Gen)

2017-04-17T16:04:26Z

WilliamPoetra: /* Details */

This page gives an overview of the Lenovo New ThinkPad X1 Carbon Ultrabook™ (4th Gen) (2016), also referred to as '''X1C4'''.<br/>
previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon 3rd|2015]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}
* '''Machine type:''' 20FB*, 20FC*
* '''Processor:''' One of the following ULV sixth generation [[Intel Core]] processors (code name: "Skylake", 14nm)
** Intel® Core™ i5-6200U (2.3-2.8GHz, 3MB L3 cache)
** Intel® Core™ i5-6300U with vPro™ (2.4-3.0GHz, 3MB L3 cache)
** Intel® Core™ i7-6500U (2.5-3.1GHz, 4MB L3 cache)
** Intel® Core™ i7-6600U with vPro™ (2.6-3.4GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel® HD Graphics 520]]
* '''Display:''' Matte IPS screen with
** 14.0" FHD (1920x1080), 300 nits
** 14.0" WQHD (2560x1440), 300 nits
* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 4GB LPDDR3 PC3-14900
** 8GB LPDDR3 PC3-14900
** 16GB LPDDR3 PC3-14900
* '''Storage:''' One of the following connected to the M.2 port
** 128GB M.2 SATA III SSD
** 180GB M.2 SATA III SSD with OPAL 2.0
** 192GB M.2 SATA III SSD
** 240GB M.2 SATA III SSD with OPAL 2.0
** 256GB Samsung PM871 M.2 SATA SSD with OPAL 2.0
** 256GB PCIE NVMe SSD with OPAL 2.0
** 512GB M.2 SATA III SSD
** 512GB PCIe NVMe SSD
** 1TB PCIe NVMe SSD
* '''WLAN:''' Intel® Dual Band Wireless-AC 8260 2x2 with Bluetooth 4.2
* '''WWAN:''' Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455) with UMTS / HSPA+ / LTE Cat.6
* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module
* '''Keyboard:''' 5-row with TrackPoint and ClickPad, illuminated keyboard keys
* '''I/O Ports:'''
** 3 x USB Type-A with USB 3.0 support
** OneLink+
** Mini DisplayPort 1.2
** HDMI 1.4
** 3.5mm Audio/Mic combo jack
** microSD card slot
** SIM slot
* '''Battery:''' 4-cell Li-Poly battery (52Wh), up to 11 hours
* '''Webcam:''' 720p HD webcam with microphone
* '''Security'''
** TPM TCG 1.2
** Kensington Lock
** Fingerprint reader
* '''Physical Dimensions'''
** Size: 13.1in x 9.0in x 0.65in (333mm x 229mm x 16.5mm)
** Weight: 2.64 lb (1.20 kg) / 3.40 lb (1.54 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon (4th Gen)

2017-04-17T15:53:53Z

WilliamPoetra:

This page gives an overview of the Lenovo New ThinkPad X1 Carbon Ultrabook™ (4th Gen) (2016), also referred to as '''X1C4'''.<br/>
previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon 3rd|2015]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}
* '''Machine type:''' 20FB*, 20FC*
* '''Processor:''' One of the following ULV sixth generation [[Intel Core]] processors (code name: "Skylake", 14nm)
** Intel® Core™ i5-6200U (2.3-2.8GHz, 3MB L3 cache)
** Intel® Core™ i5-6300U with vPro™ (2.4-3.0GHz, 3MB L3 cache)
** Intel® Core™ i7-6500U (2.5-3.1GHz, 4MB L3 cache)
** Intel® Core™ i7-6600U with vPro™ (2.6-3.4GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel® HD Graphics 520]]
* '''Display:''' Matte IPS screen with
** 14.0" FHD (1920x1080), 300 nits
** 14.0" WQHD (2560x1440), 300 nits
* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 4GB LPDDR3 PC3-14900
** 8GB LPDDR3 PC3-14900
** 16GB LPDDR3 PC3-14900
* '''Storage:''' One of the following connected to the M.2 port
** 128GB M.2 SATA III SSD
** 180GB M.2 SATA III SSD with OPAL 2.0
** 256GB M.2 SATA III SSD with OPAL 2.0
** 256GB Samsung PM871 M.2 SATA SSD with OPAL 2.0
** 512GB M.2 SATA III SSD
** 1TB PCIe NVMe SSD
* '''WLAN:''' Intel® Dual Band Wireless-AC 8260 2x2 with Bluetooth 4.2
* '''WWAN:''' Qualcomm Snapdragon X7 LTE-A (Sierra Wireless EM7455) with UMTS / HSPA+ / LTE Cat.6
* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module
* '''Keyboard:''' 5-row with TrackPoint and ClickPad, illuminated keyboard keys
* '''I/O Ports:'''
** 3 x USB Type-A with USB 3.0 support
** OneLink+
** Mini DisplayPort 1.2
** HDMI 1.4
** 3.5mm Audio/Mic combo jack
** microSD card slot
** SIM slot
* '''Battery:''' 4-cell Li-Poly battery (52Wh), up to 11 hours
* '''Webcam:''' 720p HD webcam with microphone
* '''Security'''
** TPM TCG 1.2
** Kensington Lock
** Fingerprint reader
* '''Physical Dimensions'''
** Size: 13.1in x 9.0in x 0.65in (333mm x 229mm x 16.5mm)
** Weight: 2.64 lb (1.20 kg) / 3.40 lb (1.54 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon (5th Gen)

2017-04-12T18:02:29Z

WilliamPoetra: /* Details */

The Thinkpad X1 Carbon 5th Generation is based on the Intel Kaby Lake microarchitecture and released in early 2017.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}
* '''Machine type:''' 20HQ*, 20HR*
* '''Processor:''' One of the following ULV seventh generation [[Intel Core]] processors (code name: "Kaby Lake", 14nm)
** Intel® Core™ i5-7200U (2.5-3.1GHz, 3MB L3 cache)
** Intel® Core™ i5-7300U (2.6-3.5GHz, 3MB L3 cache)
** Intel® Core™ i7-7500U (2.7-3.5GHz, 4MB L3 cache)
** Intel® Core™ vPro™ i7-7600U (2.8-3.9GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel® HD Graphics 620]]
* '''Display:''' Matte IPS screen with
** 14.0" FHD (1920x1080), 300 nits
** 14.0" WQHD (2560x1440), 300 nits (available from mid-2017)
* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 8GB LPDDR3 PC3-14900
** 16GB LPDDR3 SDRAM PC3-14900
* '''Storage:''' One of the following connected to the M.2 port
** 128GB M.2 SATA SSD
** 256GB NVMe SSD with OPAL 2.0
** 512GB Samsung PM961 NVMe SSD with OPAL 2.0
** 1TB NVMe SSD with OPAL 2.0
* '''WLAN:''' Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2
* '''WWAN:''' Qualcomm® Snapdragon™ X7 LTE-A / Sierra Wireless EM7455 (WWAN is available but must be configured at purchase, otherwise there is no WWAN antenna provided)
* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module
* '''Keyboard:''' 5-row with TrackPoint and ClickPad, illuminated keyboard keys
* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4
** Mini Ethernet jack
** 3.5mm Audio/Mic combo jack
** microSD card slot
** Micro SIM slot
* '''Battery:''' 3-cell Li-Poly battery (57Wh), up to 15.5 hours
* '''Webcam:''' 720p HD webcam with microphone
* '''Audio:''' Dolby® Audio™ Premium
* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader
* '''Physical Dimensions'''
** Size: 12.7in x 8.5in x 0.63in (324 x 217mm x 16.0mm)
** Weight: 2.52 lb (1.14 kg) / 3.30lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon (5th Gen)

2017-04-12T17:54:50Z

WilliamPoetra:

The Thinkpad X1 Carbon 5th Generation is based on the Intel Kaby Lake microarchitecture and released in early 2017.

Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]], [[:Category:X1 Carbon (3rd Gen)|2015]], [[:Category:X1 Carbon (4th Gen)|2016]]

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}
* '''Machine type:''' 20HQ*, 20HR*
* '''Processor:''' One of the following ULV seventh generation [[Intel Core]] processors (code name: "Kaby Lake", 14nm)
** Intel® Core™ i5-7200U (2.5-3.1GHz, 3MB L3 cache)
** Intel® Core™ i5-7300U (2.6-3.5GHz, 3MB L3 cache)
** Intel® Core™ i7-7500U (2.7-3.5GHz, 4MB L3 cache)
** Intel® Core™ vPro™ i7-7600U (2.8-3.9GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel® HD Graphics 620]]
* '''Display:''' Matte IPS screen with
** 14.0" FHD (1920x1080), 300 nits
** 14.0" WQHD (2560x1440), 300 nits (available from mid-2017)
* '''Memory:''' Soldered directly on the mainboard, with the following choices
** 8GB LPDDR3 PC3-14900
** 16GB LPDDR3 SDRAM PC3-14900
* '''Storage:''' One of the following connected to the M.2 port
** 128GB M.2 SATA SSD
** 256GB NVMe SSD with OPAL 2.0
** 512GB Samsung PM961 NVMe SSD with OPAL 2.0
** 1TB NVMe SSD with OPAL 2.0
* '''WLAN:''' Intel® Dual Band Wireless-AC 8265 2x2 with Bluetooth 4.2
* '''WWAN:''' Qualcomm® Snapdragon™ X7 LTE-A / Sierra Wireless EM7455 (WWAN is available but must be configured at purchase, otherwise there is no WWAN antenna provided)
* '''Bluetooth:''' Bluetooth 4.2 integrated within WLAN module
* '''Keyboard:''' 5-row with TrackPoint and ClickPad, illuminated keyboard keys
* '''I/O Ports:'''
** 2 x USB Type-C with Thunderbolt 3 and USB 3.1 support
** 2 x USB Type-A with USB 3.1 support
** HDMI 1.4
** Mini Ethernet jack
** 3.5mm Audio/Mic combo jack
** microSD card slot
** Micro SIM slot
* '''Battery:''' 3-cell Li-Poly battery (57Wh), up to 15.5 hours
* '''Webcam:''' 720p HD webcam with microphone
* '''Audio:''' Dolby® Audio™ Premium
* '''Security'''
** TPM module (dTPM 2.0)
** Fingerprint reader
* '''Physical Dimensions'''
** Size: 12.7in x 8.5in x 0.6in (324 x 217mm x 16mm)
** Weight: 2.52 lb (1.14 kg) / 3.3lb (1.50 kg) with power supply

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon (5th Gen)

2017-04-12T17:49:01Z

WilliamPoetra:

Category:X1 Carbon (5th Gen)

2017-04-12T17:42:09Z

WilliamPoetra:

Category:X1 Carbon (3rd Gen)

2017-04-12T17:20:23Z

WilliamPoetra:

This page gives an overview of the Lenovo New ThinkPad X1 Carbon Ultrabook™ (3rd Gen) (2015), also referred to as '''X1C3'''.<br/>
Previous generations: [[:Category:X1 Carbon|2012]], [[:Category:X1 Carbon 2nd|2014]]
{{QUOTE|Jonas Hendrickx|ThinkScopes.com|[http://www.thinkscopes.com/blog/2015/01/06/lenovo-thinkpad-x1-carbon-gen-3-review-2/ The new X1 Carbon Gen 3 goes by several name, internally it is referred as Mystique 2, while the gen 2 is Mystique 1, and ThinkPad X1 Carbon Gen 1 is called the Genesis]}}

= Details =
{{Todo|Please note that the specs below are incomplete, help needed!}}
* '''Machine type:''' 20BS*, 20BT*
* '''Processor:''' One of the following ULV fifth generation [[Intel Core]] processors (code name: "Broadwell"):
** Intel® Core™ i5-5200M (2.2-2.7GHz, 3MB L3 cache)
** Intel® Core™ i5-5300M (2.3-2.9GHz, 3MB L3 cache)
** Intel® Core™ i7-5500U (2.4-3.0GHz, 4MB L3 cache)
** Intel® Core™ i7-5600U (2.6-3.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 5500]]
* '''Display:'''
** 14.0" WQHD (2560x1440), 260nit, IPS with multitouch
** 14.0" WQHD (2560x1440), 300nit
** 14.0" HD+ (1920x1080), 300nit
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM PC3-12800
** 8GB DDR3L SDRAM PC3-12800
* '''Disk:'''
** 128GB SSD
** 256GB SSD
** 512GB PCIe SSD
* '''WLAN:'''
** Intel Centrino 7260 (Wilkins Peak 2 BN) 2x2 AC + Bluetooth 4.0
** Intel Centrino 7260 (Wilkins Peak 2 AC) 2x2 AC + Bluetooth 4.0
* '''WWAN:'''
** Sierra Wireless EM7355 - Gobi 5000
** Ericsson Business Mobile Networks BV N5321 gw
* '''Bluetooth:''' Bluetooth 4.0 supported by WLAN module
* '''Keyboard:''' 5-row with Trackpoint, backlit Keyboard keys
* '''I/O Ports:'''
** 2 x USB 3.0 (1 with AOU)
** Audio/Mic Combo
** OneLink Dock
** HDMI
** MiniDP
** Ethernet mini jack
** Sim card slot
* '''Battery:''' Up to 10.9 hours
* '''Webcam:''' [[Integrated camera]] 1.3MP - 720P with mute function
* '''Audio:''' Dolby® Home Theater® v4 with Digital Dual Array microphone certified for Microsoft Lync
* '''Fingerprint Reader''': yes
* '''Wired ethernet network''': yes, via a external dongle provided [https://www.flickr.com/photos/hendry/16769857511/ FRU:04X6435; Lenovo P/N:SC10A39882AB]
* Size: 13.03in x 8.94in x 0.73in (331mm x 227mm x 18.5mm)
* Weight: 3.07 lb (1.39 kg)

* [http://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-carbon-20bs-20bt Download and support page for ThinkPad X1 Carbon 3rd Gen]
* [http://download.lenovo.com/pccbbs/mobiles_pdf/x1_carbon3_hmm_en_sp40g55065.pdf Hardware Maintenance Manual Thinkpad X1 Carbon 3] (52,995,586 bytes)

= Distro resources =
==Archlinux==
Amazingly the X1C3 works out of the box on Archlinux. Only a couple of niggly issues remain:
* HDMI sound output does not work
* Trackpad is a horrible UX
* [https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Carbon_(Gen_3) Resources for running with Archlinux]

==Debian==
Debian Jessie worked out of the box via the Ethernet connection and a netinst image on USB. All buttons appear to work. Need some more time to test but amazing. Did install the non-free firmware and repos. Confirmed that HDMI audio does work however I had to configure the HDMI audio source to be higher in the list to be selected for output. ArchLinux above should work with proper settings.

==Ubuntu==
[http://fredrik.wendt.se/2015/02/24/lenovo-thinkpad-x1-carbon-3rd-gen/ Ubuntu 14.10 on ThinkPad X1 Carbon 3rd Gen]

[[Category:X1_Carbon]][[Category:X Series]]

Category:X1 Carbon (5th Gen)

2017-04-12T17:17:52Z

WilliamPoetra: â†Created page with 'The Thinkpad X1 Carbon 5th Generation is based on the Intel Kaby Lake microarchitecture and released in early 2017. Previous generations: 2012,...'

Category:X1 Carbon

2017-04-12T17:12:39Z

WilliamPoetra:

=== ThinkPad X1 Carbon ===
This page gives an overview of the ThinkPad {{X1 Carbon}} (2012).

The following generations of ThinkPad X1 Carbon exist:
* {{X1 Carbon}}: ThinkPad X1 Carbon (Type 34xx), 1st generation, appeared in 2012
* {{X1 Carbon 2nd}}: ThinkPad X1 Carbon 2nd (Type 20A7, 20A8), 2nd generation, appeared in 2014, known also as "Lenovo New Thinkpad X1 Carbon".
* [[:Category:X1 Carbon (3rd Gen) | X1 Carbon (3rd Gen)]]: ThinkPad X1 Carbon 3rd (Type 20BS, 20BT), 3rd generation, released in 2015.
* [[:Category:X1 Carbon (4th Gen) | X1 Carbon (4th Gen)]]: ThinkPad X1 Carbon 4th (Type 20FB, 20FC), 4th generation, released in 2016.
* [[:Category:X1 Carbon (5th Gen) | X1 Carbon (5th Gen)]]: ThinkPad X1 Carbon 5th (Type 20HQ, 20HR), 5th generation, released in 2017.

==== Details ====
* '''Machine type:''' 34xx
* '''Processor:''' One of the following ULV 3rd generation Intel Core processors (code name: "Ivy Bridge"):
** Intel® Core™ i5-3317U (1.7-2.6GHz, 3MB L3 cache)
** Intel® Core™ i5-3337U (1.8-2.7GHz, 3MB L3 cache)
** Intel® Core™ i5-3427U (1.8-2.8GHz, 3MB L3 cache)
** Intel® Core™ i7-3667U (2.0-3.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 4000]]
* '''Display:'''
** 14.0" HD+ Matte screen (1600x900)
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1600 MHz
** 8GB DDR3L SDRAM 1600 MHz
* '''Disk:'''
** 128GB SSD
** 250GB SSD
** 256GB SSD
* '''WLAN:'''
** Intel 801.11b/g/n
* '''WWAN:''' TODO
* '''Bluetooth:''' TODO
* '''Keyboard:''' TODO
* '''I/O Ports:'''
** 1 x USB 2.0, 1 x USB 3.0
** Mini DisplayPort
** SD Card Slot
* '''Battery:''' Up to 6.3 hours
* '''Webcam:''' [[Integrated camera]] 1.3MP (720p)
* '''Audio:'''
* Size: 13.03in x 8.90in x 0.74in (331mm x 226mm x 19mm)
* Weight: 3.00 lb (1.36 kg)

[[Category:X_Series]]

Category:X1 Carbon

2015-12-09T15:48:56Z

WilliamPoetra: /* Details */

=== ThinkPad X1 Carbon ===
This page gives an overview of the ThinkPad {{X1 Carbon}} (2012).

The following generations of ThinkPad X1 Carbon exist:
* {{X1 Carbon}}: ThinkPad X1 Carbon (Type 34xx), 1st generation, appeared in 2012
* {{X1 Carbon 2nd}}: ThinkPad X1 Carbon 2nd (Type 20A7,20A8), 2nd generation, appeared in 2014, known also as "Lenovo New Thinkpad X1 Carbon".
* [[:Category:X1 Carbon (3rd Gen) | X1 Carbon (3rd Gen)]]: ThinkPad X1 Carbon 3rd (Type 20BS*, 20BT*), 3rd generation, released in 2015.

==== Details ====
* '''Machine type:''' 34xx
* '''Processor:''' One of the following ULV 3rd generation Intel Core processors (code name: "Ivy Bridge"):
** Intel® Core™ i5-3317U (1.7-2.6GHz, 3MB L3 cache)
** Intel® Core™ i5-3337U (1.8-2.7GHz, 3MB L3 cache)
** Intel® Core™ i5-3427U (1.8-2.8GHz, 3MB L3 cache)
** Intel® Core™ i7-3667U (2.0-3.2GHz, 4MB L3 cache)
* '''Graphics:''' [[Intel HD Graphics|Intel HD Graphics 4000]]
* '''Display:'''
** 14.0" HD+ Matte screen (1600x900)
* '''Memory:''' Soldered directly on the mainboard, with capacities of:
** 4GB DDR3L SDRAM 1600 MHz
** 8GB DDR3L SDRAM 1600 MHz
* '''Disk:'''
** 128GB SSD
** 250GB SSD
** 256GB SSD
* '''WLAN:'''
** Intel 801.11b/g/n
* '''WWAN:''' TODO
* '''Bluetooth:''' TODO
* '''Keyboard:''' TODO
* '''I/O Ports:'''
** 1 x USB 2.0, 1 x USB 3.0
** Mini DisplayPort
** SD Card Slot
* '''Battery:''' Up to 6.3 hours
* '''Webcam:''' [[Integrated camera]] 1.3MP (720p)
* '''Audio:'''
* Size: 13.03in x 8.90in x 0.74in (331mm x 226mm x 19mm)
* Weight: 3.00 lb (1.36 kg)

[[Category:X_Series]]

Problem with LCD brightness buttons

2015-11-02T01:59:54Z

WilliamPoetra: /* Affected Models */

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{X61s}}
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
{{cmdroot|rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko }}

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

{{cmdroot|1=echo options video brightness_switch_enabled=0 {{!}} tee /etc/modprobe.d/video-br.conf}}

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

echo N > /sys/module/video/parameters/brightness_switch_enabled

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

Problem with LCD brightness buttons

2015-11-01T16:51:09Z

WilliamPoetra:

== Affected Models ==
* {{X60}}, {{X60s}} with BIOS 2.x
* {{T60}}, {{T60p}} with BIOS 2.x
* {{R60}} with BIOS 2.x
* {{T420s}}
* Probably all newer ThinkPads since the Lenovo acquisition

== Problem description ==

A recent change in one of the newer Lenovo BIOS updates changed the behavior of the brightness up/down keys, so that they also provide ACPI video brighness up/down events. This made ThinkPad users suffer from a bug in the Linux kernel handling of ACPI video events.

One problem is that when the brightness up {{key|Fn}}{{key|Home}} or brightness down {{key|Fn}}{{key|End}} key is pressed, that event is processed twice. It will seem to the user, that the brightness up/down keys work in steps of 2. For example, starting from 0, the brightness level will go up to 2, 4, 6, 8, 10, 12, 14, then 15. But from 15, the brightness level will go down to 13, 11, 9, 7, 5, 3, 1, then 0. It's weird behavior.

The Linux kernel handling for the ACPI video event brighness up is not implemented by the ACPI video module before Linux 2.6.20-rc?, which results in the brightness up key not working, even if the event is handled correctly.

To make matters worse, the ACPI video module in kernels up to 2.6.19.1 has a hideous bug that gets many ACPI video events wrong, and this is the probable cause for the "tries to switch video output" effect some users observed, which can cause serious problems in certain configurations, like X server hangs.

== Workaround ==

There are a number of workarounds for this problem. After applying the workarounds, you will be able to use brightness up {{key|Fn}}{{key|Home}} and brightness down {{key|Fn}}{{key|End}} to increase and decrease the LCD brightness as normal.

=== Don't load the ACPI video module ===

Don't load the ACPI video module, or don't compile in the ACPI_VIDEO option on Linux kernels that have not been patched to fix this issue. The ThinkPad BIOS will do the right thing.

For Fedora Core 6 users, issue the following command and reboot:
{{cmdroot|rename ko ko.old /lib/modules/$(uname -r)/kernel/drivers/acpi/video.ko }}

=== Specify a parameter for video.ko ===

As an alternative, one might also specify <code>brightness_switch_enabled=0</code> in <code>video.ko</code> parameters. With this parameter, all functionality of <code>video.ko</code> remains but without the brightness control and reaction to brightness ACPI events.

There is a number of ways to introduce this parameter, one of them is creating a configuration file for modprobe. The next command works on Debian 6 (and maybe some other systems):

{{cmdroot|1=echo options video brightness_switch_enabled=0 {{!}} tee /etc/modprobe.d/video-br.conf}}

=== Modify the parameter for video.ko at runtime ===

Another alternative, one can issue this command or put it in <code>/etc/rc.local</code>:

echo N > /sys/module/video/parameters/brightness_switch_enabled

== Remaining issues ==

Even with 2.6.20-rc3 ACPI video, things are still not perfect. This time, it may be Lenovo's fault.

The fixed ACPI video module will use the ACPI DSDT to increase video brighness, but the new BIOS DSDTs apparently do not keep the CMOS NVRAM completely up-to-date, so [[tpb]] and other utilities that provide on-screen-display do not get to know there was a brightness up event.

This can be argued to be a deficiency of these tools, however. The foolproof, safe way to know the current ThinkPad display brightness in Linux is to ask [[ibm-acpi]]. Note that ibm-acpi support for this functionality is new, which explains why the current tools don't use it.

Due to the fact that when nothing handles the ACPI video brighness up event, the BIOS does the right thing, it is unclear at this time exactly where the blame for this remaining issue should lie.

How to make ACPI work

2015-10-28T01:24:19Z

WilliamPoetra: /* Screen blanking (Standby) */

==General==
First, simply try using the power management features of Linux on your computer. Tell Linux to suspend (System > Preferences > Power Management in Gnome). Try closing the lid. ACPI may already work.

===Update BIOS===
ACPI requires a relatively new BIOS version. In particular, if you get the message,
ACPI: Could not use ECDT
during startup, you probably need a [[BIOS Upgrade]]. For example, a BIOS upgrade from version 1.02 to 1.10 was all that was needed for ACPI to start working on an A31 2652 running Red Hat Enterprise Linux 5 (CentOS 5).

===Kernel configuration===
Many Kernel 2.6 distributions like Red Hat Enterprise Linux 5 (Centos 5) have ACPI built in and ready to go. If not, you must enable ACPI support in your kernel.

To do this open your kernel config and enable ACPI Power Management:
:{{kernelconf|CONFIG_PM|<*>|Power Management support|Power management options|||}}
:{{kernelconf|CONFIG_ACPI|<*>|ACPI Support|Power management options|||}}

You'd most likely want to enable the following ACPI options:
:{{kernelconf|CONFIG_SUSPEND|<*>|Suspend to RAM and standby|Power management options|||}}
:{{kernelconf|CONFIG_ACPI_AC|<*>|AC Adapter|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_BATTERY|<*>|Battery|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_BUTTON|<*>|Button|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_FAN|<*>|Fan|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_PROCESSOR|<*>|Processor|ACPI|Power management options||}}
:{{kernelconf|CONFIG_ACPI_THERMAL|<*>|Thermal Zone|ACPI|Power management options||}}

If you prefer editing your {{path|.config}} file directly, you should set at least the following variables:
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BLACKLIRG_YEAR=0
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y

Then recompile your kernel.

{{HINT| ACPI SLEEP States option did only show up for me after patching [[Software Suspend 2]] into the kernel. With a vanilla 2.6.17 kernel, one must enable CONFIG_SMP and CONFIG_HOTPLUG_CPU for the option to appear, cf. [http://bugs.debian.org/383059 Debian bug #383059] .
(This should be fixed in 2.6.23, there are new CONFIG_SUSPEND and CONFIG_HIBERNATION config options)}}

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

===ThinkPad specific ACPI driver===

If you are using kernel version 2.6.22 and later, please use the [[thinkpad-acpi]] driver included with the kernel.

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

===Backlight problems with post-2.6.26 kernels===

According to [[http://www.nabble.com/T61-Brightness-keys-with-2.6.26-not-working-(NVIDIA)-td18577619.html this thread]], users with 2.6.26 kernel and higher may experience problems with ThinkPad backlight contols ('''Fn+Home''', '''Fn+End''' on T61). The symptoms are:
* backlight brightness controls do not work;
* Using '''acpi_listen''' command, there is no reaction for '''brightness down''' button, but '''brightenss up''' gives:
ibm/hotkey HKEY 00000080 00001010

The solution is that one needs to enable `CONFIG_VIDEO_OUTPUT_CONTROL`:
Device Drivers --->
Graphics Support --->
<*> Lowlevel video output switch controls

Subsequently one should enable 'CONFIG_ACPI_VIDEO':
Power Management Options --->
[*] ACPI (Advanced Configuration and Power Interface) Support --->
<*> Video

{{NOTE|Without `CONFIG_VIDEO_OUTPUT_CONTROL` enabled, one will not be able to enable `CONFIG_ACPI_VIDEO` in menuconfig or similar interface as the option will remain hidden}}

===ACPI S4 hardware signature mismatch===

Around kernel 2.6.27, a feature was introduced to check the hardware signature on resume from S4 (hibernate). This feature might be broken on some models. Resume will halt and the following error message is shown:
:ACPI: Hardware changed while hibernated, cannot resume!
:Kernel panic - not syncing: ACPI S4 hardware signature mismatch
To fix it, add the following kernel parameter:
:acpi_sleep=s4_nohwsig
This problem appeared here on a T42p, but only if the power is unplugged while hibernated, even if the battery is still plugged. Another sympton is, that resume hangs with a dark screen if the acpi_cpufreq module is loaded, even if the power is not unplugged while hibernated. With the above mentioned kernel parameter, both problems go away.

===ACPI daemon===
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].

{{NOTE|For [[acpid]] to work, the ACPI event interface <TT>/proc/acpi/event</TT> must be configured in the kernel (via <TT>CONFIG_ACPI_PROC_EVENT</TT>). As of kernel 2.6.25, this interface is deprecated. ACPI events are now distributed through the kernel's input event framework, making [[acpid]] redundant and, ultimately, obsolete. However, userspace utilities have been slow to migrate toward the new interface, and many Linux distributions continue to enable the old interface. Check your kernel configuration, or check to see if <TT>/proc/acpi/event</TT> exists.}}

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

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

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

See also [[How to reduce power consumption#LCD Backlight/Brightness]]

==Suspend to RAM (Sleep)==
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.

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

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

Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].

Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.

See the according drivers page for instructions.

== Troubleshooting ==

=== Machine reboots after shutting down ===

Try removing ehci_hcd before shutting down, eg, add the following line to rc.local.shutdown

rmmod ehci_hcd

Needed on {{X220}} and {{X230|Reboots after shutting down}}.

==ThinkPads on which it is recommended to use ACPI==
*ThinkPad {{770X}}, {{770Z}}
*ThinkPad {{A20m}}, {{A20p}}, {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}, {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
*ThinkPad {{G40}}, {{G41}}
*ThinkPad {{R30}}, {{R31}}, {{R32}}, {{R40}}, {{R40e}}, {{R50}}, {{R50e}}, {{R50p}}, {{R51}}, {{R52}}, {{R60}}
*ThinkPad {{T22}}, {{T23}}, {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}, {{T61}}
*ThinkPad {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X32}}, {{X40}}, {{X41}}, {{X41T}}
*ThinkPad {{Z60t}}, {{Z60m}}, {{Z61m}}
*ThinkPad {{X60s}}
*ThinkPad {{TransNote}}
*ThinkPad {{T20}} and {{T21}} have old ACPI implementations, but there have been some reports of using ACPI successfully on these models with Ubuntu and Mandriva in particular. Check the related pages about installing Linux on these models for details.

How to reduce power consumption

2015-10-28T01:23:15Z

WilliamPoetra: /* LCD Backlight/Brightness */

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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,

sysctl vm.block_dump=1

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==
===Enabling Power Management===
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

CPU power management: (default disabled)
PCI bus power management: (default disabled)

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

===Disabling I/O Ports===
The BIOS (at least version 3.11 on {{X200}}) can also be used to disable I/O ports, like PCMCIA/CardBus. Although this requires a reboot to change settings, using the BIOS rather than a configuration file will survive distribution changes and may make it easier to remember how to re-enable a port. Disabling these devices can reduce power consumption by several watts.

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

# 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

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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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:

grep hpet /proc/timer_list

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

hpet=force

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X40}}
* {{A31}}
* {{SL500}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

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

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
echo min_power > /sys/class/scsi_host/host2/link_power_management_policy

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

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

==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
disk write access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it by adding the <tt>relatime</tt>
option to all relevant lines in the /etc/fstab, for example:
/dev/sda1 / ext3 relatime,errors=remount-ro 0 1

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for the <tt>commit</tt> option. This defines how often changed data is written to the disk (it is cached until then). The default value is 5 seconds.

See man mount(8) for details on how the <tt>rel/noatime</tt> and <tt>commit</tt> options work.

Use laptop_mode to reduce disk usage by delaying and grouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

echo 5 > /proc/sys/vm/laptop_mode

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

echo 1500 > /proc/sys/vm/dirty_writeback_centisecs

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

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

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

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

Which host-number to use depends on your laptop. It is typically 0 for the main drive, but for example on the T61 the 0 and 1 are for the pata interface used for the optical drive, and the main hard-disk is on host2.

On Ubuntu 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. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

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

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

start polling again when on ac:

hal-disable-polling --enable-polling --device /dev/scd0 # or whatever your CD drive is

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:

xbacklight -set 50

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 5 minutes of idling:

xset +dpms
xset dpms 0 0 300

===Screensaver method===
Alternatively, you can add a screensaver that does nothing but blank the screen and turn off the display. In this example, I'm using Linux Mint MATE 17.2, please adjust the keywords below accordingly. Also, you will need to enable DPMS as above, or as in [[How to make ACPI work#Screen blanking (Standby)]].

We need to create 2 files, the first one is <code>/usr/share/applications/screensavers/screenoff.desktop</code>:

[Desktop Entry]
Name=Screen off
Comment=Turns the screen off
Exec=/usr/lib/mate-screensaver/screenoff
TryExec=/bin/true
StartupNotify=false
Terminal=false
Type=Application
Categories=Screensaver;
Keywords=MATE;screensaver;dpms;
OnlyShowIn=MATE;

The second one is <code>/usr/lib/mate-screensaver/screenoff</code>, which needs to be executable:

#!/bin/sh
pidof mate-screensaver-preferences | grep -w $PPID && exit 0
xset q | grep -q "Monitor is On" && xset dpms force off

The <code>Keywords</code> section and the <code>mate-screensaver-preferences</code> should be customized according to your desktop (like Cinnamon, or GNOME, etc).

After creating those files, open the Screensaver preferences dialog and choose the screensaver with the name "Screen off". Now, when the screensaver is activated, the screen will fade to black and backlight will be turned off by DPMS.

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

Option "NoDRI"

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.

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)

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :

echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video

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

options usbcore autosuspend=1

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

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):

usbcore.autosuspend=1

or at runtime, per device, with:

for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
for i in /sys/bus/usb/devices/*/power/level; do echo auto > $i; done

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:

rmmod uhci_hcd

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:

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

==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):

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

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

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

===Intel HD Audio===

If you have Intel HD audio as your onboard sound controller, substitute the following for the last line in the above sequence:

echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller

You also may wish to decrease the sound poweroff timeout to something shorter, like 1 second after last playback:

echo 1 > /sys/module/snd_hda_intel/parameters/power_save

===Additional Tweaks===

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:

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

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

iwpriv eth1 set_power 5

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

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

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 :

rmmod ipw2200
modprobe ipw2200 associate=0

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

options ipw2200 associate=0

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.

In recent kernels, the powersaving on the intel ipw3945 has been disabled, as
for some it is unstable. For others it worked just fine.

See [http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=blobdiff;f=drivers/net/wireless/iwlwifi/iwl-3945.c;h=e413bd35bc411a1113177f1576538eb0ac26f00c;hp=4609323d8436dc9e22c74be2f1f3cf5e97785cb2;hb=bc45a67079c916a9bd0a95b0b879cc0f259bac6e;hpb=b7bb1756cb6a610cdbac8cfdad9e79bb5670b63b this patch]. You may wish to try changing '.broken_powersave=true' to false, in /usr/src/linux/drivers/net/wireless/iwlwifi/iwl-3945.c if you wish to enable powersave.

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:

ethtool -s eth0 wol d

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

ethtool -s eth0 autoneg off speed 100

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.

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

==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>dstat -t -c --power --top-cpu --top-io --top-bio --top-latency --top-cputime</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

2015-10-28T01:21:25Z

WilliamPoetra: /* LCD Backlight/Brightness */

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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,

sysctl vm.block_dump=1

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==
===Enabling Power Management===
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

CPU power management: (default disabled)
PCI bus power management: (default disabled)

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

===Disabling I/O Ports===
The BIOS (at least version 3.11 on {{X200}}) can also be used to disable I/O ports, like PCMCIA/CardBus. Although this requires a reboot to change settings, using the BIOS rather than a configuration file will survive distribution changes and may make it easier to remember how to re-enable a port. Disabling these devices can reduce power consumption by several watts.

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

# 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

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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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:

grep hpet /proc/timer_list

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

hpet=force

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X40}}
* {{A31}}
* {{SL500}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

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

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
echo min_power > /sys/class/scsi_host/host2/link_power_management_policy

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

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

==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
disk write access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it by adding the <tt>relatime</tt>
option to all relevant lines in the /etc/fstab, for example:
/dev/sda1 / ext3 relatime,errors=remount-ro 0 1

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for the <tt>commit</tt> option. This defines how often changed data is written to the disk (it is cached until then). The default value is 5 seconds.

See man mount(8) for details on how the <tt>rel/noatime</tt> and <tt>commit</tt> options work.

Use laptop_mode to reduce disk usage by delaying and grouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

echo 5 > /proc/sys/vm/laptop_mode

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

echo 1500 > /proc/sys/vm/dirty_writeback_centisecs

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

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

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

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

Which host-number to use depends on your laptop. It is typically 0 for the main drive, but for example on the T61 the 0 and 1 are for the pata interface used for the optical drive, and the main hard-disk is on host2.

On Ubuntu 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. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

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

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

start polling again when on ac:

hal-disable-polling --enable-polling --device /dev/scd0 # or whatever your CD drive is

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:

xbacklight -set 50

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 5 minutes of idling:

xset +dpms
xset dpms 0 0 300

Alternatively, you can add a screensaver that does nothing but blank the screen and turn off the display. In this example, I'm using Linux Mint MATE 17.2, please adjust the keywords below accordingly. Also, you will need to enable DPMS as above, or as in [[How to make ACPI work#Screen blanking (Standby)]].

We need to create 2 files, the first one is <code>/usr/share/applications/screensavers/screenoff.desktop</code>:

[Desktop Entry]
Name=Screen off
Comment=Turns the screen off
Exec=/usr/lib/mate-screensaver/screenoff
TryExec=/bin/true
StartupNotify=false
Terminal=false
Type=Application
Categories=Screensaver;
Keywords=MATE;screensaver;dpms;
OnlyShowIn=MATE;

The second one is <code>/usr/lib/mate-screensaver/screenoff</code>, which needs to be executable:

#!/bin/sh
pidof mate-screensaver-preferences | grep -w $PPID && exit 0
xset q | grep -q "Monitor is On" && xset dpms force off

The <code>Keywords</code> section and the <code>mate-screensaver-preferences</code> should be customized according to your desktop (like Cinnamon, or GNOME, etc).

After creating those files, open the Screensaver preferences dialog and choose the screensaver with the name "Screen off". Now, when the screensaver is activated, the screen will fade to black and backlight will be turned off by DPMS.

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

Option "NoDRI"

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.

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)

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :

echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video

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

options usbcore autosuspend=1

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

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):

usbcore.autosuspend=1

or at runtime, per device, with:

for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
for i in /sys/bus/usb/devices/*/power/level; do echo auto > $i; done

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:

rmmod uhci_hcd

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:

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

==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):

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

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

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

===Intel HD Audio===

If you have Intel HD audio as your onboard sound controller, substitute the following for the last line in the above sequence:

echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller

You also may wish to decrease the sound poweroff timeout to something shorter, like 1 second after last playback:

echo 1 > /sys/module/snd_hda_intel/parameters/power_save

===Additional Tweaks===

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:

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

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

iwpriv eth1 set_power 5

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

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

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 :

rmmod ipw2200
modprobe ipw2200 associate=0

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

options ipw2200 associate=0

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.

In recent kernels, the powersaving on the intel ipw3945 has been disabled, as
for some it is unstable. For others it worked just fine.

See [http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=blobdiff;f=drivers/net/wireless/iwlwifi/iwl-3945.c;h=e413bd35bc411a1113177f1576538eb0ac26f00c;hp=4609323d8436dc9e22c74be2f1f3cf5e97785cb2;hb=bc45a67079c916a9bd0a95b0b879cc0f259bac6e;hpb=b7bb1756cb6a610cdbac8cfdad9e79bb5670b63b this patch]. You may wish to try changing '.broken_powersave=true' to false, in /usr/src/linux/drivers/net/wireless/iwlwifi/iwl-3945.c if you wish to enable powersave.

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:

ethtool -s eth0 wol d

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

ethtool -s eth0 autoneg off speed 100

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.

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

==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>dstat -t -c --power --top-cpu --top-io --top-bio --top-latency --top-cputime</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

2015-10-28T01:06:55Z

WilliamPoetra: code cleanup

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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,

sysctl vm.block_dump=1

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==
===Enabling Power Management===
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

CPU power management: (default disabled)
PCI bus power management: (default disabled)

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

===Disabling I/O Ports===
The BIOS (at least version 3.11 on {{X200}}) can also be used to disable I/O ports, like PCMCIA/CardBus. Although this requires a reboot to change settings, using the BIOS rather than a configuration file will survive distribution changes and may make it easier to remember how to re-enable a port. Disabling these devices can reduce power consumption by several watts.

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

# 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

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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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:

grep hpet /proc/timer_list

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

hpet=force

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X40}}
* {{A31}}
* {{SL500}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

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

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
echo min_power > /sys/class/scsi_host/host2/link_power_management_policy

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

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

==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
disk write access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it by adding the <tt>relatime</tt>
option to all relevant lines in the /etc/fstab, for example:
/dev/sda1 / ext3 relatime,errors=remount-ro 0 1

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for the <tt>commit</tt> option. This defines how often changed data is written to the disk (it is cached until then). The default value is 5 seconds.

See man mount(8) for details on how the <tt>rel/noatime</tt> and <tt>commit</tt> options work.

Use laptop_mode to reduce disk usage by delaying and grouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

echo 5 > /proc/sys/vm/laptop_mode

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

echo 1500 > /proc/sys/vm/dirty_writeback_centisecs

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

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

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

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

Which host-number to use depends on your laptop. It is typically 0 for the main drive, but for example on the T61 the 0 and 1 are for the pata interface used for the optical drive, and the main hard-disk is on host2.

On Ubuntu 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. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

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

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

start polling again when on ac:

hal-disable-polling --enable-polling --device /dev/scd0 # or whatever your CD drive is

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:

xbacklight -set 50

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 5 minutes of idling:

xset +dpms
xset dpms 0 0 300

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

Option "NoDRI"

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.

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)

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :

echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video

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

options usbcore autosuspend=1

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

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):

usbcore.autosuspend=1

or at runtime, per device, with:

for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
for i in /sys/bus/usb/devices/*/power/level; do echo auto > $i; done

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:

rmmod uhci_hcd

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:

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

==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):

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

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

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

===Intel HD Audio===

If you have Intel HD audio as your onboard sound controller, substitute the following for the last line in the above sequence:

echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller

You also may wish to decrease the sound poweroff timeout to something shorter, like 1 second after last playback:

echo 1 > /sys/module/snd_hda_intel/parameters/power_save

===Additional Tweaks===

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:

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

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

iwpriv eth1 set_power 5

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

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

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 :

rmmod ipw2200
modprobe ipw2200 associate=0

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

options ipw2200 associate=0

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.

In recent kernels, the powersaving on the intel ipw3945 has been disabled, as
for some it is unstable. For others it worked just fine.

See [http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=blobdiff;f=drivers/net/wireless/iwlwifi/iwl-3945.c;h=e413bd35bc411a1113177f1576538eb0ac26f00c;hp=4609323d8436dc9e22c74be2f1f3cf5e97785cb2;hb=bc45a67079c916a9bd0a95b0b879cc0f259bac6e;hpb=b7bb1756cb6a610cdbac8cfdad9e79bb5670b63b this patch]. You may wish to try changing '.broken_powersave=true' to false, in /usr/src/linux/drivers/net/wireless/iwlwifi/iwl-3945.c if you wish to enable powersave.

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:

ethtool -s eth0 wol d

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

ethtool -s eth0 autoneg off speed 100

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.

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

==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>dstat -t -c --power --top-cpu --top-io --top-bio --top-latency --top-cputime</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

2015-10-28T01:02:29Z

WilliamPoetra: /* Tools */

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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,

sysctl vm.block_dump=1

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==
===Enabling Power Management===
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.

===Disabling I/O Ports===
The BIOS (at least version 3.11 on {{X200}}) can also be used to disable I/O ports, like PCMCIA/CardBus. Although this requires a reboot to change settings, using the BIOS rather than a configuration file will survive distribution changes and may make it easier to remember how to re-enable a port. Disabling these devices can reduce power consumption by several watts.

==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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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>

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}, {{X40}}
* {{A31}}
* {{SL500}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

===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
echo min_power > /sys/class/scsi_host/host2/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
disk write access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it by adding the <tt>relatime</tt>
option to all relevant lines in the /etc/fstab, for example:
/dev/sda1 / ext3 relatime,errors=remount-ro 0 1

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for the <tt>commit</tt> option. This defines how often changed data is written to the disk (it is cached until then). The default value is 5 seconds.

See man mount(8) for details on how the <tt>rel/noatime</tt> and <tt>commit</tt> options work.

Use laptop_mode to reduce disk usage by delaying and grouping 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
echo min_power > /sys/class/scsi_host/host2/link_power_management_policy
</code>

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

Which host-number to use depends on your laptop. It is typically 0 for the main drive, but for example on the T61 the 0 and 1 are for the pata interface used for the optical drive, and the main hard-disk is on host2.

On Ubuntu 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. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

===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 5 minutes 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 configuration.

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/*/power/autosuspend; do echo 1 > $i; done
for i in /sys/bus/usb/devices/*/power/level; do echo auto > $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>

===Intel HD Audio===

If you have Intel HD audio as your onboard sound controller, substitute the following for the last line in the above sequence:

<code>
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>

You also may wish to decrease the sound poweroff timeout to something shorter, like 1 second after last playback:

<code>
echo 1 > /sys/module/snd_hda_intel/parameters/power_save
</code>

===Additional Tweaks===

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.

In recent kernels, the powersaving on the intel ipw3945 has been disabled, as
for some it is unstable. For others it worked just fine.

See [http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=blobdiff;f=drivers/net/wireless/iwlwifi/iwl-3945.c;h=e413bd35bc411a1113177f1576538eb0ac26f00c;hp=4609323d8436dc9e22c74be2f1f3cf5e97785cb2;hb=bc45a67079c916a9bd0a95b0b879cc0f259bac6e;hpb=b7bb1756cb6a610cdbac8cfdad9e79bb5670b63b this patch]. You may wish to try changing '.broken_powersave=true' to false, in /usr/src/linux/drivers/net/wireless/iwlwifi/iwl-3945.c if you wish to enable powersave.

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>dstat -t -c --power --top-cpu --top-io --top-bio --top-latency --top-cputime</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 configure the TrackPoint

2015-10-17T08:23:42Z

WilliamPoetra: /* Sensitivity & Speed */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |Below are several ways of configuring the kernel psmouse driver for controlling extended TrackPoint features.
|}
On a '''Modern''' distribution (like Fedora, Ubuntu or OpenSUSE) you will want to use xinput or one of the graphical front ends. For distributions that are lagging a bit (e.g. Debian Lenny and PCLOS '09) you may still want to use the old xorg config method.

=Configuration using xinput=
If you want to modify changes on the fly, you can do so with {{cmd|xinput|}} (part of the optional xorg-x11-apps rpm on Fedora).
Note that these changes are not saved when the xserver is restarted. However, you can add the lines e.g. in your {{cmd|.xsessionrc|}} (depends on your distribution) so they are executed every time X starts.

To query the available options
xinput list-props "TPPS/2 IBM TrackPoint"

More information can be found in the man-pages for evdev
man evdev

To enable vertical scrolling
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 1
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 2
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 200

To enable horizontal scrolling in addition to vertical scrolling

xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 6 7 4 5

To enable middle button emulation (using left- and right-click simultaneously)
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Emulation" 1
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Timeout" 50

== old method using xinput set-int-prop ==

Note: xinput set-int-prop is deprecated according to the xinput manpage.

To enable vertical scrolling
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 8 200

To enable horizontal scrolling in addition to vertical scrolling

xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 6 7 4 5

To enable middle button emulation (using left- and right-click simultaneously)
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Emulation" 8 1
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Timeout" 8 50

==Example: openSUSE 11.2 and ThinkPad USB Keyboard with TrackPoint ==

xinput list
will show two "Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint." with two different ids. Use the id with Axis 0 and Axis 1 items.

Suppose the id was 12. The following will enable the trackpoint scrolling:

xinput set-int-prop 12 "Evdev Wheel Emulation" 8 1
xinput set-int-prop 12 "Evdev Wheel Emulation Button" 8 2
xinput set-int-prop 12 "Evdev Wheel Emulation Timeout" 8 200

The following will enable the horizontal scrolling
xinput set-int-prop 12 "Evdev Wheel Emulation Axes" 8 6 7 4 5

To disable middle button click paste functionality, remap the middle button to something else:
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"

To do these automatically without worrying about id number, generate a bash script file:
#!/bin/sh
xinput list | sed -ne 's/^[^ ][^V].*id=$[0-9]*$.*/\1/p' | while read id
do
case `xinput list-props $id` in
*"Middle Button Emulation"*)
xinput set-int-prop $id "Evdev Wheel Emulation" 8 1
xinput set-int-prop $id "Evdev Wheel Emulation Button" 8 2
xinput set-int-prop $id "Evdev Wheel Emulation Timeout" 8 200
xinput set-int-prop $id "Evdev Wheel Emulation Axes" 8 6 7 4 5
xinput set-int-prop $id "Evdev Middle Button Emulation" 8 0
;;
esac
done

# disable middle button
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"

and save it with any name such as trackPointScrolling.sh, and make it executable:
chmod +x trackPointScrolling.sh

Next time you run it with $ ./trackPointScrolling.sh, it will enable the trackpoint scrolling and disable middle button paste.
{{Todo|some other examples}}

= Graphical Frontends =
If you are using GNOME, you might want to use [http://live.gnome.org/GPointingDeviceSettings GPointing Device Settings] or [http://tpctl.sourceforge.net/configure-trackpoint.html configure-trackpoint] as a graphical frontends.
=== GPointing Device Settings ===
It is available for Fedora 12, Ubuntu 9.10 and Debian Squeeze in the standard package repositories
{{NOTE|Unfortunately it seems no longer maintained, and does not work properly with GNOME3 [[https://bugzilla.redhat.com/show_bug.cgi?id=710053 bug]]}}

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

=== configure-trackpoint ===
To install it in Ubuntu run ...
sudo apt-get install sysfsutils
...and then download and install the deb [http://sourceforge.net/projects/tpctl/ here]. Note that saved settings are not restored after reboot in Lucid Lynx. See methods below to make settings permanent.

= Configuration using DevKit =
Most recent distributions like Ubuntu 9.10 switch from HAL (being deprecated) to DevKit. Hence, the HAL configurations explained underneath, fail to work.

The easiest way to configure your touchpad and trackpoint with DevKit is by using the [http://live.gnome.org/GPointingDeviceSettings GPointingDeviceSettings] panel that fully supports the hardware. You can easily download the panel by installing {{cmd| gpointing-device-settings|}}. On Ubuntu open a terminal and execute the command {{cmduser| sudo apt-get install gpointing-device-settings}}

Launch the UI through the {{cmduser| gpointing-device-settings}} command, but you can also add a menu entry to your System / Preferences menu for easier access to the UI panel.

= Configuration using udev and HAL =
Modern distributions like Ubuntu 8.10 and Fedora 10 use udev and HAL to configure the input devices. You should no longer make changes to xorg.conf as by default Xorg (through the evdev driver) will let the kernel now handle input devices.

But before you get started on this you should make sure you have all the updates applied from your distro vendor as both Ubuntu 8.10 and Fedora 10 require some additional fixes that you will need.

=== Scrolling ===

By default the middle mouse button is just that, a middle mouse button, which in Linux is used for the Paste operation.

You may configure it to act in the same way as in Windows, such that you can use it for vertical scrolling: keep the button pressed and move the TrackPoint up and down to scroll. (In GPointing Device Settings, this is known as "Use wheel emulation".)

'''Note:''' This setting is not compatible with using Alt + Middle Mouse Button to resize windows. If you want to resize windows with the trackpad, disable wheel emulation. On Ubuntu 11.10, this setting resides in <tt>/usr/share/X11/xorg.conf.d/11-evdev-trackpoint.conf</tt> (see below), although some touchpads use <tt>/usr/share/X11/xorg.conf.d/50-synaptics.conf</tt>.

==== xorg.conf.d ====

Some distributions now support the new Xorg hotplug configuration method via xorg.conf.d directories (in Ubuntu 10.04 Lucid Lynx) instead of hal. In contrast to the udev method below, it should be around for some time, so it might be the best way to “statically” configure scrolling.

Create the file {{path|/usr/lib/X11/xorg.conf.d/20-thinkpad.conf}} as root with the following content:

<pre>
Section "InputClass"
Identifier "Trackpoint Wheel Emulation"
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint|ThinkPad USB Keyboard with TrackPoint|USB Trackpoint pointing device|Composite TouchPad / TrackPoint"
MatchDevicePath "/dev/input/event*"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "Emulate3Buttons" "false"
Option "XAxisMapping" "6 7"
Option "YAxisMapping" "4 5"
EndSection
</pre>

Save and restart Xorg (or it'll be enabled at next reboot).

{{NOTE|For Ubuntu 10.10 Maverick Meerkat, the correct path is {{path|/usr/share/X11/xorg.conf.d}}}}
{{NOTE|For Arch Linux or Fedora or PCLinuxOS, the correct path is {{path|/etc/X11/xorg.conf.d}}}}

{{NOTE|If the above does not work for you, you may need to add a different MatchProduct string. Use <pre>find /dev/input/event* -exec udevadm info --attribute-walk --name={} \; | grep -e product -e name | sort -u</pre> to get a list of possibilities.}}

{{NOTE|If the above directory doesn't exist by default in your distribution, it probably doesn't support this method. In this case, please refer to the udev or xinput method below.}}

==== udev ====

Now that Xorg doesn't use the configuration from hal (in Debian unstable starting january 2010), the only way to “statically” configure scrolling in trackpoint is udev. (for other people, xinput method, works fine). This method will be gone (_again_) in not too long so it might be a better idea to use xinput way. YMMV.

Create the file {{path|/etc/udev/rules.d/99_trackpoint.rules}} as root with the following content:

<pre>
ACTION!="add|change", GOTO="xorg_trackpoint_end"
KERNEL!="event*", GOTO="xorg_trackpoint_end"

ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_trackpoint_end"

ENV{x11_options.EmulateWheel}="1"
ENV{x11_options.EmulateWheelButton}="2"
ENV{x11_options.XAxisMapping}="6 7"
ENV{x11_options.Emulate3Buttons}="0"

LABEL="xorg_trackpoint_end"
</pre>

Save and restart udev then Xorg (or it'll be enabled at next reboot).

{{NOTE|The ID_PATH used in the example above is a typical value. To determine the ID_PATH appropriate to the TrackPoint on a specific model see [[#Determining TrackPoint Path ID|Determining TrackPoint Path ID]]}}

==== Hal (soon to be deprecated) ====

To accomplish this create the file {{path|/etc/hal/fdi/policy/mouse-wheel.fdi}} as root with the following content:

<pre>
<match key="info.product" string="TPPS/2 IBM TrackPoint">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge>
</match>
</pre>

If you also want to have horizontal scrolling, simply add the following XAxisMapping option to the above
<pre>
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge>
</pre>
After this reboot, or restart the hal service and Xorg. You can validate the settings with {{cmd|lshal|}}.

In some models (eg: X301 and X200 since Jan 10 2010 on debian sid) you may have to use "PS/2 Generic Mouse" instead of "TPPS/2 IBM TrackPoint". Have a look to your input devices typing <code>lshal|grep input.product</code>.

Alternatively it is also possible to use the "old" Xorg configuration by adding the following lines to the {{path|/etc/X11/xorg.conf}}:

<pre>
Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection
</pre>

Using this entry HAL will not be used for the input devices.

====Reactivate Scrolling after suspend/resume====
Scrolling may be disabled after a resume from suspend.

You can manually reactivate the trackpoint by reloading the {{path|psmouse}} module as root:
:{{cmdroot|rmmod psmouse && modprobe psmouse}}

You can automatically force the pm-utils to reload this module.
Create a file {{path|/etc/pm/config.d/01reload_mouse}} as root with the following content:
<pre>
# reload psmouse to reactivate trackpoint scrolling
SUSPEND_MODULES="${SUSPEND_MODULES:+$SUSPEND_MODULES }psmouse"
</pre>

===Configuring other options (e.g. Press to select, Sensitivity and Speed)===

Create a file {{path|/etc/udev/rules.d/10-trackpoint.rules}} and add a line to suit your needs

<pre>
SUBSYSTEM=="serio", DRIVERS=="psmouse", ATTRS{press_to_select}="1", ATTRS{sensitivity}="122"
</pre>

Testing udev with {{cmdroot|udevadm test /sys/devices/platform/i8042/serio1}} should apply the new changes. All of the settings listed [[How to configure the TrackPoint#Sysfs_Options_Reference|below]] can be specified here as part of a comma separated list.
The customized values should be loaded automatically when booting. However, due to a [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549379 kernel bug] (affecting Lucid Lynx), the attributes may not yet exist when the udev rule fires. As a work around, add a WAIT_FOR condition on the attribute

<pre>
SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTRS{sensitivity}="122"
</pre>

On my system (Lucid Lynx), the above line did not work. I changed it to:
<pre>
SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="255"
</pre>
and tested with {{cmdroot|udevadm test /sys/devices/platform/i8042/serio1/serio2}}.

To avoid the wait you can also listen for the Trackpoint input device to appear and then run a script to set the parameters

<pre>
SUBSYSTEM=="input", ATTR{name}=="*TrackPoint*", RUN+="/etc/conf.d/trackpoint"
</pre>

An example {{path|/etc/conf.d/trackpoint}} would be

<pre>#! /bin/bash

## Trackpoint settings

# When run from a udev rule, DEVPATH should be set
if [ ! -z $DEVPATH ] ; then
TPDEV=/sys/$( echo "$DEVPATH" | sed 's/\/input\/input[0-9]*//' )
else
# Otherwise just look in /sys/
TPDEV=$(find /sys/devices/platform/i8042 -name name | xargs grep -Fl TrackPoint | sed 's/\/input\/input[0-9]*\/name$//')
fi

# http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint
# http://wwwcssrv.almaden.ibm.com/trackpoint/files/ykt3eext.pdf
#------------------------------------------------------------
if [ -d "$TPDEV" ]; then
echo "Configuring Trackpoint"
echo -n 255 > $TPDEV/sensitivity # Integer 128 Sensitivity
echo -n 110 > $TPDEV/speed # Integer 97 Cursor speed
echo -n 4 > $TPDEV/inertia # Integer 6 Negative intertia
else
echo "Couldn't find trackpoint device $TPDEV"
fi
</pre>

=Configuration using sysfs=
Another way to modify changes on the fly, is echoing values directly into special files in sysfs.

{{NOTE|
The examples shown below are valid for ThinkPads with both TrackPoint and Touchpad, in which case the sysfs path is {{path|/sys/devices/platform/i8042/serio1/serio2}}.

If however you have a ThinkPad without Touchpad, or with the Touchpad disabled in the BIOS, the sysfs path needs to be changed to {{path|/sys/devices/platform/i8042/serio1}} instead (notice the missing serio2 at the end).}}

If you want to set the sysfs parameters at boot, you can use the [http://linux-diag.sourceforge.net/Sysfsutils.html sysfsutils] and put the preferred value in /etc/sysfs.conf.

===Press to Select===
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}

Press to Select should now be enabled. You can disable it in a similar manner:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}

You can use this script to automate the operation

#!/bin/bash
if [ "$1" = "1" ]; then
echo "Turning on tap on TrackPoint"
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select
exit 0
fi
if [ "$1" = "0" ]; then
echo "Turning off tap on TrackPoint"
echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select
exit 0
fi
echo -n "Tap status: "
cat /sys/devices/platform/i8042/serio1/serio2/press_to_select

In Ubuntu 8.10 to make Press to Select a permanent change:

echo -n 1 | tee /sys/devices/platform/i8042/serio1/serio2/press_to_select

As root, append the above command above "exit 0" in /etc/gdm/Init/Default

===Sensitivity & Speed===
Adjusting the speed and sensitivity of the TrackPoint requires echoing a value between 0 and 255 into the appropriate file. For example, for a speed of 120 and a sensitivity of 250, type the following into a terminal:

:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed}}
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity}}

Alternatively, on my ThinkPad T420s, the correct commands are:

:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio1/speed}}
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio1/sensitivity}}

Feel free to experiment with your settings until you find a combination that is comfortable.

When you satisfy your setting, add the two lines into /etc/rc.d/rc.local in order to avoid restoring the default setting every time the system reboots. In Ubuntu 9.10, add the lines to /etc/rc.local to avoid this.

===Vertical Scrolling===
No sysfs entry exists for vertical scrolling in kernels after 2.6.11.

The feature was removed as it was not a hardware feature, but rather emulating a scroll action in software and as such did not belong in the kernel.
Instead the scroll feature of the Xserver should be used, which can be activated with HAL or xinput as described above.

=Configuration using the X server (xorg.conf)=
==Using the "evdev" driver (preferred, especially for recent Xorg versions)==
Extract from /etc/X11/xorg.conf on an X31:

Section "InputDevice"
Identifier "TPPS/2 IBM TrackPoint"
Driver "evdev"
Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"
Option "GrabDevice" "False"
Option "EmulateWheel" "true" #Enable wheel emulation for the Trackpoint
Option "EmulateWheelButton" "2" #Use the middle button for the emulation
Option "XAxisMapping" "6 7" #Map trackpoint X axis to X axis of emulated wheel
Option "YAxisMapping" "4 5" #Map trackpoint Y axis to Y axis of emulated wheel
EndSection

{{NOTE|The device path used in the example above is a typical value. To determine the device path appropriate to the TrackPoint on a specific model see [[#Determining TrackPoint Path ID|Determining TrackPoint Path ID]]}}

==Using the "mouse" driver (deprecated, only for old Xorg versions)==
{{NOTE|This only applies to old distributions with Xorg versions that did not yet use evdev. For modern distributions use one of the other methods}}
The scroll setting has been removed from the trackpoint driver in kernel versions 2.6.11 and above. Scroll emulation should now be handled in the X server.

A nice side effect of that is, that middle button scrolling applies to any mouse and not just the TrackPoint interface, which can be a quite handy feature for desktop computers or people who prefer to use an external mouse, especially when scrolling through long lists or needing to use horizontal scrolling with a mouse which has only a vertical scroll wheel.

The necessary functionality, known as "EmulateWheelTimeout" allowing to use button 2 for a middle click, wasn't implemented in Xorg prior to 6.9/7.0. However, there was a patch included in most distributions packages of Xorg, which was announced [http://www.mail-archive.com/devel@xfree86.org/msg03333.html here]. You can find an updated version of the package in the experimental branch of {{Debian}} or try to build the mouse driver yourself with the information in the announcement. This has successfully been tried with FC3's 6.8.2 packages.

Once this functionality is in the X.org, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"

It may also be necessary to add these lines:

Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"

which specify which buttons are mapped to motion in the vertical (Y) and horizontal (X) directions, respectively, in wheel emulation mode (see http://www.xfree86.org/current/mouse.4.html).

{{HINT| Use the program "xev" to see, what mouse button identifiers are sent by your mouse/touchpad/trackpoint.<br />You might want to try: "xev | grep button"}}
{{HINT| If it does not work see if evdev is installed and remove it. On gentoo do the following:<br />
eix xf86-input-evdev<br />
emerge -C xf86-input-evdev<br />
and then remove the evdev flag in make.conf INPUT_DEVICES}}

So, a complete mouse section, that implements this nicely and works very well on my R51, even with a simultaneously connected USB mouse, looks like that (tried out today, 20th of September, 2006 on Dapper):

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "on"
Option "Emulate3TimeOut" "50"
Option "EmulateWheel" "on"
Option "EmulateWheelTimeOut" "200"
Option "EmulateWheelButton" "2"
Option "YAxisMapping" "4 5"
Option "XAxisMapping" "6 7"
Option "ZAxisMapping" "4 5"
EndSection

The mappings for Y and Z are the same, since the "Z-Axis" refers to actual hardware scrolling wheels which usually scroll the screen along the Y-Axis. If there is no hardware scrolling wheel present, horizontal and vertical scrolling using the TrackPoint work fine without the Z-Axis line.

Now restart X and hold down button 2 and move the mouse to scroll, or just press and release button 2 for a middle click.

To make this work with the synaptics driver for the touchpad, you can add
Option "GuestMouseOff" "1"
to the synaptics device section. This will make the synaptics driver ignore the Trackpoint, so it will be handled by the mouse driver. This allowed me to disable the touchpad while making the TrackPoint work like it should.

{{NOTE| With the above mouse section in my xorg.conf all this works like a charm:
*I can press the wheel on my external USB mouse and move the mouse up and down for scrolling
*or I can just use the wheel on the external mouse for scrolling
*or pressing the MMB button of the trackpoint and use the trackpoint for scrolling.
*Even horizontal scrolling works automagically in Konqueror, for Firefox/Opera see below.

Simultaneously I can use
*a press on the external mouse's wheel
*or the MMB of the trackpoint

for pasting the buffer. Lovely! :) }}

{{HINT| If you don't use the middle-mouse-button for pasting and sometimes pasting things by mistake while scrolling (witch is really odd) simply set the "EmulateWheelTimeOut" to "1" as a (bloody) workaround. Middle click will only possible with pressing left and right button simultaneously!}}

=Application specific tweaks=
===Configure Opera for using trackpoint horizontal scrolling===
To fix horizontal scrolling in Opera, you need to edit the configfile <tt>standard_mouse.ini</tt> in e.g. /usr/share/opera/ui/ (Debian) or /opt/opera/share/opera/ini/ (Gentoo) and comment out the following lines
<pre>
Button6 = Back
Button7 = Forward
</pre>
so they look like that
<pre>
;Button6 = Back
;Button7 = Forward
</pre>
Remember, Button6 and Button7 do not so coincidental correspond with our X configuration we know from above:
<pre>
Option "YAxisMapping" "6 7"
</pre>
After this change you will be able to scroll vertically and horizontally with your middle button.

===Firefox 3 tweaks===
These settings make Firefox on Linux behave more like the Windows version. They were tested on an out of the box Fedora 10 system on a Thinkpad T61. Go into about:config, and set the following:

middlemouse.paste = false
middlemouse.contentLoadURL = false
general.autoScroll = true

=Sysfs Options Reference=
{{NOTE|These options are current as of kernel version 2.6.29, 3 May 2009}}
{|
|-
! Name
! Type
! Default
! Notes
|-
| sensitivity
| Integer
| 128
| Sensitivity
|-
| speed
| Integer
| 97
| Cursor speed
|-
| inertia
| Integer
| 6
| Described as "negative inertia." It acts more like friction. High values cause the cursor to snap backward when the Trackpoint is released
|-
| reach
| Integer
| 10
| Backup for Z-axis press
|-
| draghys
| Integer
| 255
| Drag hysteresis (how hard it is to drag with Z-axis pressed)
|-
| mindrag
| Integer
| 20
| Minimum amount of force needed to trigger dragging
|-
| thresh
| Integer
| 8
| Minimum value for a Z-axis press
|-
| upthresh
| Integer
| 255
| Used to generate a 'click' on Z-axis
|-
| ztime
| Integer
| 38
| How sharp of a press
|-
| jenks
| Integer
| 135
| Minimum curvature for double click
|-
| press_to_select
| Boolean
| 0
| Press to select
|-
| skipback
| Boolean
| 0
| Supress movement after drag release
|-
| ext_dev
| Boolean
| 0
| Disable external device
|}
Table info taken from [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/input/mouse/trackpoint.h;hb=HEAD here]. The given link will always point to the current version of the driver. If the notes seem sparse, that's because the code is sparse. On the other hand, the [http://wwwcssrv.almaden.ibm.com/trackpoint/files/ykt3eext.pdf Trackpoint Engineering Specification Version 4.0]  contains more documentation information than anyone ever desired.

=Determining TrackPoint Path ID=
Both the [[#udev|udev]] and [[#Configuration using the X server (xorg.conf)|xorg.conf]] configuration methods require knowledge of the Path ID of the TrackPoint. In the [[#udev|udev]] configuration method, the Path ID is used to match the ID_PATH environmental variable, in the [[#Configuration using the X server (xorg.conf)|xorg.conf]] configuration method it is the prefix for the device file name inside the {{path|/dev/input/by-id}} directory. The path ID can vary between ThinkPad models, distributions (with varying kernel patches), and between kernel versions. One way to find the path ID for the TrackPoint is to use udev's path_id utility on the sysfs device path for the TrackPoint. This device path can be found using the {{path|name}} file which describes the TrackPoint. The process can be automated using the following shell command:
/lib/udev/path_id $(find /sys/devices/platform/i8042 -name name | xargs grep -Fl TrackPoint | sed 's/\/sys$.*$\/name/\1/')

Category:X1

2015-10-11T16:57:51Z

WilliamPoetra: /* Standard Features */