[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: X upgrade, Wheel mouse stopped working -fixed



On Friday 20 February 2004 09:40 pm, Erik Steffl wrote:
> Graham Campbell wrote:
> > On Friday 20 February 2004 08:14 pm, Erik Steffl wrote:
> >>Graham Campbell wrote:
> >>>I just applied the latest X upgrades to Woody. My wheel mouse stopped
> >>>scrolling (rest works ok). Here is the relevant entries from
> >>>/etc/X11/XF86Config-4 :
> >>>Section "InputDevice"
> >>>        Identifier      "Configured Mouse"
> >>>        Driver          "mouse"
> >>>        Option          "CorePointer"
> >>>        Option          "Device"                "/dev/psaux"
> >>>        Option          "Protocol"              "ImPS/2"
> >>>        Option          "Emulate3Buttons"       "true"
> >>>        Option          "ZAxisMapping"          "4 5"
> >>>EndSection
> >>>
> >>>Section "InputDevice"
> >>>        Identifier      "Generic Mouse"
> >>>        Driver          "mouse"
> >>>        Option          "SendCoreEvents"        "true"
> >>>        Option          "Device"                "/dev/input/mice"
> >>>        Option          "Protocol"              "ImPS/2"
> >>>        Option          "Emulate3Buttons"       "true"
> >>>        Option          "ZAxisMapping"          "4 5"
> >>>EndSection
> >>
> >>   what does xev say? are you running gpm?
> >
> > xev says nothing when I roll the wheel.
> > I am not running gpm (as far as I know - this is a new distribution for
> > me)
>
>    try different protocol (for logitech I use MouseManPlusPS/2), I know
> it didn't always work the way docs said (as far as I can tell) so maybe
> the protocol you use doesn't work for your mouse anymore. Make sure that
> you change protocol of the mouse that is actually used (later in the X
> config)
>
> 	erik
Problem fixed by reverting to an old version of XF86Config-4. Unfortunately 
due to fuzzy thinking and fumble fingers, I no longer have the version that 
caused the problem, so I cannot guess what the change was that caused the 
problem. However the Mouse configuration entries were the same between the 
two!!
-- 
Graham
gc@bnl.gov
aka gc1111@optonline.net



Reply to: