From owner-freebsd-stable@FreeBSD.ORG Wed Mar 26 23:49:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 185F3106566B for ; Wed, 26 Mar 2008 23:49:19 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id CBDFA8FC15 for ; Wed, 26 Mar 2008 23:49:18 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de [129.13.72.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 48F75405C67; Thu, 27 Mar 2008 00:49:17 +0100 (CET) Message-ID: <47EAE0F8.8070707@bsdforen.de> Date: Thu, 27 Mar 2008 00:49:12 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.12 (X11/20080310) MIME-Version: 1.0 To: Cory References: <57200BF94E69E54880C9BB1AF714BBCB5DDD0A@w2003s01.double-l.local> <259066688.20080326233038@gmail.com> In-Reply-To: <259066688.20080326233038@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: mouse issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2008 23:49:19 -0000 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.