From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Date: Wed, 14 Nov 2007 21:26:01 +0100 [thread overview]
Message-ID: <19f34abd0711141226n60323630rdc4833db0bfb2eeb@mail.gmail.com> (raw)
Hello,
With 2.6.23 kernel, the laptop middle button worked fine. With
2.6.24-rc1, when I press the middle button, the cursor jumps around
the screen and this appears in the kernel log (for each time I press
the button):
psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
psmouse.c: GlidePoint at isa0060/serio1/input0 - driver resynched.
Related dmesg:
input: Macintosh mouse button emulation as /class/input/input0
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
mice: PS/2 mouse device common for all mice
input: PS/2 Mouse as /class/input/input2
input: AlpsPS/2 ALPS GlidePoint as /class/input/input3
Earlier dmesgs (2.6.23) had (only) this:
input: Macintosh mouse button emulation as /class/input/input0
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
mice: PS/2 mouse device common for all mice
input: ImPS/2 Generic Wheel Mouse as /class/input/input2
It seems that the driver used is different. What can I do to fix this?
Kind regards,
Vegard Nossum
next reply other threads:[~2007-11-14 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 20:26 Vegard Nossum [this message]
2008-01-07 20:24 ` [BISECTED] " Vegard Nossum
2008-01-11 14:47 ` Dmitry Torokhov
2008-01-15 18:28 ` Vegard Nossum
2008-01-15 20:49 ` Dmitry Torokhov
2008-01-16 15:42 ` Dmitry Torokhov
2008-01-16 17:46 ` Vegard Nossum
2008-01-16 19:33 ` Dmitry Torokhov
2008-01-16 20:19 ` Vegard Nossum
2008-01-16 20:49 ` Dmitry Torokhov
2008-01-17 20:26 ` Vegard Nossum
2008-01-17 21:11 ` 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=19f34abd0711141226n60323630rdc4833db0bfb2eeb@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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®