Date: Thu, 27 Mar 2008 00:49:12 +0100 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Cory <cory.vm@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: mouse issue Message-ID: <47EAE0F8.8070707@bsdforen.de> In-Reply-To: <259066688.20080326233038@gmail.com> References: <57200BF94E69E54880C9BB1AF714BBCB5DDD0A@w2003s01.double-l.local> <259066688.20080326233038@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Cory wrote:
> Wednesday, March 26, 2008, 1:30:07 PM, Johan wrote:
>
>> Now I have a strange issue that I need to move the mouse to see my
>> commands typed I a console or wait a few seconds.
>
> Same here, but I see this behaviour already with the shell windows in Xorg
> (no Gnome or KDE, yet). Typing is blind, only when you move the mose
> pointer, the windows get updated (all of them, not just the active window
> w/ "mouse-over").
>
> I've just recently managed to install REL_7.0 and finally got Xorg to
> display properly (ATi driver issue, now using VESA, see other post).
>
I have found a solution for this. Certain CPU-Types seem to trigger a problem
with moused. This is an example for a make.conf workaround:
# moused bug workaround
.if ${.CURDIR:M*/usr.sbin/moused}
.if defined(CPUTYPE)
.if ${CPUTYPE} == core2
CPUTYPE=athlon64
.elif ${CPUTYPE} == pentium-m
CPUTYPE=pentium3
.endif
.endif
.endif
I suspect the problem is a gcc bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47EAE0F8.8070707>