ThinkWiki - User contributions [en]

Talk:How to configure the TrackPoint

2009-03-04T12:58:37Z

Webograph: /* press to select: new mouse button */ new section

==== /sys-configuration files ====
where can i find documentation of the other files (thresh, upthresh, skipback, reach, inertia...)? [[User:Blerp|Blerp]] 01:01, 9 March 2007 (CET)
:I second that question. --[[User:Telofy|Telofy]] 18:11, 31 December 2008 (CET)

==== shifting /sys-paths ====
2007-03-13
On my Thinkpad R60 with kernel 2.6.20, the path is {{path|/sys/devices/platform/i8042/serio1/serio2}}.

On {{Fedora}} 5, with kernels 2.6.15 and forward, the path does not include
{{path|serio2}}; it stops at {{path|serio0}}.

Same thing on a {{Ubuntu}} Dapper install on an {{X31}}, again with kernel 2.6.15 (maybe that's the reason? [[User:Piccobello|Piccobello]] 17:02, 26 November 2006 (CET)).

2006-07-18
On {{Fedora}} 5, with kernels 2.6.16 and forward, the path is {{path|/sys/devices/platform/i8042/serio0/serio2}}

2005-11-07
OpenSuSE 10.0 has a kernel based on 2.6.13 (probably heavily patched), but the directory /sys/devices/platform/i8042/serio0/serio2 does not exist.
instead, it looks like this:
hoppetosse:/sys/devices/platform/i8042/serio0 # ls -l
total 0
-rw-r--r-- 1 root root 4096 Nov 7 18:38 bind_mode
lrwxrwxrwx 1 root root 0 Nov 7 18:38 bus -> ../../../../bus/serio
-r--r--r-- 1 root root 4096 Nov 7 18:38 description
lrwxrwxrwx 1 root root 0 Nov 7 18:38 driver -> ../../../../bus/serio/drivers/psmouse
--w------- 1 root root 4096 Nov 7 18:38 drvctl
drwxr-xr-x 2 root root 0 Nov 7 18:38 id
-r--r--r-- 1 root root 4096 Nov 7 18:38 modalias
drwxr-xr-x 2 root root 0 Nov 7 18:38 power
-rw-r--r-- 1 root root 4096 Nov 7 18:38 protocol
-rw-r--r-- 1 root root 4096 Nov 7 18:38 rate
-rw-r--r-- 1 root root 4096 Nov 7 18:38 resetafter
-rw-r--r-- 1 root root 4096 Nov 7 18:38 resolution
"description" says it's an "i8042 Aux Port". The page [[Patch to enable advanced trackpoint configuration]] seems to imply that a kernel patch is needed in order to get those features... this needs clarification.
hmm. where can i find out whether "drvctrl" is what i'm looking for and what options it takes? guess it's back to RTFS...

2005-10-06
It seems that new version of the patch ( 2.6.12 at least ), the press to select entry in /sys is named "press_to_select" and not "ptson". I changed the page accordingly so that it complies with the [[Patch to enable advanced trackpoint configuration]] page.
If you use an older version try :

====Press to Select====
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):

:{{cmdroot|echo 1 > /sys/devices/platform/i8042/serio0/ptson}}

Press to Select should now be enabled. You can disable it in a similar manner:

:{{cmdroot|echo 0 > /sys/devices/platform/i8042/serio0/ptson}}

Where do I have to put this script (which should automate this), so that it is executed on startup (I have kubuntu (feisty) runing)? Samba

Now I have Intrepid with the new X.org running. I could not find any source how to configure press to select with this X.org version. Can anybody help? Samba

==== No mouse in {{Fedora}} Core 6 ====
FC6 makes an X11/xorg.conf file with no mouse section, so it's not clear how to make the TrackPoint work for scrolling. Any ideas? --[[User:Whizkid|Whizkid]] 17:36, 4 December 2006 (CET)

