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

Re: Another mouse issue+Xorg after upgrade



On 03/31/2011 11:49 PM, tv.debian@googlemail.com wrote:
>> 01/04/2011 03:52, ZephyrQ wrote:
>>> On 03/31/2011 01:45 AM, Andrei Popescu wrote:
>>>> On Mi, 30 mar 11, 22:09:15, ZephyrQ wrote:
>>>>
>>>> Is it that the boot-up is not reading it?
>>>  
>>> Please boot, count to ten, replug your mouse and then post the full 
>>> output of 'dmesg'.
>>>
>>> Did you already replug the mouse? Because I see this:
>>>
>>>> (II) config/udev: Adding input device Logitech Trackball 
>>>> (/dev/input/event5)
>>> Is your "mouse" a Trackball? Later:
>>
>> Yes, it is.  The same I've used through 3 stable releases. (not the same
>> physical trackball, but I've used the same brand/type for years...)
>>
>>>> (II) config/udev: Adding input device Logitech Trackball (/dev/input/mouse0)
>>>> (II) No input driver/identifier specified (ignoring)
>>>
>>> which might be related to your problem. Please attach the full xorg.conf 
>>> used.
>>
>> Xorg.conf first, then after full output of dmesg:
>>
>> # nvidia-xconfig: X configuration file generated by nvidia-xconfig
>> # nvidia-xconfig:  version 1.0  (pbuilder@windlord)  Sun Jun 13 06:03:17
>> UTC 2010
>>
>>
>> Section "InputDevice"
>>     # generated from default
>>     Identifier     "Mouse0"
>>     Driver         "mouse"
>>     Option         "Protocol" "auto"
>>     Option         "Device" "/dev/psaux"
>>     Option         "Emulate3Buttons" "no"
>>     Option         "ZAxisMapping" "4 5"
>> EndSection
> 
> [snip]
> 
> Hi, I also use a logitech trackball (the cordless one with a blue ball
> currently) and this is what I use on Squeeze and Wheezy (mind the line
> wrapping) :
> 
> Section "InputDevice"
>   Identifier     "Mouse0"
>   Driver         "evdev"
>   Option "Device" "/dev/input/by-id/usb-Logitech_Trackball-event-mouse"
> EndSection
> 
> 
> "man evdev" will give you a list of valid options you may need.
> 
> Without this in my xorg.conf I have the same problem you are facing, the
> device initialisation is unreliable.
> 
> Hope it helps.

That seems to have done the trick.  I tried evdev before, but had the
'device' option wrong...

Thank you for the help!


Reply to: