On Sun, Jun 16, 2013 at 06:01:49PM +0200, Michiel Boland wrote: > On 06/16/2013 17:55, Jeremy Chadwick wrote: > [...] > > >Are you running moused(8)? Actually, I can see quite clearly that you > >are in your core.txt: > > > >Starting ums0 moused. > > > >Try turning that off. Don't ask me how, because devd(8) / devd.conf(5) > >might be involved. > > > > The moused is started by devd - I don't see a quick way of turning that off.
Comment out the relevant crap in devd.conf(5). Search for "ums" and comment out the two "notify" sections. > As a workaround I'm trying to run a kernel with > > options SC_NO_SYSMOUSE > > to see if the hangs go away. That's one way to do it, I guess. Be aware that I do not use X, however I have repeatedly seen mentioned on these lists problems/complexities from where people rely on moused(8) to "drive their mouse" while inside of X (or possibly that X and moused(8) are both simultaneously polling the mouse). There's apparently a very specific kind of X configuration you're supposed to use to get proper mouse/keyboard/HAL/HID/whatever support, and tons of people have it wrongt. Warren Block I think has some insights into this, or could maybe help shed some light on what I'm remembering. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
