https://www.thinkwiki.org/w/api.php?action=feedcontributions&feedformat=atom&user=MahtoThinkWiki - User contributions [en]2026-05-01T05:42:04ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=How_to_configure_the_TrackPoint&diff=54518How to configure the TrackPoint2013-04-12T02:59:31Z<p>Mahto: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |Below are several ways of configuring the kernel psmouse driver for controlling extended TrackPoint features.<br />
|}<br />
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.<br />
<br />
=Configuration using xinput=<br />
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).<br />
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.<br />
<br />
To query the available options<br />
xinput list-props "TPPS/2 IBM TrackPoint"<br />
<br />
More information can be found in the man-pages for evdev<br />
man evdev<br />
<br />
To enable vertical scrolling<br />
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 1<br />
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 2<br />
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 200<br />
<br />
To enable horizontal scrolling in addition to vertical scrolling<br />
<br />
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 6 7 4 5<br />
<br />
To enable middle button emulation (using left- and right-click simultaneously)<br />
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Emulation" 1<br />
xinput set-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Timeout" 50<br />
<br />
== old method using xinput set-int-prop ==<br />
<br />
Note: xinput set-int-prop is deprecated according to the xinput manpage.<br />
<br />
To enable vertical scrolling<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
To enable horizontal scrolling in addition to vertical scrolling<br />
<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To enable middle button emulation (using left- and right-click simultaneously)<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Timeout" 8 50<br />
<br />
==Example: openSUSE 11.2 and ThinkPad USB Keyboard with TrackPoint ==<br />
<br />
xinput list<br />
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.<br />
<br />
Suppose the id was 12. The following will enable the trackpoint scrolling:<br />
<br />
xinput set-int-prop 12 "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
The following will enable the horizontal scrolling<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To disable middle button click paste functionality, remap the middle button to something else:<br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
To do these automatically without worrying about id number, generate a bash script file:<br />
#!/bin/sh<br />
xinput list | sed -ne 's/^[^ ][^V].*id=\([0-9]*\).*/\1/p' | while read id<br />
do<br />
case `xinput list-props $id` in<br />
*"Middle Button Emulation"*)<br />
xinput set-int-prop $id "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop $id "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop $id "Evdev Wheel Emulation Timeout" 8 200<br />
xinput set-int-prop $id "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
xinput set-int-prop $id "Evdev Middle Button Emulation" 8 0<br />
;;<br />
esac<br />
done<br />
<br />
# disable middle button<br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
and save it with any name such as trackPointScrolling.sh, and make it executable:<br />
chmod +x trackPointScrolling.sh<br />
<br />
Next time you run it with $ ./trackPointScrolling.sh, it will enable the trackpoint scrolling and disable middle button paste.<br />
{{Todo|some other examples}}<br />
<br />
= Graphical Frontends =<br />
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.<br />
=== GPointing Device Settings ===<br />
It is available for Fedora 12, Ubuntu 9.10 and Debian Squeeze in the standard package repositories<br />
{{NOTE|Unfortunately it seems no longer maintained, and does not work properly with GNOME3 [[https://bugzilla.redhat.com/show_bug.cgi?id=710053 bug]]}}<br />
<br />
[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]<br />
<br />
=== configure-trackpoint ===<br />
To install it in Ubuntu run ...<br />
sudo apt-get install sysfsutils<br />
...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.<br />
<br />
= Configuration using DevKit =<br />
Most recent distributions like Ubuntu 9.10 switch from HAL (being deprecated) to DevKit. Hence, the HAL configurations explained underneath, fail to work.<br />
<br />
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}}<br />
<br />
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.<br />
<br />
= Configuration using udev and HAL =<br />
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.<br />
<br />
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.<br />
<br />
=== Scrolling ===<br />
<br />
By default the middle mouse button is just that, a middle mouse button, which in Linux is used for the Paste operation.<br />
<br />
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".)<br />
<br />
'''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>.<br />
<br />
==== xorg.conf.d ====<br />
<br />
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.<br />
<br />
Create the file {{path|/usr/lib/X11/xorg.conf.d/20-thinkpad.conf}} as root with the following content:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "Trackpoint Wheel Emulation"<br />
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint|ThinkPad USB Keyboard with TrackPoint|USB Trackpoint pointing device|Composite TouchPad / TrackPoint"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "2"<br />
Option "Emulate3Buttons" "false"<br />
Option "XAxisMapping" "6 7"<br />
Option "YAxisMapping" "4 5"<br />
EndSection<br />
</pre><br />
<br />
Save and restart Xorg (or it'll be enabled at next reboot).<br />
<br />
{{NOTE|For Ubuntu 10.10 Maverick Meerkat, the correct path is {{path|/usr/share/X11/xorg.conf.d}}}}<br />
{{NOTE|For Arch Linux or Fedora or PCLinuxOS, the correct path is {{path|/etc/X11/xorg.conf.d}}}}<br />
<br />
{{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.}}<br />
<br />
{{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.}}<br />
<br />
==== udev ====<br />
<br />
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.<br />
<br />
Create the file {{path|/etc/udev/rules.d/99_trackpoint.rules}} as root with the following content:<br />
<br />
<pre><br />
ACTION!="add|change", GOTO="xorg_trackpoint_end"<br />
KERNEL!="event*", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{x11_options.EmulateWheel}="1"<br />
ENV{x11_options.EmulateWheelButton}="2"<br />
ENV{x11_options.XAxisMapping}="6 7"<br />
ENV{x11_options.Emulate3Buttons}="0"<br />
<br />
LABEL="xorg_trackpoint_end"<br />
</pre><br />
<br />
Save and restart udev then Xorg (or it'll be enabled at next reboot).<br />
<br />
{{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]]}}<br />
<br />
==== Hal (soon to be deprecated) ====<br />
<br />
To accomplish this create the file {{path|/etc/hal/fdi/policy/mouse-wheel.fdi}} as root with the following content:<br />
<br />
<pre><br />
<match key="info.product" string="TPPS/2 IBM TrackPoint"><br />
<merge key="input.x11_options.EmulateWheel" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge><br />
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge><br />
</match><br />
</pre><br />
<br />
If you also want to have horizontal scrolling, simply add the following XAxisMapping option to the above<br />
<pre><br />
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge><br />
</pre><br />
After this reboot, or restart the hal service and Xorg. You can validate the settings with {{cmd|lshal|}}.<br />
<br />
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>.<br />
<br />
Alternatively it is also possible to use the "old" Xorg configuration by adding the following lines to the {{path|/etc/X11/xorg.conf}}:<br />
<br />
<pre><br />
Section "ServerFlags"<br />
Option "AutoAddDevices" "false"<br />
EndSection<br />
</pre><br />
<br />
Using this entry HAL will not be used for the input devices.<br />
<br />
====Reactivate Scrolling after suspend/resume====<br />
Scrolling may be disabled after a resume from suspend.<br />
<br />
You can manually reactivate the trackpoint by reloading the {{path|psmouse}} module as root:<br />
:{{cmdroot|rmmod psmouse && modprobe psmouse}}<br />
<br />
You can automatically force the pm-utils to reload this module.<br />
Create a file {{path|/etc/pm/config.d/01reload_mouse}} as root with the following content:<br />
<pre><br />
# reload psmouse to reactivate trackpoint scrolling<br />
SUSPEND_MODULES="${SUSPEND_MODULES:+$SUSPEND_MODULES }psmouse"<br />
</pre><br />
<br />
===Configuring other options (e.g. Press to select, Sensitivity and Speed)===<br />
<!--HAL wasn't made to configure sysfs settings, so we'll use udev instead --><br />
Create a file {{path|/etc/udev/rules.d/10-trackpoint.rules}} and add a line to suit your needs<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", ATTRS{press_to_select}="1", ATTRS{sensitivity}="122"<br />
</pre><br />
<br />
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.<br />
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<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTRS{sensitivity}="122"<br />
</pre><br />
<br />
On my system (Lucid Lynx), the above line did not work. I changed it to:<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="255"<br />
</pre><br />
and tested with {{cmdroot|udevadm test /sys/devices/platform/i8042/serio1/serio2}}.<br />
<br />
To avoid the wait you can also listen for the Trackpoint input device to appear and then run a script to set the parameters<br />
<br />
<pre><br />
SUBSYSTEM=="input", ATTR{name}=="*TrackPoint*", RUN+="/etc/conf.d/trackpoint"<br />
</pre><br />
<br />
An example {{path|/etc/conf.d/trackpoint}} would be<br />
<br />
<pre>#! /bin/bash<br />
<br />
## Trackpoint settings<br />
<br />
# When run from a udev rule, DEVPATH should be set<br />
if [ ! -z $DEVPATH ] ; then<br />
TPDEV=/sys/$( echo "$DEVPATH" | sed 's/\/input\/input[0-9]*//' )<br />
else<br />
# Otherwise just look in /sys/<br />
TPDEV=$(find /sys/devices/platform/i8042 -name name | xargs grep -Fl TrackPoint | sed 's/\/input\/input[0-9]*\/name$//')<br />
fi<br />
<br />
# http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint<br />
# http://wwwcssrv.almaden.ibm.com/trackpoint/files/ykt3eext.pdf<br />
#------------------------------------------------------------<br />
if [ -d "$TPDEV" ]; then<br />
echo "Configuring Trackpoint"<br />
echo -n 255 > $TPDEV/sensitivity # Integer 128 Sensitivity<br />
echo -n 110 > $TPDEV/speed # Integer 97 Cursor speed<br />
echo -n 4 > $TPDEV/inertia # Integer 6 Negative intertia<br />
else<br />
echo "Couldn't find trackpoint device $TPDEV"<br />
fi<br />
</pre><br />
<br />
=Configuration using sysfs=<br />
Another way to modify changes on the fly, is echoing values directly into special files in sysfs.<br />
<br />
{{NOTE|<br />
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}}.<br />
<br />
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).}}<br />
<br />
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.<br />
<br />
===Press to Select===<br />
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):<br />
<br />
:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
Press to Select should now be enabled. You can disable it in a similar manner:<br />
<br />
:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
You can use this script to automate the operation<br />
<br />
#!/bin/bash<br />
if [ "$1" = "1" ]; then<br />
echo "Turning on tap on TrackPoint"<br />
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
if [ "$1" = "0" ]; then<br />
echo "Turning off tap on TrackPoint"<br />
echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
echo -n "Tap status: "<br />
cat /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
In Ubuntu 8.10 to make Press to Select a permanent change:<br />
<br />
echo -n 1 | tee /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
As root, append the above command above "exit 0" in /etc/gdm/Init/Default<br />
<br />
===Sensitivity & Speed===<br />
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:<br />
<br />
:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed}}<br />
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity}}<br />
<br />
Feel free to experiment with your settings until you find a combination that is comfortable.<br />
<br />
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.<br />
<br />
===Vertical Scrolling===<br />
No sysfs entry exists for vertical scrolling in kernels after 2.6.11.<br />
<br />
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.<br />
Instead the scroll feature of the Xserver should be used, which can be activated with HAL or xinput as described above.<br />
<br />
=Configuration using the X server (xorg.conf)=<br />
==Using the "evdev" driver (preferred, especially for recent Xorg versions)==<br />
Extract from /etc/X11/xorg.conf on an X31:<br />
<br />
Section "InputDevice"<br />
Identifier "TPPS/2 IBM TrackPoint"<br />
Driver "evdev"<br />
Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"<br />
Option "GrabDevice" "False"<br />
Option "EmulateWheel" "true" #Enable wheel emulation for the Trackpoint<br />
Option "EmulateWheelButton" "2" #Use the middle button for the emulation<br />
Option "XAxisMapping" "6 7" #Map trackpoint X axis to X axis of emulated wheel<br />
Option "YAxisMapping" "4 5" #Map trackpoint Y axis to Y axis of emulated wheel<br />
EndSection<br />
<br />
{{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]]}}<br />
<br />
==Using the "mouse" driver (deprecated, only for old Xorg versions)==<br />
{{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}}<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Once this functionality is in the X.org, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:<br />
<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelButton" "2"<br />
<br />
It may also be necessary to add these lines:<br />
<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
<br />
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).<br />
<br />
{{HINT| Use the program "xev" to see, what mouse button identifiers are sent by your mouse/touchpad/trackpoint.<br />You might want to try: "xev &#124; grep button"}}<br />
{{HINT| If it does not work see if evdev is installed and remove it. On gentoo do the following:<br /><br />
eix xf86-input-evdev<br /><br />
emerge -C xf86-input-evdev<br /><br />
and then remove the evdev flag in make.conf INPUT_DEVICES}}<br />
<br />
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):<br />
<br />
Section "InputDevice"<br />
Identifier "Configured Mouse"<br />
Driver "mouse"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "ExplorerPS/2"<br />
Option "Emulate3Buttons" "on"<br />
Option "Emulate3TimeOut" "50"<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelTimeOut" "200"<br />
Option "EmulateWheelButton" "2"<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
Option "ZAxisMapping" "4 5"<br />
EndSection<br />
<br />
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.<br />
<br />
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.<br />
<br />
To make this work with the synaptics driver for the touchpad, you can add<br />
Option "GuestMouseOff" "1"<br />
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.<br />
<br />
{{NOTE| With the above mouse section in my xorg.conf all this works like a charm:<br />
*I can press the wheel on my external USB mouse and move the mouse up and down for scrolling<br />
*or I can just use the wheel on the external mouse for scrolling<br />
*or pressing the MMB button of the trackpoint and use the trackpoint for scrolling.<br />
*Even horizontal scrolling works automagically in Konqueror, for Firefox/Opera see below.<br />
<br />
Simultaneously I can use<br />
*a press on the external mouse's wheel<br />
*or the MMB of the trackpoint<br />
<br />
for pasting the buffer. Lovely! :) }}<br />
<br />
{{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!}}<br />
<br />
=Application specific tweaks=<br />
===Configure Opera for using trackpoint horizontal scrolling===<br />
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<br />
<pre><br />
Button6 = Back<br />
Button7 = Forward<br />
</pre><br />
so they look like that<br />
<pre><br />
;Button6 = Back<br />
;Button7 = Forward<br />
</pre><br />
Remember, Button6 and Button7 do not so coincidental correspond with our X configuration we know from above:<br />
<pre><br />
Option "YAxisMapping" "6 7"<br />
</pre><br />
After this change you will be able to scroll vertically and horizontally with your middle button.<br />
<br />
===Firefox 3 tweaks===<br />
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:<br />
<br />
middlemouse.paste = false<br />
middlemouse.contentLoadURL = false<br />
general.autoScroll = true<br />
<br />
=Sysfs Options Reference=<br />
{{NOTE|These options are current as of kernel version 2.6.29, 3 May 2009}}<br />
{|<br />
|-<br />
! Name<br />
! Type<br />
! Default<br />
! Notes<br />
|-<br />
| sensitivity<br />
| Integer<br />
| 128<br />
| Sensitivity<br />
|-<br />
| speed<br />
| Integer<br />
| 97<br />
| Cursor speed<br />
|-<br />
| inertia<br />
| Integer<br />
| 6<br />
| Described as "negative inertia." It acts more like friction. High values cause the cursor to snap backward when the Trackpoint is released<br />
|-<br />
| reach<br />
| Integer<br />
| 10<br />
| Backup for Z-axis press<br />
|-<br />
| draghys<br />
| Integer<br />
| 255<br />
| Drag hysteresis (how hard it is to drag with Z-axis pressed)<br />
|-<br />
| mindrag<br />
| Integer<br />
| 20<br />
| Minimum amount of force needed to trigger dragging<br />
|-<br />
| thresh<br />
| Integer<br />
| 8<br />
| Minimum value for a Z-axis press<br />
|-<br />
| upthresh<br />
| Integer<br />
| 255<br />
| Used to generate a 'click' on Z-axis<br />
|-<br />
| ztime<br />
| Integer<br />
| 38<br />
| How sharp of a press<br />
|-<br />
| jenks<br />
| Integer<br />
| 135<br />
| Minimum curvature for double click<br />
|-<br />
| press_to_select<br />
| Boolean<br />
| 0<br />
| Press to select<br />
|-<br />
| skipback<br />
| Boolean<br />
| 0<br />
| Supress movement after drag release<br />
|-<br />
| ext_dev<br />
| Boolean<br />
| 0<br />
| Disable external device<br />
|}<br />
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] <!--if this link breaks, I recommend a quick Google search for "trackpoint version 4 engineering specifications" --> contains more documentation information than anyone ever desired.<br />
<br />
=Determining TrackPoint Path ID=<br />
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:<br />
/lib/udev/path_id $(find /sys/devices/platform/i8042 -name name | xargs grep -Fl TrackPoint | sed 's/\/sys\(.*\)\/name/\1/')</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=How_to_configure_the_TrackPoint&diff=48839How to configure the TrackPoint2010-06-22T01:27:45Z<p>Mahto: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |Below are several ways of configuring the kernel psmouse driver for controlling extended TrackPoint features.<br />
|}<br />
<br />
While there seem to be many options to get Trackpoint scrolling to work editing xorg.conf is still the easiest and works fine for Debian Lenny and PCLOS '09.<br />
<br />
=Configuration using xinput=<br />
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).<br />
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.<br />
<br />
To query the available options<br />
xinput list-props "TPPS/2 IBM TrackPoint"<br />
<br />
More information can be found in the man-pages for evdev<br />
man evdev<br />
<br />
To enable vertical scrolling<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
To enable horizontal scrolling in addition to vertical scrolling<br />
<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To enable middle button emulation (using left- and right-click simultaneously)<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Timeout" 8 50<br />
<br />
==Example: openSUSE 11.2 and ThinkPad USB Keyboard with TrackPoint ==<br />
<br />
xinput list <br />
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.<br />
<br />
Suppose the id was 12. The following will enable the trackpoint scrolling:<br />
<br />
xinput set-int-prop 12 "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
The following will enable the horizontal scrolling<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To disable middle button click paste functionality, remap the middle button to something else:<br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
To do these automatically without worrying about id number, generate a bash script file:<br />
#!/bin/sh<br />
xinput list | sed -ne 's/^[^ ][^V].*id=\([0-9]*\).*/\1/p' | while read id<br />
do<br />
case `xinput list-props $id` in<br />
*"Middle Button Emulation"*)<br />
xinput set-int-prop $id "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop $id "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop $id "Evdev Wheel Emulation Timeout" 8 200<br />
xinput set-int-prop $id "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
xinput set-int-prop $id "Evdev Middle Button Emulation" 8 0<br />
;;<br />
esac<br />
done<br />
<br />
# disable middle button <br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
and save it with any name such as trackPointScrolling.sh, and make it executable:<br />
chmod +x trackPointScrolling.sh<br />
<br />
Next time you run it with $ ./trackPointScrolling.sh, it will enable the trackpoint scrolling and disable middle button paste.<br />
{{Todo|some other examples}}<br />
<br />
= Graphical Frontends =<br />
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.<br />
=== GPointing Device Settings ===<br />
It is available for Fedora 12, Ubuntu 9.10 and Debian Squeeze in the standard package repositories<br />
<br />
[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]<br />
<br />
=== configure-trackpoint ===<br />
To install it in Ubuntu run ...<br />
sudo apt-get install sysfsutils<br />
...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.<br />
<br />
= Configuration using DevKit =<br />
Most recent distributions like Ubuntu 9.10 switch from HAL (being deprecated) to DevKit. Hence, the HAL configurations explained underneath, fail to work. <br />
<br />
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}}<br />
<br />
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.<br />
<br />
= Configuration using udev and HAL =<br />
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.<br />
<br />
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.<br />
<br />
=== Scrolling ===<br />
By default the middle mouse button is that, a middle mouse button, which in Linux is used for the Paste operation.<br />
<br />
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). <br />
<br />
==== xorg.conf.d ====<br />
<br />
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.<br />
<br />
Create the file {{path|/usr/lib/X11/xorg.conf.d/20-thinkpad.conf}} as root with the following content:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "Trackpoint Wheel Emulation"<br />
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint|ThinkPad USB Keyboard with TrackPoint|USB Trackpoint pointing device"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "2"<br />
Option "Emulate3Buttons" "false"<br />
Option "XAxisMapping" "6 7"<br />
Option "YAxisMapping" "4 5"<br />
EndSection<br />
</pre><br />
<br />
Save and restart Xorg (or it'll be enabled at next reboot).<br />
<br />
{{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 product | sort -u</pre> to get a list of possibilities.}}<br />
<br />
{{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.}}<br />
<br />
==== udev ====<br />
<br />
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.<br />
<br />
Create the file {{path|/etc/udev/rules.d/99_trackpoint.rules}} as root with the following content:<br />
<br />
<pre><br />
ACTION!="add|change", GOTO="xorg_trackpoint_end"<br />
KERNEL!="event*", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{x11_options.EmulateWheel}="1"<br />
ENV{x11_options.EmulateWheelButton}="2"<br />
ENV{x11_options.XAxisMapping}="6 7"<br />
ENV{x11_options.Emulate3Buttons}="0"<br />
<br />
LABEL="xorg_trackpoint_end"<br />
</pre><br />
<br />
Save and restart udev then Xorg (or it'll be enabled at next reboot).<br />
<br />
{{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]]}}<br />
<br />
==== Hal (soon to be deprecated) ====<br />
<br />
To accomplish this create the file {{path|/etc/hal/fdi/policy/mouse-wheel.fdi}} as root with the following content:<br />
<br />
<pre><br />
<match key="info.product" string="TPPS/2 IBM TrackPoint"><br />
<merge key="input.x11_options.EmulateWheel" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge><br />
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge><br />
</match><br />
</pre><br />
<br />
If you also want to have horizontal scrolling, simply add the following XAxisMapping option to the above<br />
<pre><br />
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge><br />
</pre><br />
After this reboot, or restart the hal service and Xorg. You can validate the settings with {{cmd|lshal|}}.<br />
<br />
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>.<br />
<br />
Alternatively it is also possible to use the "old" Xorg configuration by adding the following lines to the {{path|/etc/X11/xorg.conf}}:<br />
<br />
<pre><br />
Section "ServerFlags"<br />
Option "AutoAddDevices" "false"<br />
EndSection<br />
</pre><br />
<br />
Using this entry HAL will not be used for the input devices.<br />
<br />
====Reactivate Scrolling after suspend/resume====<br />
Scrolling may be disabled after a resume from suspend. <br />
<br />
You can manually reactivate the trackpoint by reloading the {{path|psmouse}} module as root:<br />
:{{cmdroot|rmmod psmouse && modprobe psmouse}}<br />
<br />
You can automatically force the pm-utils to reload this module.<br />
Create a file {{path|/etc/pm/config.d/01reload_mouse}} as root with the following content:<br />
<pre><br />
# reload psmouse to reactivate trackpoint scrolling<br />
SUSPEND_MODULES="${SUSPEND_MODULES:+$SUSPEND_MODULES }psmouse"<br />
</pre><br />
<br />
===Configuring other options (e.g. Press to select, Sensitivity and Speed)===<br />
<!--HAL wasn't made to configure sysfs settings, so we'll use udev instead --><br />
Create a file {{path|/etc/udev/rules.d/10-trackpoint.rules}} and add a line to suit your needs<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", ATTR{press_to_select}="1", ATTR{sensitivity}="122"<br />
</pre><br />
<br />
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.<br />
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<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="122"<br />
</pre><br />
<br />
=Configuration using sysfs=<br />
Another way to modify changes on the fly, is echoing values directly into special files in sysfs.<br />
<br />
{{NOTE|<br />
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}}.<br />
<br />
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).}}<br />
<br />
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.<br />
<br />
===Press to Select===<br />
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):<br />
<br />
:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
Press to Select should now be enabled. You can disable it in a similar manner:<br />
<br />
:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
You can use this script to automate the operation<br />
<br />
#!/bin/bash<br />
if [ "$1" = "1" ]; then<br />
echo "Turning on tap on TrackPoint"<br />
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
if [ "$1" = "0" ]; then<br />
echo "Turning off tap on TrackPoint"<br />
echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
echo -n "Tap status: "<br />
cat /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
In Ubuntu 8.10 to make Press to Select a permanent change:<br />
<br />
echo -n 1 | tee /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
As root, append the above command above "exit 0" in /etc/gdm/Init/Default<br />
<br />
===Sensitivity & Speed===<br />
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:<br />
<br />
:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed}}<br />
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity}}<br />
<br />
Feel free to experiment with your settings until you find a combination that is comfortable.<br />
<br />
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.<br />
<br />
===Vertical Scrolling===<br />
No sysfs entry exists for vertical scrolling in kernels after 2.6.11.<br />
<br />
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.<br />
Instead the scroll feature of the Xserver should be used, which can be activated with HAL or xinput as described above.<br />
<br />
=Configuration using the X server (xorg.conf)=<br />
==Using the "evdev" driver (preferred, especially for recent Xorg versions)==<br />
Extract from /etc/X11/xorg.conf on an X31:<br />
<br />
Section "InputDevice"<br />
Identifier "TPPS/2 IBM TrackPoint"<br />
Driver "evdev"<br />
Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"<br />
Option "GrabDevice" "False"<br />
Option "EmulateWheel" "true" #Enable wheel emulation for the Trackpoint<br />
Option "EmulateWheelButton" "2" #Use the middle button for the emulation<br />
Option "XAxisMapping" "6 7" #Map trackpoint X axis to X axis of emulated wheel<br />
Option "YAxisMapping" "4 5" #Map trackpoint Y axis to Y axis of emulated wheel<br />
EndSection<br />
<br />
{{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]]}}<br />
<br />
==Using the "mouse" driver (deprecated, only for old Xorg versions)==<br />
{{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}}<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Once this functionality is in the X.org, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:<br />
<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelButton" "2"<br />
<br />
It may also be necessary to add these lines:<br />
<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
<br />
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).<br />
<br />
{{HINT| Use the program "xev" to see, what mouse button identifiers are sent by your mouse/touchpad/trackpoint.<br />You might want to try: "xev &#124; grep button"}}<br />
{{HINT| If it does not work see if evdev is installed and remove it. On gentoo do the following:<br /><br />
eix xf86-input-evdev<br /><br />
emerge -C xf86-input-evdev<br /><br />
and then remove the evdev flag in make.conf INPUT_DEVICES}}<br />
<br />
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):<br />
<br />
Section "InputDevice"<br />
Identifier "Configured Mouse"<br />
Driver "mouse"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "ExplorerPS/2"<br />
Option "Emulate3Buttons" "on"<br />
Option "Emulate3TimeOut" "50"<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelTimeOut" "200"<br />
Option "EmulateWheelButton" "2"<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
Option "ZAxisMapping" "4 5"<br />
EndSection<br />
<br />
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.<br />
<br />
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.<br />
<br />
To make this work with the synaptics driver for the touchpad, you can add<br />
Option "GuestMouseOff" "1"<br />
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.<br />
<br />
{{NOTE| With the above mouse section in my xorg.conf all this works like a charm: <br />
*I can press the wheel on my external USB mouse and move the mouse up and down for scrolling<br />
*or I can just use the wheel on the external mouse for scrolling<br />
*or pressing the MMB button of the trackpoint and use the trackpoint for scrolling.<br />
*Even horizontal scrolling works automagically in Konqueror, for Firefox/Opera see below.<br />
<br />
Simultaneously I can use <br />
*a press on the external mouse's wheel <br />
*or the MMB of the trackpoint<br />
<br />
for pasting the buffer. Lovely! :) }}<br />
<br />
{{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!}}<br />
<br />
=Application specific tweaks=<br />
===Configure Opera for using trackpoint horizontal scrolling===<br />
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<br />
<pre><br />
Button6 = Back<br />
Button7 = Forward<br />
</pre><br />
so they look like that<br />
<pre><br />
;Button6 = Back<br />
;Button7 = Forward<br />
</pre><br />
Remember, Button6 and Button7 do not so coincidental correspond with our X configuration we know from above:<br />
<pre><br />
Option "YAxisMapping" "6 7"<br />
</pre><br />
After this change you will be able to scroll vertically and horizontally with your middle button.<br />
<br />
===Firefox 3 tweaks===<br />
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:<br />
<br />
middlemouse.paste = false<br />
middlemouse.contentLoadURL = false<br />
general.autoScroll = true<br />
<br />
=Sysfs Options Reference=<br />
{{NOTE|These options are current as of kernel version 2.6.29, 3 May 2009}}<br />
{| <br />
|-<br />
! Name<br />
! Type<br />
! Default<br />
! Notes<br />
|-<br />
| sensitivity<br />
| Integer<br />
| 128<br />
| Sensitivity<br />
|-<br />
| speed<br />
| Integer<br />
| 97<br />
| Cursor speed<br />
|-<br />
| inertia<br />
| Integer<br />
| 6<br />
| Described as "negative inertia." It acts more like friction. High values cause the cursor to snap backward when the Trackpoint is released<br />
|-<br />
| reach<br />
| Integer<br />
| 10<br />
| Backup for Z-axis press<br />
|-<br />
| draghys<br />
| Integer<br />
| 255<br />
| Drag hysteresis (how hard it is to drag with Z-axis pressed)<br />
|-<br />
| mindrag<br />
| Integer<br />
| 20<br />
| Minimum amount of force needed to trigger dragging<br />
|-<br />
| thresh<br />
| Integer<br />
| 8<br />
| Minimum value for a Z-axis press<br />
|-<br />
| upthresh<br />
| Integer<br />
| 255<br />
| Used to generate a 'click' on Z-axis<br />
|-<br />
| ztime<br />
| Integer<br />
| 38<br />
| How sharp of a press<br />
|-<br />
| jenks<br />
| Integer<br />
| 135<br />
| Minimum curvature for double click<br />
|-<br />
| press_to_select<br />
| Boolean<br />
| 0<br />
| Press to select<br />
|-<br />
| skipback<br />
| Boolean<br />
| 0<br />
| Supress movement after drag release <br />
|-<br />
| ext_dev<br />
| Boolean<br />
| 0<br />
| Disable external device<br />
|}<br />
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] <!--if this link breaks, I recommend a quick Google search for "trackpoint version 4 engineering specifications" --> contains more documentation information than anyone ever desired.<br />
<br />
=Determining TrackPoint Path ID=<br />
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:<br />
/lib/udev/path_id $(find /sys/devices/platform/i8042 -name name | xargs grep -Fl TrackPoint | sed 's/\/sys\(.*\)\/name/\1/')</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=How_to_configure_the_TrackPoint&diff=48838How to configure the TrackPoint2010-06-22T01:24:11Z<p>Mahto: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |Below are several ways of configuring the kernel psmouse driver for controlling extended TrackPoint features.<br />
|}<br />
<br />
=While there seem to be many options to get Trackpoint scrolling to work editing xorg.conf is still the easiest and works fine for Debian Lenny and PCLOS '09.<br />
<br />
=Configuration using xinput=<br />
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).<br />
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.<br />
<br />
To query the available options<br />
xinput list-props "TPPS/2 IBM TrackPoint"<br />
<br />
More information can be found in the man-pages for evdev<br />
man evdev<br />
<br />
To enable vertical scrolling<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
To enable horizontal scrolling in addition to vertical scrolling<br />
<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To enable middle button emulation (using left- and right-click simultaneously)<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Timeout" 8 50<br />
<br />
==Example: openSUSE 11.2 and ThinkPad USB Keyboard with TrackPoint ==<br />
<br />
xinput list <br />
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.<br />
<br />
Suppose the id was 12. The following will enable the trackpoint scrolling:<br />
<br />
xinput set-int-prop 12 "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
The following will enable the horizontal scrolling<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To disable middle button click paste functionality, remap the middle button to something else:<br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
To do these automatically without worrying about id number, generate a bash script file:<br />
#!/bin/sh<br />
xinput list | sed -ne 's/^[^ ][^V].*id=\([0-9]*\).*/\1/p' | while read id<br />
do<br />
case `xinput list-props $id` in<br />
*"Middle Button Emulation"*)<br />
xinput set-int-prop $id "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop $id "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop $id "Evdev Wheel Emulation Timeout" 8 200<br />
xinput set-int-prop $id "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
xinput set-int-prop $id "Evdev Middle Button Emulation" 8 0<br />
;;<br />
esac<br />
done<br />
<br />
# disable middle button <br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
and save it with any name such as trackPointScrolling.sh, and make it executable:<br />
chmod +x trackPointScrolling.sh<br />
<br />
Next time you run it with $ ./trackPointScrolling.sh, it will enable the trackpoint scrolling and disable middle button paste.<br />
{{Todo|some other examples}}<br />
<br />
= Graphical Frontends =<br />
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.<br />
=== GPointing Device Settings ===<br />
It is available for Fedora 12, Ubuntu 9.10 and Debian Squeeze in the standard package repositories<br />
<br />
[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]<br />
<br />
=== configure-trackpoint ===<br />
To install it in Ubuntu run ...<br />
sudo apt-get install sysfsutils<br />
...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.<br />
<br />
= Configuration using DevKit =<br />
Most recent distributions like Ubuntu 9.10 switch from HAL (being deprecated) to DevKit. Hence, the HAL configurations explained underneath, fail to work. <br />
<br />
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}}<br />
<br />
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.<br />
<br />
= Configuration using udev and HAL =<br />
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.<br />
<br />
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.<br />
<br />
=== Scrolling ===<br />
By default the middle mouse button is that, a middle mouse button, which in Linux is used for the Paste operation.<br />
<br />
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). <br />
<br />
==== xorg.conf.d ====<br />
<br />
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.<br />
<br />
Create the file {{path|/usr/lib/X11/xorg.conf.d/20-thinkpad.conf}} as root with the following content:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "Trackpoint Wheel Emulation"<br />
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint|ThinkPad USB Keyboard with TrackPoint|USB Trackpoint pointing device"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "2"<br />
Option "Emulate3Buttons" "false"<br />
Option "XAxisMapping" "6 7"<br />
Option "YAxisMapping" "4 5"<br />
EndSection<br />
</pre><br />
<br />
Save and restart Xorg (or it'll be enabled at next reboot).<br />
<br />
{{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 product | sort -u</pre> to get a list of possibilities.}}<br />
<br />
{{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.}}<br />
<br />
==== udev ====<br />
<br />
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.<br />
<br />
Create the file {{path|/etc/udev/rules.d/99_trackpoint.rules}} as root with the following content:<br />
<br />
<pre><br />
ACTION!="add|change", GOTO="xorg_trackpoint_end"<br />
KERNEL!="event*", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{x11_options.EmulateWheel}="1"<br />
ENV{x11_options.EmulateWheelButton}="2"<br />
ENV{x11_options.XAxisMapping}="6 7"<br />
ENV{x11_options.Emulate3Buttons}="0"<br />
<br />
LABEL="xorg_trackpoint_end"<br />
</pre><br />
<br />
Save and restart udev then Xorg (or it'll be enabled at next reboot).<br />
<br />
{{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]]}}<br />
<br />
==== Hal (soon to be deprecated) ====<br />
<br />
To accomplish this create the file {{path|/etc/hal/fdi/policy/mouse-wheel.fdi}} as root with the following content:<br />
<br />
<pre><br />
<match key="info.product" string="TPPS/2 IBM TrackPoint"><br />
<merge key="input.x11_options.EmulateWheel" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge><br />
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge><br />
</match><br />
</pre><br />
<br />
If you also want to have horizontal scrolling, simply add the following XAxisMapping option to the above<br />
<pre><br />
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge><br />
</pre><br />
After this reboot, or restart the hal service and Xorg. You can validate the settings with {{cmd|lshal|}}.<br />
<br />
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>.<br />
<br />
Alternatively it is also possible to use the "old" Xorg configuration by adding the following lines to the {{path|/etc/X11/xorg.conf}}:<br />
<br />
<pre><br />
Section "ServerFlags"<br />
Option "AutoAddDevices" "false"<br />
EndSection<br />
</pre><br />
<br />
Using this entry HAL will not be used for the input devices.<br />
<br />
====Reactivate Scrolling after suspend/resume====<br />
Scrolling may be disabled after a resume from suspend. <br />
<br />
You can manually reactivate the trackpoint by reloading the {{path|psmouse}} module as root:<br />
:{{cmdroot|rmmod psmouse && modprobe psmouse}}<br />
<br />
You can automatically force the pm-utils to reload this module.<br />
Create a file {{path|/etc/pm/config.d/01reload_mouse}} as root with the following content:<br />
<pre><br />
# reload psmouse to reactivate trackpoint scrolling<br />
SUSPEND_MODULES="${SUSPEND_MODULES:+$SUSPEND_MODULES }psmouse"<br />
</pre><br />
<br />
===Configuring other options (e.g. Press to select, Sensitivity and Speed)===<br />
<!--HAL wasn't made to configure sysfs settings, so we'll use udev instead --><br />
Create a file {{path|/etc/udev/rules.d/10-trackpoint.rules}} and add a line to suit your needs<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", ATTR{press_to_select}="1", ATTR{sensitivity}="122"<br />
</pre><br />
<br />
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.<br />
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<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="122"<br />
</pre><br />
<br />
=Configuration using sysfs=<br />
Another way to modify changes on the fly, is echoing values directly into special files in sysfs.<br />
<br />
{{NOTE|<br />
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}}.<br />
<br />
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).}}<br />
<br />
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.<br />
<br />
===Press to Select===<br />
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):<br />
<br />
:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
Press to Select should now be enabled. You can disable it in a similar manner:<br />
<br />
:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
You can use this script to automate the operation<br />
<br />
#!/bin/bash<br />
if [ "$1" = "1" ]; then<br />
echo "Turning on tap on TrackPoint"<br />
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
if [ "$1" = "0" ]; then<br />
echo "Turning off tap on TrackPoint"<br />
echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
echo -n "Tap status: "<br />
cat /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
In Ubuntu 8.10 to make Press to Select a permanent change:<br />
<br />
echo -n 1 | tee /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
As root, append the above command above "exit 0" in /etc/gdm/Init/Default<br />
<br />
===Sensitivity & Speed===<br />
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:<br />
<br />
:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed}}<br />
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity}}<br />
<br />
Feel free to experiment with your settings until you find a combination that is comfortable.<br />
<br />
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.<br />
<br />
===Vertical Scrolling===<br />
No sysfs entry exists for vertical scrolling in kernels after 2.6.11.<br />
<br />
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.<br />
Instead the scroll feature of the Xserver should be used, which can be activated with HAL or xinput as described above.<br />
<br />
=Configuration using the X server (xorg.conf)=<br />
==Using the "evdev" driver (preferred, especially for recent Xorg versions)==<br />
Extract from /etc/X11/xorg.conf on an X31:<br />
<br />
Section "InputDevice"<br />
Identifier "TPPS/2 IBM TrackPoint"<br />
Driver "evdev"<br />
Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"<br />
Option "GrabDevice" "False"<br />
Option "EmulateWheel" "true" #Enable wheel emulation for the Trackpoint<br />
Option "EmulateWheelButton" "2" #Use the middle button for the emulation<br />
Option "XAxisMapping" "6 7" #Map trackpoint X axis to X axis of emulated wheel<br />
Option "YAxisMapping" "4 5" #Map trackpoint Y axis to Y axis of emulated wheel<br />
EndSection<br />
<br />
{{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]]}}<br />
<br />
==Using the "mouse" driver (deprecated, only for old Xorg versions)==<br />
{{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}}<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Once this functionality is in the X.org, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:<br />
<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelButton" "2"<br />
<br />
It may also be necessary to add these lines:<br />
<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
<br />
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).<br />
<br />
{{HINT| Use the program "xev" to see, what mouse button identifiers are sent by your mouse/touchpad/trackpoint.<br />You might want to try: "xev &#124; grep button"}}<br />
{{HINT| If it does not work see if evdev is installed and remove it. On gentoo do the following:<br /><br />
eix xf86-input-evdev<br /><br />
emerge -C xf86-input-evdev<br /><br />
and then remove the evdev flag in make.conf INPUT_DEVICES}}<br />
<br />
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):<br />
<br />
Section "InputDevice"<br />
Identifier "Configured Mouse"<br />
Driver "mouse"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "ExplorerPS/2"<br />
Option "Emulate3Buttons" "on"<br />
Option "Emulate3TimeOut" "50"<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelTimeOut" "200"<br />
Option "EmulateWheelButton" "2"<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
Option "ZAxisMapping" "4 5"<br />
EndSection<br />
<br />
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.<br />
<br />
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.<br />
<br />
To make this work with the synaptics driver for the touchpad, you can add<br />
Option "GuestMouseOff" "1"<br />
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.<br />
<br />
{{NOTE| With the above mouse section in my xorg.conf all this works like a charm: <br />
*I can press the wheel on my external USB mouse and move the mouse up and down for scrolling<br />
*or I can just use the wheel on the external mouse for scrolling<br />
*or pressing the MMB button of the trackpoint and use the trackpoint for scrolling.<br />
*Even horizontal scrolling works automagically in Konqueror, for Firefox/Opera see below.<br />
<br />
Simultaneously I can use <br />
*a press on the external mouse's wheel <br />
*or the MMB of the trackpoint<br />
<br />
for pasting the buffer. Lovely! :) }}<br />
<br />
{{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!}}<br />
<br />
=Application specific tweaks=<br />
===Configure Opera for using trackpoint horizontal scrolling===<br />
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<br />
<pre><br />
Button6 = Back<br />
Button7 = Forward<br />
</pre><br />
so they look like that<br />
<pre><br />
;Button6 = Back<br />
;Button7 = Forward<br />
</pre><br />
Remember, Button6 and Button7 do not so coincidental correspond with our X configuration we know from above:<br />
<pre><br />
Option "YAxisMapping" "6 7"<br />
</pre><br />
After this change you will be able to scroll vertically and horizontally with your middle button.<br />
<br />
===Firefox 3 tweaks===<br />
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:<br />
<br />
middlemouse.paste = false<br />
middlemouse.contentLoadURL = false<br />
general.autoScroll = true<br />
<br />
=Sysfs Options Reference=<br />
{{NOTE|These options are current as of kernel version 2.6.29, 3 May 2009}}<br />
{| <br />
|-<br />
! Name<br />
! Type<br />
! Default<br />
! Notes<br />
|-<br />
| sensitivity<br />
| Integer<br />
| 128<br />
| Sensitivity<br />
|-<br />
| speed<br />
| Integer<br />
| 97<br />
| Cursor speed<br />
|-<br />
| inertia<br />
| Integer<br />
| 6<br />
| Described as "negative inertia." It acts more like friction. High values cause the cursor to snap backward when the Trackpoint is released<br />
|-<br />
| reach<br />
| Integer<br />
| 10<br />
| Backup for Z-axis press<br />
|-<br />
| draghys<br />
| Integer<br />
| 255<br />
| Drag hysteresis (how hard it is to drag with Z-axis pressed)<br />
|-<br />
| mindrag<br />
| Integer<br />
| 20<br />
| Minimum amount of force needed to trigger dragging<br />
|-<br />
| thresh<br />
| Integer<br />
| 8<br />
| Minimum value for a Z-axis press<br />
|-<br />
| upthresh<br />
| Integer<br />
| 255<br />
| Used to generate a 'click' on Z-axis<br />
|-<br />
| ztime<br />
| Integer<br />
| 38<br />
| How sharp of a press<br />
|-<br />
| jenks<br />
| Integer<br />
| 135<br />
| Minimum curvature for double click<br />
|-<br />
| press_to_select<br />
| Boolean<br />
| 0<br />
| Press to select<br />
|-<br />
| skipback<br />
| Boolean<br />
| 0<br />
| Supress movement after drag release <br />
|-<br />
| ext_dev<br />
| Boolean<br />
| 0<br />
| Disable external device<br />
|}<br />
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] <!--if this link breaks, I recommend a quick Google search for "trackpoint version 4 engineering specifications" --> contains more documentation information than anyone ever desired.<br />
<br />
=Determining TrackPoint Path ID=<br />
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:<br />
/lib/udev/path_id $(find /sys/devices/platform/i8042 -name name | xargs grep -Fl TrackPoint | sed 's/\/sys\(.*\)\/name/\1/')</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=How_to_configure_the_TrackPoint&diff=48837How to configure the TrackPoint2010-06-22T01:22:09Z<p>Mahto: </p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |Below are several ways of configuring the kernel psmouse driver for controlling extended TrackPoint features.<br />
|}<br />
<br />
While there seem to be many options to get Trackpoint scrolling to work editing xorg.conf is still the easiest and works fine for Debian stable and PCLOS.<br />
<br />
=Configuration using xinput=<br />
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).<br />
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.<br />
<br />
To query the available options<br />
xinput list-props "TPPS/2 IBM TrackPoint"<br />
<br />
More information can be found in the man-pages for evdev<br />
man evdev<br />
<br />
To enable vertical scrolling<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
To enable horizontal scrolling in addition to vertical scrolling<br />
<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To enable middle button emulation (using left- and right-click simultaneously)<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Emulation" 8 1<br />
xinput set-int-prop "TPPS/2 IBM TrackPoint" "Evdev Middle Button Timeout" 8 50<br />
<br />
==Example: openSUSE 11.2 and ThinkPad USB Keyboard with TrackPoint ==<br />
<br />
xinput list <br />
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.<br />
<br />
Suppose the id was 12. The following will enable the trackpoint scrolling:<br />
<br />
xinput set-int-prop 12 "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Timeout" 8 200<br />
<br />
The following will enable the horizontal scrolling<br />
xinput set-int-prop 12 "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
<br />
To disable middle button click paste functionality, remap the middle button to something else:<br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
To do these automatically without worrying about id number, generate a bash script file:<br />
#!/bin/sh<br />
xinput list | sed -ne 's/^[^ ][^V].*id=\([0-9]*\).*/\1/p' | while read id<br />
do<br />
case `xinput list-props $id` in<br />
*"Middle Button Emulation"*)<br />
xinput set-int-prop $id "Evdev Wheel Emulation" 8 1<br />
xinput set-int-prop $id "Evdev Wheel Emulation Button" 8 2<br />
xinput set-int-prop $id "Evdev Wheel Emulation Timeout" 8 200<br />
xinput set-int-prop $id "Evdev Wheel Emulation Axes" 8 6 7 4 5<br />
xinput set-int-prop $id "Evdev Middle Button Emulation" 8 0<br />
;;<br />
esac<br />
done<br />
<br />
# disable middle button <br />
xmodmap -e "pointer = 1 9 3 4 5 6 7 8 2"<br />
<br />
and save it with any name such as trackPointScrolling.sh, and make it executable:<br />
chmod +x trackPointScrolling.sh<br />
<br />
Next time you run it with $ ./trackPointScrolling.sh, it will enable the trackpoint scrolling and disable middle button paste.<br />
{{Todo|some other examples}}<br />
<br />
= Graphical Frontends =<br />
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.<br />
=== GPointing Device Settings ===<br />
It is available for Fedora 12, Ubuntu 9.10 and Debian Squeeze in the standard package repositories<br />
<br />
[[image:Screenshot-GPointing Device Settings-TrackPoint.png]]<br />
<br />
=== configure-trackpoint ===<br />
To install it in Ubuntu run ...<br />
sudo apt-get install sysfsutils<br />
...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.<br />
<br />
= Configuration using DevKit =<br />
Most recent distributions like Ubuntu 9.10 switch from HAL (being deprecated) to DevKit. Hence, the HAL configurations explained underneath, fail to work. <br />
<br />
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}}<br />
<br />
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.<br />
<br />
= Configuration using udev and HAL =<br />
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.<br />
<br />
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.<br />
<br />
=== Scrolling ===<br />
By default the middle mouse button is that, a middle mouse button, which in Linux is used for the Paste operation.<br />
<br />
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). <br />
<br />
==== xorg.conf.d ====<br />
<br />
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.<br />
<br />
Create the file {{path|/usr/lib/X11/xorg.conf.d/20-thinkpad.conf}} as root with the following content:<br />
<br />
<pre><br />
Section "InputClass"<br />
Identifier "Trackpoint Wheel Emulation"<br />
MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint|ThinkPad USB Keyboard with TrackPoint|USB Trackpoint pointing device"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "EmulateWheel" "true"<br />
Option "EmulateWheelButton" "2"<br />
Option "Emulate3Buttons" "false"<br />
Option "XAxisMapping" "6 7"<br />
Option "YAxisMapping" "4 5"<br />
EndSection<br />
</pre><br />
<br />
Save and restart Xorg (or it'll be enabled at next reboot).<br />
<br />
{{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 product | sort -u</pre> to get a list of possibilities.}}<br />
<br />
{{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.}}<br />
<br />
==== udev ====<br />
<br />
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.<br />
<br />
Create the file {{path|/etc/udev/rules.d/99_trackpoint.rules}} as root with the following content:<br />
<br />
<pre><br />
ACTION!="add|change", GOTO="xorg_trackpoint_end"<br />
KERNEL!="event*", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{ID_PATH}!="platform-i8042-serio-1", GOTO="xorg_trackpoint_end"<br />
<br />
ENV{x11_options.EmulateWheel}="1"<br />
ENV{x11_options.EmulateWheelButton}="2"<br />
ENV{x11_options.XAxisMapping}="6 7"<br />
ENV{x11_options.Emulate3Buttons}="0"<br />
<br />
LABEL="xorg_trackpoint_end"<br />
</pre><br />
<br />
Save and restart udev then Xorg (or it'll be enabled at next reboot).<br />
<br />
{{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]]}}<br />
<br />
==== Hal (soon to be deprecated) ====<br />
<br />
To accomplish this create the file {{path|/etc/hal/fdi/policy/mouse-wheel.fdi}} as root with the following content:<br />
<br />
<pre><br />
<match key="info.product" string="TPPS/2 IBM TrackPoint"><br />
<merge key="input.x11_options.EmulateWheel" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge><br />
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge><br />
</match><br />
</pre><br />
<br />
If you also want to have horizontal scrolling, simply add the following XAxisMapping option to the above<br />
<pre><br />
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge><br />
</pre><br />
After this reboot, or restart the hal service and Xorg. You can validate the settings with {{cmd|lshal|}}.<br />
<br />
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>.<br />
<br />
Alternatively it is also possible to use the "old" Xorg configuration by adding the following lines to the {{path|/etc/X11/xorg.conf}}:<br />
<br />
<pre><br />
Section "ServerFlags"<br />
Option "AutoAddDevices" "false"<br />
EndSection<br />
</pre><br />
<br />
Using this entry HAL will not be used for the input devices.<br />
<br />
====Reactivate Scrolling after suspend/resume====<br />
Scrolling may be disabled after a resume from suspend. <br />
<br />
You can manually reactivate the trackpoint by reloading the {{path|psmouse}} module as root:<br />
:{{cmdroot|rmmod psmouse && modprobe psmouse}}<br />
<br />
You can automatically force the pm-utils to reload this module.<br />
Create a file {{path|/etc/pm/config.d/01reload_mouse}} as root with the following content:<br />
<pre><br />
# reload psmouse to reactivate trackpoint scrolling<br />
SUSPEND_MODULES="${SUSPEND_MODULES:+$SUSPEND_MODULES }psmouse"<br />
</pre><br />
<br />
===Configuring other options (e.g. Press to select, Sensitivity and Speed)===<br />
<!--HAL wasn't made to configure sysfs settings, so we'll use udev instead --><br />
Create a file {{path|/etc/udev/rules.d/10-trackpoint.rules}} and add a line to suit your needs<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", ATTR{press_to_select}="1", ATTR{sensitivity}="122"<br />
</pre><br />
<br />
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.<br />
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<br />
<br />
<pre><br />
SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="122"<br />
</pre><br />
<br />
=Configuration using sysfs=<br />
Another way to modify changes on the fly, is echoing values directly into special files in sysfs.<br />
<br />
{{NOTE|<br />
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}}.<br />
<br />
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).}}<br />
<br />
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.<br />
<br />
===Press to Select===<br />
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):<br />
<br />
:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
Press to Select should now be enabled. You can disable it in a similar manner:<br />
<br />
:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select}}<br />
<br />
You can use this script to automate the operation<br />
<br />
#!/bin/bash<br />
if [ "$1" = "1" ]; then<br />
echo "Turning on tap on TrackPoint"<br />
echo -n 1 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
if [ "$1" = "0" ]; then<br />
echo "Turning off tap on TrackPoint"<br />
echo -n 0 > /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
exit 0<br />
fi<br />
echo -n "Tap status: "<br />
cat /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
In Ubuntu 8.10 to make Press to Select a permanent change:<br />
<br />
echo -n 1 | tee /sys/devices/platform/i8042/serio1/serio2/press_to_select<br />
<br />
As root, append the above command above "exit 0" in /etc/gdm/Init/Default<br />
<br />
===Sensitivity & Speed===<br />
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:<br />
<br />
:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed}}<br />
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio1/serio2/sensitivity}}<br />
<br />
Feel free to experiment with your settings until you find a combination that is comfortable.<br />
<br />
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.<br />
<br />
===Vertical Scrolling===<br />
No sysfs entry exists for vertical scrolling in kernels after 2.6.11.<br />
<br />
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.<br />
Instead the scroll feature of the Xserver should be used, which can be activated with HAL or xinput as described above.<br />
<br />
=Configuration using the X server (xorg.conf)=<br />
==Using the "evdev" driver (preferred, especially for recent Xorg versions)==<br />
Extract from /etc/X11/xorg.conf on an X31:<br />
<br />
Section "InputDevice"<br />
Identifier "TPPS/2 IBM TrackPoint"<br />
Driver "evdev"<br />
Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"<br />
Option "GrabDevice" "False"<br />
Option "EmulateWheel" "true" #Enable wheel emulation for the Trackpoint<br />
Option "EmulateWheelButton" "2" #Use the middle button for the emulation<br />
Option "XAxisMapping" "6 7" #Map trackpoint X axis to X axis of emulated wheel<br />
Option "YAxisMapping" "4 5" #Map trackpoint Y axis to Y axis of emulated wheel<br />
EndSection<br />
<br />
{{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]]}}<br />
<br />
==Using the "mouse" driver (deprecated, only for old Xorg versions)==<br />
{{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}}<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Once this functionality is in the X.org, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:<br />
<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelButton" "2"<br />
<br />
It may also be necessary to add these lines:<br />
<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
<br />
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).<br />
<br />
{{HINT| Use the program "xev" to see, what mouse button identifiers are sent by your mouse/touchpad/trackpoint.<br />You might want to try: "xev &#124; grep button"}}<br />
{{HINT| If it does not work see if evdev is installed and remove it. On gentoo do the following:<br /><br />
eix xf86-input-evdev<br /><br />
emerge -C xf86-input-evdev<br /><br />
and then remove the evdev flag in make.conf INPUT_DEVICES}}<br />
<br />
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):<br />
<br />
Section "InputDevice"<br />
Identifier "Configured Mouse"<br />
Driver "mouse"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "ExplorerPS/2"<br />
Option "Emulate3Buttons" "on"<br />
Option "Emulate3TimeOut" "50"<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelTimeOut" "200"<br />
Option "EmulateWheelButton" "2"<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
Option "ZAxisMapping" "4 5"<br />
EndSection<br />
<br />
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.<br />
<br />
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.<br />
<br />
To make this work with the synaptics driver for the touchpad, you can add<br />
Option "GuestMouseOff" "1"<br />
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.<br />
<br />
{{NOTE| With the above mouse section in my xorg.conf all this works like a charm: <br />
*I can press the wheel on my external USB mouse and move the mouse up and down for scrolling<br />
*or I can just use the wheel on the external mouse for scrolling<br />
*or pressing the MMB button of the trackpoint and use the trackpoint for scrolling.<br />
*Even horizontal scrolling works automagically in Konqueror, for Firefox/Opera see below.<br />
<br />
Simultaneously I can use <br />
*a press on the external mouse's wheel <br />
*or the MMB of the trackpoint<br />
<br />
for pasting the buffer. Lovely! :) }}<br />
<br />
{{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!}}<br />
<br />
=Application specific tweaks=<br />
===Configure Opera for using trackpoint horizontal scrolling===<br />
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<br />
<pre><br />
Button6 = Back<br />
Button7 = Forward<br />
</pre><br />
so they look like that<br />
<pre><br />
;Button6 = Back<br />
;Button7 = Forward<br />
</pre><br />
Remember, Button6 and Button7 do not so coincidental correspond with our X configuration we know from above:<br />
<pre><br />
Option "YAxisMapping" "6 7"<br />
</pre><br />
After this change you will be able to scroll vertically and horizontally with your middle button.<br />
<br />
===Firefox 3 tweaks===<br />
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:<br />
<br />
middlemouse.paste = false<br />
middlemouse.contentLoadURL = false<br />
general.autoScroll = true<br />
<br />
=Sysfs Options Reference=<br />
{{NOTE|These options are current as of kernel version 2.6.29, 3 May 2009}}<br />
{| <br />
|-<br />
! Name<br />
! Type<br />
! Default<br />
! Notes<br />
|-<br />
| sensitivity<br />
| Integer<br />
| 128<br />
| Sensitivity<br />
|-<br />
| speed<br />
| Integer<br />
| 97<br />
| Cursor speed<br />
|-<br />
| inertia<br />
| Integer<br />
| 6<br />
| Described as "negative inertia." It acts more like friction. High values cause the cursor to snap backward when the Trackpoint is released<br />
|-<br />
| reach<br />
| Integer<br />
| 10<br />
| Backup for Z-axis press<br />
|-<br />
| draghys<br />
| Integer<br />
| 255<br />
| Drag hysteresis (how hard it is to drag with Z-axis pressed)<br />
|-<br />
| mindrag<br />
| Integer<br />
| 20<br />
| Minimum amount of force needed to trigger dragging<br />
|-<br />
| thresh<br />
| Integer<br />
| 8<br />
| Minimum value for a Z-axis press<br />
|-<br />
| upthresh<br />
| Integer<br />
| 255<br />
| Used to generate a 'click' on Z-axis<br />
|-<br />
| ztime<br />
| Integer<br />
| 38<br />
| How sharp of a press<br />
|-<br />
| jenks<br />
| Integer<br />
| 135<br />
| Minimum curvature for double click<br />
|-<br />
| press_to_select<br />
| Boolean<br />
| 0<br />
| Press to select<br />
|-<br />
| skipback<br />
| Boolean<br />
| 0<br />
| Supress movement after drag release <br />
|-<br />
| ext_dev<br />
| Boolean<br />
| 0<br />
| Disable external device<br />
|}<br />
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] <!--if this link breaks, I recommend a quick Google search for "trackpoint version 4 engineering specifications" --> contains more documentation information than anyone ever desired.<br />
<br />
=Determining TrackPoint Path ID=<br />
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:<br />
/lib/udev/path_id $(find /sys/devices/platform/i8042 -name name | xargs grep -Fl TrackPoint | sed 's/\/sys\(.*\)\/name/\1/')</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_notes_ca.2007&diff=33642Installation notes ca.20072007-10-03T04:18:05Z<p>Mahto: minor edits and HW config</p>
<hr />
<div>notes:<br />
<br />
6/07 I'm upgrading from {{A31p}} to {{T42p}} and am going to document Linux installs. I previously had an {{A30}} which was very nix friendly, but the A31p was another story altogether. I also have an {{X22}} with {{Fedora}}6 and a {{T23}} with PCLinuxOS 93a.<br />
<br />
When I purchased the A31 over 2 years ago getting a fully functional Thinkpad using an ATI vid card in Linux was over my head. Not that I've become an expert by any means, but I feel confident I can get the T42P working for personal and work use. <br />
When I assumed the position...hehe...I have at work 1 1/2 years ago I chose to provide my own PC rather than use what was offered (D*ll! pos!) So the A31 migrated from personal desktop replacement (DTR) to my work DTR. Since then that's where it's been, not mobile and running a custom WinXP.<br />
Now after settling into the job (Net Admin f/ISP) and deciding to stay for a while, I find I need Internet and network access from 3 different locations as well as to have a light, small, long-lived PC for field work. I used to use the T23 for field work, but it's no lightweight. Now I'm using the X22 and am very, very happy with it. I plan to upgrade it next to an {{X31}} or {{X40}}. For the 3 different locations (Office, Apt, Home) I had 3 different PCs and OSs! Now I'm planning to carry the T42p, it being w/o battery almost 3 lbs lighter than the A31p, between Homes and Office and the X22 will remain in my field pack for onsite work.<br />
<br />
Circumstances, I sold the A31 and haven't received the T42 yet, cause me to use the T23 temporarily as my desktop. Also, when I get the T42 I'll have to slam XP onto it and get back to work, because the T23 can't handle some of the app's I use. Also I still need to figure out Kivio and Google Earth Pro in Linux to replace Visio and TopoUSA in Winderz. Until I do that and migrate all of my proprietary files, I can't go Linux at work.<br />
<br />
Since I'll be using the T42 for personal as well as work use, I'll be dual-booting by day 2. My current favorite personal desktop distro is PCLinuxOS 93a and I'll be trying that first to see how it likes the T42.<br />
<br />
I'll be back @ 7/07 to submit the initial installation notes.<br />
<br />
06-24-2007 - Installed PCLinuxOS 2007 after using the LiveCD for an evening. The install has a few quirks that need attention for full laptop functionality.<br />
<br />
First thing is to get cpufreq working, because mine was running full-speed all the time. Temps were @ 60c until I added an Antec cooling pad, which reduced temps to @ 52c. After config of cpufreq, about 15 min ago, my cpu temp is @ 48c. Hopefully a good cleaning and some Artic Silver will drop the temps some more.<br />
<br />
10-02-1007 edit:<br />
The cpufreq info below needs an edit, because I disabled the script and have gotten better functionality with KCC and the Laptop module config. After trying a number of different BIOS, ACPI, Power/Battery settings I managed a fully functional ACPI with Suspend to RAM and CPU Throttling working very well<br />
<br />
The cpufreq script is located at /etc/sysconfig/cpufreq on my machine.<br />
I added the min_freq and max_freq values, the rest are default entries.<br />
<br />
#uncomment to set cpufreq governor after module load<br />
#possible choices are ondemand powersave userspace performance<br />
GOVERNOR=ondemand<br />
#minimum frequency<br />
MIN_FREQ=600<br />
#maximum frequency<br />
MAX_FREQ=1600<br />
#Uncomment to use acpi-cpufrq as fallback<br />
#USE_ACPI_CPUFREQ=yes<br />
<br />
I found quite a bit of discussion regarding cpufreq previously and will have to search for it again. I may edit the above accordingly. <br />
And, I'll edit this whole mess and make it a standard wiki page when I get back from vacation.<br />
<br />
9/11/07 - A tardy update...like with the T23 and PCLinuxOS 93, I stumbled on a working config after initially having serious problems with the install. And unfortunately like the T23 install, I didn't keep track of what worked and what didn't. In both cases I thought I would have to re-install and possibly even with another Linux distro. And in both cases I ended up with a very functional, albeit relatively slow, virtually bug-free and enjoyable OS.<br />
<br />
Of the numerous Linux distros I've used over the last few years PCLinuOS continues to surprise and satisfy me. I'm actually using it full-time for work and personal use, have a mash up of our DB and Google Earth working and only boot Winderz to edit existing network diagrams with Visio and run a couple of other proprietary apps.<br />
<br />
For now I'll list my current HW config and summarize the OS config...next....<br />
<br />
Hardware:<br />
<br />
T42P 2379-DYU<br />
1.8GHz Centrino<br />
Fire-GL 128MB, etc.<br />
Seagate 80GB, 7200RPM<br />
2x1GB Samsung PC2700 RAM<br />
and 2xPort Replicator II</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_notes_ca.2007&diff=33065Installation notes ca.20072007-09-12T04:15:06Z<p>Mahto: update</p>
<hr />
<div>notes:<br />
<br />
6/07 I'm upgrading from {{A31p}} to {{T42p}} and am going to document Linux installs. I previously had an {{A30}} which was very nix friendly, but the A31p was another story altogether. I also have an {{X22}} with {{Fedora}}6 and a {{T23}} with PCLinuxOS 93a.<br />
<br />
When I purchased the A31 over 2 years ago getting a fully functional Thinkpad using an ATI vid card in Linux was over my head. Not that I've become an expert by any means, but I feel confident I can get the T42P working for personal and work use. <br />
When I assumed the position...hehe...I have at work 1 1/2 years ago I chose to provide my own PC rather than use what was offered (D*ll! pos!) So the A31 migrated from personal desktop replacement (DTR) to my work DTR. Since then that's where it's been, not mobile and running a custom WinXP.<br />
Now after settling into the job (Net Admin f/ISP) and deciding to stay for a while, I find I need Internet and network access from 3 different locations as well as to have a light, small, long-lived PC for field work. I used to use the T23 for field work, but it's no lightweight. Now I'm using the X22 and am very, very happy with it. I plan to upgrade it next to an {{X31}} or {{X40}}. For the 3 different locations (Office, Apt, Home) I had 3 different PCs and OSs! Now I'm planning to carry the T42p, it being w/o battery almost 3 lbs lighter than the A31p, between Homes and Office and the X22 will remain in my field pack for onsite work.<br />
<br />
Circumstances, I sold the A31 and haven't received the T42 yet, cause me to use the T23 temporarily as my desktop. Also, when I get the T42 I'll have to slam XP onto it and get back to work, because the T23 can't handle some of the app's I use. Also I still need to figure out Kisio and Google Earth Pro in Linux to replace Visio and TopoUSA in Winderz. Until I do that and migrate all of my proprietary files, I can't go Linux at work.<br />
<br />
Since I'll be using the T42 for personal as well as work use, I'll be dual-booting by day 2. My current favorite personal desktop distro is PCLinuxOS 93a and I'll be trying that first to see how it likes the T42.<br />
<br />
I'll be back @ 7/07 to submit the initial installation notes.<br />
<br />
06-24-2007 - Installed PCLinuxOS 2007 after using the LiveCD for an evening. The install has a few quirks that need attention for full laptop functionality.<br />
<br />
First thing is to get cpufreq working, because mine was running full-speed all the time. Temps were @ 60c until I added an Antec cooling pad, which reduced temps to @ 52c. After config of cpufreq, about 15 min ago, my cpu temp is @ 48c. Hopefully a good cleaning and some Artic Silver will drop the temps some more.<br />
<br />
The cpufreq script is located at /etc/sysconfig/cpufreq on my machine.<br />
I added the min_freq and max_freq values, the rest are default entries.<br />
<br />
#uncomment to set cpufreq governor after module load<br />
#possible choices are ondemand powersave userspace performance<br />
GOVERNOR=ondemand<br />
#minimum frequency<br />
MIN_FREQ=600<br />
#maximum frequency<br />
MAX_FREQ=1600<br />
#Uncomment to use acpi-cpufrq as fallback<br />
#USE_ACPI_CPUFREQ=yes<br />
<br />
I found quite a bit of discussion regarding cpufreq previously and will have to search for it again. I may edit the above accordingly. <br />
And, I'll edit this whole mess and make it a standard wiki page when I get back from vacation.<br />
<br />
9/11/07 - A tardy update...like with the T23 and PCLinuxOS 93, I stumbled on a working config after initially having serious problems with the install. And unfortunately like the T23 install, I didn't keep track of what worked and what didn't. In both cases I thought I would have to re-install and possibly even with another Linux distro. And in both cases I ended up with a very functional, albeit relatively slow, virtually bug-free and enjoyable OS.<br />
<br />
Of the numerous Linux distros I've used over the last few years PCLinuOS continues to surprise and satisfy me. I'm actually using it full-time for work and personal use, have a mash up of our DB and Google Earth working and only boot Winderz to edit existing network diagrams with Visio and run a couple of other proprietary apps.<br />
<br />
For now I'll list my current HW config and summarize the OS config...next....</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_notes_ca.2007&diff=33064Installation notes ca.20072007-09-12T04:13:06Z<p>Mahto: </p>
<hr />
<div>notes:<br />
<br />
6/07 I'm upgrading from {{A31p}} to {{T42p}} and am going to document Linux installs. I previously had an {{A30}} which was very nix friendly, but the A31p was another story altogether. I also have an {{X22}} with {{Fedora}}6 and a {{T23}} with PCLinuxOS 93a.<br />
<br />
When I purchased the A31 over 2 years ago getting a fully functional Thinkpad using an ATI vid card in Linux was over my head. Not that I've become an expert by any means, but I feel confident I can get the T42P working for personal and work use. <br />
When I assumed the position...hehe...I have at work 1 1/2 years ago I chose to provide my own PC rather than use what was offered (D*ll! pos!) So the A31 migrated from personal desktop replacement (DTR) to my work DTR. Since then that's where it's been, not mobile and running a custom WinXP.<br />
Now after settling into the job (Net Admin f/ISP) and deciding to stay for a while, I find I need Internet and network access from 3 different locations as well as to have a light, small, long-lived PC for field work. I used to use the T23 for field work, but it's no lightweight. Now I'm using the X22 and am very, very happy with it. I plan to upgrade it next to an {{X31}} or {{X40}}. For the 3 different locations (Office, Apt, Home) I had 3 different PCs and OSs! Now I'm planning to carry the T42p, it being w/o battery almost 3 lbs lighter than the A31p, between Homes and Office and the X22 will remain in my field pack for onsite work.<br />
<br />
Circumstances, I sold the A31 and haven't received the T42 yet, cause me to use the T23 temporarily as my desktop. Also, when I get the T42 I'll have to slam XP onto it and get back to work, because the T23 can't handle some of the app's I use. Also I still need to figure out Kisio and Google Earth Pro in Linux to replace Visio and TopoUSA in Winderz. Until I do that and migrate all of my proprietary files, I can't go Linux at work.<br />
<br />
Since I'll be using the T42 for personal as well as work use, I'll be dual-booting by day 2. My current favorite personal desktop distro is PCLinuxOS 93a and I'll be trying that first to see how it likes the T42.<br />
<br />
I'll be back @ 7/07 to submit the initial installation notes.<br />
<br />
06-24-2007 - Installed PCLinuxOS 2007 after using the LiveCD for an evening. The install has a few quirks that need attention for full laptop functionality.<br />
<br />
First thing is to get cpufreq working, because mine was running full-speed all the time. Temps were @ 60c until I added an Antec cooling pad, which reduced temps to @ 52c. After config of cpufreq, about 15 min ago, my cpu temp is @ 48c. Hopefully a good cleaning and some Artic Silver will drop the temps some more.<br />
<br />
The cpufreq script is located at /etc/sysconfig/cpufreq on my machine.<br />
I added the min_freq and max_freq values, the rest are default entries.<br />
<br />
#uncomment to set cpufreq governor after module load<br />
#possible choices are ondemand powersave userspace performance<br />
GOVERNOR=ondemand<br />
#minimum frequency<br />
MIN_FREQ=600<br />
#maximum frequency<br />
MAX_FREQ=1600<br />
#Uncomment to use acpi-cpufrq as fallback<br />
#USE_ACPI_CPUFREQ=yes<br />
<br />
I found quite a bit of discussion regarding cpufreq previously and will have to search for it again. I may edit the above accordingly. <br />
And, I'll edit this whole mess and make it a standard wiki page when I get back from vacation.<br />
<br />
9/11/07 - A tardy update...like with the T23 and PCLinuxOS 93, I stumbled on a working config after initially having serious problems with the install. And unfortunately like the T23 install, I didn't keep track of what worked and what didn't. In both cases I thought I would have to re-install and possibly even with another Linux distro. And in both cases I ended up with a very functional, albeit relatively slow, virtually bug-free and enjoyable OS.<br />
<br />
Of the numerous Linux distros I've used oner the last few years PCLinuOS continues to surprise and satisfy me. I'm actually using it full-time for work and personal use, have a mash up of our DB and Google Earth working and only boot Winderz to edit existing network diagrams with Visio and run a couple of other proprietary apps.<br />
<br />
For now I'll list my current HW config and summarize the OS config...next....</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Category:T42p&diff=32576Category:T42p2007-08-27T11:41:25Z<p>Mahto: /* ThinkPad T42p */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top" |<br />
[[image:ThinkPadT40.jpg|ThinkPad T42p]]<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== ThinkPad T42p ===<br />
This pages gives an overview of all ThinkPad T42p related topics.<br />
<br />
Machine Type: 2373, 2374, 2378. 2379<br />
==== Standard Features ====<br />
* [[Intel Pentium M (Dothan)]] 1.7, 1.8, 2.0 or 2.1GHz CPU<br />
* [[ATI Mobility FireGL T2]] with 128MB or<br />
* [[ATI Mobility Radeon 9600]] with 64MB<br />
** 14.1" TFT display with 1400x1050 resolution<br />
** 15.0" TFT display with 1600x1200 resolution<br />
* 512MB or 1GB [[PC2700]] memory standard<br />
* 60 or 80GB HDD<br />
* [[AD1981B]] AC'97 Audio controller<br />
* Intel 10/100/1000 Ethernet<br />
* [[UltraBay|UltraBay Slim]] with one of the following:<br />
** DVD-ROM/CD-RW Combo<br />
** DVD-RW<br />
* [[CDC slot]] with one of the following:<br />
** [[IBM Integrated 56K Modem (MDC-2)]]<br />
** [[IBM Integrated Bluetooth III with 56K Modem (BMDC-2)]]<br />
* [[MiniPCI slot]] with one of the following:<br />
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]<br />
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]<br />
** [[Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter]]<br />
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]<br />
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]<br />
* (2) Type II [[CardBus slot|CardBus slots]] or (1) type III<br />
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]<br />
* [[Active Protection System|IBM Active Protection System]]<br />
* [[Integrated Fingerprint Reader]] on select systems<br />
</div><br />
|}<br />
<br />
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/13n6243.pdf ThinkPad T40/p, T41/p, T42, T42p - Hardware Maintenance Manual (April 2004)] (5,391,719 Bytes)<br />
<br />
[[Category:T Series]]</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_notes_ca.2007&diff=30672Installation notes ca.20072007-06-25T04:58:37Z<p>Mahto: 1st edit</p>
<hr />
<div>notes:<br />
<br />
6/07 I'm upgrading from {{A31p}} to {{T42p}} and am going to document Linux installs. I previously had an {{A30}} which was very nix friendly, but the A31p was another story altogether. I also have an {{X22}} with {{Fedora}}6 and a {{T23}} with PCLinuxOS 93a.<br />
<br />
When I purchased the A31 over 2 years ago getting a fully functional Thinkpad using an ATI vid card in Linux was over my head. Not that I've become an expert by any means, but I feel confident I can get the T42P working for personal and work use. <br />
When I assumed the position...hehe...I have at work 1 1/2 years ago I chose to provide my own PC rather than use what was offered (D*ll! pos!) So the A31 migrated from personal desktop replacement (DTR) to my work DTR. Since then that's where it's been, not mobile and running a custom WinXP.<br />
Now after settling into the job (Net Admin f/ISP) and deciding to stay for a while, I find I need Internet and network access from 3 different locations as well as to have a light, small, long-lived PC for field work. I used to use the T23 for field work, but it's no lightweight. Now I'm using the X22 and am very, very happy with it. I plan to upgrade it next to an {{X31}} or {{X40}}. For the 3 different locations (Office, Apt, Home) I had 3 different PCs and OSs! Now I'm planning to carry the T42p, it being w/o battery almost 3 lbs lighter than the A31p, between Homes and Office and the X22 will remain in my field pack for onsite work.<br />
<br />
Circumstances, I sold the A31 and haven't received the T42 yet, cause me to use the T23 temporarily as my desktop. Also, when I get the T42 I'll have to slam XP onto it and get back to work, because the T23 can't handle some of the app's I use. Also I still need to figure out Kisio and Google Earth Pro in Linux to replace Visio and TopoUSA in Winderz. Until I do that and migrate all of my proprietary files, I can't go Linux at work.<br />
<br />
Since I'll be using the T42 for personal as well as work use, I'll be dual-booting by day 2. My current favorite personal desktop distro is PCLinuxOS 93a and I'll be trying that first to see how it likes the T42.<br />
<br />
I'll be back @ 7/07 to submit the initial installation notes.<br />
<br />
06-24-2007 - Installed PCLinuxOS 2007 after using the LiveCD for an evening. The install has a few quirks that need attention for full laptop functionality.<br />
<br />
First thing is to get cpufreq working, because mine was running full-speed all the time. Temps were @ 60c until I added an Antec cooling pad, which reduced temps to @ 52c. After config of cpufreq, about 15 min ago, my cpu temp is @ 48c. Hopefully a good cleaning and some Artic Silver will drop the temps some more.<br />
<br />
The cpufreq script is located at /etc/sysconfig/cpufreq on my machine.<br />
I added the min_freq and max_freq values, the rest are default entries.<br />
<br />
#uncomment to set cpufreq governor after module load<br />
#possible choices are ondemand powersave userspace performance<br />
GOVERNOR=ondemand<br />
#minimum frequency<br />
MIN_FREQ=600<br />
#maximum frequency<br />
MAX_FREQ=1600<br />
#Uncomment to use acpi-cpufrq as fallback<br />
#USE_ACPI_CPUFREQ=yes<br />
<br />
I found quite a bit of discussion regarding cpufreq previously and will have to search for it again. I may edit the above accordingly. <br />
And, I'll edit this whole mess and make it a standard wiki page when I get back from vacation.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_notes_ca.2007&diff=30529Installation notes ca.20072007-06-17T19:20:31Z<p>Mahto: </p>
<hr />
<div>notes:<br />
<br />
6/07 I'm upgrading from {{A31p}} to {{T42p}} and am going to document Linux installs. I previously had an {{A30}} which was very nix friendly, but the A31p was another story altogether. I also have an {{X22}} with {{Fedora}}6 and a {{T23}} with PCLinuxOS 93a.<br />
<br />
When I purchased the A31 over 2 years ago getting a fully functional Thinkpad using an ATI vid card in Linux was over my head. Not that I've become an expert by any means, but I feel confident I can get the T42P working for personal and work use. <br />
When I assumed the position...hehe...I have at work 1 1/2 years ago I chose to provide my own PC rather than use what was offered (D*ll! pos!) So the A31 migrated from personal desktop replacement (DTR) to my work DTR. Since then that's where it's been, not mobile and running a custom WinXP.<br />
Now after settling into the job (Net Admin f/ISP) and deciding to stay for a while, I find I need Internet and network access from 3 different locations as well as to have a light, small, long-lived PC for field work. I used to use the T23 for field work, but it's no lightweight. Now I'm using the X22 and am very, very happy with it. I plan to upgrade it next to an {{X31}} or {{X40}}. For the 3 different locations (Office, Apt, Home) I had 3 different PCs and OSs! Now I'm planning to carry the T42p, it being w/o battery almost 3 lbs lighter than the A31p, between Homes and Office and the X22 will remain in my field pack for onsite work.<br />
<br />
Circumstances, I sold the A31 and haven't received the T42 yet, cause me to use the T23 temporarily as my desktop. Also, when I get the T42 I'll have to slam XP onto it and get back to work, because the T23 can't handle some of the app's I use. Also I still need to figure out Kisio and Google Earth Pro in Linux to replace Visio and TopoUSA in Winderz. Until I do that and migrate all of my proprietary files, I can't go Linux at work.<br />
<br />
Since I'll be using the T42 for personal as well as work use, I'll be dual-booting by day 2. My current favorite personal desktop distro is PCLinuxOS 93a and I'll be trying that first to see how it likes the T42.<br />
<br />
I'll be back @ 7/07 to submit the initial installation notes.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_notes_ca.2007&diff=30528Installation notes ca.20072007-06-17T19:19:46Z<p>Mahto: â†Created page with 'notes: 6/07 I'm upgrading from {{A31p}} to {{T42p}} and am going to document Linux installs. I previously had an {{A30}} which was very nix friendly, but the A31p was ano...'</p>
<hr />
<div>notes:<br />
<br />
6/07 I'm upgrading from {{A31p}} to {{T42p}} and am going to document Linux installs. I previously had an {{A30}} which was very nix friendly, but the A31p was another story altogether. I also have an {{X22}} with {{Fedora Core}}6 and a {{T23}} with PCLinuxOS 93a.<br />
<br />
When I purchased the A31 over 2 years ago getting a fully functional Thinkpad using an ATI vid card in Linux was over my head. Not that I've become an expert by any means, but I feel confident I can get the T42P working for personal and work use. <br />
When I assumed the position...hehe...I have at work 1 1/2 years ago I chose to provide my own PC rather than use what was offered (D*ll! pos!) So the A31 migrated from personal desktop replacement (DTR) to my work DTR. Since then that's where it's been, not mobile and running a custom WinXP.<br />
Now after settling into the job (Net Admin f/ISP) and deciding to stay for a while, I find I need Internet and network access from 3 different locations as well as to have a light, small, long-lived PC for field work. I used to use the T23 for field work, but it's no lightweight. Now I'm using the X22 and am very, very happy with it. I plan to upgrade it next to an {{X31}} or {{X40}}. For the 3 different locations (Office, Apt, Home) I had 3 different PCs and OSs! Now I'm planning to carry the T42p, it being w/o battery almost 3 lbs lighter than the A31p, between Homes and Office and the X22 will remain in my field pack for onsite work.<br />
<br />
Circumstances, I sold the A31 and haven't received the T42 yet, cause me to use the T23 temporarily as my desktop. Also, when I get the T42 I'll have to slam XP onto it and get back to work, because the T23 can't handle some of the app's I use. Also I still need to figure out Kisio and Google Earth Pro in Linux to replace Visio and TopoUSA in Winderz. Until I do that and migrate all of my proprietary files, I can't go Linux at work.<br />
<br />
Since I'll be using the T42 for personal as well as work use, I'll be dual-booting by day 2. My current favorite personal desktop distro is PCLinuxOS 93a and I'll be trying that first to see how it likes the T42.<br />
<br />
I'll be back @ 7/07 to submit the initial installation notes.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T42p&diff=30527Installation instructions for the ThinkPad T42p2007-06-17T18:16:08Z<p>Mahto: /* General Notes */</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T42p}}.<br />
<br />
==General Notes==<br />
[[Installation notes ca.2007]]<br />
<br />
==Distro specific Instructions==<br />
*{{Install|Debian|/Sid|T42p}}<br />
*{{Install|Fedora| Core 4|T42p (2373-HBU)}}<br />
<br />
==External Sources==</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T42p&diff=30525Installation instructions for the ThinkPad T42p2007-06-17T17:51:42Z<p>Mahto: /* General Notes */</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T42p}}.<br />
<br />
==General Notes==<br />
<br />
==Distro specific Instructions==<br />
*{{Install|Debian|/Sid|T42p}}<br />
*{{Install|Fedora| Core 4|T42p (2373-HBU)}}<br />
<br />
==External Sources==</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Template:Linux_on_T42P&diff=30524Template:Linux on T42P2007-06-17T17:49:55Z<p>Mahto: editing</p>
<hr />
<div>notes:<br />
<br />
6/07 I'm upgrading from A31p to T42p and going to document Linux installs. I previously had an A30 which was very nix friendly, but the A31P was another story altogether. I also have an X22 with Fedora Core6 and a T23 with PCLinuxOS 93a.<br />
<br />
When I purchased the A31P over 2 years ago getting a fully functional Thinkpad using an ATI vid card in Linux was over my head. Not that I've become an expert by any means, but I feel confident I can get the T42P working for personal and work use.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T42p&diff=30523Installation instructions for the ThinkPad T42p2007-06-17T17:49:27Z<p>Mahto: /* General Notes */</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T42p}}.<br />
<br />
==General Notes==<br />
{{Linux on T42P}}<br />
<br />
==Distro specific Instructions==<br />
*{{Install|Debian|/Sid|T42p}}<br />
*{{Install|Fedora| Core 4|T42p (2373-HBU)}}<br />
<br />
==External Sources==</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T42p&diff=30521Installation instructions for the ThinkPad T42p2007-06-17T17:30:04Z<p>Mahto: /* General Notes */</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T42p}}.<br />
<br />
==General Notes==<br />
{{Installation Linux on T42P}}<br />
<br />
==Distro specific Instructions==<br />
*{{Install|Debian|/Sid|T42p}}<br />
*{{Install|Fedora| Core 4|T42p (2373-HBU)}}<br />
<br />
==External Sources==</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T42p&diff=30520Installation instructions for the ThinkPad T42p2007-06-17T17:28:45Z<p>Mahto: /* General Notes */</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T42p}}.<br />
<br />
==General Notes==<br />
{{Install|Linux on T42P}}<br />
<br />
==Distro specific Instructions==<br />
*{{Install|Debian|/Sid|T42p}}<br />
*{{Install|Fedora| Core 4|T42p (2373-HBU)}}<br />
<br />
==External Sources==</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T42p&diff=30519Installation instructions for the ThinkPad T42p2007-06-17T17:27:46Z<p>Mahto: /* General Notes */</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T42p}}.<br />
<br />
==General Notes==<br />
{{Install | Linux on T42P}}<br />
<br />
==Distro specific Instructions==<br />
*{{Install|Debian|/Sid|T42p}}<br />
*{{Install|Fedora| Core 4|T42p (2373-HBU)}}<br />
<br />
==External Sources==</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Template:PCLOS&diff=30517Template:PCLOS2007-06-17T14:21:26Z<p>Mahto: created</p>
<hr />
<div>As of this writing, [http://www.pclinuxos.com PCLinuxOS] is the one of the most popular Linux distro at [http://www.distrowatch.com Distrowatch] and is way ahead of Ubuntu for the last 30 days. The current release is 2007, but the release that helped popularize the distro was 93a.<br />
Release 93a was offered as 3 different versions: the standard live CD; a mini ISO of @200MB; and "Big Daddy". All versions are Live CDs which can be easily installed and produce a working KDE desktop. PCLOS is considered to be very user friendly and is very well suited to personal desktop use.<br />
<br />
...more later<br />
<br />
[http://www.example.com link title]</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Installation_instructions_for_the_ThinkPad_T42p&diff=30512Installation instructions for the ThinkPad T42p2007-06-17T05:23:58Z<p>Mahto: /* General Notes */</p>
<hr />
<div>Specific installation notes for the ThinkPad {{T42p}}.<br />
<br />
==General Notes==<br />
{{Installation Linux on T42P}}<br />
<br />
==Distro specific Instructions==<br />
*{{Install|Debian|/Sid|T42p}}<br />
*{{Install|Fedora| Core 4|T42p (2373-HBU)}}<br />
<br />
==External Sources==</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Madwifi&diff=26595Madwifi2006-11-27T01:24:13Z<p>Mahto: /* Problems with system-config-network and Fedora Core 5 */</p>
<hr />
<div>== Multiband Atheros Driver for WiFi ==<br />
Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.<br />
<br />
The following adapters sold by IBM use the Atheros chips:<br />
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]<br />
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]<br />
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]<br />
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]<br />
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]<br />
* IBM 802.11a Wireless LAN Cardbus Adapter<br />
* IBM 11 a/b/g Wireless Cardbus Adapter<br />
<br />
=== Project Homepage ===<br />
http://www.madwifi.org (old page: http://sourceforge.net/projects/madwifi)<br />
<br />
=== Packages ===<br />
*Official {{Debian}} packages in the [http://packages.debian.org/src:madwifi non-free section]. See also the [http://alioth.debian.org/projects/pkg-madwifi/ Alioth project page] and the [http://madwifi.org/wiki/UserDocs/Distro/Debian Madwifi wiki].<br />
*{{Debian}} Packages: http://www.marlow.dk/site.php/tech/madwifi<br />
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/misc/madwiki.txt<br />
*{{Fedora}} Packages(1): http://rpm.livna.org<br />
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/<br />
*{{Gentoo}} ebuild: {{cmduser|emerge net-wireless/madwifi-driver net-wireless/madwifi-tools}}<br />
*{{SUSE}} Packages http://www.madwifi.org/suse/<br />
*{{Ubuntu}} Package: {{cmduser|sudo apt-get install linux-restricted-modules-`uname -r`}}<br />
*[http://madwifi.org/wiki/UserDocs/GettingMadwifi MadWifi packages and source] for these and other distributions<br />
<br />
=== Source ===<br />
<br />
Detailed instructions can be found [http://madwifi.org/wiki/UserDocs/GettingMadwifi on the MadWiFi Wiki].<br />
<br />
* Daily snapshots: http://snapshots.madwifi.org/<br />
* madwifi-ng:<br />
:{{cmduser|svn checkout http://svn.madwifi.org/trunk madwifi-ng}}<br />
* madwifi-old:<br />
:{{cmduser|svn checkout http://svn.madwifi.org/branches/madwifi-old madwifi-old}}<br />
<br />
<br />
=== Installation ===<br />
<br />
*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install<br />
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by<br />
:{{cmduser|iwconfig --version}}<br />
<br />
Setting up [[wpa_supplicant]] with wpa-psk.<br />
<br />
You can enable the wireless LAN status LED on your Thinkpad by following [http://madwifi.org/wiki/UserDocs/EnableLEDs these instructions] (tested on Thinkpad x60s).<br />
<br />
=== Status ===<br />
in development, usable<br />
<br />
=== OpenSource HAL ===<br />
The "official" driver consists of an opensource wrapper with binary HAL (Hardware Abstraction Layer). This HAL is not a binary firmware like with the Intel Wireless chips, but a piece of code that needs to runs in the Linux kernel.<br />
The vendors reasoning behind this is, that since the Atheros chip could be tuned to any frequency, and hence interfere with systems operating in those frequencies, that we simply need to accept this binary module.<br><br />
Obviously this binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel.<br><br />
Some OpenBSD developers facing the same issue, reverse engineered the binary HAL and have produced an OpenSource version. Hopefully a driver based on this might be included with the Linux kernel at some point in time, and picked up by the mainstream distributions.<br />
<br />
=== Problems with system-config-network and Fedora Core 5 ===<br />
If you use the livna repository to install madwifi for Fedora Core 5, it doesn't correctly update the modprobe configuration files. A [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187640 bug] has been filed. The quick fix is to move the lines that were in<br />
/etc/modprobe.d/madwifi into /etc/modprobe.conf and system-config-network now can configure the card.<br />
<br />
=== Much easier on Fedora Core 6 ===<br />
<br />
I'm using FC6 w/KDE on an X22 and wireless was very easy using madwifi from Livna and a Linksys WPC55AG PC card.<br />
I had already installed knetworkmanager, klaptop and configured working radeonfb and <br />
working S3 suspend.<br />
I then simply used yum to install madwifi, including a kernel upgrade, enabled the knetworkmanager services and rebooted.<br />
After restarting, knetworkmanager found the Atheros card and my AP. I just had to choose the connection and was online in seconds.<br />
<br />
===Using Madwifi with SUSE Linux 10.1===<br />
As of [[Category:SUSE SUSE Linux]] 10.1, the Madwifi packages are no longer included in the SUSE distribution because of the presence of closed source code. However, I was able to download, install, and configure Madwifi for my [[:Category:T40|IBM T40]] with the <br />
[[IBM 11a/b/g Wireless LAN Mini PCI Adapter|IBM 11a/b/g Wireless Adapter (Atheros AR5212 802.11abg)]] as follows:<br />
* Start yast2 and select Software--Installation Source. Add http://madwifi.org/suse/ as a source<br />
* Install packages <tt>madwifi</tt> and <tt>madwifi-kmp-default</tt> (the latter has the kernel module, replace <tt>default</tt> with <tt>smp</tt> or other non-default kernel package if you're not running the default Suse kernel package as determined by <tt>uname -r</tt>)<br />
* Reboot so the kernel modules can be loaded.<br />
* Load the kernel modules by hand and see if the kernel recognizes your hardware:<br />
<tt>modprobe aes; modprobe wlan_ccmp; modprobe ath_pci; lsmod |egrep 'Module|aes|wlan|ath'</tt><br />
* If recognized, put the modprobe lines above in your <tt>/etc/init.d/boot.local</tt> file. Otherwise, check for Linux kernel/Madwifi incompatibilities and hardware issues.<br />
* Start yast2 and go to Network Devices-->Network Card and add and configure your wireless card. I recommmend checking the "Network Manager" box, as that allows dynamic GUI control over the wireless and Ethernet NICs.<br />
* I have WPA-PSK enabled, so here's the fields I filled out: "User Controlled" device activation, DHCP Automatic Address Setup, "Managed" operating mode, "any" ESSID, "WPA-PSK" auth mode, key input type "passphrase" and I typed in my passphrase. I left expert settings alone.<br />
<br />
=== Related links === <br />
* [http://www.madwifi.org/wiki MadWiFi Wiki]<br />
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]<br />
* [http://www.ath-driver.org/ OpenSource Atheros driver for Linux]<br />
<br />
[[Category:Drivers]]</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=IRQ_Interrupts&diff=26467IRQ Interrupts2006-11-18T04:37:26Z<p>Mahto: IRQ moved to IRQ Interrupts: accuracy</p>
<hr />
<div>On my T42p, the BIOS settings for IRQs were factory set to 11. Changing those settings from 11 to 'auto' fixed some lockup issues I was having with the wireless interface after a resume from suspend-to-ram.<br />
<br />
This is true and still accurate with FC 6, at least on my {{X22}}.<br />
By changing the BIOS settings for PCI IRQs from "11" to "Auto" I solved random lockups. <br />
*View /proc/interrupts for conflicts on IRQ 11.<br />
*Reboot to BIOS-Config-PCI and change all to "Auto.<br />
*Save and Reboot.<br />
<br />
S3 Suspend was already working for me.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=IRQ&diff=26468IRQ2006-11-18T04:37:26Z<p>Mahto: IRQ moved to IRQ Interrupts: accuracy</p>
<hr />
<div>#REDIRECT [[IRQ Interrupts]]</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=IRQ_Interrupts&diff=26466IRQ Interrupts2006-11-18T04:35:40Z<p>Mahto: </p>
<hr />
<div>On my T42p, the BIOS settings for IRQs were factory set to 11. Changing those settings from 11 to 'auto' fixed some lockup issues I was having with the wireless interface after a resume from suspend-to-ram.<br />
<br />
This is true and still accurate with FC 6, at least on my {{X22}}.<br />
By changing the BIOS settings for PCI IRQs from "11" to "Auto" I solved random lockups. <br />
*View /proc/interrupts for conflicts on IRQ 11.<br />
*Reboot to BIOS-Config-PCI and change all to "Auto.<br />
*Save and Reboot.<br />
<br />
S3 Suspend was already working for me.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=IRQ_Interrupts&diff=26465IRQ Interrupts2006-11-18T04:27:42Z<p>Mahto: </p>
<hr />
<div>On my T42p, the BIOS settings for IRQs were factory set to 11. Changing those settings from 11 to 'auto' fixed some lockup issues I was having with the wireless interface after a resume from suspend-to-ram.<br />
<br />
This is true and still accurate with FC6, at least on my X22.<br />
By changing the BIOS settings for PCI IRQs from "11" to "Auto" I solved random lockups. <br />
*View /proc/interrupts for conflicts on IRQ 11.<br />
*Reboot to BIOS-Config-PCI and change all to "Auto.<br />
*Save and Reboot.<br />
<br />
S3 Suspend was already working for me.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Problem_with_high_power_drain_in_ACPI_sleep&diff=26386Problem with high power drain in ACPI sleep2006-11-13T05:14:16Z<p>Mahto: /* including radeonfb into your initrd */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
==Problem description==<br />
Several people realized that their ThinkPads eat up too much power while suspended to ram via ACPI. Compared to APM suspend to ram the power drain is experienced to be about 10 times as high, 2-5 Watts. This empties the battery within one or two days.<br />
|}<br />
<br />
==Affected Models==<br />
{| border="1" cellspacing="0" cellpadding="2" style="float:right;margin-left:20px;"<br />
|-<br />
! style="vertical-align:top;background-color:#ffcfbc;" | affected models<br />
! style="vertical-align:top;background-color:#cfefcf;" | unaffected models <br />
|-<br />
| style="vertical-align:top;background-color:#fff0e0;" |<br />
* {{R32}}<br />
** 2658-BQG<br />
* {{R40}}<br />
** 2722-3GG<br />
** 2722-5MG<br />
** 2722-B3G<br />
** 2722-CDG<br />
** 2897-GWU<br />
** 2722-6YU<br />
** 2722-CDG<br />
* {{R50}}<br />
** 1829-7RG<br />
** 1829-6DM<br />
** 1836-3SU<br />
* {{R51}}<br />
** 1829-9MG<br />
** 1829-EHG<br />
** 1829-R6G<br />
** 1830-DG4<br />
** 1836-Q6U<br />
* {{T23}}<br />
**2647-???<br />
* {{T30}}<br />
** 2366-81A<br />
** 2366-97U<br />
** 2366-FBU<br />
** 2366-96G<br />
*{{T40}}<br />
**2373-19G<br />
**2373-22G<br />
**2373-42G<br />
**2373-75G <br />
**2373-82U<br />
**2373-92U<br />
**2373-A1U<br />
**2373-MU3<br />
*{{T40p}}<br />
**2373-G1U <br />
**2373-G3U<br />
**2373-G3G<br />
**2373-G1G<br />
**2373-G5G<br />
* {{T41}}<br />
**2379-DJU<br />
**2373-3KG<br />
**2373-9HU<br />
**2373-4FG<br />
**2373-4PG<br />
**2373-1FG<br />
**2373-2FG<br />
**2373-2GG<br />
**2373-6U4<br />
**2373-7JU<br />
**2373-CY0<br />
**2373-TG5<br />
**2373-3HM<br />
**2373-4GU<br />
* {{T41p}}<br />
**2373-9FU<br />
* {{T42}}<br />
**2373-C19<br />
**2373-CTO<br />
**2378-DTU<br />
**2378-DUU<br />
**2378-XXE<br />
**2378-R4U<br />
**2373-FWG<br />
**2374-ZEP<br />
**2373-F2G<br />
**2373-JTU<br />
**2373-VUW<br />
**[[2373-6ZG]]<br />
* {{X21}}<br />
**2662-BSG<br />
* {{X32}}<br />
**2884-A3U<br />
*{{X41T}}<br />
** 1869-5CU<br />
| style="vertical-align:top;background-color:#e9f9e9;" |<br />
*[[:Category:A22m | A22m]]<br />
**2628<br />
*[[:Category:A31 | A31]]<br />
**2652-D5G<br />
*[[:Category:R50p | R50p]]<br />
*[[:Category:R52 | R52]]<br />
**1858-6MM<br />
*[[:Category:T41 | T41]]<br />
**2373-GEU<br />
*[[:Category:T41p | T41p]]<br />
**2373-GKG<br />
**2373-GGG<br />
**[[2373-GHG]]<br />
*[[:Category:T42 | T42]]<br />
**[[2373-M1G]]<br />
**[[2373-WBZ]]<br />
**[[2373-F7G]]<br />
**[[2378-DXU]]<br />
**[[2378-FVU]]<br />
**[[2378-RTU]]<br />
**[[2378-RRU]]<br />
*[[:Category:T42p | T42p]]<br />
**[[2373-HTG]]<br />
**[[2373-W6M]]<br />
**[[2373-GTG]]<br />
**[[2373-GXG]]<br />
**2373-KXM<br />
*[[:Category:T43 | T43]]<br />
**[[2668-W12]]<br />
*[[:Category:T43p | T43p]]<br />
**[[2668-G2G]]<br />
*[[:Category:X40 | X40]]<br />
**2371<br />
|}<br />
*Different symptoms have been reported for different models. In some models the origin of the power drain is obvious ([[Problem with LCD backlight remaining on during ACPI sleep|backlight on during suspend]]), in other models there is no obvious reason.<br />
<br />
*On some models/configurations the higher power drain couldn't even be realized or was at least significantly lower.<br />
<br />
*The T4x ThinkPad series and other Radeon based models suspend to ram just fine, and there are no components that are obviously left powered up. The [[UltraBay]] and network light is on, but that is the same under windows (but under APM sleep to RAM those lights are OFF). For these models the higher power drain is caused by a driver problem and can be fixed in software. Starting with linux 2.6.18 this fix is in the official kernel.<br />
<br />
The table on the right gives an overview of the models suffering from the mysterious power drain. To find out about your model, you may use the following [[ACPI sleep power drain test script | script]]. It creates a file {{path|/var/log/battery.log}} which will tell you if you are affected or not.<br />
<br />
==Affected Operating Systems==<br />
*Linux, all flavours.<br />
*Windows, for some models as well (only when using non-IBM drivers).<br />
*FreeBSD (on the A22M)<br />
<br />
==Radeon GPU not powered off==<br />
A frequent cause of the mysterious power drain is the Radeon GPU, which requires extra steps to suspend properly. We identified affected thinkpads, and [[radeonfb]] activates the workaround on those models automatically (starting with linux kernel 2.6.18).<br />
<br />
===Status===<br />
*The official bugzilla entry for the radeon suspend issue is in the [http://bugme.osdl.org/show_bug.cgi?id=3022 OSDL Bugzilla]. There you can find the above-mentioned patch for older kernel versions. The patch removes the CONFIG_PPC_PMAC condition for enabling D2 sleep in {{path|drivers/video/aty/radeon_pm.c}}. If you suspect that this patch makes things worse, you can disable it by the kernel parameter {{bootparm|video|radeonfb:ignore_devlist|1}}. Similarly, if the patch is not automatically activated on your notebook you can force it by {{bootparm|video|radeonfb:force_sleep|1}}. In case that improves your sleep, please leave a note in the bugzilla including the output of {{cmdroot|lspci -d "1002:*" -vn}}. See also [http://thread.gmane.org/gmane.linux.hardware.thinkpad/25355 the linux-thinkpad ML post requesting this information] for more information. <br />
<br />
*Most certainly, the DSDT is not at fault. (Interesting to note: The DSDT from BIOS 3.13 (Nov 04) for the T42p compiles without bugs.)<br />
<br />
===Solutions===<br />
You must use a recent (or patched) version of the [[radeonfb]] driver, even if you are only interested in using the X window system. The radeon frame buffer suspends the radeon chip correctly during ACPI sleep. Starting with linux 2.6.18, this patch is in the official (kernel.org) kernels.<br />
<br />
If the patch is known to work on your notebook, it is automatically enabled. If you think that your computer would profit from the patch as well, you can force it by including the module parameter {{bootparm|video|radeonfb:force_sleep|1}}. If it does not work this can result in system hangs.<br />
<br />
Alas, in many cases [[radeonfb]] cannot coexist with the [[radeon]] X.org driver (causing corrupted rendering and hangs). Using the <tt>Option "UseFBDev" "True"</tt> of [[radeon]] may help, but this is incompatible with [[radeon]]'s mergedfb mode. A "GPU device layer" architecture which may, one day, resolve this was proposed by Dave Airlie [http://airlied.livejournal.com/#item30632 here] and [http://lkml.org/lkml/2006/7/22/45 here].<br />
{{HELP|Is there ''any'' fully working solution?}}<br />
<br />
====Fedora Core====<br />
* Fedora Core 6: Ships with kernel >= 2.6.18, only needs initrd (see below).<br />
* Fedora Core 5: The latest kernel from updates (2.6.18-1.2200.fc5) seems to actually fix this issue, you only have to make custom initrd because the default one does not contain radeonfb.<br />
* Fedora Core 4: Fedora ships a patched radeon frame buffer (radeonfb.ko), but you must enable it yourself. {{Fedora}} compiles it as a module rather than including it in the kernel, therefore you cannot activate it at boot time without a custom initrd. You must arrange for the module to be loaded before X starts (for example, using an init script).<br />
* Fedora Core 3: this is also true for updated kernels (at least for kernel-2.6.12-1.1376_FC3) but '''not''' for the initially shipped version.<br />
<br />
====testing radeonfb without changing initrd====<br />
If you want to try the radeon frame buffer, you can enable it as follows:<br />
*First, switch to a console ({{key|Ctrl}}{{key|Alt}}{{key|F1}}) and log in as root.<br />
*Stop X: {{cmdroot|init 3}}<br />
*Now you can load the module: {{cmdroot|1=modprobe radeonfb force_sleep=1}}<br />
*Finally, resume X: {{cmdroot|init 5}}<br />
<br />
====Gentoo====<br />
After installing the patch on {{Gentoo}} (it works fine with gentoo-sources: {{cmdroot|cd /usr/src/linux/drivers/video/aty}}, and execute {{cmdroot|patch -p4 < <patchname>}}, then recompile the kernel), one needs to add {{bootparm|video|radeonfb:force_sleep}} to the kernel parameters.<br />
<br />
====including radeonfb into your initrd====<br />
As an alternative you can build your customized initrd. This is as simple as running<br />
:{{cmdroot|1=mkinitrd --with=radeonfb /boot/<name-of-your-new-initrd> `uname -r`}}<br />
and replacing the initrd in {{path|/boot/grub/grub.conf}} with your new one. You also need to add the kernel command line argument {{bootparm|video|2=radeonfb:force_sleep}}.<br />
<br />
With FC6 and KDE I had to:<br />
*Login as root<br />
*Enter the command as {{cmdroot|1=mkinitrd --with=radeonfb /boot/<name-of-your-new-initrd> <kernel version>}}<br />
:e.g. {{cmdroot|1=mkinitrd --with=radeonfb /boot/initrd-2.6.18-1.2798.fc6-my.img 2.6.18-1.2798.fc6}}<br />
:And the kernel command line argument was added to /etc/sysconfig/grub.<br />
<br />
==Backlight staying on==<br />
It is possible that [[radeontool]] will help some people if the backlight stays on.<br />
(simply run "radeontool light off" before suspend and "radeontool light on" after resume).<br />
A radeontool patch for freebsd is here: http://www.init-main.com/radeontool.patch (by Takanori Watanabe).<br />
<br />
===Notes for gnome-power-manager===<br />
If you suspend from Gnome and need to run radeontool to turn the backlight off you need to find the suspend script for HAL. In Ubuntu, the scripts are located in /usr/share/hal/scripts/. Add the following the script "hal-system-power-suspend":<br />
chvt 1<br />
radeontool light off<br />
And in the resume script ("restore-after-standby"):<br />
radeontool light on<br />
chvt 7<br />
<br />
This worked for me. YMMV. [[User:Etnoy|Etnoy]] 16:27, 9 November 2006 (CET)<br />
<br />
===For models without Radeon graphics===<br />
The Problem seems to be solved when you use the [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to turn the LCD off before suspending ...<br />
:{{cmdroot|vbetool dpms off}}<br />
and turning it on afterwards again...<br />
:{{cmdroot|vbetool dpms on}}<br />
You have to change to a normal console before turning the LCD off.<br />
Additionally you have to deactivate the Wake-On-Lan feature like mentioned above ...<br />
:{{cmdroot|ethtool -s eth0 wol d}}<br />
With these commands used together the "testing script" reports no high power drain while suspending.<br />
<br />
==Other problems causing the power drain==<br />
On my [[R51]] using Gentoo Linux, the high power drain was not caused by the graphics adaptor but by several components not powered down properly before putting the Thinkpad into S3.<br />
<br />
If the above did not help you, this might do:<br />
<br />
Walk through<br />
/sys/devices/*/*/power/state<br />
and try to disable each of it, every time checking the power drain. (See linux/Documentation/power/devices.txt for values to write into the state-files. 3 should be the value you want to try)<br />
Do the same for other components (Like the Ultrabay, etc.). Please add your experiences here.<br />
<br />
===R51: Ultrabay and networking===<br />
On my system, ultrabay and networking light were still on while in S3. So were the devices theirselves.<br />
echo -n eject > /proc/acpi/ibm/bay # Disable ultrabay<br />
ethtool -s eth0 wol d # Disable Wake-On-Lan (And so the eth-adaptor)<br />
echo mem > /sys/power/state # Sleep<br />
<br />
For me, this lowered the power drain from >700mW to 338 mW.<br />
<br />
===USB===<br />
My initial testing of a [[T43]] (2669-model) revealed no power drain issues. However, after several rounds of BIOS and kernel upgrades I have discovered that the power drain has risen to >700mWh. Having tested things a bit, I have discoved that removing ehci_hcd module solved the high power drain. This is a [[T43]] laptop, with kernel 2.6.17-r5 and BIOS 1.28/EC 1.06. For me, issuing {{cmdroot|modprobe -r ehci_hcd}} before going to sleep and reloading the module ({{cmdroot|modprobe ehci_hcd}}) after waking up dropped the power drain down to 277mWh in suspend2ram, which seems fair. The unloading/reloading can be put into the suitable ACPI script called to suspend the laptop.<br />
<br />
===Wake-on-LAN===<br />
Some additional power savings can be achieved by turning off the wake-on-lan ({{cmdroot|ethtool -s eth0 wol d}}). The power drain of the wol feature is far smaller than the radeon bug, but can be noticeable.</div>Mahtohttps://www.thinkwiki.org/w/index.php?title=Problem_with_high_power_drain_in_ACPI_sleep&diff=26385Problem with high power drain in ACPI sleep2006-11-13T05:07:34Z<p>Mahto: /* including radeonfb into your initrd */</p>
<hr />
<div>{| width="100%"<br />
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__<br />
|style="vertical-align:top" |<br />
==Problem description==<br />
Several people realized that their ThinkPads eat up too much power while suspended to ram via ACPI. Compared to APM suspend to ram the power drain is experienced to be about 10 times as high, 2-5 Watts. This empties the battery within one or two days.<br />
|}<br />
<br />
==Affected Models==<br />
{| border="1" cellspacing="0" cellpadding="2" style="float:right;margin-left:20px;"<br />
|-<br />
! style="vertical-align:top;background-color:#ffcfbc;" | affected models<br />
! style="vertical-align:top;background-color:#cfefcf;" | unaffected models <br />
|-<br />
| style="vertical-align:top;background-color:#fff0e0;" |<br />
* {{R32}}<br />
** 2658-BQG<br />
* {{R40}}<br />
** 2722-3GG<br />
** 2722-5MG<br />
** 2722-B3G<br />
** 2722-CDG<br />
** 2897-GWU<br />
** 2722-6YU<br />
** 2722-CDG<br />
* {{R50}}<br />
** 1829-7RG<br />
** 1829-6DM<br />
** 1836-3SU<br />
* {{R51}}<br />
** 1829-9MG<br />
** 1829-EHG<br />
** 1829-R6G<br />
** 1830-DG4<br />
** 1836-Q6U<br />
* {{T23}}<br />
**2647-???<br />
* {{T30}}<br />
** 2366-81A<br />
** 2366-97U<br />
** 2366-FBU<br />
** 2366-96G<br />
*{{T40}}<br />
**2373-19G<br />
**2373-22G<br />
**2373-42G<br />
**2373-75G <br />
**2373-82U<br />
**2373-92U<br />
**2373-A1U<br />
**2373-MU3<br />
*{{T40p}}<br />
**2373-G1U <br />
**2373-G3U<br />
**2373-G3G<br />
**2373-G1G<br />
**2373-G5G<br />
* {{T41}}<br />
**2379-DJU<br />
**2373-3KG<br />
**2373-9HU<br />
**2373-4FG<br />
**2373-4PG<br />
**2373-1FG<br />
**2373-2FG<br />
**2373-2GG<br />
**2373-6U4<br />
**2373-7JU<br />
**2373-CY0<br />
**2373-TG5<br />
**2373-3HM<br />
**2373-4GU<br />
* {{T41p}}<br />
**2373-9FU<br />
* {{T42}}<br />
**2373-C19<br />
**2373-CTO<br />
**2378-DTU<br />
**2378-DUU<br />
**2378-XXE<br />
**2378-R4U<br />
**2373-FWG<br />
**2374-ZEP<br />
**2373-F2G<br />
**2373-JTU<br />
**2373-VUW<br />
**[[2373-6ZG]]<br />
* {{X21}}<br />
**2662-BSG<br />
* {{X32}}<br />
**2884-A3U<br />
*{{X41T}}<br />
** 1869-5CU<br />
| style="vertical-align:top;background-color:#e9f9e9;" |<br />
*[[:Category:A22m | A22m]]<br />
**2628<br />
*[[:Category:A31 | A31]]<br />
**2652-D5G<br />
*[[:Category:R50p | R50p]]<br />
*[[:Category:R52 | R52]]<br />
**1858-6MM<br />
*[[:Category:T41 | T41]]<br />
**2373-GEU<br />
*[[:Category:T41p | T41p]]<br />
**2373-GKG<br />
**2373-GGG<br />
**[[2373-GHG]]<br />
*[[:Category:T42 | T42]]<br />
**[[2373-M1G]]<br />
**[[2373-WBZ]]<br />
**[[2373-F7G]]<br />
**[[2378-DXU]]<br />
**[[2378-FVU]]<br />
**[[2378-RTU]]<br />
**[[2378-RRU]]<br />
*[[:Category:T42p | T42p]]<br />
**[[2373-HTG]]<br />
**[[2373-W6M]]<br />
**[[2373-GTG]]<br />
**[[2373-GXG]]<br />
**2373-KXM<br />
*[[:Category:T43 | T43]]<br />
**[[2668-W12]]<br />
*[[:Category:T43p | T43p]]<br />
**[[2668-G2G]]<br />
*[[:Category:X40 | X40]]<br />
**2371<br />
|}<br />
*Different symptoms have been reported for different models. In some models the origin of the power drain is obvious ([[Problem with LCD backlight remaining on during ACPI sleep|backlight on during suspend]]), in other models there is no obvious reason.<br />
<br />
*On some models/configurations the higher power drain couldn't even be realized or was at least significantly lower.<br />
<br />
*The T4x ThinkPad series and other Radeon based models suspend to ram just fine, and there are no components that are obviously left powered up. The [[UltraBay]] and network light is on, but that is the same under windows (but under APM sleep to RAM those lights are OFF). For these models the higher power drain is caused by a driver problem and can be fixed in software. Starting with linux 2.6.18 this fix is in the official kernel.<br />
<br />
The table on the right gives an overview of the models suffering from the mysterious power drain. To find out about your model, you may use the following [[ACPI sleep power drain test script | script]]. It creates a file {{path|/var/log/battery.log}} which will tell you if you are affected or not.<br />
<br />
==Affected Operating Systems==<br />
*Linux, all flavours.<br />
*Windows, for some models as well (only when using non-IBM drivers).<br />
*FreeBSD (on the A22M)<br />
<br />
==Radeon GPU not powered off==<br />
A frequent cause of the mysterious power drain is the Radeon GPU, which requires extra steps to suspend properly. We identified affected thinkpads, and [[radeonfb]] activates the workaround on those models automatically (starting with linux kernel 2.6.18).<br />
<br />
===Status===<br />
*The official bugzilla entry for the radeon suspend issue is in the [http://bugme.osdl.org/show_bug.cgi?id=3022 OSDL Bugzilla]. There you can find the above-mentioned patch for older kernel versions. The patch removes the CONFIG_PPC_PMAC condition for enabling D2 sleep in {{path|drivers/video/aty/radeon_pm.c}}. If you suspect that this patch makes things worse, you can disable it by the kernel parameter {{bootparm|video|radeonfb:ignore_devlist|1}}. Similarly, if the patch is not automatically activated on your notebook you can force it by {{bootparm|video|radeonfb:force_sleep|1}}. In case that improves your sleep, please leave a note in the bugzilla including the output of {{cmdroot|lspci -d "1002:*" -vn}}. See also [http://thread.gmane.org/gmane.linux.hardware.thinkpad/25355 the linux-thinkpad ML post requesting this information] for more information. <br />
<br />
*Most certainly, the DSDT is not at fault. (Interesting to note: The DSDT from BIOS 3.13 (Nov 04) for the T42p compiles without bugs.)<br />
<br />
===Solutions===<br />
You must use a recent (or patched) version of the [[radeonfb]] driver, even if you are only interested in using the X window system. The radeon frame buffer suspends the radeon chip correctly during ACPI sleep. Starting with linux 2.6.18, this patch is in the official (kernel.org) kernels.<br />
<br />
If the patch is known to work on your notebook, it is automatically enabled. If you think that your computer would profit from the patch as well, you can force it by including the module parameter {{bootparm|video|radeonfb:force_sleep|1}}. If it does not work this can result in system hangs.<br />
<br />
Alas, in many cases [[radeonfb]] cannot coexist with the [[radeon]] X.org driver (causing corrupted rendering and hangs). Using the <tt>Option "UseFBDev" "True"</tt> of [[radeon]] may help, but this is incompatible with [[radeon]]'s mergedfb mode. A "GPU device layer" architecture which may, one day, resolve this was proposed by Dave Airlie [http://airlied.livejournal.com/#item30632 here] and [http://lkml.org/lkml/2006/7/22/45 here].<br />
{{HELP|Is there ''any'' fully working solution?}}<br />
<br />
====Fedora Core====<br />
* Fedora Core 6: Ships with kernel >= 2.6.18, only needs initrd (see below).<br />
* Fedora Core 5: The latest kernel from updates (2.6.18-1.2200.fc5) seems to actually fix this issue, you only have to make custom initrd because the default one does not contain radeonfb.<br />
* Fedora Core 4: Fedora ships a patched radeon frame buffer (radeonfb.ko), but you must enable it yourself. {{Fedora}} compiles it as a module rather than including it in the kernel, therefore you cannot activate it at boot time without a custom initrd. You must arrange for the module to be loaded before X starts (for example, using an init script).<br />
* Fedora Core 3: this is also true for updated kernels (at least for kernel-2.6.12-1.1376_FC3) but '''not''' for the initially shipped version.<br />
<br />
====testing radeonfb without changing initrd====<br />
If you want to try the radeon frame buffer, you can enable it as follows:<br />
*First, switch to a console ({{key|Ctrl}}{{key|Alt}}{{key|F1}}) and log in as root.<br />
*Stop X: {{cmdroot|init 3}}<br />
*Now you can load the module: {{cmdroot|1=modprobe radeonfb force_sleep=1}}<br />
*Finally, resume X: {{cmdroot|init 5}}<br />
<br />
====Gentoo====<br />
After installing the patch on {{Gentoo}} (it works fine with gentoo-sources: {{cmdroot|cd /usr/src/linux/drivers/video/aty}}, and execute {{cmdroot|patch -p4 < <patchname>}}, then recompile the kernel), one needs to add {{bootparm|video|radeonfb:force_sleep}} to the kernel parameters.<br />
<br />
====including radeonfb into your initrd====<br />
As an alternative you can build your customized initrd. This is as simple as running<br />
:{{cmdroot|1=mkinitrd --with=radeonfb /boot/<name-of-your-new-initrd> `uname -r`}}<br />
and replacing the initrd in {{path|/boot/grub/grub.conf}} with your new one. You also need to add the kernel command line argument {{bootparm|video|2=radeonfb:force_sleep}}.<br />
<br />
With FC6 and KDE I had to:<br />
*Login as root<br />
*Enter the command as {{cmdroot|1=mkinitrd --with=radeonfb /boot/<name-of-your-new-initrd> <kernel version>}}<br />
:e.g. {{cmdroot|1=mkinitrd --with=radeonfb /boot/initrd-2.6.18-1.2798.fc6-my.img 2.6.18-1.2798.fc6}}<br />
<br />
==Backlight staying on==<br />
It is possible that [[radeontool]] will help some people if the backlight stays on.<br />
(simply run "radeontool light off" before suspend and "radeontool light on" after resume).<br />
A radeontool patch for freebsd is here: http://www.init-main.com/radeontool.patch (by Takanori Watanabe).<br />
<br />
===Notes for gnome-power-manager===<br />
If you suspend from Gnome and need to run radeontool to turn the backlight off you need to find the suspend script for HAL. In Ubuntu, the scripts are located in /usr/share/hal/scripts/. Add the following the script "hal-system-power-suspend":<br />
chvt 1<br />
radeontool light off<br />
And in the resume script ("restore-after-standby"):<br />
radeontool light on<br />
chvt 7<br />
<br />
This worked for me. YMMV. [[User:Etnoy|Etnoy]] 16:27, 9 November 2006 (CET)<br />
<br />
===For models without Radeon graphics===<br />
The Problem seems to be solved when you use the [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to turn the LCD off before suspending ...<br />
:{{cmdroot|vbetool dpms off}}<br />
and turning it on afterwards again...<br />
:{{cmdroot|vbetool dpms on}}<br />
You have to change to a normal console before turning the LCD off.<br />
Additionally you have to deactivate the Wake-On-Lan feature like mentioned above ...<br />
:{{cmdroot|ethtool -s eth0 wol d}}<br />
With these commands used together the "testing script" reports no high power drain while suspending.<br />
<br />
==Other problems causing the power drain==<br />
On my [[R51]] using Gentoo Linux, the high power drain was not caused by the graphics adaptor but by several components not powered down properly before putting the Thinkpad into S3.<br />
<br />
If the above did not help you, this might do:<br />
<br />
Walk through<br />
/sys/devices/*/*/power/state<br />
and try to disable each of it, every time checking the power drain. (See linux/Documentation/power/devices.txt for values to write into the state-files. 3 should be the value you want to try)<br />
Do the same for other components (Like the Ultrabay, etc.). Please add your experiences here.<br />
<br />
===R51: Ultrabay and networking===<br />
On my system, ultrabay and networking light were still on while in S3. So were the devices theirselves.<br />
echo -n eject > /proc/acpi/ibm/bay # Disable ultrabay<br />
ethtool -s eth0 wol d # Disable Wake-On-Lan (And so the eth-adaptor)<br />
echo mem > /sys/power/state # Sleep<br />
<br />
For me, this lowered the power drain from >700mW to 338 mW.<br />
<br />
===USB===<br />
My initial testing of a [[T43]] (2669-model) revealed no power drain issues. However, after several rounds of BIOS and kernel upgrades I have discovered that the power drain has risen to >700mWh. Having tested things a bit, I have discoved that removing ehci_hcd module solved the high power drain. This is a [[T43]] laptop, with kernel 2.6.17-r5 and BIOS 1.28/EC 1.06. For me, issuing {{cmdroot|modprobe -r ehci_hcd}} before going to sleep and reloading the module ({{cmdroot|modprobe ehci_hcd}}) after waking up dropped the power drain down to 277mWh in suspend2ram, which seems fair. The unloading/reloading can be put into the suitable ACPI script called to suspend the laptop.<br />
<br />
===Wake-on-LAN===<br />
Some additional power savings can be achieved by turning off the wake-on-lan ({{cmdroot|ethtool -s eth0 wol d}}). The power drain of the wol feature is far smaller than the radeon bug, but can be noticeable.</div>Mahto