ThinkWiki - User contributions [en]

How to configure the TrackPoint

2008-12-08T17:56:16Z

Craftyguy: /* TrackPoint under Ubuntu 8.10 and Fedora 10 using HAL */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |The [[Patch to enable advanced trackpoint configuration|kernel trackpoint driver]] is controlled by echoing values to special files. Common configuration options are outlined below.
{{NOTE|
*With kernels 2.6.19 and above config files for this driver are located in <tt>/sys/devices/platform/i8042/serio1</tt>.
*With kernels 2.6.13 (inclusive) to 2.6.19 (exclusive) config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0/serio2</tt>.
*With kernels 2.6.11 (inclusive) to 2.6.13 (exclusive) config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0</tt>.
*With kernels 2.6.9 (inclusive) to 2.6.11 (exclusive) config files for this driver are located in <tt>/proc/trackpoint</tt>.
*Prior to kernel 2.6.9, configuration was not done through files but through command-line options to the psmouse module. (Note this means you must compile psmouse as a module!) See http://stephen.evanchik.com/node/16.
}}
|}

==General Configuration==
The configuration options are reflected by the files you can find in {{path|/sys/devices/platform/i8042/serio0/serio2}}. See the [[Patch to enable advanced trackpoint configuration|TrackPoint driver page]] for a complete list.
Configuration is done by echoing the appropriate values into these special files.

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.

==Most common Features==
The most common settings are '''Press to Select''', '''sensitivity''', '''speed''' and '''scrolling'''.

===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/serio0/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/serio0/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/serio0/serio2/press_to_select
exit 0
fi
if [ "$1" = "0" ]; then
echo "Turning off tap on TrackPoint"
echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/press_to_select
exit 0
fi
echo -n "Tap status: "
cat /sys/devices/platform/i8042/serio0/serio2/press_to_select

===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/serio0/serio2/speed}}
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio0/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.

===Scrolling===
====Using a kernel prior to 2.6.11====
The scrolling action is essentially the same as is used in the TrackPoint Windows drivers. To enable this feature, type the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /proc/trackpoint/scroll}}

Then press the middle button and push the stick up and down to scroll. Similarly, to disable scrolling:

:{{cmdroot|echo -n 0 > /proc/trackpoint/scroll}}

====Using the X server (kernel 2.6.11+)====
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!}}

===== EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper) =====

