From owner-freebsd-questions Thu Oct 29 11:35:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09511 for freebsd-questions-outgoing; Thu, 29 Oct 1998 11:35:44 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from europa.com (thetics.europa.com [199.2.194.14]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA09506 for ; Thu, 29 Oct 1998 11:35:42 -0800 (PST) (envelope-from nesius@europa.com) Received: from localhost (3141 bytes) by europa.com via sendmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Thu, 29 Oct 1998 11:35:32 -0800 (PST) (Smail-3.2.0.98 1997-Oct-16 #2 built 1997-Oct-19) Message-Id: From: nesius@europa.com (Robert Nesius) Subject: Re: Mouse In-Reply-To: <199810291622.IAA13680@stennis.ca.sandia.gov> from "Bruce A. Mah" at "Oct 29, 98 08:22:36 am" To: bmah@CA.Sandia.GOV Date: Thu, 29 Oct 1998 11:35:31 -0800 (PST) Cc: freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL37 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First off - thanks to everyone for their responses at this point. Bruce A. Mah on -268446040 wrote: > > specified the moused_protocol in rc.conf to be many things, > > including ps/2, logitech, busmouse, mouseman, etc... With > > ps/2 as the protocol, moused complains about a "-t" option. > > And how exactly does it complain? I used "-t auto" (see below) to let moused > try to figure out what the mouse is via PnP. > > Here are my moused-related options from /etc/rc.conf: > > moused_enable="YES" # Run the mouse daemon. > moused_type="auto" # See man page for rc.conf(5) for available settings. > moused_port="/dev/cuaa0" # Set to your mouse port. > moused_flags="" # Any additional flags to moused. > With these options, during boot time I get: rc.i386 configuring syscons: mousedmoused: unable to open -t: No such file or directory. > My gut feeling is that the problem lies before this point...for something > easier to test, see if "vidcontrol -m on" will give you a text-mode mouse > cursor. I don't get a text-mode mouse. > > c) How can I confirm that moused really found a device to talk to? > > d) How can I confirm that cuaa0 is really the device to point moused at? > > Try... > > /usr/sbin/moused -i all -t auto -p /dev/cuaa0 > > ...which should tell you something about the mouse. On my system, I get > /dev/cuaa0 serial mouseman generic > What do you get for this? I get: /usr/sbin/moused -i all -t auto -p /dev/cuaa0 /dev/cuaa0 unknown unknown generic /usr/sbin/moused -i all -t logitech -p /dev/cuaa0 /dev/cuaa0 unknown logitech generic The second set of output seems to be generated with all the other protocol types too. I also tried /dev/cuaa0 and /dev/cuaa1 with the mouse attached to each of the DB9 serial ports. I also tried the /stand/sysinstall, and used the configuration area for the mouse. I tried about every combination of ports, protocols, with the mouse also plugged into each port. Someone mentioned possible IRQ conflicts. What's the best way to check for these? I don't use PCs in general. I've always used Unix boxes and Macs. This is the first box with Intel hardware I've had to configure. > Bruce. > >PS. By any chance is there a switchbox between the FreeBSD box and the mouse? > I'm having some odd problems in which moused's PnP detection fails in this > configuration, which I've partially solved by merging in some of the moused > code from -CURRENT. No switch box. Let me know if I haven't answered any further requests for info - I've tried to answer them all. Thanks again for everyone's help. Thanks! -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message