ETPS/2 Elantech Touchpad does not work (but its buttons do)

Bug #355161 reported by Sebastian Urban
50
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Jaunty by monsag
Nominated for Karmic by monsag

Bug Description

Binary package hint: xfree86-driver-synaptics

This touchpad is recognized but it does not work, i.e. the touch surface does not work. However its two buttons (left/right click) do work. It worked fine in Hardy.

A workaround is executing
modprobe -r psmouse
modprobe psmouse proto=imps
but this does not seem to be a real solution.

xinput list:
...
"ETPS/2 Elantech Touchpad" id=4 [XExtensionPointer]
 Num_buttons is 12
 Num_axes is 2
 Mode is Relative
 Motion_buffer is 256
 Axis 0 :
  Min_value is 32
  Max_value is 544
  Resolution is 1
 Axis 1 :
  Min_value is 32
  Max_value is 352
  Resolution is 1

/proc/bus/input/devices:
...
I: Bus=0011 Vendor=0002 Product=000e Version=0000
N: Name="ETPS/2 Elantech Touchpad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input11
U: Uniq=
H: Handlers=mouse2 event9
B: EV=f
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: REL=3
B: ABS=3

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-input-synaptics 0.99.3-2ubuntu4
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009
SourcePackage: xfree86-driver-synaptics
Uname: Linux 2.6.28-11-generic i686

[lspci]
00:00.0 Host bridge [0600]: VIA Technologies, Inc. K8M800 Host Bridge [1106:0204]
     Subsystem: TWINHEAD INTERNATIONAL Corp Device [14ff:0322]
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] [1106:3108] (rev 01)
     Subsystem: TWINHEAD INTERNATIONAL Corp Device [14ff:0322]

Revision history for this message
Sebastian Urban (surban) wrote :
Bryce Harrington (bryce)
Changed in xfree86-driver-synaptics (Ubuntu):
status: New → Confirmed
Revision history for this message
Vincent Lönngren (bice77) wrote :

I have the same problem, with xserver-xorg-input-synaptics in Jaunty. It seems to work when the touchpad is specified in xorg.conf, the old way, but not when relying on HAL.

Revision history for this message
Vincent Lönngren (bice77) wrote : Re: [Bug 355161] Re: ETPS/2 Elantech Touchpad does not work (but its buttons do)
  • laptop Edit (108 bytes, text/plain; name="laptop"; charset="UTF-8")
  • uname-a Edit (91 bytes, text/plain; name="uname-a"; charset="UTF-8")
  • version_signature Edit (28 bytes, text/plain; name="version_signature"; charset="UTF-8")
  • lspci-vvnn Edit (20.4 KiB, text/plain; name="lspci-vvnn"; charset="UTF-8")
  • lshal Edit (122.5 KiB, text/plain; name="lshal"; charset="UTF-8")
  • devices Edit (2.7 KiB, text/plain; name="devices"; charset="UTF-8")
  • dmesg Edit (44.7 KiB, text/plain; name="dmesg"; charset="UTF-8")

--
Vincent Lönngren <email address hidden>

Revision history for this message
Chris (chris-yourdreamnet) wrote :

I can confirm this too. I have tried both the modprobe work around and the uncommented of the Xorg setting and it still does not work though. Do I need to disable HAL for the device also?

I recommend that the importance is set to High because not being able to use the mouse is pretty major, more so than anything other than the keyboard.

Bryce Harrington (bryce)
description: updated
Revision history for this message
Matthew Lenz (matthew-nocturnal) wrote :

confirmed with jaunty release the modprobe work around seems to work. is there anyway to make this permanent?

Revision history for this message
Chris (chris-yourdreamnet) wrote :

To get this to work on startup you just need to run the following command:

echo "options psmouse proto=imps" |sudo tee -a /etc/modprobe.d/psmouse

It's not a fix, but it's a good workaround.

Revision history for this message
Nick Bolton (nick.bolton.uk) wrote :

I can confirm this bug in Ubuntu 9.04, the problem seems to occur only when Ubuntu is installed from Windows XP. When booting using the Live CD this problem does not occur.

The work around by Sebastian Urban, solves the problem with no obvious side effects:

sudo modprobe -r psmouse
sudo modprobe psmouse proto=imps

I'm using a Philips Freevents X51 laptop, which seems to be quite rare, since Philips don't officially make laptops.

Revision history for this message
Mischa Stolz (michael-stolz) wrote :

I can confirm this bug with 9.04 and a Twinhead Stylebook 12D. The workaround (sudo modprobe -r psmouse;sudo modprobe psmouse proto=imps) also works for me. The issue appeared after the upgrade to 9.04. The touchpad had worked before with 8.10.

Revision history for this message
Robert Hooker (sarvatt) wrote :

This is completely from the sideline, but it might be useful if you could try a newer kernel out to see if the problem was fixed there since there have been some fixes to psmouse since jaunty's kernel and if it is fixed by the newer kernel it would help narrow down the fix needed.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30/

linux-image for your architecture should be all you need unless you have extra modules that need to be installed, then you can grab the header packages as well.

Revision history for this message
Andy_Capp (done-fishin) wrote :

I have been using live CD's (9.04 and the Super OS (formerly Ubuntu) 9.04)

the problem remains, whilst using live CD's of 8.04 & 8.10 touchpad works well.

I am using a Philips Notebook F12DT also known as Freevent X50.
This is manufactured by Twinhead under the name of Stylebook 12D and it is also badged as an Averatec AV3715.

Under windows the touchpad appears to be installed as a Microsoft Mouse directly connected to Port PS/2 however no mouse or port can be seen to be physically attached.

Revision history for this message
Sebastian Urban (surban) wrote :

The problem seems to be fixed in Ubuntu Karmic Alpha 2 using the live cd.

Bryce Harrington (bryce)
affects: xfree86-driver-synaptics (Ubuntu) → xserver-xorg-input-synaptics (Ubuntu)
Bryce Harrington (bryce)
tags: added: jaunty
Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Rgpublic (rgpublic) wrote :

This bug still happens with Natty.
The workaround:

modprobe -r psmouse
modprobe psmouse proto=imps

still helps. The touchpad immediately starts working again.

tags: added: natty
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Expired → New
Revision history for this message
Ahmed Shams (ashams) wrote :

Bug confirmed: Kernel failed to detect touchpad.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: New → Confirmed
Revision history for this message
Ahmed Shams (ashams) wrote :

Nothing to do on xserver, moving to kernel (linux)

affects: xserver-xorg-input-synaptics (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → New
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Won't Fix
Revision history for this message
Vincent Lönngren (bice77) wrote :

I used to have this problem on earlier versions of Ubuntu. On a 64-bit Natty system, the touchpad mostly works as expected but stops responding after waking up from standby. Removing and reloading the module as above works.

Revision history for this message
Torsten Casselt (blu2lz) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.