From: Javier Kohen <jkohen@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Touchpad problems with latest kernels
Date: Sun, 27 Aug 2006 18:26:14 -0300 [thread overview]
Message-ID: <1156713975.20067.15.camel@null.tough.com.ar> (raw)
Hi,
I just got a HP dv8301nr laptop and found out about this problem. I'm
running kernel 2.6.17-debian and 2.6.17-ck1. The Touchpad is a model: 1,
fw: 6.2, id: 0x1a0b1, caps: 0xa04713/0x200000.
I've tried many suggested workarounds that I found on the net to no
avail. Even forcing the imps/exps protocols cause a similar problem
here: no pointer freezes as with the SynPS protocol, but yes periodical
random jerky mouse movements and clicks. Moreover, I haven't found a way
to disable the mouse-tap feature (which I find annoying) when using this
protocol and X. I haven't tried the bare protocol because I'm very used
to the scrolling wheel behavior.
Incidentally, it seems that the driver resynchs are always useless, at
least for me.
I booted with the ec_intr=0 option (it took effect according to the boot
logs) to no avail. I'd like to help fix this problem, so if there is
anything that I can do, please let me know. I modified synaptics.c to
print the packets that were failed the validation check to fail, but
they don't say much to me.
Meanwhile, I think I'll get a cheap external mouse (I read they work
fine) and keep my hopes up.
Thanks in advance,
--
Javier Kohen <jkohen@users.sourceforge.net>
ICQ: blashyrkh #2361802
Jabber: jkohen@jabber.org
next reply other threads:[~2006-08-27 22:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 21:26 Javier Kohen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-14 17:09 Touchpad problems with latest kernels Voluspa
2006-08-14 19:27 ` Dmitry Torokhov
2006-08-15 3:06 ` Voluspa
2006-08-15 14:57 ` Luke Sharkey
2006-08-15 16:33 ` Voluspa
2006-08-15 17:12 ` Dmitry Torokhov
2006-08-15 19:00 ` Voluspa
2006-08-15 17:10 ` Dmitry Torokhov
2006-08-16 13:59 ` Luke Sharkey
2006-08-16 14:42 ` Dmitry Torokhov
[not found] ` <BAY114-F39F04F7AD7901A482EB648FA4D0@phx.gbl>
2006-08-17 15:28 ` Dmitry Torokhov
2006-08-14 13:58 Luke Sharkey
2006-08-14 14:36 ` Dmitry Torokhov
2006-08-14 15:18 ` Dave Jones
2006-08-14 14:38 ` Gene Heskett
2006-08-14 15:06 ` Ian Stirling
2006-08-14 15:19 ` Gene Heskett
2006-08-14 15:41 ` Ian Stirling
2006-08-14 15:13 ` Dmitry Torokhov
2006-08-14 15:25 ` Mattia Dongili
2006-08-14 15:34 ` Gene Heskett
2006-08-14 15:53 ` Dmitry Torokhov
2006-08-14 16:33 ` Gene Heskett
2006-08-14 16:59 ` Dmitry Torokhov
2006-08-14 15:20 ` Andreas Mohr
2006-08-14 15:41 ` Dmitry Torokhov
2006-08-14 15:54 ` Andreas Mohr
2006-08-14 16:06 ` Dmitry Torokhov
2006-08-14 19:30 ` Dmitry Torokhov
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=1156713975.20067.15.camel@null.tough.com.ar \
--to=jkohen@users.sourceforge.net \
--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