Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Jul 2001 17:02:53 -0400
From:      User & Ian Patrick Thomas <ipthomas_77@yahoo.com>
To:        Matt Crawford <crawdad@fnal.gov>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Problem with sysmouse protocol or XFree86 4.0
Message-ID:  <20010719170253.B1458@localhost>
In-Reply-To: <200107191534.f6JFYXF23511@gungnir.fnal.gov>; from crawdad@fnal.gov on Thu, Jul 19, 2001 at 10:34:33AM -0500
References:  <200107191534.f6JFYXF23511@gungnir.fnal.gov>

next in thread | previous in thread | raw e-mail | index | archive | help
As it was put forth by Matt Crawford on Thu, Jul 19, 2001 at 10:34:33AM -0500...
> I've just done a from-scratch reinstallation of FreeBSD 4.3 with
> XFree86 4.0.2 on a Sony Vaio laptop with an ALPS glidepoint
> touchpad.  (I don't know how much of this is relevant.)  If I run
> "moused -3 -p /dev/psm0" the mouse works find in the system console
> mode.  But then using the following mouse definitions in XF86Config:
> 
> Section "InputDevice"
> # Identifier and driver
>     Identifier	"Mouse1"
>     Driver	"mouse"
>     Option "Protocol"    "SysMouse"
>     Option "Device"      "/dev/sysmouse"
> EndSection
> # ...
> Section "ServerLayout"
> # The Identifier line must be present
>     Identifier  "Simple Layout"
>     Screen "Screen 1"
>     InputDevice "Mouse1" "CorePointer"
>     InputDevice "Keyboard1" "CoreKeyboard"
> EndSection
> 
> 
> I diagnose the following problem with the help of xev: ButtonRelease
> events are not being received until the next ButtonPress or
> MotionNotify event.
> 
> If I kill moused and run the server as 'XFree86 -layout "Raw Mouse Device"'
> with the following sections added to XF86Config, everything works
> great, including taps on the touchpad being interpretted as button 1:
> 
> 
> Section "InputDevice"
> # Identifier and driver
>     Identifier  "Mouse0"
>     Driver      "mouse"
>     Option "Protocol"    "PS/2"
>     Option "Device"      "/dev/psm0"
> # Emulate3Buttons is an option for 2-button Microsoft mice
> # Emulate3Timeout is the timeout in milliseconds (default is 50ms)
>     Option "Emulate3Buttons"
>     Option "Emulate3Timeout"    "100"
> EndSection
> # ...
> Section "ServerLayout"
> # The Identifier line must be present
>     Identifier  "Raw Mouse Device"
>     Screen "Screen 1"
>     InputDevice "Mouse0" "CorePointer"
>     InputDevice "Keyboard1" "CoreKeyboard"
> EndSection
> 
> 
> So I don't know if this is a problem in moused or in X ..
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
	I have had problems using sysmouse in X also.  This is a regular
ps/2 logitech with three buttons.  Buttons do not respond well and it
takes alot more movement to get the pointer across the screen.  I 
switched to using the raw mouse support in X as it works much better.
I'm currently working on a script that would suspend moused or stop it
once X starts and restart it once I exit out of an X session.  I'll post 
it to the list if it is any good.

Ian


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010719170253.B1458>