From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Andreas Mohr" <andi@rhlx01.fht-esslingen.de>
Cc: "Gene Heskett" <gene.heskett@verizon.net>, linux-kernel@vger.kernel.org
Subject: Re: Touchpad problems with latest kernels
Date: Mon, 14 Aug 2006 12:06:06 -0400 [thread overview]
Message-ID: <d120d5000608140906x47bc572blb1b9821ead987d7e@mail.gmail.com> (raw)
In-Reply-To: <20060814155437.GA801@rhlx01.fht-esslingen.de>
On 8/14/06, Andreas Mohr <andi@rhlx01.fht-esslingen.de> wrote:
> On Mon, Aug 14, 2006 at 11:41:29AM -0400, Dmitry Torokhov wrote:
> > On 8/14/06, Andreas Mohr <andi@rhlx01.fht-esslingen.de> wrote:
> > >Plus, I'm sometimes having issues with pointer movement (cursor won't
> > >advance
> > >any more unless I stop touching the touchpad for a few seconds to let it
> > >reset somehow - probably a bytestream hickup issue).
> > >
> > >Any clues?
> > >
> >
> > Yes, you might want to reseat your touchpad connector and vacuum the
> > case a bit. Inspiron 8000 is almost the same as 8100 and I am using it
> > constantly ;) Well, I thought my keyboard broke because PgUp stopped
> > working but it recovered after I got a hairball from under the key.
>
> Hmm, might need to verify that, but I've been cleaning it from time to time
> (Murphy tells me that it was the regular cleaning which broke it ;).
>
That could be too ;)
> > Just make sure you do not pull ACPI battery info to often.
>
> Uh... why!?
>
On many laptops (including mine) polling battery takes a loooong time
and is done in SMI mode in BIOS causing lost keypresses, jerky mouse
etc. It is pretty common problem. I think I have my ACPI client
refreshing every 3 minutes.
--
Dmitry
next prev parent reply other threads:[~2006-08-14 16:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-08-14 20:06 ` Polling for battery stauts and lost keypresses (was: Touchpad problems with latest kernels) Giuseppe Bilotta
2006-08-14 20:17 ` Dmitry Torokhov
2006-08-16 7:31 ` Polling for battery stauts and lost keypresses Giuseppe Bilotta
2006-08-19 15:50 ` Dmitry Torokhov
2006-08-19 16:02 ` Arjan van de Ven
2006-08-21 11:56 ` Giuseppe Bilotta
2006-08-21 12:34 ` Dmitry Torokhov
2006-08-21 12:52 ` Arjan van de Ven
2006-08-24 20:31 ` Pavel Machek
2006-08-14 19:30 ` Touchpad problems with latest kernels Dmitry Torokhov
2006-08-14 17:09 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-27 21:26 Javier Kohen
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=d120d5000608140906x47bc572blb1b9821ead987d7e@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=gene.heskett@verizon.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
all inboxes | Powered by JetHome®