Date: Sat, 26 Aug 2000 20:21:52 -0700 (PDT) From: Gary Kline <kline@thought.org> To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Cc: kline@thought.org (Gary Kline), freebsd-stable@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: mouse question.... Message-ID: <200008270321.UAA28285@tao.thought.org> In-Reply-To: <200008260746.QAA26455@zodiac.mech.utsunomiya-u.ac.jp> from "Kazutaka YOKOTA" at Aug 26, 2000 04:46:58 PM
next in thread | previous in thread | raw e-mail | index | archive | help
According to Kazutaka YOKOTA: > > > 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 > > This is getting stranger and stranger. I just bought a new Logitech mouse and have it plugged directly into the COM1 port. The results are the same as before for trying your (4) above, and moused -p /dev/cuaa0 -d -f -t mouseman moused: port: /dev/cuaa0 interface: unknown type: mouseman model: generic moused: received char 0x0 for the above. The ``received char 0x0'' only happened one time. Does this suggest anything to you? Or anyone else on the list? 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?200008270321.UAA28285>