Date: Wed, 13 Aug 2014 12:14:20 +0200 From: Polytropon <freebsd@edvax.de> To: David Benfell <benfell@parts-unknown.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Kensington Mouse, was Re: operation not permitted on entropy file Message-ID: <20140813121420.2769b8ad.freebsd@edvax.de> In-Reply-To: <20140813100139.GB5311@home.parts-unknown.org> References: <20140811101822.41851cc7.freebsd@edvax.de> <20140811142707.GA10186@home.parts-unknown.org> <CA%2BtpaK2RC0w7Y4etxs%2Byx59_gAURNEtB38h=sV8pEFkBRWVFWQ@mail.gmail.com> <20140811171653.b7c60e58.freebsd@edvax.de> <20140811153535.GA30506@home.parts-unknown.org> <20140811183912.ef0f20a6.freebsd@edvax.de> <20140812023229.GB84770@home.parts-unknown.org> <alpine.BSF.2.11.1408121837430.66504@wonkity.com> <20140813011849.GC25757@home.parts-unknown.org> <20140813103139.ec75155d.freebsd@edvax.de> <20140813100139.GB5311@home.parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Aug 2014 03:01:39 -0700, David Benfell wrote:
> I unplugged the mouse--a Kensington trackball--from my notebook and
> plugged it into the server. It still took a couple tries to get moused
> to run. For one thing 'auto' for moused_type really does need to be in
> lower case; it won't recognize 'AUTO'.
This is correct; "man moused" states:
-t type
Specify the protocol type of the mouse attached to the port. You
may explicitly specify a type listed below, or use auto to let
the moused utility automatically select an appropriate protocol
for the given mouse. If you entirely omit this option in the
command line, -t auto is assumed.
So it can be omitted.
> The other thing is I had to
> specify moused_port.
That would probably be /dev/ums0.
> But by the time I got into X, the mouse was unresponsive.
This is to be expected, because it now interferes with HAL.
The autodetection magic doesn't work anymore.
> Could it be that my favorite trackball doesn't get along with FreeBSD
> so well?
That is possible. Some _few_ mice and trackballs don't play nice
with the protocol standards. On "Windows", the manufacturer usually
provides a proprietary driver that gets you around the issues and
therefore "just works" - implementing all the non-standard things.
On FreeBSD, the system assumes that _if_ the device identifies
itself as a mouse, _then_ it has to understand the corresponding
protocol. If it doesn't... well... no soup for you. ;-)
In case you want to check with moused, use it in non-daemon mode
and have it output diagnostic messages:
# moused -f -d -t auto -p /dev/ums0
You can also try to get information with
# moused -p /dev/ums0 -i all
while moused is _not_ running.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140813121420.2769b8ad.freebsd>