Bug 153201

On a DELL D400 laptop, the touchpad still gets detected but the tapping is now
way too sensitive... not sure it's the same problem, but i can only reproduce
this with FC3's 2.6.11 kernels (-7 and -14) from updates-testing (works fine
with 2.6.10 and haven't tried vanilla kernels)

I just upgraded to kernel 2.6.11-1.14_FC3 from 2.6.10-1.770_FC3 and my touchpad
now exhibits the same symptoms after the upgrade: jerky motion and no more
single, double ot triple 'tap' operation.

The 2.6.11 'broken' kernel now reports my mousepad as:

Apr 11 20:27:33 localhost kernel: ALPS Touchpad (Glidepoint) detected
Apr 11 20:27:33 localhost kernel:   Disabling hardware tapping
Apr 11 20:27:33 localhost kernel: input: AlpsPS/2 ALPS TouchPad on isa0060/serio4

The older 'working' kernel (2.6.10) reports the mousepad as:

Apr 11 21:11:10 localhost kernel: input: PS/2 Generic Mouse on isa0060/serio4

I have also encountered the same problems you guys are having, after upgrading
to kernel 2.6.11-1.14 movement on the touchpad of my Vaio FX-201 laptop became
very jumpy and nearly unusable. In addition tapping the touchpad no longer acts
as a mouse click, it is simply ignored.

This is not a problem with the laptop because booting back into
kernel-2.6.10-1.770 makes the touchpad work perfectly.

I don't know how this kernel passed QA guys, its totally unusable on 2 / 2 of my
systems.

I have the same trouble on a DELL 8600. The touchpad is jumpy as heck after the
kernel upgrade to 2.6.11.  Like the previous report, with kernel upgrade 2.6.10,
the startup says

Apr 13 00:04:00 pols111 kernel: mice: PS/2 mouse device common for all mice
Apr 13 00:04:00 pols111 kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Apr 13 00:04:00 pols111 kernel: input: PS/2 Generic Mouse on isa0060/serio1


With 2.6.11, it has a more-detailed and correct looking message:

Apr 12 23:26:48 pols111 kernel: mice: PS/2 mouse device common for all mice
Apr 12 23:26:48 pols111 kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Apr 12 23:26:48 pols111 kernel: ALPS Touchpad (Dualpoint) detected

I have no way of knowing if this laptop actually has ALPS Dualpoint. How could I?

I've been scanning the internet and I have seen several suggested patches for
the kernel, but I'll prefer to wait until the experts say it is save to step up
again.

*** Bug 154716 has been marked as a duplicate of this bug. ***

Summary from bug 154716:

no form of tapping possible since the alps support was merged into 2.6.11 (Sony
vaio R505TSK).

with X using default/legacy ps2 mode I see the same jerky movements as the
original poster. with X using the synaptics driver movements are ok but still no
tapping.

I backed down to 2.6.10-770 since this is my primary (only) pointing device.
 

*** Bug 154790 has been marked as a duplicate of this bug. ***

I'm running a Toshiba Satellite A10 and the touchpad turned into an Apple style
one one me (no touch tap) after upgrading kernels:

[nesscg@heidrun ~]$ uname -a
Linux heidrun.localdomain 2.6.11-1.14_FC3 #1 Thu Apr 7 19:23:49 EDT 2005 i686
i686 i386 GNU/Linux

Interesting DMESG Output:
=========================
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
ALPS Touchpad (Glidepoint) detected
  Disabling hardware tapping
input: AlpsPS/2 ALPS TouchPad on isa0060/serio1
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27

Anybody know how to enable hardware tapping?
Chris

Same issue exactly with Acer TravelMate 290. 2.6.10-1.770_FC3 works fine; 
2.6.11-1.14_FC3  produces the behavior described.

Thanks,
Avi

On my Sony VAIO GRT-170, it happens the same, it detects it as
input: AT Translated Set 2 keyboard on isa0060/serio0
ALPS Touchpad (Glidepoint) detected
  Disabling hardware tapping
input: AlpsPS/2 ALPS TouchPad on isa0060/serio1

With 2.6.10 it works fine, with 2.6.11, the mouse / touchpad is screwed.

Basit.

Same problem here. Have improved situation a little by using workaround
suggested on fedora users list (see below for /etc/X11/xorg.conf section),
but double-tapping still doesn't work in gterm or address bar of firefox:

