Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Jun 2012 15:39:22 +0000 (UTC)
From:      Walter Hurry <walterhurry@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   FreeBSD: SOLVED: FreeBSD9 - I can't get my mouse to work (was : FreeBSD9 - I can't get my mouse to work)
Message-ID:  <jqt6ba$r15$1@dough.gmane.org>
References:  <jqm3sr$1l5$1@dough.gmane.org> <CADGWnjUBP73DdS3Nk%2Bu635duPM6h4Cv7CZTMv3BBZ590q14kSg@mail.gmail.com> <CADGWnjUadM-rjZwaPtcQUbYUf-moTyN0bdE-M4eFYGb1UkDGbw@mail.gmail.com> <20120607145901.3022770d@scorpio>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 07 Jun 2012 14:59:01 -0400, Jerry wrote:

> Ubuntu,
> Debian, and Fedora, and projects such as KDE, GNOME and X.org are in the
> process of deprecating HAL as it has "become a large monolithic
> unmaintainable mess".

Well, I finally got it working. I'm far from an expert in this area, but 
what I think was happening was that the touchpad was grabbing /dev/psm0, 
and then X.org tried to allocate the same port for the USB mouse, which 
of course failed (even though I had specified a Device of /dev/ums0, and 
set AutoAddDevices to Off so as to take hald out of the picture).

The solution for me was to run moused *on port /dev/ums0* and then 
specify the device as /dev/sysmouse in xorg.conf.

However, that leads me to another question: my amateurish way to get 
moused to run on /dev/ums0 was to hack /etc/rc.d/moused and hard code it. 
I don't think that's very good, and I suspect that the "right" way to do 
it was to set some variable in /etc/rc.conf.

Can anyone guide me on how that should be done, or point me to a fine 
manual?

Thamks to all for the responses.  




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jqt6ba$r15$1>