linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: albert@users.sourceforge.net, linux-kernel@vger.kernel.org
Cc: 0@pervalidus.tk, akpm@osdl.org, linux-yoann@ifrance.com,
	pavel@ucw.cz, vojtech@suse.cz, zwane@arm.linux.org.uk
Subject: Re: another must-fix: major PS/2 mouse problem
Date: Wed, 30 Jul 2003 21:18:01 +0200 (MEST)	[thread overview]
Message-ID: <200307301918.h6UJI19q020560@harpo.it.uu.se> (raw)

On 30 Jul 2003 08:29:32 -0400, Albert Cahalan wrote:
>> > > psmouse.c: Lost synchronization, throwing 3 bytes away.
>> > > psmouse.c: Lost synchronization, throwing 1 bytes away.
>> > > 
>> > > Arrrrgh! The TSC is my only good time source!
>> > 
>> > Arrrgh!  More PS/2 problems!
>> > 
>> > I think the lost synchronisation is the problem, would you agree?
>> > 
>> > The person who fixes this gets a Nobel prize.
...
>It won't make the mouse run well. Maybe you'd stop the
>mouse from going crazy from time to time, but there'd
>still temporary freezes from time to time. (not OK!)

FWIW, the problems my Dell Latitude had with the external
mice I use with it were significantly reduced once I added
"psmouse_noext" to the kernel's command line. That one
change eliminated all lost sync messages and general craziness
after resumes from suspended state.

To make the mouse move at proper speed w/o jerkiness I
also had to tweak the rate and scaling programmed into it
to match 2.4 defaults. (rate 100, scale 2:1)

In fairness, only my old Latitude has these PS/2 issues.

/Mikael

             reply	other threads:[~2003-07-30 19:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 19:18 Mikael Pettersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-01  1:46 another must-fix: major PS/2 mouse problem Albert Cahalan
2003-06-04  5:47 ` Yoann
     [not found]   ` <20030603232155.1488c02f.akpm@digeo.com>
2003-06-04  7:47     ` Vojtech Pavlik
2003-06-04  7:53       ` Andrew Morton
2003-06-04  8:00         ` Vojtech Pavlik
2003-06-04  8:14           ` Andrew Morton
2003-06-04  8:40             ` Vojtech Pavlik
2003-06-04 19:20               ` Yoann
2003-06-04 23:09             ` Albert Cahalan
     [not found] ` <3EDCF47A.1060605@ifrance.com>
     [not found]   ` <1054681254.22103.3750.camel@cube>
     [not found]     ` <3EDD8850.9060808@ifrance.com>
2003-07-23  0:44       ` Albert Cahalan
2003-07-24 17:30         ` Andrew Morton
2003-07-25  1:46           ` Albert Cahalan
2003-07-26  3:19             ` Andrew Morton
2003-07-26 15:16               ` Zwane Mwaikambo
2003-07-29  2:55                 ` Albert Cahalan
2003-07-29  3:14                   ` Andrew Morton
2003-07-29 12:40                     ` Albert Cahalan
2003-07-29 18:58                       ` Andrew Morton
2003-07-29 19:36                         ` Zwane Mwaikambo
2003-07-29 19:43                         ` Chris Friesen
2003-07-30  5:08                     ` Pavel Machek
2003-07-30  6:32                       ` Andrew Morton
2003-07-30 12:29                       ` Albert Cahalan

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=200307301918.h6UJI19q020560@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=0@pervalidus.tk \
    --cc=akpm@osdl.org \
    --cc=albert@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-yoann@ifrance.com \
    --cc=pavel@ucw.cz \
    --cc=vojtech@suse.cz \
    --cc=zwane@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).