Unfortunately, there was a regression so that EmulateWheelTimeout was broken in X.org 6.9.0, and fixed
on March 20th, 2006.
You can see the [https://bugs.freedesktop.org/show_bug.cgi?id=5071 primary bug report] here, and also reports on the [http://qa.mandriva.com/show_bug.cgi?id=21196 Mandriva] and [http://lists.debian.org/debian-x/2006/01/msg00249.html Debian] ([http://bugs.debian.org/346098 #346098], [http://bugs.debian.org/320136 #320136]) packages.

Unfortunately, this bug is still present in Ubuntu Dapper Drake's xserver-xorg-input-mouse package (version 1.0.3.1+cvs.20060109-0ubuntu1)!

{{HINT|xserver-xorg-input-mouse (version 1.0.3.1+cvs.20060109-0ubuntu1.1) is in dapper-updates since July 3rd, 2006. You don't need to patch it anymore.}}

Use the following procedure to make it (middle button scrolling & middle button pasting) work:

:{{cmduser|cd /desired/path && mkdir tmp && cd tmp}} (create temporary directory somewhere)
:{{cmduser|sudo nano /etc/apt/sources.list}} (insert/uncomment the deb-src lines, save and exit)
:{{cmduser|sudo apt-get update}}
:{{cmduser|apt-get source xserver-xorg-input-mice}} (in order to get the source code)
:{{cmduser|sudo aptitude install xserver-xorg-dev}} (this package and the packages it depends on are needed in order to compile the source code, use aptitude for easy removal later on)
:{{cmduser|cd xserver-xorg-input-mouse-1.0.3.1+cvs.20060109/}}
:{{cmduser|wget http://librarian.launchpad.net/2639933/xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2.debdiff}} (downloads the patch that fixes the bug)
:{{cmduser|patch -p1 < xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2.debdiff}} (applies the bug fix)
:{{cmduser|fakeroot dpkg-buildpackage}} (rebuilds the package... watch out for errors and install other missing packages)
:{{cmduser|sudo dpkg -i ../xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2_i386.deb}} (installs the rebuilt built package)
:{{cmduser|sudo aptitude remove xserver-xorg-dev}} (removes the packages needed to rebuild the package)

Hope it works for you, it did work for me!
CrypTom

===== Older versions of X.org =====

For older versions of Xorg or for Xfree86 ({{path|/etc/X11/XF86Config}}) try this:

Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

Now restart X and hold down button two and move the mouse for scrolling. To get a middle click, press buttons 1 and 3 simultaneously.

==Soft Transparent Mode==
If you wish to connect a special device to the external PS/2 port, you should consider using "Soft Transparent Mode" so that the TrackPoint controller does not interpret any commands sent to the external PS/2 port. You can enable soft transparent mode by typing the following in to a terminal:

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

Disabling soft transparent mode is similar:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

==Modify trackpoint parameter permanently in trackpoint.h==
If you do not want to run a script to reconfigure the trackpoint
you can change the default settings in the trackpoint header file that is located in
/usr/src/<KERNEL_VERSION>/drivers/input/mouse/trackpoint.h.

First you must convert the values (decimal numbers) you normaly echo to /sys/[...] to hex:

'''echo -e 'obase=16;<DECIMAL_NUMBER>' | bc'''

Then simply replace the default hex values in trackpoint.h, run 'make && make modules_install' to recompile and install psmouse.ko (should be compiled as module)

Example patch (speed=100, sensitivity=190, press_to_select=1):
<pre>
--- trackpoint.h.orig 2006-01-17 16:18:30.000000000 +0100
+++ trackpoint.h 2006-01-17 16:25:47.000000000 +0100
@@ -108,9 +108,9 @@
/*
* Default power on values
*/
-#define TP_DEF_SENS 0x80
+#define TP_DEF_SENS 0xBE
#define TP_DEF_INERTIA 0x06
-#define TP_DEF_SPEED 0x61
+#define TP_DEF_SPEED 0x64
#define TP_DEF_REACH 0x0A

#define TP_DEF_DRAGHYS 0xFF
@@ -123,7 +123,7 @@

/* Toggles */
#define TP_DEF_MB 0x00
-#define TP_DEF_PTSON 0x00
+#define TP_DEF_PTSON 0x01
#define TP_DEF_SKIPBACK 0x00
#define TP_DEF_EXT_DEV 0x01
</pre>

==Configure firefox for using trackpoint horizontal scrolling==
Vertical Scrolling seems to work out of the box in firefox if you followed the steps above.
Anyway, there is a problem when you don't scroll exactly vertical, because horizontal scrolling turns into
browser BACK/FORWARD commands.
You can avoid this by typing about:config + ENTER in the address bar of firefox.
You have to adjust the following options:

<pre>
mousewheel.horizscroll.withcontrolkey.action = 3;
mousewheel.horizscroll.withcontrolkey.numlines = 1;
mousewheel.horizscroll.withcontrolkey.sysnumlines = true;

mousewheel.horizscroll.withnokey.action = 0;
mousewheel.horizscroll.withnokey.numlines = 1;
mousewheel.horizscroll.withnokey.sysnumlines = true;

mousewheel.horizscroll.withshiftkey.action = 1;
mousewheel.horizscroll.withshiftkey.numlines = 1;
mousewheel.horizscroll.withshiftkey.sysnumlines = true;
</pre>

FWIW, you can change only the following value to remove the browser BACK/FORWARD commands:

<pre>
mousewheel.horizscroll.withnokey.action = 0;
</pre>

With that, you can still go BACK/FORWARD by pressing together the shift or the alt key, while with the control key you increase or decrease the font size.

{{NOTE|This appears to be fixed by default in Firefox 3.}}

==Configure Opera for using trackpoint horizontal scrolling==
You'll experience the same annoying problem with the popular browser Opera. To fix this you need to edit the configfile <tt>standard_mouse.ini</tt> in e.g. /usr/share/opera/ini/ (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.

==Fixing trackpoint under Ubuntu 7.10 Gutsy Gibbon==
===Using trackpoint deamon===
My default Ubuntu Gutsy (running on an X61s) would give the following error messages when running the trackpoint daemon. Running
<pre>
/etc/init.d/trackpoint restart
</pre>
caused a bunch of error messages, as the wrong device was in
<pre>
/etc/trackpoint/trackpoint.conf
</pre>

I fixed this by changing:
<pre>
echo -n > /sys/devices/platform/i8042/serio0/serio2/sensitivity
</pre>
to
<pre>
echo -n > /sys/devices/platform/i8042/serio1/sensitivity
</pre>
in /etc/trackpoint/trackpoint.conf.

In addition, Ubuntu ran the appropriate /etc/init.d/trackpoint script on booting, but would give a bunch of errors (which, oddly, I could never find in any of the log files).

It seems that it was running the scripts too early in the boot sequence. The Gutsy package provided
<pre>
/etc/rc2.d/S20trackpoint
</pre>

so I renamed this to S99trackpoint (and in all the other rc.? directories) and it now works on boot.

===Editing the kernel config files===
Another way of configuring the trackpoint without using the trackpoint daemon is to edit the values of the trackpoint files which, BTW, are located in
/sys/devices/platform/i8042/serio1/serio2.

The script should be executed during boot. This can be done in an init script (e.g. /etc/bootmisc.sh in some distros)

Script:
<pre>
#! /bin/sh

#
# configuration du trackpoint
#

# vitesse
echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed

# sensibilité
echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity

# press to select
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select
</pre>
===An Ubuntu/Fedora example===
Another script that I've created seems to work with all versions of Ubuntu/Fedora that I've been able to try (comment out and uncomment the appropriate lines for fedora/ubuntu as necessary)
Place in /etc/rc.local or equivalent for your distro:

Script:
<pre>
#*************************
## START TRACKPOINT CONFIG
#*************************

# For fedora (the slash after "speed" is returned)
# TRACKPATH=$(find /sys -print0 | grep -FzZ "/serio2/speed" | sed s^speed/^^)

# For ubuntu (the slash after "speed" is not returned)
TRACKPATH=$(find /sys -print0 | grep -FzZ "/serio2/speed" | sed s/speed//)

## Select "press_to_select" on the trackpoint input device
## We need to specify the TRACKPATH above because the device under "serio#"
## changes between system boots. (We first test to see if the file we want
## to modify exists, if it does, we make the change
#[ -f $TRACKPATH/press_to_select ] && echo -n 1 > $TRACKPATH/press_to_select

## Adjust the speed setting of the trackpoint input device
[ -f $TRACKPATH/speed ] && echo -n 120 > $TRACKPATH/speed
## Adjust the sensitivity setting of the trackpoint input device
[ -f $TRACKPATH/sensitivity ] && echo -n 200 > $TRACKPATH/sensitivity

#***********************
## END TRACKPOINT CONFIG
#***********************
</pre>

==TrackPoint under Xorg-7.4+ using HAL==

Because Xorg 7.4 uses HAL FDI policy files instead of xorg.conf for device configuration, you must do the following to get the scrolling working:
(see: http://forum.ubuntuusers.de/topic/mouse-wheel-emulation-in-xorg.conf/?highlight=hal+trackpoint#post-1558282 )

Create the file '''/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.XAxisMapping" type="string">6 7</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge>
</match>
</pre>

In Fedora 10, this fix also works, and with '''lshal''' you can see that the changes do indeed take effect. However, you will need to update the evdev drivers ('''yum --enablerepo=rawhide update xorg-x11-drv-evdev''') before X will use these settings correctly. I'm still not sure what the problem is with the drivers in vanilla Fedora 10, but with version 2.1.0 of these drivers, I have full functionality.

Note: You must restart both hal and X to see these changes, so it's probably easiest to just reboot.

Confirmed to work in Gentoo as well. You MUST upgrade to x11-drivers/xf86-input-evdev-2.1.0. As of today (12/8/08), this package is only found in the x11 overlay.

https://wiki.ubuntu.com/X/Config

Note: After setting this up, scrolling seems to fail once in a while after resuming from suspend. Re-suspending and then re-resuming causes it to work again. I don't know why this might be.

How to configure the TrackPoint

2008-12-08T17:54:05Z

Craftyguy:

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |The [[Patch to enable advanced trackpoint configuration|kernel trackpoint driver]] is controlled by echoing values to special files. Common configuration options are outlined below.
{{NOTE|
*With kernels 2.6.19 and above config files for this driver are located in <tt>/sys/devices/platform/i8042/serio1</tt>.
*With kernels 2.6.13 (inclusive) to 2.6.19 (exclusive) config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0/serio2</tt>.
*With kernels 2.6.11 (inclusive) to 2.6.13 (exclusive) config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0</tt>.
*With kernels 2.6.9 (inclusive) to 2.6.11 (exclusive) config files for this driver are located in <tt>/proc/trackpoint</tt>.
*Prior to kernel 2.6.9, configuration was not done through files but through command-line options to the psmouse module. (Note this means you must compile psmouse as a module!) See http://stephen.evanchik.com/node/16.
}}
|}

==General Configuration==
The configuration options are reflected by the files you can find in {{path|/sys/devices/platform/i8042/serio0/serio2}}. See the [[Patch to enable advanced trackpoint configuration|TrackPoint driver page]] for a complete list.
Configuration is done by echoing the appropriate values into these special files.

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.

==Most common Features==
The most common settings are '''Press to Select''', '''sensitivity''', '''speed''' and '''scrolling'''.

===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/serio0/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/serio0/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/serio0/serio2/press_to_select
exit 0
fi
if [ "$1" = "0" ]; then
echo "Turning off tap on TrackPoint"
echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/press_to_select
exit 0
fi
echo -n "Tap status: "
cat /sys/devices/platform/i8042/serio0/serio2/press_to_select

===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/serio0/serio2/speed}}
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio0/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.

===Scrolling===
====Using a kernel prior to 2.6.11====
The scrolling action is essentially the same as is used in the TrackPoint Windows drivers. To enable this feature, type the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /proc/trackpoint/scroll}}

Then press the middle button and push the stick up and down to scroll. Similarly, to disable scrolling:

:{{cmdroot|echo -n 0 > /proc/trackpoint/scroll}}

====Using the X server (kernel 2.6.11+)====
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!}}

===== EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper) =====

Unfortunately, there was a regression so that EmulateWheelTimeout was broken in X.org 6.9.0, and fixed
on March 20th, 2006.
You can see the [https://bugs.freedesktop.org/show_bug.cgi?id=5071 primary bug report] here, and also reports on the [http://qa.mandriva.com/show_bug.cgi?id=21196 Mandriva] and [http://lists.debian.org/debian-x/2006/01/msg00249.html Debian] ([http://bugs.debian.org/346098 #346098], [http://bugs.debian.org/320136 #320136]) packages.

Unfortunately, this bug is still present in Ubuntu Dapper Drake's xserver-xorg-input-mouse package (version 1.0.3.1+cvs.20060109-0ubuntu1)!

{{HINT|xserver-xorg-input-mouse (version 1.0.3.1+cvs.20060109-0ubuntu1.1) is in dapper-updates since July 3rd, 2006. You don't need to patch it anymore.}}

Use the following procedure to make it (middle button scrolling & middle button pasting) work:

:{{cmduser|cd /desired/path && mkdir tmp && cd tmp}} (create temporary directory somewhere)
:{{cmduser|sudo nano /etc/apt/sources.list}} (insert/uncomment the deb-src lines, save and exit)
:{{cmduser|sudo apt-get update}}
:{{cmduser|apt-get source xserver-xorg-input-mice}} (in order to get the source code)
:{{cmduser|sudo aptitude install xserver-xorg-dev}} (this package and the packages it depends on are needed in order to compile the source code, use aptitude for easy removal later on)
:{{cmduser|cd xserver-xorg-input-mouse-1.0.3.1+cvs.20060109/}}
:{{cmduser|wget http://librarian.launchpad.net/2639933/xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2.debdiff}} (downloads the patch that fixes the bug)
:{{cmduser|patch -p1 < xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2.debdiff}} (applies the bug fix)
:{{cmduser|fakeroot dpkg-buildpackage}} (rebuilds the package... watch out for errors and install other missing packages)
:{{cmduser|sudo dpkg -i ../xserver-xorg-input-mouse_1.0.3.1+cvs.20060109-0ubuntu2_i386.deb}} (installs the rebuilt built package)
:{{cmduser|sudo aptitude remove xserver-xorg-dev}} (removes the packages needed to rebuild the package)

Hope it works for you, it did work for me!
CrypTom

===== Older versions of X.org =====

For older versions of Xorg or for Xfree86 ({{path|/etc/X11/XF86Config}}) try this:

Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

Now restart X and hold down button two and move the mouse for scrolling. To get a middle click, press buttons 1 and 3 simultaneously.

==Soft Transparent Mode==
If you wish to connect a special device to the external PS/2 port, you should consider using "Soft Transparent Mode" so that the TrackPoint controller does not interpret any commands sent to the external PS/2 port. You can enable soft transparent mode by typing the following in to a terminal:

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

Disabling soft transparent mode is similar:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

==Modify trackpoint parameter permanently in trackpoint.h==
If you do not want to run a script to reconfigure the trackpoint
you can change the default settings in the trackpoint header file that is located in
/usr/src/<KERNEL_VERSION>/drivers/input/mouse/trackpoint.h.

First you must convert the values (decimal numbers) you normaly echo to /sys/[...] to hex:

'''echo -e 'obase=16;<DECIMAL_NUMBER>' | bc'''

Then simply replace the default hex values in trackpoint.h, run 'make && make modules_install' to recompile and install psmouse.ko (should be compiled as module)

Example patch (speed=100, sensitivity=190, press_to_select=1):
<pre>
--- trackpoint.h.orig 2006-01-17 16:18:30.000000000 +0100
+++ trackpoint.h 2006-01-17 16:25:47.000000000 +0100
@@ -108,9 +108,9 @@
/*
* Default power on values
*/
-#define TP_DEF_SENS 0x80
+#define TP_DEF_SENS 0xBE
#define TP_DEF_INERTIA 0x06
-#define TP_DEF_SPEED 0x61
+#define TP_DEF_SPEED 0x64
#define TP_DEF_REACH 0x0A

#define TP_DEF_DRAGHYS 0xFF
@@ -123,7 +123,7 @@

/* Toggles */
#define TP_DEF_MB 0x00
-#define TP_DEF_PTSON 0x00
+#define TP_DEF_PTSON 0x01
#define TP_DEF_SKIPBACK 0x00
#define TP_DEF_EXT_DEV 0x01
</pre>

==Configure firefox for using trackpoint horizontal scrolling==
Vertical Scrolling seems to work out of the box in firefox if you followed the steps above.
Anyway, there is a problem when you don't scroll exactly vertical, because horizontal scrolling turns into
browser BACK/FORWARD commands.
You can avoid this by typing about:config + ENTER in the address bar of firefox.
You have to adjust the following options:

<pre>
mousewheel.horizscroll.withcontrolkey.action = 3;
mousewheel.horizscroll.withcontrolkey.numlines = 1;
mousewheel.horizscroll.withcontrolkey.sysnumlines = true;

mousewheel.horizscroll.withnokey.action = 0;
mousewheel.horizscroll.withnokey.numlines = 1;
mousewheel.horizscroll.withnokey.sysnumlines = true;

mousewheel.horizscroll.withshiftkey.action = 1;
mousewheel.horizscroll.withshiftkey.numlines = 1;
mousewheel.horizscroll.withshiftkey.sysnumlines = true;
</pre>

FWIW, you can change only the following value to remove the browser BACK/FORWARD commands:

<pre>
mousewheel.horizscroll.withnokey.action = 0;
</pre>

With that, you can still go BACK/FORWARD by pressing together the shift or the alt key, while with the control key you increase or decrease the font size.

{{NOTE|This appears to be fixed by default in Firefox 3.}}

==Configure Opera for using trackpoint horizontal scrolling==
You'll experience the same annoying problem with the popular browser Opera. To fix this you need to edit the configfile <tt>standard_mouse.ini</tt> in e.g. /usr/share/opera/ini/ (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.

==Fixing trackpoint under Ubuntu 7.10 Gutsy Gibbon==
===Using trackpoint deamon===
My default Ubuntu Gutsy (running on an X61s) would give the following error messages when running the trackpoint daemon. Running
<pre>
/etc/init.d/trackpoint restart
</pre>
caused a bunch of error messages, as the wrong device was in
<pre>
/etc/trackpoint/trackpoint.conf
</pre>

I fixed this by changing:
<pre>
echo -n > /sys/devices/platform/i8042/serio0/serio2/sensitivity
</pre>
to
<pre>
echo -n > /sys/devices/platform/i8042/serio1/sensitivity
</pre>
in /etc/trackpoint/trackpoint.conf.

In addition, Ubuntu ran the appropriate /etc/init.d/trackpoint script on booting, but would give a bunch of errors (which, oddly, I could never find in any of the log files).

It seems that it was running the scripts too early in the boot sequence. The Gutsy package provided
<pre>
/etc/rc2.d/S20trackpoint
</pre>

so I renamed this to S99trackpoint (and in all the other rc.? directories) and it now works on boot.

===Editing the kernel config files===
Another way of configuring the trackpoint without using the trackpoint daemon is to edit the values of the trackpoint files which, BTW, are located in
/sys/devices/platform/i8042/serio1/serio2.

The script should be executed during boot. This can be done in an init script (e.g. /etc/bootmisc.sh in some distros)

Script:
<pre>
#! /bin/sh

#
# configuration du trackpoint
#

# vitesse
echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed

# sensibilité
echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity

# press to select
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select
</pre>
===An Ubuntu/Fedora example===
Another script that I've created seems to work with all versions of Ubuntu/Fedora that I've been able to try (comment out and uncomment the appropriate lines for fedora/ubuntu as necessary)
Place in /etc/rc.local or equivalent for your distro:

Script:
<pre>
#*************************
## START TRACKPOINT CONFIG
#*************************

# For fedora (the slash after "speed" is returned)
# TRACKPATH=$(find /sys -print0 | grep -FzZ "/serio2/speed" | sed s^speed/^^)

# For ubuntu (the slash after "speed" is not returned)
TRACKPATH=$(find /sys -print0 | grep -FzZ "/serio2/speed" | sed s/speed//)

## Select "press_to_select" on the trackpoint input device
## We need to specify the TRACKPATH above because the device under "serio#"
## changes between system boots. (We first test to see if the file we want
## to modify exists, if it does, we make the change
#[ -f $TRACKPATH/press_to_select ] && echo -n 1 > $TRACKPATH/press_to_select

## Adjust the speed setting of the trackpoint input device
[ -f $TRACKPATH/speed ] && echo -n 120 > $TRACKPATH/speed
## Adjust the sensitivity setting of the trackpoint input device
[ -f $TRACKPATH/sensitivity ] && echo -n 200 > $TRACKPATH/sensitivity

#***********************
## END TRACKPOINT CONFIG
#***********************
</pre>

==TrackPoint under Ubuntu 8.10 and Fedora 10 using HAL==

Because Ubuntu 8.10 uses HAL you must do the following to get the scrolling working:
(see: http://forum.ubuntuusers.de/topic/mouse-wheel-emulation-in-xorg.conf/?highlight=hal+trackpoint#post-1558282 )

Create the file '''/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.XAxisMapping" type="string">6 7</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge>
</match>
</pre>

In Fedora 10, this fix also works, and with '''lshal''' you can see that the changes do indeed take effect. However, you will need to update the evdev drivers ('''yum --enablerepo=rawhide update xorg-x11-drv-evdev''') before X will use these settings correctly. I'm still not sure what the problem is with the drivers in vanilla Fedora 10, but with version 2.1.0 of these drivers, I have full functionality.

Note: You must restart both hal and X to see these changes, so it's probably easiest to just reboot.

Confirmed to work in Gentoo as well. You MUST upgrade to x11-drivers/xf86-input-evdev-2.1.0. As of today (12/8/08), this package is only found in the x11 overlay.

https://wiki.ubuntu.com/X/Config

Note: After setting this up, scrolling seems to fail once in a while after resuming from suspend. Re-suspending and then re-resuming causes it to work again. I don't know why this might be.

Problems with ACPI suspend-to-ram

2008-10-15T05:25:21Z

Craftyguy: /* Troubles on suspend */

The following glitches may or may not occur in relation to suspending to RAM:

==Troubles on suspend==
;Permissions:If your suspend is failing, and a {{cmdroot|tail /var/log/acpid}} shows "Permission denied" errors, be sure that your new ACPI event and action scripts have the appropriate permissions.

;Write error:If {{cmdroot|echo mem > /sys/power/state}} shows "write error: Operation not permitted", verify that CONFIG_HOTPLUG_CPU option is enabled in the kernel. [[Software_Suspend_2|Suspend2]] automatically selects this option.

;Broken sysfs interface:You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} or {{cmdroot|echo mem > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running or if the usb hcd modules are still loaded.

;Immediate Resume after Suspend:If a resume starts a few seconds after suspend a reason might be the USB modules. Unload the modules uhci_hcd and ehci_hcd before you suspend. Users of hibernate-scripts add "UnloadModules uhci_hcd ehci_hcd" to {{path|/etc/hibernate/common.conf}}.

;Hangs on "switching to UP code":You may be using a [[How to make use of Dynamic Frequency Scaling|frequency scaling governor]] such as "conservative" or "ondemand", which sometimes have problems with suspending. Switching to a governor such as "powersave" or "performance" before suspending may solve this problem.

;MySQL daemon running:If you're running MySQL, sleep may also not work, so stop MySQL first, then sleep. Remember to restart MySQL when you wakeup.

;LCD backlight remains on during sleep:When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.

;High power drain during sleep:Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

;Built-in MMC reader:If you have an MMC reader, and the computer hangs when attempting suspend then remove sdhci, mmc_block, and mmc_core modules before suspending.

;Could not power down device <NULL>: error -22:If you have the acpi_cpufreq kernel module loaded, this prevents suspension.

;Immediate Resume, but Suspend "moon" light continues to flash:???

;Hard system lock up:If you are using savagefb, make sure to [[Problem_with_unusable_console|disable the "Console Acceleration" option]] (CONFIG_FB_SAVAGE_ACCEL) in the kernel config. Otherwise, susped-to-RAM may lock up your system such that you must remove the AC adapter and battery to get it to boot again.

;Hard system lock up 2: If you are using a Thinkpad G40 and Ubuntu (this problem experienced on 8.04), you may experience problems with ACPI when opening your laptop lid that freezes the system. You can disable ACPI in your kernel parameters, or modify {{path|/etc/acpi/lid.sh}} to switch to a plain text console on close and back to Gnome/KDE on open (use {{path|/usr/bin/chvt 1}} and {{path|/usr/bin/chvt 7}}, respectively)

;Solid 'moon' but fans still spinning: On a T61p with an nvidia quadro 570M, you might experience a near-complete suspend, with the backlight turned off, unresponsive usb, and a solid 'moon' lit, however system fans are still going. The proprietary nvidia module is to blame. On gentoo, appending "NVreg_Mobile=3" to the 'option' line in /etc/modules.d/nvidia fixed the issue for me. On other distros, look in your module autoloading conf file

==Troubles on resume==
;Blank display on resume:
:When resuming from a suspend-to-ram the display might remain black (on {{X60}}) or might only show the pre-suspend output (the system is still rebootable via {{key|ctrl}}{{key|alt}}{{key|del}}). See [[Problem with display remaining black after resume]] for solutions. See also '''System hang on resume''' on this page - which may be potentially mismatched with this one.

;No mouse cursor on resume:
:When resuming from a suspend-to-ram your X cursor might be invisible(on {{X40}}) when using {{path|/sys/power/state}} directly to suspend, they way to fix this is to rerun the post bios code after returning for suspending.
:{{cmdroot|FGCONSOLE<nowiki>=</nowiki>`fgconsole\`}}
:{{cmdroot|chvt 1 && echo -n mem >/sys/power/state}}
:{{cmdroot|vbetool post && chvt 7 && chvt $FGCONSOLE}}

;Garbage on text consoles on resume:When resuming from suspend-to-ram the text console displays may show garbage instead of actual text. The machine is otherwise still responsive and X displays fine. If all of this is true, then adding the kernel option {{bootparm|acpi_sleep|s3_bios,s3_mode}} in your menu.lst or lilo.conf may solve the problem.

;Broken hardware support after resume:
:*The '''serial port''' of the port replicator might not work after resume.
:*The '''parallel port''' might not work after resume. A possible fix is to unload and reload the parallel port drivers: {{cmdroot|rmmod lp parport_pc parport; modprobe lp}}.
:*Problems with the '''CD-RW/DVD drive''' after wake up from ram have been experienced.
:*There is a known Problem regarding '''battery info''' after suspend to RAM. A [http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/2429.html small patch] exists for kernels 2.6.14/2.6.15.
:*On {{X20}} and {{X21}} (and possibly other) models, the '''sleep LED''' is not reset properly on resume and will keep blinking. If you have the [[ibm-acpi]] kernel module loaded with the {{bootparm|ibm-acpi.experimental|1}} option, you can switch it off on resume by appending the following line to your suspend script: {{cmdroot|echo 7 off > /proc/acpi/ibm/led}}

;Crash on resume:
:*When using '''older ATI proprietary drivers''' a crash on resume can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool]. See the example suspend script [[Problem with display remaining black after resume#Solution for ThinkPads with Intel I830 Chipset]]. This is no longer necessary with recent revisions of the ATI proprietary driver.
:*A crash could also be caused by having '''apic support''' enabled in the kernel config. Try disabling it (in the "Processor type and features" section).
:*On machines with Savage chipsets, the '''savagefb framebuffer driver''' might crash the machine on resume. Make sure it is disabled in your kernel config and use the standard vesafb driver instead.
:*SATA-based laptops utilize the '''libata layer for disk access''' which does not have fully-working power-management support before Linux kernel 2.6.16 (ata_piix) and 2.6.19 (ahci). Suspend to RAM crashes these machines on resume. See the [[Problems with SATA and Linux#Hang on resume from suspend to RAM|relevant section]] on the [[Problems with SATA and Linux]] page.
:*Using [[HDAPS]] as a module causes a crash on resume with the Linux kernel 2.6.19 (possibly even earlier versions). This was observed on a {{X41}}. Try unloading the module before suspending.
:*Gnome-power-manager might be using the wrong backend. If you are able to suspend from the commandline with a certain method, make sure the others are not available so that g-p-m doesn't choose the wrong one. For example, if you suspend with {{cmdroot|echo mem > /sys/power/state}}, make sure '''uswsusp''' and '''hibernate''' are uninstalled.

;System hang on resume:
:System hangs immediately upon attempted resume if suspended with USB devices attached to dock. Try using the laptop's own USB ports instead. That fixed the problem for me. Details: https://bugs.launchpad.net/ubuntu/+bug/218760 --[[User:Dave abrahams|Dave abrahams]] 17:45, 28 April 2008 (CEST)
:When system resumes it hangs right after restarting tasks. Strange thing is, that you may be even able to restart your ThinkPad using {{key|ctrl}}{{key|alt}}{{key|del}}, but if you try to blindly exec a command, it will not work, (eg. touch FILE) so it's not only the problem of videocard. This may be fixed by passing {{bootparm|ec_intr|0}} on kernel cmdline. Affected models: {{T20}}, {{T21}} (at least [[2648-46U]] (T20),[[2647-8AG]] (T21)).
:'''Note:''' ''this is resolved in kernel 2.6.20, there is no need to pass the {{bootparm|ec_intr|0}} bootparam anymore (moreover, you are discouraged to use it) See [http://bugzilla.kernel.org/show_bug.cgi?id=6749 revelant kernel bug report]''
:See also [https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/73546 this bug report], I can confirm some strange problems on resume with Bluetooth enabled - my T61 may freeze in a couple of minutes after resuming. This problem is gone as soon as I disable Bluetooth (stop all bluetooth related services and `echo "disable" > /proc/acpi/ibm/bluetooth`).

;Shutdown on resume:
:If your system immediately begins to shut down right after resume, make sure you don't have acpid running with the power button tied to shutdown. The system is simply sensing the power button event and shutting down. This issue has been reported as a bug against the kernel ACPI subsystem, refer to [http://bugzilla.kernel.org/show_bug.cgi?id=6612 kernel.org bugzilla bug #6612].

;Immediate suspend on resume:
:When running GNOME, sometimes gnome-power-manager will put the system back into suspend immediately after resuming. This is caused by a known bug in HAL that causes some ACPI events to be reported incorrectly after a suspend-to-ram. A simple workaround can be found [http://live.gnome.org/GnomePowerManager/Faq?action=recall&rev=28#head-b8b1280115b0a51c2cc27b13a57121130ebf36cb here].
:Note that suspend being triggered by unrelated ACPI events such as disconnecting the AC adapter may also be fixed by the above method.

;Power Off when suspended laptop is docked
:When T60p is suspended, docking laptop into Advanced Dock immediately turns off laptop and crescent moon sleep indicator LED. Pressing power button initiates cold boot. Also reported by multiple people on thinkpads.com.

;SectorIdNotFound disk errors when laptop is resumed
:The errors look like this:
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 14 17:35:02 cacharro kernel: hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=115896900, sector=115896900
Oct 14 17:35:02 cacharro kernel: ide: failed opcode was: unknown

:This happens when you have [[Hidden Protected Area]] (HPA) enabled on the hard drive. There is a [http://bugzilla.kernel.org/show_bug.cgi?id=6840 kernel bug report with an unfinished patch] to fix this. This is not fixed as of kernel 2.16.18. Adding {{bootparm|libata.ignore_hpa|1}} to the kernel command line might help.