From owner-freebsd-questions Mon Jan 15 17:49:15 2001 Delivered-To: freebsd-questions@freebsd.org Received: from kraeusen.nbrewer.com (unknown [208.42.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 1A14F37B6A0 for ; Mon, 15 Jan 2001 17:48:58 -0800 (PST) Received: by kraeusen.nbrewer.com (Postfix, from userid 1001) id 7D57A1743E; Mon, 15 Jan 2001 19:48:56 -0600 (CST) Date: Mon, 15 Jan 2001 19:48:56 -0600 From: Christopher Farley To: Jason Hunt Cc: freebsd-questions@freebsd.org Subject: Re: no mouse pointer Message-ID: <20010115194856.B30698@northernbrewer.com> Mail-Followup-To: Christopher Farley , Jason Hunt , freebsd-questions@freebsd.org References: <3A637BA8.CBBC270E@niicommunications.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A637BA8.CBBC270E@niicommunications.com>; from jason.hunt@niicommunications.com on Mon, Jan 15, 2001 at 04:37:28PM -0600 Organization: Northern Brewer, St. Paul, MN Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Hunt (jason.hunt@niicommunications.com) wrote: > > hardware: > > sis6326 8mb video card > xfree86 4.01 > intellimouse explorer (ps/2) > freebsd 4.2 > > problem: > > > mouse acts correclty, but there is no pointer. > have tried, Intellimouse, MouseSystems, auto > for pointer protocol with no lock. Tried > /dev/sysmouse. dev/psm0, dev/mouse with mousd > running and disabled - no luck. > > Anyone have the correct pointer / dev for > this mouse and xfree86? Its the larger > of the two explorers -- the grey one, not > the white. PS/2 mouse configuration should be straightforward on BSD. X does not require moused, so you may certainly kill it entirely, and this will possibly make the configuration easier. PS/2 mice use /dev/psm0, and the protocol is always "PS/2" or "Auto" (does not matter). Personally, I find the /dev/mouse link tends to complicate configuration issues. Cheap KVM switches will complicate the configuration. Reboot the machine with the mouse directly connected if configuration is problematic. It may be easier to diagnose/configure the mouse from console mode, rather than from X. There are some good command-line tools to help with mouse configuration. Consult man moused for details, but here's what I have found useful: Query the mouse with the command 'moused -i all -p /dev/psm0' (for PS/2 mice). That will provide good feedback on your mouse type or protocol, whether it is indeed a ps/2 mouse, etc. You can then test your configurtion with: # vidcontrol -m on # moused -f -p /dev/psm0 -t ps/2 -- Christopher Farley Northern Brewer / 1150 Grand Avenue / St. Paul, MN 55105 www.northernbrewer.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message