Date: Fri, 28 Mar 2008 14:08:53 +1100 From: Norberto Meijome <freebsd@meijome.net> To: Dominic Fandrey <kamikaze@bsdforen.de> Cc: freebsd-stable@freebsd.org, Cory <cory.vm@gmail.com> Subject: Re: mouse issue Message-ID: <20080328140853.4a999225@meijome.net> In-Reply-To: <47EAE0F8.8070707@bsdforen.de> References: <57200BF94E69E54880C9BB1AF714BBCB5DDD0A@w2003s01.double-l.local> <259066688.20080326233038@gmail.com> <47EAE0F8.8070707@bsdforen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Mar 2008 00:49:12 +0100
Dominic Fandrey <kamikaze@bsdforen.de> wrote:
> Cory wrote:
> > Wednesday, March 26, 2008, 1:30:07 PM, Johan wrote:
> >
> 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.
I tried this and it didn't work ( I rebuilt moused , confirmed pentium3 and pentium4 (tried both) were used and installed, rebooted. I also rebuilt + reinstall all of world just in case).
Removing moused from rc.conf fixes the problem (but leaves me w/o usb mouse)
Jun-uk's posting about Xorg-server w/o HAL support did the trick. I'm now working again with moused, usb mouse + touchpad, xorg sans-hal and no crazy refresh/choppiness issues.
thanks!!!
B
________
{Beto|Norberto|Numard} Meijome
I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.
I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080328140853.4a999225>