Date: Wed, 2 Apr 2008 14:29:27 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: freebsd-ports-bugs@FreeBSD.org, freebsd-x11@FreeBSD.org Subject: Re: ports/122363: x11-servers/xorg-server 1.4_7, 1 locks up on mouse detection Message-ID: <alpine.BSF.1.10.0804021412300.79814@wonkity.com> In-Reply-To: <200804021546.14393.jkim@FreeBSD.org> References: <200804020055.m320tEKh075558@freefall.freebsd.org> <200804021314.12780.jkim@FreeBSD.org> <alpine.BSF.1.10.0804021314060.79600@wonkity.com> <200804021546.14393.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Apr 2008, Jung-uk Kim wrote: > Nothing seems obviously wrong to me. :-( In fact, I was not able to > replicate the problem, i.e., hal, xorg-server, USB mouse, PS/2 mouse, > and moused on /dev/ums0. Is moused running on /dev/ums0 > and/or /dev/psm0? > > ps -p `pgrep -x moused` > > If not, please add the following line in /etc/rc.conf and reboot: > > moused_enable="YES" moused_enable was "NO", and enabling it fixes the problem, allowing xorg-server to continue startup. The new requirement for moused should be mentioned in /usr/ports/UPDATING. The combination of moused disabled, hald, and xorg-server 1.4_7 stops/locks on mouse detection and prevents keyboard console switching. That seems like a bug. New xorg log XINPUT section: (II) evaluating device (Keyboard0) (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) evaluating device (Mouse0) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse, level is 1 ...and continues on, unlike the earlier log. -Warren Block * Rapid City, South Dakota USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0804021412300.79814>