Date: Tue, 10 Nov 1998 12:40:57 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Mark Turpin <mturpin@saturn.spel.com> Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: psmintr: out of sync Message-ID: <199811100340.MAA14161@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Mon, 09 Nov 1998 15:34:11 EST." <Pine.BSF.4.05.9811091524170.203-100000@saturn.spel.com> References: <Pine.BSF.4.05.9811091524170.203-100000@saturn.spel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I am getting the following error when I run X. Would you describe your system? Motherboard, CPU, X server... >Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (0000 != 0008). >Nov 9 15:13:34 saturn /kernel: psmintr: out of sync (00c8 != 0008). Do you see them often, or just occasionally? Is the mouse working, or is it totally unusable? If the mouse is working and you see the above messages just occasionally, please ignore the messages. The "psmintor: out of sync" message is generated if a) there is mismatch of the mouse protocol; the psm driver is expecting a wrong data format (this is unlikely in your case because your mouse is correctly recognized as NetMouse). If this happens, we need to fix the psm driver; there is a bug somewhere. b) Or, if some data bytes from the mouse are somehow lost. While I don't like this happening, it is relatively harmless because the psm driver should be able to resyunc with the mouse data stream. c) Or, if you are using a display/keyboard/mouse switch box. Some swich box products do not constantly supply power to the mouse and may momentalily cut the power when switching between host computers. This will reset the mouse and lose settings in the mouse which the psm driver has carefully set up. This may lead to out-of-sync situation sooner or later. Other switch products do supply power OK, but its built-in CPU tries to emulate/translate mouse data. The problem is that the firmware of the built-in CPU is sometimes just buggy or is not good enough and may confuse the psm driver. >An older message said to try adding flags 0x100 to the device line in the >kernel config file. That did make the errors stop. Do you mean that the mouse was not working but now works because of the flags 0x100? Or, the mouse was working and it now works too AND there is no more error messages? >The mouse is a Genius NetMouse Pro. Below are the startup messages. > [...] >Nov 9 15:19:07 saturn /kernel: psm0: current command byte:0065 >Nov 9 15:19:07 saturn /kernel: kbdio: TEST_AUX_PORT status:0000 >Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX return code:00fa >Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX status:00aa >Nov 9 15:19:07 saturn /kernel: kbdio: RESET_AUX ID:0000 >Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64 >Nov 9 15:19:07 saturn /kernel: psm: status 00 03 06 >Nov 9 15:19:07 saturn /kernel: psm: status 00 33 55 >Nov 9 15:19:07 saturn /kernel: psm: data 18 ff 00 >Nov 9 15:19:07 saturn /kernel: psm: status 00 02 64 >Nov 9 15:19:08 saturn /kernel: psm0 at 0x60-0x64 irq 12 on motherboard >Nov 9 15:19:08 saturn /kernel: psm0: model NetMouse, device ID 0, 3 buttons >Nov 9 15:19:08 saturn /kernel: psm0: config:00000000, flags:00000000, packet >size:4 >Nov 9 15:19:08 saturn /kernel: psm0: syncmask:c8, syncbits:08 NetMouse Pro is a variant of NetMouse. Looks like it is correctly recognized. Kazu yokota@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811100340.MAA14161>