From: Voluspa <lista1@comhem.se>
To: lukesharkey@hotmail.co.uk
Cc: linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
gene.heskett@verizon.net, ian.stirling@mauve.plus.com,
davej@redhat.com, andi@rhlx01.fht-esslingen.de,
malattia@linux.it
Subject: Re: Touchpad problems with latest kernels
Date: Mon, 14 Aug 2006 19:09:59 +0200 [thread overview]
Message-ID: <20060814190959.df449d55.lista1@comhem.se> (raw)
On 2006-08-14 13:58:09 Luke Sharkey wrote:
> While on 2054 it generally works fine, On the latest kernels (2154,
> 2174 etc.) I have only to e.g. open a konqueror window for the
> onscreen pointer to start going funny, and jerking about (As happens on
> computers with v. low RAM). I know its not a RAM problem, as a)
> everything else works fine, there is no slow down of any of the
> programs I run, only problems with the mouse and b) I have just
> upgraded from 512 MB of RAM to 1 GB.
>
> If I plug in a mouse, the pointer works fine. Though I would happily
> use a mouse, this is often inconvenient on a laptop.
>
> Do you have any ideas what's wrong?
This is a known problem (and fixed in Windows) with the synaptics touch
pad. About one year ago I did a web search amounting to something like
"synaptics rubber band" and found a fixed windows driver. But since
there is no OS of that kind on this machine, I contacted the developer
of the synaptics X driver.
We had a discussion (swedish only) in private mail, where I ran the
driver in debug mode - he no longer had a machine with that hardware.
Unfortunately I've lost the whole communication due to a voltage frying
of everything in the mail machine, so can not give any details.
If Peter Österlund still has the e-mails I hereby give full permission
to disclose a translated copy to anyone interested.
But I think it all came down to Peter not being able to do anything...
In earlier kernels the issue _seemed_ to lessen if booting with
i8042.nomux but nowadays that kernel option only gets rid of the 'lost
sync' messages from the pad that turn up in /var/log/messages
(Btw, excessive printing of that message Dmitry!)
Mvh
Mats Johannesson
next reply other threads:[~2006-08-14 17:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 17:09 Voluspa [this message]
2006-08-14 19:27 ` Touchpad problems with latest kernels 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
-- strict thread matches above, loose matches on Subject: below --
2006-08-27 21:26 Javier Kohen
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=20060814190959.df449d55.lista1@comhem.se \
--to=lista1@comhem.se \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=davej@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gene.heskett@verizon.net \
--cc=ian.stirling@mauve.plus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukesharkey@hotmail.co.uk \
--cc=malattia@linux.it \
/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