From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Gunter Königsmann" <gunter.koenigsmann@gmx.de>,
"Gunter Königsmann" <gunter@peterpall.de>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>,
Peter Berg Larsen <pebl@math.ku.dk>
Subject: Re: Synaptics Touchpad workaround for strange behavior after Sync loss (With Patch). (fwd)
Date: Sun, 11 Jan 2004 11:38:49 -0500 [thread overview]
Message-ID: <200401111138.49858.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0401111652510.1271@calcula.uni-erlangen.de>
On Sunday 11 January 2004 11:27 am, Gunter Königsmann wrote:
> Strike! Helps.
>
> No more warnings, no more bad clicks, and a *real* smooth movement.
>
Great!
Could you tell us what kind of laptop you have (manufacturer/model)
so other people would not have such pain as you had with it?
> Never thought, a touchpad can work *this* well... ;-)
>
> Anyway, I still get those 4 lines on leaving X, but don't know, if it
> is an error of the kernel, anyway, and doesn't do anything bad exept of
> warning me:
>
> atkbd.c: Unknown key released (translated set 2, code 0x7a on
> isa0060/serio0). atkbd.c: Unknown key released (translated set 2, code
> 0x7a on isa0060/serio0). atkbd.c: Unknown key released (translated set
> 2, code 0x7a on isa0060/serio0). atkbd.c: Unknown key released
> (translated set 2, code 0x7a on isa0060/serio0).
I believe Vojtech said that it's because X on startup tries to talk to the
keyboard controller directly, nothing to worry about... But I might be
mistaken.
>
>
> Yours,
>
> Gunter.
Dmitry
next prev parent reply other threads:[~2004-01-11 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 16:27 Synaptics Touchpad workaround for strange behavior after Sync loss (With Patch). (fwd) Gunter Königsmann
2004-01-11 16:38 ` Dmitry Torokhov [this message]
2004-01-11 17:13 ` Gunter Königsmann
2004-01-11 17:23 ` Gunter Königsmann
2004-02-04 9:27 ` Gunter Königsmann
2004-01-11 18:08 ` 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=200401111138.49858.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=gunter.koenigsmann@gmx.de \
--cc=gunter@peterpall.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pebl@math.ku.dk \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.