From owner-freebsd-questions@FreeBSD.ORG Wed Aug 13 10:14:22 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 71EF363D for ; Wed, 13 Aug 2014 10:14:22 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F1B2201A for ; Wed, 13 Aug 2014 10:14:21 +0000 (UTC) Received: from r56.edvax.de (port-92-195-111-1.dynamic.qsc.de [92.195.111.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 54B192775A; Wed, 13 Aug 2014 12:14:20 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s7DAEKZV002564; Wed, 13 Aug 2014 12:14:20 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Wed, 13 Aug 2014 12:14:20 +0200 From: Polytropon To: David Benfell 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> <20140811171653.b7c60e58.freebsd@edvax.de> <20140811153535.GA30506@home.parts-unknown.org> <20140811183912.ef0f20a6.freebsd@edvax.de> <20140812023229.GB84770@home.parts-unknown.org> <20140813011849.GC25757@home.parts-unknown.org> <20140813103139.ec75155d.freebsd@edvax.de> <20140813100139.GB5311@home.parts-unknown.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 10:14:22 -0000 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, ...