==== TrackPoint scrolling inverted in Firefox ====
Running Ubuntu Feisty, Firefox 2.0.0.3, I edited /etc/X11/xorg.conf like described in the article and set mousewheel.horizscroll.withnokey.action = 0; in Firefox.
Scrolling works perfectly in other applications. Up-Down scrolling in Firefox, too, but right-left is inverted (only in Firefox). Does anybody have an idea why this could be? [[User:Tec|Tec]] 11:15, 30 March 2007 (CEST)

Yes: you have to configure mousewheel.horizscroll.withnokey.numlines as well. I have the value set to 1, but you may need to set it to -1.
There is also a mousewheel.horizscroll.withnokey.sysnumlines setting, which you must set to false. --[[User:RichardNeill|RichardNeill]] 03:22, 4 April 2007 (CEST)

Thanks a lot. mousewheel.horizscroll.withnokey.sysnumlines was set to false correctly, but mousewheel.horizscroll.withnokey.numlines was set to -1 as a standard setting. Switched to 1 and it works perfectly :-) BTW, is there a good explanation available in the net, what all those parameters of about:config mean? I searched for it and didn't find anything :-( [[User:Tec|Tec]]

==== Sensitivity and Speed settings under Gutsy Gibbon ====

Sensitivity and speed value editing seem broken in gutsy.
Its no writeable even as root. Tools like configure-trackpoint do not start arguing a lack of root tights.

:Hm, I just installed the deb 0.6-1 available at sourceforge and sudo configure-trackback works for me. Maybe you'd better ask in some forum or file a bug to find out why it's not working on your machine? [[User:Tec|Tec]]

::I confirm that even root can not edit the config files with an editor (vim or nano). But the echo > file works fine.
::{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio1/serio2/speed}}
:: I have put these echo in a script executed by root at bootime with a @reboot entry in the root's crontab. Should also work with a call to that script in /etc/bootmisc.sh
::[[User:Ripat|Ripat]] 10:20, 6 January 2008 (CET)

:::Same on my machine. Config files are not writable with an editor, but echo > file works. {{cmduser|sudo configure-trackpoint}} works, too (sorry, I misspelled this before) [[User:Tec|Tec]] 16:00, 12 January 2008 (CET)

== No scroll in Ubuntu 7.10 without UltraNav installed in Windows Vista ==

I could not get trackpoint scroll working in Ubuntu 7.10 (Gutsy Gibbon) on my Z61t using the xorg.conf modifications listed here until I installed the UltraNav Utility on Windows Vista (dual-boot configuration). Scrolling worked fine without the UltraNav utility and with just the UltraNav driver on Windows. It's weird to me that installing the UltraNav utility in Vista would have an effect on Ubuntu. (I know it's not a coincidence because I ran into it once before.) Any explanation for this strangeness?
--[[User:Threexk|Threexk]] 04:05, 18 February 2008 (CET)

== press to select: new mouse button ==

is it possible to put the z axis button (aka pressing the stick) on another x mouse button (and, further on, set EmulateWheelButton to that button)? i use all three buttons both for clicking and dragging and lack a scroll wheel; having the mouse send scroll events when z axis button is pressed instead of moving the mouse would provide that without damaging the other buttons' functionalities. --[[User:Webograph|Webograph]] 12:58, 4 March 2009 (UTC)

ATI Mobility FireGL V5200

2007-08-29T12:43:27Z

Webograph: /* Proprietary ATI driver on Ubuntu Feisty */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ATI Mobility FireGL V5200 ===
This is an ATI video adapter

=== Features ===
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Not supported by the Xorg radeon driver.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correctly. Changing the driver from "ati" to "vesa" in xorg.conf will start X but with a lower resolution than expected.

Full resolution can be achieved when all modelines are removed and mode 1600x1200 with depth 24 is selected.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===
Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

Note: On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga=791' or to remove 'splash' from the grub/lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]