public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Westgate <oryn@oryn.fsck.tv>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.6.1 synaptics problems tapping and tap'n'drag
Date: Fri, 09 Jan 2004 23:04:30 +0000	[thread overview]
Message-ID: <3FFF337E.3040603@oryn.fsck.tv> (raw)

Hi,
I'm not sure if this is the right place to ask but if I run 2.6.1
I get mouse problems that I didn't get with 2.6.0
I'm running a compaq m300 (600MHz PIII) with a synaptics touch pad.

In 2.6.0 there was an option to include or not include support for the 
synaptics touchpad (I found that my touchpad worked just fine with that 
option unchecked) in 2.6.1 that option is nolonger there.

In 2.6.1 I find that the operation of the mouse is very erratic its 
almost impossible to take your finger off the pad without the cursor 
moving, Tapping doesn't work, The pad seems very accelerated (ie you 
drag your finger a short distance and the cursor is at the other side of 
the screen before you know it), Lastly if you dragged your finger to the 
edge of the pad it used to continue on smoothly. This no longer works.

My question is:
Is there a command line or append option I can put in lilo.conf to 
prevent the synaptics driver from trying to reprogram my touchpad? I 
quite like its default behavior. There is definatly something trying to 
reprogram it as I have to turn off my laptop for it's behavior to return 
to normal. Even if I reset it still needs a power cycle to fix it.
dmesg says my touchpad is this:
input: PS/2 Synaptics TouchPad on isa0060/serio4

I'm not running any special drivers or settings in XF86Config
I just have /dev/input/mice setup with protocol set as ImPS/2

Regards
Jon Westgate



             reply	other threads:[~2004-01-09 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 23:04 Jon Westgate [this message]
2004-01-10  2:26 ` kernel 2.6.1 synaptics problems tapping and tap'n'drag Marcos D. Marado Torres
2004-01-10  2:28 ` Marcos D. Marado Torres
2004-01-10 19:18   ` Jon Westgate
2004-01-10 17:42 ` Vojtech Pavlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FFF337E.3040603@oryn.fsck.tv \
    --to=oryn@oryn.fsck.tv \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox