From owner-freebsd-stable Sun Apr 25 12:12:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kleopatra.acc.umu.se (kleopatra.acc.umu.se [130.239.18.150]) by hub.freebsd.org (Postfix) with ESMTP id EE48315564 for ; Sun, 25 Apr 1999 12:12:07 -0700 (PDT) (envelope-from saska@acc.umu.se) Received: from hirohito.acc.umu.se (saska@hirohito.acc.umu.se [130.239.18.140]) by kleopatra.acc.umu.se (8.9.3/8.9.3) with ESMTP id VAA32004 for ; Sun, 25 Apr 1999 21:12:05 +0200 Date: Sun, 25 Apr 1999 21:12:04 +0200 (CEST) From: Markus Holmberg To: freebsd-stable@freebsd.org Subject: moused problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi.. Running FreeBSD-STABLE (3.1). I've had a problem with moused for a while now, which is that there seems to be a race condition if it will work or not. I load moused like this: "moused -p /dev/mouse -t intellimouse" When it doesn't work, I simply don't get any response by moving the mouse. This happens about 1/3 of the times when I boot. It usually helps to kill -9 moused and try to reload it a few times (up to 10 times). I have checked that the hardware is ok, and it works fine in Windows NT. One thing that especially quizzes me is that the mouse always correctly detects the mouse type (intellimouse) when running "moused -p /dev/mouse -i all", even immediately before and after I try to (re)start moused without success. Something that might be of a little help (and more headache for me) is that I had this same problem with Debian 2.1.. randomly not working.. I don't know, but it might still be a software problem of some kind if there's code shared.. Might I be doing something wrong, or is there someone out there with the same experiences and maybe a solution to this (frustrating) problem? Thanks in advance.. /Markus -- Markus Holmberg | Give me UNIX or give me a typewriter. saska@acc.umu.se | http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message