ThinkWiki - User contributions [en]

How to configure the TrackPoint

2017-03-21T10:22:49Z

Fhackenberger: /* Configuring other options (e.g. Press to select, Sensitivity and 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. In order to make sure you are using the right constraints (SUBSYSTEM, DRIVERS, etc), you can run {{cmdroot|udevadm info --query all --attribute-walk --path /sys/devices/platform/i8042/serio1/serio2}}.

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

On trusty, the following works for me:
<pre>
KERNEL=="serio2", SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="255"
</pre>

On xenial (16.04) the following line works for me (WAIT_FOR is not supported anymore):
<pre>
KERNEL=="serio2", SUBSYSTEM=="serio", DRIVERS=="psmouse", ATTR{sensitivity}:="255", ATTR{speed}:="255"
</pre>

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. 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: 
eix xf86-input-evdev 
emerge -C xf86-input-evdev 
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/')

Problem with CPU frequency scaling

2016-09-21T11:28:59Z

Fhackenberger: /* Nothing else works and you know what you are doing? */

{{stub}}

{{WARN|CPU frequency limitation is a safety feature of your ThinkPad, do not work around it! If you have set the BIOS to performance mode and it is still limiting maximum CPU frequency, there is almost always a good reason for it.}}

==Symptom==
If the battery pack is removed and the laptop is powered by a 65W AC adapter only, the CPU downclocks to the lowest multiplier and remains locked in low speed. This happens irrespective of the scaling method in use (kernelspace or userspace) and of the frequency governor selected (ondemand, performance, etc.).

Output of {{cmduser|cpupower frequency-info}} (on AC power without battery):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Output of {{cmduser|cpupower frequency-info}} (on AC power with battery plugged in):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

==Explanation==

The 65W AC adaptor does not supply enough power to handle peak power draws from the CPU/disk/GPU on the later ThinkPads. The battery is required to supply the peak demand and ensure correct system operation.

Messing with this can cause data loss, data corruption, and hardware damage.

==Solution==

=== Is thermal mangament limiting the speed? ===
* Make sure no BIOS setting is limiting the CPU frequency range (e.g., thermal management = "BALANCED").

=== Is the ThinkPad running on a 65W power adapter? ===
* Either replace the 65W AC adapter with a 90W AC adapter, or
* Install a battery

=== Nothing else works and you know what you are doing? ===
* Add "processor.ignore_ppc=1" to kernel boot command line or run {{cmduser|echo 1 | sudo tee /sys/module/processor/parameters/ignore_ppc}}. This allows to disable BIOS frequency limit, but can be cause the computer to malfunction if its power consumption is higher than 65W and you are running off a 65W AC power adapter with no battery installed.

== Affected Models ==

Confirmed for these models
* {{T410}}
* {{T410s}}
* {{T43p}}
* {{T60p}}
* {{T61}}
* {{X201}}
* {{X61}}
* {{Z61m}}

but it is probably true of all Lenovo ThinkPads. One can actually track this through the DSDT, but it is not worth the effort.

Problem with CPU frequency scaling

2016-09-21T11:27:58Z

Fhackenberger: /* Nothing else works and you know what you are doing? */

Problem with CPU frequency scaling

2016-09-21T11:27:24Z

Fhackenberger: /* Nothing else works and you know what you are doing? */

{{stub}}

{{WARN|CPU frequency limitation is a safety feature of your ThinkPad, do not work around it! If you have set the BIOS to performance mode and it is still limiting maximum CPU frequency, there is almost always a good reason for it.}}

==Symptom==
If the battery pack is removed and the laptop is powered by a 65W AC adapter only, the CPU downclocks to the lowest multiplier and remains locked in low speed. This happens irrespective of the scaling method in use (kernelspace or userspace) and of the frequency governor selected (ondemand, performance, etc.).

Output of {{cmduser|cpupower frequency-info}} (on AC power without battery):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Output of {{cmduser|cpupower frequency-info}} (on AC power with battery plugged in):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

==Explanation==

The 65W AC adaptor does not supply enough power to handle peak power draws from the CPU/disk/GPU on the later ThinkPads. The battery is required to supply the peak demand and ensure correct system operation.

Messing with this can cause data loss, data corruption, and hardware damage.

==Solution==

=== Is thermal mangament limiting the speed? ===
* Make sure no BIOS setting is limiting the CPU frequency range (e.g., thermal management = "BALANCED").

=== Is the ThinkPad running on a 65W power adapter? ===
* Either replace the 65W AC adapter with a 90W AC adapter, or
* Install a battery

=== Nothing else works and you know what you are doing? ===
* Add "processor.ignore_ppc=1" to kernel boot command line or run "echo 1 | sudo tee /sys/module/processor/parameters/ignore_ppc". This allows to disable BIOS frequency limit, but can be cause the computer to malfunction if its power consumption is higher than 65W and you are running off a 65W AC power adapter with no battery installed.

== Affected Models ==

Confirmed for these models
* {{T410}}
* {{T410s}}
* {{T43p}}
* {{T60p}}
* {{T61}}
* {{X201}}
* {{X61}}
* {{Z61m}}

