All of lore.kernel.org
 help / color / mirror / Atom feed
From: r2 <torsten.foertsch@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Mouse Problems with 2.6
Date: Tue, 14 Sep 2004 23:43:46 +0200	[thread overview]
Message-ID: <200409142344.00646.r2@opi.home> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

since I have recently updated to kernel 2.6 (Suse 2.6.5-7.108-default) my 
mouse is going crazy from time to time and I am seeing such messages in my 
logfile:

kernel: psmouse.c: Mouse at isa0060/serio2/input0 lost synchronization, 
throwing 2 bytes away.

How can this be avoided?

My notebook has a touchpad built in and I have additional connected an old 
Logitech 3 Button PS/2 mouse:

<6>input: PS/2 Logitech Mouse on isa0060/serio2
<6>serio: i8042 AUX2 port at 0x60,0x64 irq 12
<6>serio: i8042 AUX3 port at 0x60,0x64 irq 12
<6>Synaptics Touchpad, model: 1
<6> Firmware: 5.6
<6> 180 degree mounted touchpad
<6> Sensor: 18
<6> new absolute packet format
<6> Touchpad has extended capability bits
<6> -> four buttons
<6> -> multifinger detection
<6> -> palm detection
<6>input: SynPS/2 Synaptics TouchPad on isa0060/serio4

I'd also like to get the old kernel 2.4 touchpad behaviour. With 2.4 the it 
had sent a Button1 event by simply touching it. Now I have to press the 
appropriate button.

I have seen the module parameter "proto" in the source. Is it worth to play 
with it?

Thanks,
Torsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBR2YWwicyCTir8T4RAjCfAKCmHnMSqXUOYmimEB1HhneZjOsVPACeIU0U
zYaC0HEupjEHsJTreBF0NQM=
=aYmG
-----END PGP SIGNATURE-----

             reply	other threads:[~2004-09-14 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 21:43 r2 [this message]
2004-09-14 22:50 ` Mouse Problems with 2.6 Lee Revell
2004-09-15  2:21 ` 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=200409142344.00646.r2@opi.home \
    --to=torsten.foertsch@gmx.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 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.