ThinkWiki - User contributions [en]

How to configure the TrackPoint

2010-05-06T15:32:44Z

Youam: gpointing-device-settings is in squeeze/sid, too

{| 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.
|}

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

= Configuration using Gnome=
If you are using GNOME, you might want to use [http://live.gnome.org/GPointingDeviceSettings GPointing Device Settings] as a graphical frontend.

It is available for Fedora 12, Ubuntu 9.10 and Debian Squeeze in the standard package repositories

[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]

= 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 that, a middle mouse button, which in Linux is used for the Paste operation.

But you can 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).

==== 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"
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|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", ATTR{press_to_select}="1", ATTR{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.

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

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/')

Installing Debian 4.0 (Etch) on a ThinkPad X300

2009-01-31T22:30:26Z

Youam: add article to category X300

===Installation (Network-Install)===

Installing from the Debian Netinstall-CDROM worked without any problems.
The SSD is recognized as an S-ATA drive using the ahci-driver.
The Gigabit-Ethernet-Port works out-of-the-box.

===Kernel Update===

The Kernel shipped with Debian stable (2.6.18 at the time of writing this) doesn't support many
of the features. I manually upgraded it to 2.6.25. The .config can be found
[http://scriptkiller.de/pub/thinkpad_x300_2.6.25.config here]. Alternatively you can use
more recent snapshots as described here http://wiki.debian.org/DebianKernel .

===WLAN (Intel 4965AGN)===

The driver for the wireless lan interface (iwl4965) is included in the Kernel sources.
You only need to install the binary firmware from here:
[http://packages.debian.org/lenny/firmware-iwlwifi] (you can install it in stable without problems).

I had problems with WPA-EAP/TTLS using the 2.6.25 drivers, these could be fixed with a fresh driver snapshot from http://wireless.kernel.org/en/users/Download (I used compat-wireless-2008-04-25).

===Graphics (Intel GMA965 / X3100)===

For graphics you'll need the intel_agp module from a recent kernel as well as xserver-xorg-video-intel (not in stable at the time of writing,
get it from testing).

Nothing special in xorg.conf:

Section "Device"
Identifier "Generic Video Card"
Driver "intel"
EndSection

If you want 3D-acceleration and DRI I suggest to use testing instead of stable, because many of the xserver and mesa-packages in stable are not ready, yet.

If you want to activate CRT output use `xrandr --output VGA --mode 1440x900`. If your data projector is not able to display wide screen try `xrandr --output VGA --mode 1280x1024`. For more detailed info see: [[Installing Ubuntu on a ThinkPad R60e]].

===ACPI===

You'll need the thinkpad_acpi module. I had to tweak some settings to make the backlight work:

modprobe thinkpad_acpi brightness_enable=1 brightness_mode=0 fan_control=1

To make this change permanent execute
echo "options thinkpad_acpi fan_control=1 brightness_enable=1 brightness_mode=0" \
> /etc/modprobe.d/thinkpad

After inserting the module that way, backlight can be controlled using

echo XX > /sys/class/backlight/thinkpad_screen/brightness

Where XX is a number between 0 and 15.

===Fingerprint Reader===

A short test with [[How_to_enable_the_fingerprint_reader_with_ThinkFinger|Thinkfinger]] showed no problems.

===Synaptics Touchpad===

Seems to work only with Protocol auto-dev and /dev/psaux:

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "20"
EndSection

===Fan===

Unfortunately the fan is spinning almost all the time, haven't found a way around this, yet.

[2008-4-27] The fan's controller turns off or at a low enough speed to be silent (~1800 rpm) when the CPU temp gets below 108 F. It goes back to full speed at around 111 F. At least my system sits around 108-115 F under normal usage. I don't think there's any problem with the fan staying on all the time. It's a tiny fan and air duct and is bound to make noise trying to push any reasonable amount of air. --fritz

[2008-5-13] First off, the fan shouldn't be on at all unless the CPU is being used. When I run Windows the fan is almost never on. I've worked a bit on this and have had no success. I shutdown all processes including X and the fan still runs. Therefore, this seems to be an issue with the kernel and possibly Linux not leveraging speedstep or something else on the chip correctly. I'll do a bit more digging, but this is pretty annoying and would be nice to fix because it would also mean longer battery life (heat = power). --bpontarelli

[2008-6-11] If fan_control=1 is added to thinkpad_acpi then fan speed can be controlled by `echo level 0-7 > /proc/acpi/ibm/fan`. 1 gives speed about 2000, the fan is really silent but its cooling ability is low. When I set 2, then speed is 5100 - same speed as if it's left on auto. :( For more info see: [[How to control fan speed]]. --semik

[2008-7-07] You can use the fancontrol daemon which comes with the lm-sensors package to regulate the fan from userspace. With 1800 rpm the temperature stays around 50 C when idle and the fan is barely noticable.

===HDAPS-Fun (Motion sensor)===

The X300 has a motion sensor, but it is not yet recognized by the standard hdaps-module, but if you install [[Tp smapi]] (which i suggest, because it provides a lot of information about your battery) it works fine.

===Bluetooth===

You need to do:

echo enable > /proc/acpi/ibm/bluetooth

or (as the proc interface to acpi gets deprecated)

echo -n 1 > /sys/devices/platform/thinkpad_acpi/bluetooth_enable

And magically, the Bluetooth-Daughterboard appears as an USB device:

Bus 003 Device 003: ID 0a5c:2110 Broadcom Corp.

If you like to use the ThinkPad [[Bluetooth Laser Mouse]] see the article on how to set it up.

===Sound===

Sound works if you build alsa modules yourself:
* Download latest alsa snapshot from [ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ here].
* Unpack and run:
./configure --with-debug=detect
make
make install
/etc/init.d/alsasound stop
/etc/init.d/alsasound start

*[2008-12-01] With hardy-heron 2.6.24-22-generic and alsa-driver-1.0.18a, a straight make ran into header problems. But by limiting the cards that were actually being compiled (in particular removing the '''hrtimer''' card) by reconfiguring before making, the compile worked and the sound worked. I used the following command

./configure --with-debug=basic --with-sequencer=yes --with-cards=ens1371,es1938,es1968,fm801,hda-intel,hdsp,hdspm,hifier,ice1712,ice1724,intel8x0,intel8x0m,korg1212 --with-card-options=all

but the following simplification should work also

./configure --with-debug=basic --with-sequencer=yes --with-cards=hda-intel --with-card-options=all

* You may need to modify the last two lines for your distro (or just restart if you're lazy...)
* If you're using ubuntu hardy, you probably need to create a softlink:
ln -s /lib/modules/<your kernel>/kernel/sound/ /lib/modules/<your kernel>/ubuntu/sound/alsa-driver
The alsa-driver directory may already exist, and you should either remove or rename it.

This patch is in the git kernel and won't be committed until 2.6.26, so this is your only option for a good while.

The sound works out of the box using kernel 2.6.26-rc9.

[2008-07-10] Sound works nearly out of the box with the last FC9 2.6.25.9-76 kernel (the audio codec has to be recognized exactly as "Analog Devices AD1984A", one can check it in /proc/asound/card0/codec#0) : give the module snd-hda-intel the option "model=thinkpad" -- Ptyx

===Camera===

If you build the Linux UVC drivers from SVN, the cam gets recognized:

Linux video capture interface: v2.00
uvcvideo: Found UVC 1.00 device <unnamed> (17ef:4807)
input: UVC Camera (17ef:4807) as /class/input/input9
usbcore: registered new interface driver uvcvideo
USB Video Class driver (SVN r205)

In order to build latest uvc driver:
svn checkout svn://svn.berlios.de/linux-uvc/linux-uvc/trunk
cd trunk
make
make install
rmmod uvcvideo
modprobe uvcvideo

You can display the video-stream using mplayer:

mplayer -fps 25 tv://

You'll want to use a newer version of gstreamer as well ( > 0.10.15).

The camera works out of the box starting from kernel 2.6.26-rc9.

[2008-07-10] Camera works out of the box with the last FC9 2.6.25.9-76 kernel. -- Ptyx

===Suspend & Hibernate===
Hibernation works on Lenny out of box with uswsusp package. It's pretty fast comparing to my old DELL D410, I guess thanks to SSD drive.

Suspending fails because of the e1000 driver. I must remove eth0 driver to keep notebook sleeping. If the driver is present then notebook resumes 1-2 seconds after suspending. Newer kernels (at least 2.6.26-rc9 upwards) use the e1000e driver to control the network interface, but suspending still fails. Just add
a file in /etc/pm/config.d/ and add one line

SUSPEND_MODULES="e1000e"

Now suspend works.

[2008-07-23] To fix an issue with rebooting instead of powering off after suspending to disk, set this option in /etc/uswsusp.conf --Timo

shutdown method = shutdown

===Some interesting facts===

# lspci
00:00.0 Host bridge: Intel Corporation Mobile Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile Integrated Graphics Controller (rev 0c)
00:19.0 Ethernet controller: Intel Corporation Unknown device 1049 (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation Mobile LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation Mobile IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation Unknown device 4230 (rev 61)

# lsusb
Bus 007 Device 001: ID 1d6b:0001
Bus 006 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 003 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0001
Bus 002 Device 002: ID 17ef:4807
Bus 002 Device 001: ID 1d6b:0002
Bus 001 Device 001: ID 1d6b:0002

# cat /proc/cpuinfo (at 800 Mhz)
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU L7100 @ 1.20GHz
stepping : 11
cpu MHz : 800.000
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm ida
bogomips : 2421.98
clflush size : 64

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU L7100 @ 1.20GHz
stepping : 11
cpu MHz : 800.000
cache size : 4096 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm ida
bogomips : 2394.01
clflush size : 64

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: SAMSUNG MCCOE64G Rev: PS10
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: MATSHITA Model: DVD-RAM UJ-844 Rev: RC02
Type: CD-ROM ANSI SCSI revision: 05

# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 270 MB in 3.01 seconds = 89.74 MB/sec

==References==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation guides survey (IBM/Lenovo)].

[[Category:X300]]

How to make use of Graphics Chips Power Management features

2007-01-21T04:42:56Z

Youam: nobse does not provide debian sarge xorg backports, use backports.org

=ATI Radeon Mobility chips=

==Power saving with a framebuffer console==
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:
radeonfb: Dynamic Clock Power Management enabled

==Using the X.org Radeon driver==
===Activation===
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM ThinkPad"
BoardName "ATI Radeon Mobility M9"
'''Option "DynamicClocks" "on"'''
EndSection

With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):

(**) RADEON(0): Option "DynamicClocks" "on"
(II) RADEON(0): Dynamic Clock Scaling Enabled

You do not need to do anything else, it dynamically manages the power consumption itself.

{{NOTE|Enabling DynamicClocks crashes some models. If the CPU is entering one of the lower power states (C3 or lower) during Xorg startup the display may stay black. As a workaround disable DynamicClocks in Xorg and use [[Rovclock]] instead. But it does not scale the clocks to match the workload. Update 5/2/2006: Seems fixed in Xorg6.9}}

===Problem with <tt>vbetool</tt>===

When <tt>vbetool</tt> is used to restore the display state (as done by some suspend/resume scripts), the setting of <tt>DynamicClocks</tt> is forgotten and the GPU will consume more power until the next X server startup. You can manually enable DynamicTools again by starting a blank second X server (e.g., by running {{cmdroot|X :1}}) and then exiting it via {{key|Ctrl}}{{key|Alt}}{{key|Backspace}}.

===Problem with suspend-to-disk===

Upon resume from suspend-to-disk, the setting of <tt>DynamicClocks</tt> is forgotten and the GPU will consume more power until the next X server startup. You can manually enable DynamicClocks again by starting a blank second X server (e.g., by running {{cmdroot|X :1}}) and then exiting it via {{key|Ctrl}}{{key|Alt}}{{key|Backspace}}.

If you're using the hibernate script that's part of [[Software Suspend 2]], setting UseDummyXServer to yes in {{path|hibernate.conf}} automatically starts a second X server, hence enabling DynamicClocks again. (Remember to disable UseDummyXServer if you switch to the [[fglrx]] driver, otherwise your computer will hang upon resume.)

Note: When using the [[Synaptics TouchPad driver for X]] with the SHMConfig-Option set to true in {{path|xorg.conf}}, starting a second X server breaks the Shared Memory and the touchpad can't be configured with {{cmd|synclient|}} any longer. Starting the dummy X server with a different xorg.conf file is a solution to this, a patch can be found in the [http://bugzilla.suspend2.net/show_bug.cgi?id=138 suspend2 bugzilla].

===Debian Notes===
If your {{Debian}} doesn't have Xorg, yet, see [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].

Sarge backports are available from [http://www.backports.org/ here].

==Using the ATI proprietary driver==

Versions 8.19.10 and higher of the ATI [[fglrx]] driver support "PowerPlay", which "allows for the user to switch between power consumption modes".

To list available modes do:
:{{cmdroot|aticonfig --list-powerstates}}
:{{cmdresult|   core/mem     [flags]}}
:{{cmdresult|---------------}}
:{{cmdresult|1: 105/122 MHz  [low voltage]}}
:{{cmdresult|2: 209/182 MHz  [low voltage]}}
:{{cmdresult|3: 297/230 MHz  [default state]}}

(Strangely, the same ThinkPad {{T43}} with [[ATI Mobility Radeon X300]] running [[fglrx]] 8.19.10 sometimes gives other, non-sensical results, perhaps due to interaction with [[rovclock]].)

To changing the power mode on the fly:
:{{cmdroot|1=aticonfig --set-powerstate=2 --effective=now}}

With newer driver versions (8.26 and later), <tt>atieventsd</tt> should dynamically change the power state and clock, depending on thermal conditions and AC plug.

Limitations (as of [[fglrx]] 8.19.10):
* You can't set the power state in {{path|/etc/X11/xorg.conf}} .
* You can't activate power saving when using dual-head mode (e.g., LCD+CRT).

{{NOTE|[[fglrx]] power saving is not compatible with the [[Rovclock]] utility. Setting power saving mode using both [[fglrx]] and [[Rovclock]] results in an unusably slow desktop.}}

==External sources==
*[http://www.ati.com/products/pdf/powerplaywp2.pdf Marketing information from ATI]

=Other graphics chips=
No instructions are presently known for other chips.

But see [[Problem with display remaining black after resume]].

[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]