but it is probably true of all Lenovo ThinkPads. One can actually track this through the DSDT, but it is not worth the effort.

How to configure the TrackPoint

2016-03-18T11:22:05Z

Fhackenberger: Fixed cmdroot display

{| 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. In order to make sure you are using the right constraints (SUBSYSTEM, DRIVERS, etc), you can run {{cmdroot|udevadm info --query all --attribute-walk --path /sys/devices/platform/i8042/serio1/serio2}}.

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

On trusty, the following works for me:
<pre>
KERNEL=="serio2", SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="255"
</pre>

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. 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: 
eix xf86-input-evdev 
emerge -C xf86-input-evdev 
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/')

How to configure the TrackPoint

2016-03-18T11:18:57Z

Fhackenberger: Fix for udev rule on trusty

{| 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. In order to make sure you are using the right constraints (SUBSYSTEM, DRIVERS, etc), you can run {{cmdroot|udevadm info --query=all --attribute-walk --path=/sys/devices/platform/i8042/serio1/serio2}}.

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

On trusty, the following works for me:
<pre>
KERNEL=="serio2", SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="255"
</pre>

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. 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: 
eix xf86-input-evdev 
emerge -C xf86-input-evdev 
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 Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-03T10:16:53Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen] and optionally [https://launchpad.net/~f-hackenberger/+archive/x220-intel-mesa x220 intel mesa PPA from fhackenberger] (for 3D and desktop effects), update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel. Suspend works, even with USB 3.0 and 3D.

Just for reference here are the versions of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
libgl1-mesa-dri 7.10.2-0ubuntu3
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-03T10:16:15Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen] and optionally [https://launchpad.net/~f-hackenberger/+archive/x220-intel-mesa x220 intel mesa PPA from fhackenberger] (for 3D and desktop effects), update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel. Suspend works, even with USB 3.0 and 3D.

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
libgl1-mesa-dri 7.10.2-0ubuntu3
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-03T10:15:29Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen] and optionally [https://launchpad.net/~f-hackenberger/+archive/x220-intel-mesa x220 intel mesa PPA from fhackenberger] (for 3D and desktop effects), update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel. Suspend works, even with USB 3.0 and 3D.

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-03T10:13:50Z

Fhackenberger: Added info regarding 3D

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

If you would like to have 3D (Desktop effects), you can also add the [https://launchpad.net/~f-hackenberger/+archive/x220-intel-mesa x220 intel mesa PPA from fhackenberger].

You have to reboot to load the new kernel. Suspend works, even with USB 3.0.

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-03T09:37:31Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel. Suspend works, even with USB 3.0. Compiz does not yet work, as the Sandybridge GPU 3D mesa driver is not yet available as a PPA for lucid and the card is [https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/644372 blacklisted]. Using the compiz packages from [https://launchpad.net/~compiz/+archive/ppa compiz-ppa] did not help, as they do not seem to contain the fix.

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

How to configure the TrackPoint

2011-06-02T10:18:16Z

Fhackenberger: /* Configuring other options (e.g. Press to select, Sensitivity and 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-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

[[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 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|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, 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}}

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. 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: 
eix xf86-input-evdev 
emerge -C xf86-input-evdev 
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 Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T13:16:48Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel. Suspend works, even with USB 3.0. Compiz does not yet work, as the Sandybridge GPU is [https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/644372 blacklisted]. Using the compiz packages from [https://launchpad.net/~compiz/+archive/ppa compiz-ppa] did not help, as they do not seem to contain the fix.

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T13:06:46Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel. Suspend works, even with USB 3.0. Compiz does not yet work, as the Sandybridge GPU is [https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/644372 blacklisted].

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T12:57:34Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel. Suspend works, even with USB 3.0.

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T12:56:23Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~kernel-ppa/+archive/ppa Ubuntu kernel PPA] and the [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-natty''' (linux-image-generic-lts-backport-natty is an alternative if you don't have > 4GB memory). That pulls in a 2.6.38 kernel backported from Natty, which is required for the updated intel video driver (version 2.15) to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels. Make sure you install the kernel AFTER upgrading libdrm (which is provided by [https://launchpad.net/~glasen/+archive/intel-driver intel-driver PPA from glasen], or run ''update-initramfs -u -k all''). Otherwise the new libdrm will not be loaded and the xorg driver will not work.

You have to reboot to load the new kernel.

Just for reference here are the version of the critical packages I have tested:
<pre>
linux-image-generic-pae-lts-backport-natty 2.6.38.8.18
xserver-xorg-video-intel 2:2.15.0~lucid~ppa4
libdrm-intel1 2.4.25~glasen~lucid~ppa1
libdrm2 2.4.25~glasen~lucid~ppa1
</pre>

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T11:46:33Z

Fhackenberger: /* Kernel & Graphics */

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~xorg-edgers/+archive/ppa edgers ppa], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-maverick''' (exchange ''generic-pae'' for your preferred flavour/architecture). That pulls in a 2.6.35 kernel backported from Maverick, which is required for the updated intel video driver to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels.

You have to reboot to load the new kernel.

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz on the terminal (before logging in using the GUI) by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T11:45:51Z

Fhackenberger:

== Kernel & Graphics ==
In order to get an intel video driver to recognise the new Sandybridge, you have to add the [https://launchpad.net/~xorg-edgers/+archive/ppa edgers ppa], update all package (this pulls in a new xorg version) and then install '''linux-image-generic-pae-lts-backport-maverick''' (exchange ''generic-pae'' for your preferred flavour/architecture). That pulls in a 2.6.35 kernel backported from Maverick, which is required for the updated intel video driver to work. It also contains an updated e1000e driver for your network card, which does not work with the Lucid kernels.

You have to reboot to load the new kernel.

If you have compiz enabled, you might experience a hanging machine after logging in. If you are running Gnome, you can disable compiz by editing ''~/.gconf/desktop/gnome/session/required_components/%gconf.xml'' and replacing compiz with ''metacity''.

== Wireless Lucid Kernel ==
In order to get wireless to work with the Lucid kernel (it did not connect to any AP on my {{X220}} machine and could not upgrade because the Ethernet did not work either), you have to pass the parameter ''11n_disable=0'' to the iwlagn module. Simply do:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn 11n_disable=0
</pre>

As an alternative you can create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
I had to do that a few times, before it worked.
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T10:28:10Z

Fhackenberger:

== Wireless ==
In order to get wireless to work (it did not connect to any AP on my {{X220}} machine), you have to create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T10:27:14Z

Fhackenberger:

== Wireless ==
In order to get wireless to work (it did not connect to any AP on my machine), you have to create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.conf'' with the following content:
<pre>
options iwlagn 11n_disable=0
</pre>
Then reload the wireless driver:
<pre>
sudo modprobe -r iwlagn
sudo modprobe iwlagn
</pre>
[[Category:X220]]
[[Category:Ubuntu 10.04]]

Installing Ubuntu 10.04 (Lucid Lynx) on a ThinkPad X220

2011-06-01T10:26:16Z

Fhackenberger: â†Created page with '== Wireless == In order to get wireless to work (it did not connect to any AP on my machine), you have to create the file ''/etc/modprobe.d/intel-5300-iwlagn-disable11n.co...'

How to configure the TrackPoint

2010-08-11T18:41:22Z

Fhackenberger: On ubuntu 10.04 grepping for product does not work, it's ATTRS{name} in that case

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

[[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 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|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|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", 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.
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", ATTR{sensitivity}="122"
</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}}

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. 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: 
eix xf86-input-evdev 
emerge -C xf86-input-evdev 
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 Ubuntu 7.04 (Feisty Fawn) on an X61 Tablet

2008-02-24T13:57:42Z

Fhackenberger: /* Suspend and Hibernate */

You can get Linux running pretty smoothly on this machine. I will simply repeat the steps I used to get my tablet working, some of these steps might be superfluous. Please edit, if some of the steps are unneccessary. I expect Gutsy Gibbon installs to be much smoother, when the system comes out in October...

===Helpful Guides===
A helpful guide for me was http://luke.no-ip.org/x60tablet/

===Feisty v. Gutsy===
I have gotten the computer to work well with both Feisty and Gutsy Tribe 4 and 5. If you install Feisty, you will have to upgrade to the 2.6.22 kernel to get all the drivers to work. I would advise using Gutsy, as it makes everything easier to set up (with drivers). The 2.6.23 kernel, once it officially comes out, should *probably* make this laptop an out-of-the-box machine. (the 2.6.23 kernel has plans to include the graphics, sound, and wireless drivers for this machine by default)

===Known Problems===
These are issues that I have run into and have not resolved yet. None of them are 'show stoppers' in my book. If you have a fix, please add how to resolve the issue on this page (preferrably in the respective how-to section..)

*Screen rotation with 3D acceleration. Both screen rotation (through xrandr) and 3d acceleration work independantly, however a rotated screen crashes when you try to run a 3d application.
*ALSA sound glitch when rotating to tablet mode. For some reason rotating to tablet mode from laptop mode causes the sound to cut out. Sound works otherwise.
*Brightness auto-adjust on Gutsy. Brightness auto adjust cannot determine what level to stay at, and indefinitely adjusts up and down. Pressing the brightness keys fixes this. See launchpad for the official bug '''Already fixed in Gutsy'''

===Actual installation===
***Works in both Feisty and Gutsy

The trickiest part about actually installing Ubuntu on this machine is that there is no CD drive. If you've shelled out the $200 for the 'ultrabase' then you can just pop the CD in that, and procede normally. I had to install via a pendrive. Instructions on how to do this are at

http://www.pendrivelinux.com/2007/02/12/usb-ubuntu-tutorial-for-linux-users/

*On my machine, and with my particular USB drive, I found that it was difficult get power to the USB drive in a normal boot process. I had to enter the BIOS (F1 during power on), configure the USB HDD to be first boot choice, and then enable the POST memory check (extended boot?, I think it was called). Then I had to insert the USB drive during the memory check, and make sure the light on the USB came on in order to get it to boot from the installer. Hopefully most people won't have this problem, but I did, so if you have problems getting the drive to be seen, make sure the USB is getting powered.

===Graphics Card===
***Feisty
The X3100 with an Intel GMA965 runs Compiz Fusion very nicely, once the proper drivers are installed. The 'i810' driver that is installed by default with Feisty does not support the X3100, but there are newer drivers (simply named 'intel') that do support it. Source is available from http://www.intellinuxgraphics.org/. Unfortunately, installing on the stock kernel (2.6.18, if I remember) does not work with these drivers, as agpgart is incorrectly registered. I upgraded to 2.6.22 and the drivers work nicely. Here's the walkthrough...

*Install the new kernel

# gedit /etc/apt/sources.list
Add the Gutsy repositories
# deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
# deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
Save and exit gedit

Install the new kernel
# apt-get update
# apt-get install linux-image-2.6.22-9-generic linux-ubuntu-modules-2.6.22-9-generic linux-backports-modules-2.6.22-9-generic linux-headers-2.6.22-9 linux-headers-2.6.22-9-generic linux-restricted-modules-2.6.22-9-generic

Reboot. Make sure to select the new kernel in GRUB when you turn on the computer.

Install the graphics card drivers from the repositories
# sudo apt-get install xserver-xorg-video-intel xserver-xorg libgl1-mesa-dri libgl1-mesa-glx libglu1-mesa mesa-utils

Let X11 know to use the Intel drivers
# gedit /etc/X11/xorg.conf

Change
Section "Device"
Identifier "Generic Video Card"
Driver "vesa"
BusID "PCI:0:2:0"
EndSection

to

Section "Device"
Identifier "Generic Video Card"
Driver "intel"
BusID "PCI:0:2:0"
EndSection

Reboot

***Gutsy
3d acceleration works out of the box, but I had to compile compiz fusion and awm from source to get them to work. If I find time, I'll make a deb for both....

===Solving the Weird Resolution Problems===
***Applies to both Feisty and Gutsy
When you reboot into the new drivers, it seems that X defaults to the graphics card's 'TV' output instead of the 'LVDS' option as it should. This will cause X to be confused about where the screen edges are, and in general make everything weird. This can be corrected in one of two ways

*Solution 1:
Everytime you log in, enter this command
# xrandr --output TV --off

*Solution 2:
Edit xorg.conf to automatically correct this problem. Note that this will cause xrandr (which you may want to use for screen rotation) to fail when you try to use it.

add this to the device section

Option "monitor-TV" "TVOutput"
Option "CacheLines" "32768"
Option "TripleBuffer" "true"
Option "DRI" "true"
Option "PageFlip" "true"

add this at the bottom

Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection

save and exit, restart X

===Installing compiz fusion===
***Feisty
Basically, I followed the instructions at
http://fosswire.com/2007/07/11/how-to-compiz-fusion-on-ubuntu-704-feisty-fawn/

The line about adding the GPG keys is malformed, copying and pasting won't work. Use this command
# gpg --keyserver subkeys.pgp.net --recv-keys 81836EBF
# gpg --export --armor 81836EBF | sudo apt-key add -

***Gutsy
I had to compile from source. This is a kinda long process, and you have to have programming/compiling skills, but it definitely works well if you can do it.

There you go! Now you have a visually gorgeous system running :-D! All the effects run very smoothly for me, I was very pleased with this integrated card's performance... (no stuttering for even complex effects like explode or airplane)

===Wireless===
This essential laptop feature will definitely work. The intel ABG card has drivers, guides should abound as to how to install it. (if anyone has time, put how you got it to work here) I purchased the newer AGN card, and this is how I installed the new drivers.

Walkthough for newbies :-)

download these:
http://intellinuxwireless.org/mac80211/downloads/mac80211-8.0.2.tgz
http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-4965-ucode-4.44.17.tgz
http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-1.0.0.tgz

extract them

prepare the build environment
# sudo mkdir /lib/firmware/$(uname -r)
# sudo ln -s /usr/src/linux-headers-$(uname -r) /lib/modules/$(uname -r)/source

make everything

# cd mac80211-8.0.2
# sudo make patch_kernel

# cd ../iwlwifi-1.0.0
# make
# sudo make install

# cd ../iwlwifi-4965-ucode-4.44.17
# sudo cp iwlwifi-4965.ucode /lib/firmware/$(uname -r)

Finally, Load the modules
sudo modprobe mac80211
sudo modprobe iwl4965

You should have wifi now!

Thanks goes to rye_ of ubuntuforums!

They work pretty well, I've only noticed them being flaky once.

===Wacom===
We bought this machine largely for the tablet abilities, and the pen works out of the box! Yay! The side button automatically maps to scrollwheel-pressed-down, but you can remap it to right click if you want. Eraser also works.

===Tablet-Specific Applications===
We're tablet users and we have special needs! Here are some apps I found these apps indespensible

Jot.
When I placed my order for my tablet, Lenovo said I had a full month wait til it arrived. I filled the time writing a handwriting recognition app for Linux. My goal is to allow for full sentence or full word recognition. As of 8/20/2007, its still in alpha testing, but I should have a pretty good release mid-September to early October. Source is available from http://bazaar.launchpad.net/~kdub432/jot/trunk. You need libfakekey0, gtkmm-2.4-dev, libcairomm-1.0-dev installed so the makefile will work...

Onestroke.
This program will recognize a single character at a time pretty well. Its written by Michael Levin, and is in pretty usuable condition. Onestroke can be found at
http://www.paperaffinity.com/risujin/onestroke.php

Xournal
A journal clone, that is great for taking notes. Fully functional, an all-around great app.
#apt-get install xournal

'''[[CellWriter]]'''

CellWriter is a grid-entry natural handwriting input panel. As you write characters into the cells, your writing is instantly recognized at the character level. When you press Enter on the panel, the input you entered is sent to the currently focused application as if typed on the keyboard.

GoK warning!!! Running GoK on Feisty screwed up some things for me. It may be that I was just too lazy to fix my dependancies, but I was real ticked at how it installed itself when I was running Feisty. Use the default Ubuntu program onboard ('onboard' from a terminal) if you want an onscreen keyboard

===Sound===
Sound does not work out of the box, with Gutsy or Feisty, but the mercurial/cvs alsa drivers do have support. This issue was extremely hard to track down, and requires some advanced knowledge. I will provide a short walkthrough to give some guidance.

Step 1 Setup a fundamental build environment
# sudo apt-get install mercurial build-essential libncurses5-dev python2.5 automake libtool
# sudo mkdir /usr/src/alsa
# cd /usr/src/alsa

(This was taken just from memory, if you get errors about something not being installed, just install whatever it complains about...)

Next, get latest alsa drivers
# sudo hg clone http://hg.alsa-project.org/alsa-driver alsa-driver
# sudo hg clone http://hg.alsa-project.org/alsa-kernel alsa-kernel
# sudo hg clone http://hg.alsa-project.org/alsa-lib alsa-lib
# sudo hg clone http://hg.alsa-project.org/alsa-utils alsa-utils

Install everything
# cd alsa-driver
# sudo ./cvscompile --with-cards=all --with-card-options=all (Nota Bene, this makes all the drivers. do more research if you just want the intel ones ;-D)
# sudo make install
# cd ../alsa-lib
# sudo ./cvscompile
# sudo make install
# cd ../alsa-utils
# sudo ./cvscompile
# sudo make install

Phew, that was tough. Its not over yet though, you've gotta edit some configuration files
sudo nano /etc/modprobe.d/alsa-base

and add this to the bottom,

options snd-hda-intel model=thinkpad

Save, exit and reboot.

THIS IS VERY IMPORTANT! IT TOOK ME 5+ HOURS TO FIGURE THIS OUT ON MY OWN!

YOU MUST HAVE BIOS SET TO FACTORY INSTALL (for the most part)

Certain BIOS options seem to break these drivers! I'm not sure which, but the factory settings work fine.

On next login, you should have sound. If you don't, make sure nothing is muted in alsaconf/alsamixer.
Also, make sure your login name is in the 'audio' or 'users' groups.

Alright, you have sound now! Yay!

Both headphones and speakers work, theres a switch on a tab in the gnome panel audio adjustment properties that turns either on/off

Note! It has been brought to my attention that an ubuntu developer has compiled packages for these drivers. I have not tested these yet and cannot ensure that they will work, although there are people on this site who have reported sucess using these packages
https://bugs.launchpad.net/ubuntu/+bug/122560

For what it's worth, I installed Ubuntu 7.10 on my new X61 tablet and sound worked (almost) out of the box. The bugs I see are that the built-in volume control buttons are mapped to the microphone channel instead of the speaker channel, and there's an issue with XMMS not being able to share the sound channel with Firefox (though maybe that's a wider issue than the X61tablet).

===Keyboard and Buttons===
You should have no trouble with getting the main 105 keys to work.

Some of the Fn buttons work, some don't. I'm still wading through ways to get these to work, but they're not super-high on my priority list. If you find ways, feel free to post :-)....

Screen Buttons.
The D-pad will work, but by default maps to weird values. Add
setkeycodes 6f 108
setkeycodes 71 103
setkeycodes 6e 105
setkeycodes 6d 106

to /etc/rc.local to make the D-pad work like your keyboard arrow keys. The middle button is 'Enter'

The other buttons also work. I have not mapped them to anything specific yet, but in a real terminal (no X environment), you can use the showkey command and setkeycodes to map the other 4 buttons to whatever you want. More instructions on this will follow once I decide what I want to use these 4 buttons for

===Suspend and Hibernate===
The default Ubuntu suspend and resume cycle causes a kernel panic. I got my computer to flawlessly suspend and resume by installing pm-utils
sudo apt-get install pm-utils

then you can suspend using the command
sudo pm-suspend --quirk-s3-bios --quirk-s3-mode

I'm content with suspend working, but if anyone figures out hibernate, let me know :-D

Works for Gutsy (please confirm for Feisty): In order to make the quirk settings the default for your machine, apply the following patch:
<pre>
--- /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi.orig 2007-10-08 13:35:45.000000000 +0200
+++ /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi 2008-01-20 11:16:58.000000000 +0100
@@ -2,6 +2,11 @@
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
+ 
+ <match key="system.hardware.product" prefix="776796U">
+ <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
+ <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
+ </match>

<match key="system.hardware.product" prefix="1702">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
</pre>
Make sure you adjust the prefix="776796U" to match your particular model, using the output from the following command:
<pre>
lshal |grep system.hardware.product
</pre>
You have to reboot your machine to make the changes permanent (restarting hal should actually be sufficient, but was not on my system). After that, gnome should be able to suspend/resume your system without crashing the machine or leaving the video backlight off. The only issue left on my system is that NetworkManager hangs after a resume, but that is easily solved by creating the following script in /etc/pm/sleep.d/01NetworkManagerRestart and making it executable by 'sudo chmod +x /etc/pm/sleep.d/01NetworkManagerRestart':
<pre>
#!/bin/bash
case $1 in
hibernate)
;;
suspend)
;;
thaw)
;;
resume)
/bin/sh -c 'sleep 3;modprobe -r ipw3945;modprobe ipw3945;' &
;;
*) echo "somebody is calling me totally wrong."
;;
esac
</pre>

== Other x61 install guides on the web ==
* http://bayleshanks.com/tips-computer-lenovoX61t-gnuLinuxSetup (feel free to integrate the content on that page into this wiki -- Bayle)

[[Category:X61 Tablet]]

Installing Ubuntu 7.04 (Feisty Fawn) on an X61 Tablet

2008-01-20T10:28:21Z

Fhackenberger:

You can get Linux running pretty smoothly on this machine. I will simply repeat the steps I used to get my tablet working, some of these steps might be superfluous. Please edit, if some of the steps are unneccessary. I expect Gutsy Gibbon installs to be much smoother, when the system comes out in October...

===Helpful Guides===
A helpful guide for me was http://luke.no-ip.org/x60tablet/

===Feisty v. Gutsy===
I have gotten the computer to work well with both Feisty and Gutsy Tribe 4 and 5. If you install Feisty, you will have to upgrade to the 2.6.22 kernel to get all the drivers to work. I would advise using Gutsy, as it makes everything easier to set up (with drivers). The 2.6.23 kernel, once it officially comes out, should *probably* make this laptop an out-of-the-box machine. (the 2.6.23 kernel has plans to include the graphics, sound, and wireless drivers for this machine by default)

===Known Problems===
These are issues that I have run into and have not resolved yet. None of them are 'show stoppers' in my book. If you have a fix, please add how to resolve the issue on this page (preferrably in the respective how-to section..)

*Screen rotation with 3D acceleration. Both screen rotation (through xrandr) and 3d acceleration work independantly, however a rotated screen crashes when you try to run a 3d application.
*ALSA sound glitch when rotating to tablet mode. For some reason rotating to tablet mode from laptop mode causes the sound to cut out. Sound works otherwise.
*Brightness auto-adjust on Gutsy. Brightness auto adjust cannot determine what level to stay at, and indefinitely adjusts up and down. Pressing the brightness keys fixes this. See launchpad for the official bug '''Already fixed in Gutsy'''

===Actual installation===
***Works in both Feisty and Gutsy

The trickiest part about actually installing Ubuntu on this machine is that there is no CD drive. If you've shelled out the $200 for the 'ultrabase' then you can just pop the CD in that, and procede normally. I had to install via a pendrive. Instructions on how to do this are at

http://www.pendrivelinux.com/2007/02/12/usb-ubuntu-tutorial-for-linux-users/

*On my machine, and with my particular USB drive, I found that it was difficult get power to the USB drive in a normal boot process. I had to enter the BIOS (F1 during power on), configure the USB HDD to be first boot choice, and then enable the POST memory check (extended boot?, I think it was called). Then I had to insert the USB drive during the memory check, and make sure the light on the USB came on in order to get it to boot from the installer. Hopefully most people won't have this problem, but I did, so if you have problems getting the drive to be seen, make sure the USB is getting powered.

===Graphics Card===
***Feisty
The X3100 with an Intel GMA965 runs Compiz Fusion very nicely, once the proper drivers are installed. The 'i810' driver that is installed by default with Feisty does not support the X3100, but there are newer drivers (simply named 'intel') that do support it. Source is available from http://www.intellinuxgraphics.org/. Unfortunately, installing on the stock kernel (2.6.18, if I remember) does not work with these drivers, as agpgart is incorrectly registered. I upgraded to 2.6.22 and the drivers work nicely. Here's the walkthrough...

*Install the new kernel

# gedit /etc/apt/sources.list
Add the Gutsy repositories
# deb http://archive.ubuntu.com/ubuntu gutsy main restricted universe multiverse
# deb-src http://security.ubuntu.com/ubuntu gutsy main restricted universe multiverse
Save and exit gedit

Install the new kernel
# apt-get update
# apt-get install linux-image-2.6.22-9-generic linux-ubuntu-modules-2.6.22-9-generic linux-backports-modules-2.6.22-9-generic linux-headers-2.6.22-9 linux-headers-2.6.22-9-generic linux-restricted-modules-2.6.22-9-generic

Reboot. Make sure to select the new kernel in GRUB when you turn on the computer.

Install the graphics card drivers from the repositories
# sudo apt-get install xserver-xorg-video-intel xserver-xorg libgl1-mesa-dri libgl1-mesa-glx libglu1-mesa mesa-utils

Let X11 know to use the Intel drivers
# gedit /etc/X11/xorg.conf

Change
Section "Device"
Identifier "Generic Video Card"
Driver "vesa"
BusID "PCI:0:2:0"
EndSection

to

Section "Device"
Identifier "Generic Video Card"
Driver "intel"
BusID "PCI:0:2:0"
EndSection

Reboot

***Gutsy
3d acceleration works out of the box, but I had to compile compiz fusion and awm from source to get them to work. If I find time, I'll make a deb for both....

===Solving the Weird Resolution Problems===
***Applies to both Feisty and Gutsy
When you reboot into the new drivers, it seems that X defaults to the graphics card's 'TV' output instead of the 'LVDS' option as it should. This will cause X to be confused about where the screen edges are, and in general make everything weird. This can be corrected in one of two ways

*Solution 1:
Everytime you log in, enter this command
# xrandr --output TV --off

*Solution 2:
Edit xorg.conf to automatically correct this problem. Note that this will cause xrandr (which you may want to use for screen rotation) to fail when you try to use it.

add this to the device section

Option "monitor-TV" "TVOutput"
Option "CacheLines" "32768"
Option "TripleBuffer" "true"
Option "DRI" "true"
Option "PageFlip" "true"

add this at the bottom

Section "Monitor"
Identifier "TVOutput"
Option "Disable" "true"
EndSection

save and exit, restart X

===Installing compiz fusion===
***Feisty
Basically, I followed the instructions at
http://fosswire.com/2007/07/11/how-to-compiz-fusion-on-ubuntu-704-feisty-fawn/

The line about adding the GPG keys is malformed, copying and pasting won't work. Use this command
# gpg --keyserver subkeys.pgp.net --recv-keys 81836EBF
# gpg --export --armor 81836EBF | sudo apt-key add -

***Gutsy
I had to compile from source. This is a kinda long process, and you have to have programming/compiling skills, but it definitely works well if you can do it.

There you go! Now you have a visually gorgeous system running :-D! All the effects run very smoothly for me, I was very pleased with this integrated card's performance... (no stuttering for even complex effects like explode or airplane)

===Wireless===
This essential laptop feature will definitely work. The intel ABG card has drivers, guides should abound as to how to install it. (if anyone has time, put how you got it to work here) I purchased the newer AGN card, and this is how I installed the new drivers.

Walkthough for newbies :-)

download these:
http://intellinuxwireless.org/mac80211/downloads/mac80211-8.0.2.tgz
http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-4965-ucode-4.44.17.tgz
http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-1.0.0.tgz

extract them

prepare the build environment
# sudo mkdir /lib/firmware/$(uname -r)
# sudo ln -s /usr/src/linux-headers-$(uname -r) /lib/modules/$(uname -r)/source

make everything

# cd mac80211-8.0.2
# sudo make patch_kernel

# cd ../iwlwifi-1.0.0
# make
# sudo make install

# cd ../iwlwifi-4965-ucode-4.44.17
# sudo cp iwlwifi-4965.ucode /lib/firmware/$(uname -r)

Finally, Load the modules
sudo modprobe mac80211
sudo modprobe iwl4965

You should have wifi now!

Thanks goes to rye_ of ubuntuforums!

They work pretty well, I've only noticed them being flaky once.

===Wacom===
We bought this machine largely for the tablet abilities, and the pen works out of the box! Yay! The side button automatically maps to scrollwheel-pressed-down, but you can remap it to right click if you want. Eraser also works.

===Tablet-Specific Applications===
We're tablet users and we have special needs! Here are some apps I found these apps indespensible

Jot.
When I placed my order for my tablet, Lenovo said I had a full month wait til it arrived. I filled the time writing a handwriting recognition app for Linux. My goal is to allow for full sentence or full word recognition. As of 8/20/2007, its still in alpha testing, but I should have a pretty good release mid-September to early October. Source is available from http://bazaar.launchpad.net/~kdub432/jot/trunk. You need libfakekey0, gtkmm-2.4-dev, libcairomm-1.0-dev installed so the makefile will work...

Onestroke.
This program will recognize a single character at a time pretty well. Its written by Michael Levin, and is in pretty usuable condition. Onestroke can be found at
http://www.paperaffinity.com/risujin/onestroke.php

Xournal
A journal clone, that is great for taking notes. Fully functional, an all-around great app.
#apt-get install xournal

'''[[CellWriter]]'''

CellWriter is a grid-entry natural handwriting input panel. As you write characters into the cells, your writing is instantly recognized at the character level. When you press Enter on the panel, the input you entered is sent to the currently focused application as if typed on the keyboard.

GoK warning!!! Running GoK on Feisty screwed up some things for me. It may be that I was just too lazy to fix my dependancies, but I was real ticked at how it installed itself when I was running Feisty. Use the default Ubuntu program onboard ('onboard' from a terminal) if you want an onscreen keyboard

===Sound===
Sound does not work out of the box, with Gutsy or Feisty, but the mercurial/cvs alsa drivers do have support. This issue was extremely hard to track down, and requires some advanced knowledge. I will provide a short walkthrough to give some guidance.

Step 1 Setup a fundamental build environment
# sudo apt-get install mercurial build-essential libncurses5-dev python2.5 automake libtool
# sudo mkdir /usr/src/alsa
# cd /usr/src/alsa

(This was taken just from memory, if you get errors about something not being installed, just install whatever it complains about...)

Next, get latest alsa drivers
# sudo hg clone http://hg.alsa-project.org/alsa-driver alsa-driver
# sudo hg clone http://hg.alsa-project.org/alsa-kernel alsa-kernel
# sudo hg clone http://hg.alsa-project.org/alsa-lib alsa-lib
# sudo hg clone http://hg.alsa-project.org/alsa-utils alsa-utils

Install everything
# cd alsa-driver
# sudo ./cvscompile --with-cards=all --with-card-options=all (Nota Bene, this makes all the drivers. do more research if you just want the intel ones ;-D)
# sudo make install
# cd ../alsa-lib
# sudo ./cvscompile
# sudo make install
# cd ../alsa-utils
# sudo ./cvscompile
# sudo make install

Phew, that was tough. Its not over yet though, you've gotta edit some configuration files
sudo nano /etc/modprobe.d/alsa-base

and add this to the bottom,

options snd-hda-intel model=thinkpad

Save, exit and reboot.

THIS IS VERY IMPORTANT! IT TOOK ME 5+ HOURS TO FIGURE THIS OUT ON MY OWN!

YOU MUST HAVE BIOS SET TO FACTORY INSTALL (for the most part)

Certain BIOS options seem to break these drivers! I'm not sure which, but the factory settings work fine.

On next login, you should have sound. If you don't, make sure nothing is muted in alsaconf/alsamixer.
Also, make sure your login name is in the 'audio' or 'users' groups.

Alright, you have sound now! Yay!

Both headphones and speakers work, theres a switch on a tab in the gnome panel audio adjustment properties that turns either on/off

Note! It has been brought to my attention that an ubuntu developer has compiled packages for these drivers. I have not tested these yet and cannot ensure that they will work, although there are people on this site who have reported sucess using these packages
https://bugs.launchpad.net/ubuntu/+bug/122560

For what it's worth, I installed Ubuntu 7.10 on my new X61 tablet and sound worked (almost) out of the box. The bugs I see are that the built-in volume control buttons are mapped to the microphone channel instead of the speaker channel, and there's an issue with XMMS not being able to share the sound channel with Firefox (though maybe that's a wider issue than the X61tablet).

===Keyboard and Buttons===
You should have no trouble with getting the main 105 keys to work.

Some of the Fn buttons work, some don't. I'm still wading through ways to get these to work, but they're not super-high on my priority list. If you find ways, feel free to post :-)....

Screen Buttons.
The D-pad will work, but by default maps to weird values. Add
setkeycodes 6f 108
setkeycodes 71 103
setkeycodes 6e 105
setkeycodes 6d 106

to /etc/rc.local to make the D-pad work like your keyboard arrow keys. The middle button is 'Enter'

The other buttons also work. I have not mapped them to anything specific yet, but in a real terminal (no X environment), you can use the showkey command and setkeycodes to map the other 4 buttons to whatever you want. More instructions on this will follow once I decide what I want to use these 4 buttons for

===Suspend and Hibernate===
The default Ubuntu suspend and resume cycle causes a kernel panic. I got my computer to flawlessly suspend and resume by installing pm-utils
sudo apt-get install pm-utils

then you can suspend using the command
sudo pm-suspend --quirk-s3-bios --quirk-s3-mode

I'm content with suspend working, but if anyone figures out hibernate, let me know :-D

Works for Gutsy (please confirm for Feisty): In order to make the quirk settings the default for your machine, apply the following patch:
<pre>
--- /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi.orig 2007-10-08 13:35:45.000000000 +0200
+++ /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi 2008-01-20 11:16:58.000000000 +0100
@@ -2,6 +2,11 @@
<deviceinfo version="0.2">
<device>
<match key="system.hardware.vendor" string="LENOVO">
+ 
+ <match key="system.hardware.product" prefix="776796U">
+ <merge key="power_management.quirk.s3_bios" type="bool">true</merge>
+ <merge key="power_management.quirk.s3_mode" type="bool">true</merge>
+ </match>

<match key="system.hardware.product" prefix="1702">
<merge key="power_management.quirk.s3_bios" type="bool">true</merge>
</pre>
Make sure you adjust the prefix="776796U" to match your particular model, using the output from the following command:
<pre>
lshal |grep system.hardware.product
</pre>
You have to reboot your machine to make the changes permanent (restarting hal should actually be sufficient, but was not on my system). After that, gnome should be able to suspend/resume your system without crashing the machine or leaving the video backlight off. The only issue left on my system is that NetworkManager hangs after a resume, but that is easily solved with:
<pre>
sudo killall NetworkManager
sudo /etc/dbus-1/event.d/25NetworkManager start
</pre>

== Other x61 install guides on the web ==
* http://bayleshanks.com/tips-computer-lenovoX61t-gnuLinuxSetup (feel free to integrate the content on that page into this wiki -- Bayle)

[[Category:X61 Tablet]]