Date: Wed, 29 Oct 1997 22:35:42 -0400 (GMT-0400) From: Snob Art Genre <ben@multivac.narcissus.net> To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> Cc: hackers@freebsd.org Subject: Re: PS/2 mouse (was: Re: svgalib? ) Message-ID: <Pine.NXT.3.96.971029223337.480A-100000@multivac.narcissus.net> In-Reply-To: <199710300310.MAA11241@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 30 Oct 1997, Kazutaka YOKOTA wrote: > So long as your MouseMan is "Serial-MousePort" type (see label on the > belly of the mouse), it can be attached to the PS/2 port. It can be attached to either the PS/2 port or the serial port. I know because I have attached it to both. > Would you attach the mouse at the PS/2 mouse port, boot your system > giving "-v" option at the "Boot:" prompt and check dmesg output? > You should look for "psm0:..." and "kbdio:..." lines. Thanks, but I'm not interested in debugging the PS/2 connection, since the mouse is working fine as a serial mouse and I don't need the port for anything. > You can also test your PS/2 mouse by doing the following. > > 1. If you run moused, kill it for now. > 2. Stop X either. > 3. As root, run moused in the debug mode. > moused -d -f -p /dev/psm0 -t ps/2 > 4. Move mouse. Moused will print X and Y movement counter and button > status. > 5. ^C will stop moused. > > If you are not sure if the output is correct, I will analyze it for > you if you send me the output. > > There also are following advices: > > 1. If the PS/2 mouse port is not directly soldered on the motherboard > and the mouse port (DIN connector) on the case and the motherboard > is connected via a flat cable, verify it's the write cable and > correctly oriented. One user bought the cable and motherboard separately > and later found that they are not compatible. This can happen > because pin assignment on the motherboard side is not standardized. > The cable for one motherboard (say, from ASUS) may not be used with > another (say, from GIGABYTE). > > 2. XF86Setup isn't good at handling mice. If you are using it to > configure XF86Config, do not touch your mouse until you have specified > everything about the mouse. (device: /dev/psm0, protocol: PS/2) > And do NOT change mouse settings again until you quit XF86Setup. > > Kazu > > > > > Ben "You have your mind on computers, it seems."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NXT.3.96.971029223337.480A-100000>