From owner-freebsd-questions Wed Jan 8 16:19: 6 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA3BE37B401 for ; Wed, 8 Jan 2003 16:19:02 -0800 (PST) Received: from freddy.inty.net (freddy.inty.net [195.224.93.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FA2643EDC for ; Wed, 8 Jan 2003 16:19:00 -0800 (PST) (envelope-from chris@furrie.net) Received: from inty.furrie.net (furrie.net [213.208.115.165]) by freddy.inty.net (8.11.6/8.11.6) with ESMTP id h090Ipf91401 for ; Thu, 9 Jan 2003 00:18:51 GMT Received: from furriebox.furrie.net ([10.6.8.5]) (authenticated bits=0) by inty.furrie.net (8.12.1/8.12.1) with ESMTP id h090If68005563 for ; Thu, 9 Jan 2003 00:18:41 GMT Subject: Re: Mouse Murder From: Christopher J Phillips To: freebsd-questions@freebsd.org In-Reply-To: <3E1CBD0A.6000207@ucsb.edu> References: <1042070481.244.28.camel@furriebox.furrie.net> <3E1CBD0A.6000207@ucsb.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 09 Jan 2003 00:18:41 +0000 Message-Id: <1042071522.244.42.camel@furriebox.furrie.net> Mime-Version: 1.0 X-Sender-IP: 10.6.8.5 X-Been-Processed: yes X-INT-DeliveryDone: h090If68005563 X-suppress-rcpt-virus-notify: yes X-Skip-Virus-Check: yes X-Virus-Checked: 2038 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, I'll try with another mouse ps2 style & see if it is any different. As far as killing the moused, I'd be fine if I knew exactly how to restart it, to see if that will fix the problem without rebooting... I believe it's currently set up as /dev/sysmouse. I have not actually needed to "set it up" as simply starting the mouse demon in /stand/sysinstall makes it work. I have not configured it since. MS Windows sees the mouse pad as a ps2 mouse. Thanks Randall On Thu, 2003-01-09 at 00:06, randall s. ehren wrote: > your mouse may just be bad. windows might be compensating better than > XFree86 can for the jitters. > > you can try kill -9 if kill -1 doensn't work, but that won't fix any > hardware problems. > > -randall > > > Christopher J Phillips wrote: > > Chris suggested killing moused like this: - > > > > furrie@furriebox% ps -ax | grep moused > > 123 ?? Ss 0:00.70 moused -p /dev/psm0 -t auto > > furrie@furriebox% kill -1 123 > > furrie@furriebox% ps -ax | grep moused > > 123 ?? Ss 0:00.70 moused -p /dev/psm0 -t auto > > > > The process is still there & my pointer aim problems continue :-( > > > > Should the pid change? > > > > Having tried it like this & my mouse still not aiming correctly, I'm > > losing hope... Unless you guys can provide any? > > > > --- Previously I wrote --- > > During X sessions, my mouse pointer is fine (usually). Intermittently, > > and without any "obvious" reason, the mouse pointer aim "shifts" > > approximately 1.3cm to the right of where the actual pointer is acting. > > > > I feel like I have to explain further as its "that weird"... > > > > If I wanted to select the ***** section, in the "Test Area:" below, I > > would position my cursor / pointer in front of the first * & then > > click_n_drag to the right, till all the *s were selected. In fact what > > actually happens is that I'd have the @@@@@s selected instead. That's > > how far out of alignment it goes. It makes things a bit difficult using > > windows & dialog boxes, when you have to place the pointer over one > > button, to be able to press another! > > > > Test Area: @@@@@***** > > > > This "weirdness" also happened when I was using Linux Mandrake 8.2, > > (before I discovered what a great idea FreeBSD is ;-) > > Not wanting to sound (too) lame, this didn't ever occur when I used > > Windows 2k Pro or XP Pro. > > I get the same problem when in either GNOME or KDE. > > I had it when I installed FreeBSD 4.7 RELEASE & still have it after > > updating (tracking STABLE), using CVSup. > > > > A reboot is all that will get things back on track for me. I know how > > to kill moused but I am not sure how to restart it within or without X > > from the command line (which I might be able to reach without a mouse, > > right?)... > > I suppose I could exit X, kill moused, restart it, then get back into X, > > but I'd still need to know how to run moused (OK, I'm sounding lame > > now). > > > > Just in case you need it: - > > > > My Hardware: > > Compaq Evo N150 Laptop > > 800MHz Intel Celeron CPU > > Upgraded to 320MB RAM, (when purchased) > > > > Uname -a: > > FreeBSD furriebox.furrie.net 4.7-STABLE FreeBSD 4.7-STABLE #1: Sun Jan > > 5 19:39:40 GMT 2003 > > root@furriebox.furrie.net:/usr/obj/usr/src/sys/FURRIEBOX i386 > > > > Can anybody point me in the right direction for maybe a some logs that I > > can peruse to see if anything obvious is afoot? I'm a fan of RTFM but > > could do with a helpful nudge in the right direction... > > > > > > > > intY has scanned this email for all known viruses (www.inty.com) > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > -- > - randall s. ehren :// 805.893.5632 > systems administrator :// isber|survey|avss.ucsb.edu > institute for social, behavioral, and economic research > > > intY has scanned this email for all known viruses (www.inty.com) > > intY has scanned this email for all known viruses (www.inty.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message