Section "InputDevice"
  Driver        "synaptics"
  Identifier    "Mouse1"
  Option        "Device"                "/dev/psaux"
  Option        "Protocol"              "auto-dev"
  Option        "LeftEdge"              "120"
  Option        "RightEdge"             "830"
  Option        "TopEdge"               "120"
  Option        "BottomEdge"            "650"
  Option        "FingerLow"             "14"
  Option        "FingerHigh"            "15"
  Option        "MaxTapTime"            "180"
  Option        "MaxTapMove"            "110"
  Option        "EmulateMidButtonTime"  "75"
  Option        "VertScrollDelta"       "20"
  Option        "HorizScrollDelta"      "20"
  Option        "MinSpeed"              "0.3"
  Option        "MaxSpeed"              "0.75"
  Option        "AccelFactor"           "0.015"
  Option        "EdgeMotionMinSpeed"    "200"
  Option        "EdgeMotionMaxSpeed"    "200"
  Option        "UpDownScrolling"       "1"
  Option        "CircularScrolling"     "1"
  Option        "CircScrollDelta"       "0.1"
  Option        "CircScrollTrigger"     "2"
EndSection
                                                              138,9         Bot

I had the same problem with 2.6.11.7, and able to resolve it with either of the
following approaches.
try: (if psmosue is compiled a module, in /etc/modprobe.conf)
options psmouse proto=imps
or: (if psmouse is compiled into kernel, put the line below as kernel boot
option in grub.conf)
psmouse.proto=imps

(In reply to comment #12)
> I had the same problem with 2.6.11.7, and able to resolve it with either of 
the
> following approaches.
> try: (if psmosue is compiled a module, in /etc/modprobe.conf)
> options psmouse proto=imps
> or: (if psmouse is compiled into kernel, put the line below as kernel boot
> option in grub.conf)
> psmouse.proto=imps

Thanks, Doctor Shahri. This worked a charm! 

--
Avi Jacobson, avi-j

experience same on Dell 600m.

from dmesg:

mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
ALPS Touchpad (Glidepoint) detected
  Disabling hardware tapping
input: AlpsPS/2 ALPS TouchPad on isa0060/serio1

have not had a chance to try suggested fixes.  Just reporting another affected
platform.

hello,

I am running FC4 after upgrade and my mouse is also detected as:

input: DualPoint Stick on isa0060/serio1
input: AlpsPS/2 ALPS DualPoint TouchPad on isa0060/serio1

and it is way too jumpy as described by everyone else.  I have a dell inspiron 8200.

my xorg.conf is:

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "yes"
EndSection

hello,

i added psmouse.proto=exps
 to my grub.conf file and that fixed the problem for my alps touchpad on fc4.

Kyle

Same mouse / touchpad behaviour here.

2.6.11 kernel "Jerky". "Over-sensitive" - responding as if "clicked" on buttons
- even if I haven't - hence unwanted launching of applications or menu options.

Mouse performance fine under 2.6.10 kernel.

Log info below:

Jun 29 08:00:39 localhost syslogd 1.4.1: restart.
Jun 29 08:00:39 localhost syslog: syslogd startup succeeded
Jun 29 08:00:39 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jun 29 08:00:39 localhost kernel: Linux version 2.6.11-1.27_FC3
(bhcompile.redhat.com) (gcc version 3.4.3 20050227 (Red Hat
3.4.3-22)) #1 Tue May 17 20:27:37 EDT 2005
Jun 29 08:00:39 localhost kernel: BIOS-provided physical RAM map:
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 0000000000000000 -
000000000009f400 (usable)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 000000000009f400 -
00000000000a0000 (reserved)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 00000000000d0000 -
00000000000d8000 (reserved)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 00000000000e4000 -
0000000000100000 (reserved)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 0000000000100000 -
000000001fdf0000 (usable)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 000000001fdf0000 -
000000001fdfb000 (ACPI data)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 000000001fdfb000 -
000000001fe00000 (ACPI NVS)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 000000001fe00000 -
0000000020000000 (reserved)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 00000000fec00000 -
00000000fec10000 (reserved)
Jun 29 08:00:39 localhost syslog: klogd startup succeeded
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 00000000fee00000 -
00000000fee01000 (reserved)
Jun 29 08:00:39 localhost kernel:  BIOS-e820: 00000000fff80000 -
0000000100000000 (reserved)
Jun 29 08:00:39 localhost kernel: 0MB HIGHMEM available.
Jun 29 08:00:39 localhost kernel: 509MB LOWMEM available.

<< cut >>

Jun 29 08:00:42 localhost kernel: mice: PS/2 mouse device common for all mice
Jun 29 08:00:42 localhost kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Jun 29 08:00:42 localhost kernel: ALPS Touchpad (Glidepoint) detected
Jun 29 08:00:42 localhost kernel:   Disabling hardware tapping
Jun 29 08:00:42 localhost kernel: input: AlpsPS/2 ALPS TouchPad on isa0060/serio4


<< cut >>

Jun 30 10:18:34 localhost syslogd 1.4.1: restart.
Jun 30 10:18:34 localhost syslog: syslogd startup succeeded
Jun 30 10:18:34 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jun 30 10:18:34 localhost kernel: Linux version 2.6.11-1.27_FC3
(bhcompile.redhat.com) (gcc version 3.4.3 20050227 (Red Hat
3.4.3-22)) #1 Tue May 17 20:27:37 EDT 2005
Jun 30 10:18:34 localhost kernel: BIOS-provided physical RAM map:
<< cut >>
Jun 30 10:18:36 localhost kernel: mice: PS/2 mouse device common for all mice
Jun 30 10:18:36 localhost kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Jun 30 10:18:36 localhost kernel: ALPS Touchpad (Glidepoint) detected
Jun 30 10:18:36 localhost kernel:   Disabling hardware tapping
Jun 30 10:18:36 localhost kernel: input: AlpsPS/2 ALPS TouchPad on isa0060/serio4
Jun 30 12:01:01 localhost crond(pam_unix)[18644]: session opened

An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Problem is now resolved on my hw with the new kernel: 2.6.12-1.1372_FC3.

psmouse.proto=imps fixed it with the old kernels.

kernel-2.6.12-1.1372_FC3 works fine even without adding this line. Looks like
the bugâs been fixed.

I'm currently using a vanilla 2.6.12 kernel with swsusp2 patch added so I can
hibernate, so I can't test this for the exact redhat kernel. I'll take the
others' word for it that it is fixed.

I no longer have that hardware so I can not verify the fix.

One last thing- after testing the synaptics driver in 2.6.12+swsusp2, I am
unable to configure Xorg to use the synaptics driver, following the directions
for the synaptics rpm (in the docs). When I try to use "auto-dev" or "synaptics"
as the Driver for the input device, Xorg tells me "unknown driver", though I can
see that the .so provided by the synaptics rpm is indeed installed.

Hmm; I'm still seeing problems with the updated kernel on FC3, although not the
same problem as before:

1) Click-drag doesn't work. This is most notable for window title-bars. With the
old drivers (or with psmouse.proto=imps2 on the kernel command line) a tap
followed by a drag starts a window drag. With the new driver this doesn't work.

