All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob <recbo@nishanet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test11 ps2 mouse giving corrupt data?
Date: Fri, 12 Dec 2003 23:02:39 -0500	[thread overview]
Message-ID: <3FDA8F5F.1030506@nishanet.com> (raw)
In-Reply-To: <20031212141521.GA27405@ucw.cz>

Vojtech Pavlik wrote:

>On Fri, Dec 12, 2003 at 12:36:38PM +0000, Andrew Walrond wrote:
>  
>
>>I have just switched from l2.4 to 2.6 on my thinkpad, and the mouse does 
>>something wierd when I boot into x (kde)
>>
>>startx, then wait for everything to load, then move mouse. Mouse goes crazy, 
>>menus pop up everywhere as though I were pressing buttons, and after about 3 
>>seconds, it all settles down and works perfectly.
>>    
>>
>
>Most likely X does something nasty to the keyboard controller while it
>is starting up. The psmouse kernel driver has an autosync feature which
>can get it out of trouble if you don't move the mouse for two seconds.
>  
>
When did the autosync feature arrive?
It doesn't work for me(k2.6.11 with
MSI K7N2 Delta nforce2 mboard
and k2.6.11 with Shuttle Xpc SK41G
FX41 mboard with VIA fsb) if ps2
kvm switch(Belkin) is switched away.

When sync is lost on my pc's I have to
reboot. Symptoms are the same, on X or
text term--any mouse movement triggers
selects and buttons down but the correct
events do not occur.

With a kvm switch k-2.6.? loses psmouse
sync on the off pc. Rebooting is the only
solution. I got tired of this and moved the
mouse(logitech trackman fx) to one pc,
so the other only has to boot with the
mouse attached either to kvm or ps2
port on pc. That's fine until moving the
mouse back and forth for rebooting
causes the pc with X running to lose
sync. Then it can't regain sync.

-Bob

  reply	other threads:[~2003-12-13  4:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 12:36 2.6.0-test11 ps2 mouse giving corrupt data? Andrew Walrond
2003-12-12 14:15 ` Vojtech Pavlik
2003-12-13  4:02   ` Bob [this message]
2003-12-15 16:49     ` 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=3FDA8F5F.1030506@nishanet.com \
    --to=recbo@nishanet.com \
    --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.