Date: Sat, 26 Aug 2000 10:10:01 -0700 From: Gary Kline <kline@thought.org> To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> Cc: Gary Kline <kline@thought.org>, freebsd-stable@FreeBSD.ORG Subject: Re: mouse question.... Message-ID: <20000826101000.A23999@tao.thought.org> In-Reply-To: <200008260746.QAA26455@zodiac.mech.utsunomiya-u.ac.jp>; from yokota@zodiac.mech.utsunomiya-u.ac.jp on Sat, Aug 26, 2000 at 04:46:58PM %2B0900 References: <200008250449.VAA05812@tao.thought.org> <200008260746.QAA26455@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 26, 2000 at 04:46:58PM +0900, Kazutaka YOKOTA wrote: > > > This is a long shot, but here goes. --On my other FBSD system > > which is as 4.0, the mouse won't work. A friend just checked > > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > > nothing. He tried the mouse on this system on the other. Again, > > nothinng. He thinks that in my upgrading to 4.0, part of my > > mouse software may have been hosed. > > > > Any suggestions how I can diagnose the software side of this? > > > > I'm stumped. > > It is not easy to determine what is wrong based on relatively > few information. > > Please do the following to diagnose the problem. > > 1. Hook up the mouse (it's a serial mouse, right?) to COM1 > > 2. Become root. > > 3. Don't run X yet. Kill `moused' if it is already running. > (Run "ps aux | grep mouse" to see if it is running. Kill it if any.) > > 4. Run moused in the information mode as follows: > moused -p /dev/cuaa0 -i all > You should get some information if the mouse is a PnP mouse or a > Microsoft-compatible mouse. Something like: > /dev/cuaa0 serial microsoft generic > > 5. Run moused again, this time in the debug mode: > moused -p /dev/cuaa0 -d -f > If you move mouse and click buttons, you should see mouse status > information should be printed. Type ^C to stop moused. > If this seems Ok, then you should edit /etc/rc.conf and > put the following lines there: > moused_enable="YES" > moused_type="auto" > moused_port="/dev/cuaa0" > Then, edit /etc/XF86Config and set the mouse protocol to "Auto" and > the mouse device to "/dev/sysmouse". > Start moused in the daemon mode by hand for now (this will automatically > done the next time the system is rebooted.) > moused -p /dev/cuaa0 -t auto > > 6. If moused says 'cannot determine mouse type...' in 4, the mouse > may be a MouseSystems-compatible mouse, or it may be broken. > If the mouse is considered MouseSystems-compatible, you can > test the mouse as follows: > moused -p /dev/cuaa0 -d -f -t mousesystems > If this is successful Ok, then you should edit /etc/rc.conf and > put the following lines there: > moused_enable="YES" > moused_type="mousesystems" > moused_port="/dev/cuaa0" > Edit /etc/XF86Config and set the mouse protocol to "Auto" and > the mouse device to "/dev/sysmouse". > Start moused in the daemon mode by hand for now (this will automatically > done the next time the system is rebooted.) > moused -p /dev/cuaa0 -t mousesystems > > Hope this might help.... > This has been very helpful. It tells me (I believe) that my upgrade installation of 4.0 was|is *not* faulty. And that the mouse is probably bad. Here is the output from (4) above: sage# moused -p /dev/cuaa0 -i all moused: cannot determine mouse type on /dev/cuaa0 /dev/cuaa0 unknown unknown generic And from (6): sage# moused -p /dev/cuaa0 -d -f -t mousesystems moused: port: /dev/cuaa0 interface: unknown type: mousesystems model: generic This mouse was an inexpensive give-away, switchable between "MS" and "PS/2", but even if I switch to the PS/2 setting, I get the same ``cannot determing'' diagnostic. It's time to buy a new mouse! Thanks very much for your help, gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000826101000.A23999>