2) ACPI suspend/resume stops the pointing device from working, as reported by
others (https://www.redhat.com/archives/fedora-list/2005-June/msg02707.html and
bug #161546). On my system (Dell Lattitude D600) even a reboot won't bring it
back - I have to do a  full power-off shutdown and reboot.

psmouse.proto=imps2 doesn't exhibit either of these problems.

Reopen, or file a new bug for the click/drag problem?

The click-to-drag behavior is supposed to be configurable, either from sysctl
(don't know the settings) or from xorg.conf. I've tried the latter, using the
synaptics X driver, but as mentioned above was unable to get it to recognize the
protocol...

Additional manifestation of the problem on a Dell D800 running 2.6.11-1.27_FC3.

The buttons associated with the stick do not work at all.

I can't upgrade to 2.6.12-1.1372_FC3 because that release doesn't contain the
build directory under /lib/module/2.6.12-1.1372_FC3/ (it is a link to the source
directory that is not in the binary rpm) so I can't rebuild the NVidia drivers.

Donald, There was a slight change in the packaging of the kernel in the last
update, if you install the kernel-devel package you should be able to build your
nvidia driver as usual. The next kernel update should take things back to the
way things used to be, so FC3 wonât need the kernel-devel package to build
modules, but it does for now.

Some more info can be found over at bug 163406

(In reply to comment #18)
> An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3)[...]
> 
> If you have updated to Fedora Core 4 since this bug was opened, and the problem
> still occurs with the latest updates for that release

Problem still exists in 2.6.12-1.1398_FC4 for me: Mouse is painfully slow and
does not react in any way to acceleration settings in "Mouse Preferences". In
that setup, FC4 is not usable on my Laptop (Sony Z600NE).

psmouse.proto=imps in grub.conf makes the touchpad usable for me -- thanks a
lot to the original poster of this workaround!

> please change the version field of this bug to 'fc4'.

Can't: »You tried to change the Version field from fc3 to fc4, but only the
owner or submitter of the bug, or a sufficiently empowered user, may change
that field.«

I'm the original reporter, and I have upgraded to FC4 and kernel 2.6.12. I
haven't seen any reply to my comment about the synaptics X driver not appearing
to work. The performance problems have gone away, but without being able to
configure the synaptics driver, I still have to revert to the imps workaround
because I want to be able to tap-click. 

Aside from Kai's apparently problems, it seems the original performance problems
have been resolved for everyone attached to this bug. Unless there are any
objections, I'm satisfied with re-closing this and opening a more specific bug
wrt the synaptics driver (and Mark, if you're still having ACPI issues, I
suggest you write those up as well).

Ok, there are a number of other bugs open iirc related to touchpad, if any of
you are still seeing problems, check if any of those apply to you, and if not,
please open a new bug.

Thanks.