Date: Wed, 08 Apr 2009 02:35:18 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: Alex Dupre <ale@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: xorg loops Message-ID: <1239176118.1954.11.camel@balrog.2hip.net> In-Reply-To: <49DC5066.1010607@FreeBSD.org> 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> <49DC5066.1010607@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-afH9t9wMXAM0NK+z2dIB Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2009-04-08 at 09:21 +0200, Alex Dupre wrote: > 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. >=20 > Thanks for your work and explanation. >=20 > > 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. >=20 > Actually I have a common USB mouse. xorg.conf contains the following=20 > section (autogenerated by "X -configure"): >=20 > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection >=20 > moused is not enabled in rc.conf, but the following process is started=20 > at boot by devd: >=20 > /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid Right, all usb mice start moused unless moused_nondefault_enable is set to no in rc.conf. This configuration should be fine, in fact if your using hal, the above is totally ignored. I generally use gnome, unless I'm working on drm drivers that are either broken or don't yet support enough whiz bang to run gnome. In those cases, I'm just using startx to get twm going for basic testing. Your configuration should work fine in all of those cases. kdm and xdm when started from /etc/ttys are still a problem apparently, at least some of the time. > I think this is one of the most common scenario. I use kdm from=20 > /etc/ttys, but it shouldn't be related, since I did tests with "X=20 > -config" from terminal console with the same results. > Is it normal that hal-device doesn't show any mouse? So, I think your issue is probably related to the other thread. "Re: Hal and KDM breakage". robert. --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-afH9t9wMXAM0NK+z2dIB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEABECAAYFAkncU7YACgkQM4TrQ4qfROOoQwCeNUQKEBwGVHZBEaX/C55Wurkz nUYAn1JEy5tSK60v5Gf58zPfm4p7+NEt =N/0p -----END PGP SIGNATURE----- --=-afH9t9wMXAM0NK+z2dIB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1239176118.1954.11.camel>