Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!howland.reston.ans.net!newsfeed.internetmci.com!uwm.edu!homer.alpha.net!usenet From: molson@milwaukee.rbvdnr.com (Matto) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Help: Dead mouse in XFree86 Date: 28 Dec 1995 18:33:12 GMT Organization: Your Organization Lines: 31 Message-ID: <4bunt8$19q@homer.alpha.net> References: <4brhb7$k17@ns1.tstt.net.tt> <4bubn9$ep7@ra.ibr.cs.tu-bs.de> NNTP-Posting-Host: 156.46.64.73 X-Newsreader: WinVN 0.92.6+ In article <4bubn9$ep7@ra.ibr.cs.tu-bs.de>, y0001415@ws.rz.tu-bs.de (Martin Butkus) says: > >feisal@tstt.net.tt wrote: >: From: molson@milwaukee.rbvdnr.com (Matto) >: >The cursor appears on the screen but X doesn't respond to >: >the mouse. I have a bus mouse connected to COM1. I haven't >: >been able to "find" the connection using "cat /dev/mouse" or >: >"cat /dev/cuaa*". I'm sure this is the problem but I don't > >: Try using "/dev/ttyd1" in your XF86Config, the ttyd are for >: "in" like logging in or mouse while cuaa's are for out like >: modems etc. > >: -Feisal > >Wrong: use /dev/ttyd0. BTW, some Logitech mice require a different baud rate >than the standard 1200 bps. Been there-done that. Still doesn't work. BTW it's a Mouse Systems serial mouse-not a bus mouse, my mistake. I'm now checking to be sure my external serial port is actually set as COM1. I get no response from cuaa0,cuaa1,ttyd0,or ttyd1. Both COM1 and COM2 are found and configured by the kernel. I understand that tty's are for dial-in and cuaa's are for dial-out devices, but why do some people say they are finding their mice on a cuaa* device? Someone please explain this to me. Any other help on this serial mouse thing would be appreciated. Also, what's a good way to test your modem? Thanks, Matto (I'm getting there)