Date: Thu, 22 Jul 1999 03:34:34 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Greg Lynn <dglynn@vaview5.vavu.vt.edu> Cc: freebsd-stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: sio problems on 3.2 Message-ID: <199907211834.DAA24529@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Wed, 21 Jul 1999 14:15:27 -0400." <Pine.BSF.3.96.990721135858.16702B-100000@vaview5.vavu.vt.edu> References: <Pine.BSF.3.96.990721135858.16702B-100000@vaview5.vavu.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>I posted the other day about sio problems and >it seems that I'm still having trouble. Below >is various output for sio (cuaa0). I'm trying to >get the darn mouse to work ( to get X up and be done >with it!) but I'm running into problems. For one, >I can't seem to debug this problem so if ANYONE knows >what I can do at the kernel level to produce a more >detailed message please let me know. > >The problem is that moused doesn't seem to work >on cuaa0. I've looked in /etc/ttys to see if any getty >is on sio0 (in/out) and there doesn't seem to be. Is >there any thing else I can check that would be locked >on that port? I haven't installed any progs that use >that port and are loaded up from an rc file. One >interesting thing from the output of the command: > >moused -i all -p /dev/cuaa0: > >moused: cannot determine mouse type on /dev/cuaa0 >/dev/cuaa0 unknown unknown generic Ok, the problem seems to be with the mouse, rather than the serial port. Give me some more details about your serial mouse. What model from which manufacuture is it? I suspect it's rather an old model, because moused should be able to detemine the protocol type if it is one of newer PnP seiral mice. Kazu 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?199907211834.DAA24529>