From owner-freebsd-current@FreeBSD.ORG Wed Apr 8 07:21:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99519106566B for ; Wed, 8 Apr 2009 07:21:13 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from andxor.it (relay.andxor.it [195.223.2.3]) by mx1.freebsd.org (Postfix) with SMTP id E5D9D8FC08 for ; Wed, 8 Apr 2009 07:21:12 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: (qmail 60279 invoked from network); 8 Apr 2009 07:21:10 -0000 Received: from unknown (HELO ale.andxor.it) (192.168.2.5) by andxor.it with SMTP; 8 Apr 2009 07:21:10 -0000 Message-ID: <49DC5066.1010607@FreeBSD.org> Date: Wed, 08 Apr 2009 09:21:10 +0200 From: Alex Dupre User-Agent: Thunderbird 2.0.0.21 (X11/20090328) MIME-Version: 1.0 To: Robert Noland References: <49D8D03B.8090302@arcor.de> <3a142e750904050919l1388b559t9bbd751546e239e7@mail.gmail.com> <1238957462.1829.8.camel@balrog.2hip.net> <49D90363.6010602@arcor.de> <1238959921.1829.10.camel@balrog.2hip.net> <49DB573C.3020703@FreeBSD.org> <1239129677.1947.14.camel@balrog.2hip.net> In-Reply-To: <1239129677.1947.14.camel@balrog.2hip.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: xorg loops X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2009 07:21:13 -0000 Robert Noland ha scritto: > The root of the issue is that there are just too many ways to configure > input devices... Particularly mice. Marcus, jkim and I have tried to > make accommodations for all of the cases, but it gets rather tricky. > Users can have mice configured using psm0, ums0, (serial even), moused > and we have to be able to figure out if they are statically configured > in X or not, based on whether or not X has already opened one of the > file descriptors. Based on analyzing all of that, we decide whether or > not to advertise to X that it should attach the device. Thanks for your work and explanation. > If you are using moused, then hald *should* recognize that and > advertise /dev/sysmouse to X. Additional input devices, get added via > moused and hald knows that /dev/sysmouse is already opened by X, so it > shouldn't re-advertise the same port again. Actually I have a common USB mouse. xorg.conf contains the following section (autogenerated by "X -configure"): Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection moused is not enabled in rc.conf, but the following process is started at boot by devd: /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid I think this is one of the most common scenario. I use kdm from /etc/ttys, but it shouldn't be related, since I did tests with "X -config" from terminal console with the same results. Is it normal that hal-device doesn't show any mouse? -- Alex Dupre