Date: Thu, 27 May 1999 20:10:03 -0700 (PDT) From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-bugs@FreeBSD.org Subject: Re: i386/11597: cmouse complaints: "/kernel: psmintr: out of sync (00c0 != 0008)". FAQ150 outdated. Message-ID: <199905280310.UAA81429@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/11597; it has been noted by GNATS.
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To: crawford@cs.ucdavis.edu
Cc: freebsd-gnats-submit@freebsd.org,
yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: i386/11597: cmouse complaints: "/kernel: psmintr: out of sync (00c0
!= 0008)". FAQ150 outdated.
Date: Fri, 28 May 1999 12:04:45 +0900
>Number: 11597
>Category: i386
>Synopsis: cmouse complaints: "/kernel: psmintr: out of sync (00c0 != 0008)". FAQ150 outdated.
[...]
>Arrival-Date: Sat May 8 19:10:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Rick Crawford
>Release: 3.1
>Organization:
>Environment:
FreeBSD 3.1-Release #0 Mon. Feb. 15 11:08GMT 1999
jkh@usw3.freebsd.org:/usr/src/sys/compile/GENERIC i386
>Description:
>6 month old Gateway with what seems to be Intellimouse (2 button + roller),
>ps/2 interface. syslog logs numerous complaints from line 1851 of
>/usr/src/sys/i386/isa/psm.c of form:
> "/kernel: psmintr: out of sync (00c0 != 0008)"
>Mouse operation is balky -- movement often is interpreted as cut/paste,
>yet intentional cut/paste is difficult.
>Not clear if these are separate problems from the out of sync msgs.
Would you please send me the output from `dmesg' soon after the system
is started, and tell me the model name and number written on the label
of the mouse? Did the mouse come with this Gateway system? Or did you
buy it separately?
Do you use any keyboard/monitor/mouse switch, such as Cybex KVM
switch? These switch products are know to cause troubles for mice.
Also, please carry out the following test so that I can get some
information about your mouse.
1. Switch to vty1 or vty2 (Press Alt-F2 or Alt-F3). Login as root.
2. Kill moused if it is running.
3. Run moused as follows:
moused -i all -d -p /dev/psm0
It will show some information about the mouse.
4. Run moused in the foreground mode as follows:
vidcontrol -m on
moused -f -p /dev/psm0
Move mouse and see if the mouse cursor moves correctly.
Hit ^C to kill moused.
5. Run moused in the debug mode as follows:
moused -d -f -p /dev/psm0 -l 2
When you move the mouse or click buttons, you will see moused
will dump data bytes it receives from the mouse.
Please capture its output using `script' command and send it
to me.
Hit ^C to kill moused.
>How-To-Repeat:
>start moused; move mouse
>Fix:
>The old FAQ150 workaround of giving moused "flags" of 0x100
>doesn't work -- moused no longer accepts that as input arg.
>Quick hardcoded hacks to moused.c didn't help.
'flags 0x100' is not for moused; it's for the psm driver. This flag
is still valid and accepted by the psm driver. See the man page for
psm(4).
(But, I don't know if this flag will entirely solve the problem in
your particular case.)
Kazu
yokota@FreeBSD.ORG
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905280310.UAA81429>