> Allen,
> What else is plugged into USB? (I.E. the output of lsusb) I've heard
> rumors of certain other USB devices causing mouse problems in ubuntu
> 8.10.
~$ lsusb
Bus 005 Device 007: ID 046d:c041 Logitech, Inc.
Bus 005 Device 005: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage
Device
Bus 005 Device 004: ID 5986:0241 Acer, Inc
Bus 005 Device 003: ID 2001:f103 D-Link Corp. [hex]
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 047b:0002 Silitek Corp. Keyboard and Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
But here, let me unplug everything except the mouse. OK
$ lsusb
Bus 005 Device 005: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage
Device
Bus 005 Device 004: ID 5986:0241 Acer, Inc
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 046d:c041 Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Evidently the SD interface on this laptop interfaces thru USB.
And the problem remains.
> Usually this is a symptom of the system trying to set the pointer
> via another device like a gamepad or such. I had a similar issue a few
> years ago where a touchpad that was going bad interfered with my mouse.
> You could try unplugging all other USB devices or input devices other
> than the keyboard and mouse and see if the problem remains.
There is still the mousepad. I don't know how to disable that.
This is an S10 from Lenovo.
> Ubuntu has moved mouse config out of xorg and into the HAL stuff.
How fitting...
User: I want to configure the mouse
HAL: I'm sorry Dave, I can't let you do that.
> You
> can use "xinput" to see what devices X is recognizing and how they are
> configured. Try "xinput list" to find out what the id for your mouse
> is. Then run "xinput test [idnum]" to capture all events from the
> device to the console for a while. Ctrl+c will stop the capture. if
> you run this you can see whether the events causing the motion come from
> the mouse itself. (I recommend moving the mouse to the upper left corner
> where it should report its location as 0,0) If no events show up then
> the mouse isn't your cause. Test each input device in turn until you
> find the one that is sending the spurious events.
The spurious events only occur when the USB mouse is moving. And
they seem to be the worst when I move the mouse slowest. Moving
the mouse quickly seems to be more accurate. But of course I can't
hit a small target at high speed.
There were ids from 0-6. The first two are virtual and ignored by
"xinput test". The mouse is id=6. It wasn't obvious that the
outputs it produced were wrong. Here is the list output for it.
"Logitech USB Gaming Mouse" id=6 [XExtensionPointer]
Num_buttons is 32
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 1
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 1
And here is some slow motion test output.
motion a[0]=131 a[1]=130
motion a[0]=132 a[1]=131
motion a[0]=133 a[1]=131
motion a[0]=133 a[1]=129
motion a[0]=133 a[1]=130
motion a[0]=133 a[1]=129
motion a[0]=134 a[1]=129
motion a[0]=133 a[1]=129
motion a[0]=134 a[1]=129
motion a[0]=134 a[1]=131
motion a[0]=135 a[1]=131
motion a[0]=134 a[1]=131
motion a[0]=133 a[1]=132
motion a[0]=134 a[1]=132
motion a[0]=134 a[1]=133
motion a[0]=128 a[1]=131
motion a[0]=128 a[1]=130
motion a[0]=127 a[1]=131
motion a[0]=128 a[1]=131
motion a[0]=129 a[1]=131
motion a[0]=125 a[1]=135
motion a[0]=126 a[1]=135
motion a[0]=126 a[1]=127
motion a[0]=126 a[1]=125
motion a[0]=127 a[1]=125
motion a[0]=128 a[1]=126
motion a[0]=127 a[1]=125
motion a[0]=127 a[1]=126
motion a[0]=128 a[1]=126
motion a[0]=128 a[1]=127
motion a[0]=129 a[1]=127
motion a[0]=133 a[1]=131
motion a[0]=133 a[1]=132
motion a[0]=136 a[1]=132
motion a[0]=136 a[1]=131
motion a[0]=137 a[1]=132
motion a[0]=136 a[1]=131
motion a[0]=136 a[1]=130
motion a[0]=135 a[1]=130
motion a[0]=136 a[1]=130
This represented slow smooth continuous motion down and to the right.
So I would expect the numbers to be increasing monotonically.
Instead they go up and down. And there are a couple of jumps,
particularly in the a[1] column. 135->127 and 127->131
> I hope this helps.
> -Mike
>
Well, I'm learning things. I'm just not sure what.
--
Allen Brown
http://brown.armoredpenguin.com/~abrown
> "The Earth is the cradle of the mind, but one cannot eternally live in a
> cradle." - Konstantin E. Tsiolkovsky
> On Tue, 2009-03-24 at 19:59 -0700, Allen Brown wrote:
>> > I've been using USB mice exclusively for several years. Wireless
>> > ones, even. No problems. (Well, occasional problems, but not like
>> > yours.)
>> >
>> > Your symptoms make it sound like you've got a really long polling
>> > interval. It could be a driver problem. It could be an X11 problem.
>> > If you're running a VM or a remote protocol like VNC, synergy, or
>> > xtox, that could be the problem. Or maybe your X server is thrashing.
>>
>> A long polling interval would cause it to jump, but only to the
>> next position, right? What I'm seeing is random directions. It
>> generally trends in the right direction, but with huge jumps in
>> random directions superimposed.
>>
>> > I don't know how to diagnose a driver problem, aside from looking at
>> > the dmesg tea leaves.
>>
>> I just unplugged and replugged the mouse.
>> [40519.102785] usb 5-2.3: USB disconnect, address 6
>> [40526.628354] usb 5-2.4: new full speed USB device using ehci_hcd and
>> address 7
>> [40526.733423] usb 5-2.4: configuration #1 chosen from 1 choice
>> [40526.742749] input: Logitech USB Gaming Mouse as
>> /devices/pci0000:00/0000:00:1d.7/usb5/5-2/5-2.4/5-2.4:1.0/input/input13
>> [40526.780410] input,hidraw2: USB HID v1.11 Mouse [Logitech USB Gaming
>> Mouse] on usb-0000:00:1d.7-2.4
>> [40526.799774] hiddev96hidraw3: USB HID v1.11 Device [Logitech USB
>> Gaming
>> Mouse] on usb-0000:00:1d.7-2.4
>>
>> > If it's a VM or remote protocol problem, you'd notice that it gets
>> > better when you use the local, native host.
>>
>> I'm not using VM or remote. It's all local.
>>
>> > If it's an X11 problem, it could be that you've got multiple mouse
>> > drivers configured in xorg.conf. The excerpt below is what I have and
>> > you should have something similar. Specifically, you should NOT have
>> > SampleRate or Resolution options configured (unless they really do
>> > make your current mouse work better).
>> >
>> >
>> > Section "InputDevice"
>> > Identifier "Configured Mouse"
>> > Driver "mouse"
>> > Option "CorePointer"
>> > Option "Device" "/dev/input/mice"
>> > Option "Protocol" "ImPS/2"
>> > Option "ZAxisMapping" "4 5"
>> > Option "Emulate3Buttons" "true"
>> > EndSection
>> >
>> > For more info, see the mousedrv(4) man page.
>>
>> That looks like what I've used in the past. And if my desktop
>> was running I would check what's there. Currently I'm reduced
>> to the laptop, which runs Ubuntu 8.10 I think. And it is running
>> the latest xorg which has a very short xorg.conf file. Short
>> enough I can include it in its entirety.
>>
>> Section "Device"
>> Identifier "Configured Video Device"
>> Option "UseFBDev" "true"
>> EndSection
>>
>> Section "Monitor"
>> Identifier "Configured Monitor"
>> EndSection
>>
>> Section "Screen"
>> Identifier "Default Screen"
>> Monitor "Configured Monitor"
>> Device "Configured Video Device"
>> EndSection
>>
>> Section "InputDevice"
>> Identifier "Generic Keyboard"
>> Driver "kbd"
>> Option "CoreKeyboard"
>> Option "XkbRules" "xorg"
>> Option "XkbModel" "pc105"
>> Option "XkbLayout" "us"
>> Option "XkbOptions" "lv3:ralt_switch"
>> Option "XkbOptions" "ctrl:nocaps"
>> EndSection
>>
>> As you can see there is no mention of a mouse. And
>> about half the time the system seems to ignore this
>> file anyway since I don't always get the ctrl:nocaps
>> mapping.
>> --
>> Allen Brown
>> http://brown.armoredpenguin.com/~abrown
>>
>>
>> > On Tue, Mar 24, 2009 at 7:17 PM, Allen Brown <[email protected]> wrote:
>> >> I've tried to USB mouses with Linux. They suck beyond belief.
>> >> The graphic cursor is extremely jumpy, making it hard to
>> >> click on anything, even the big targets. Small targets
>> >> are extremely frustrating. I'm talking about jumping by
>> >> up to 1/2 inch on the screen.
>> >>
>> >> Somebody is screwing up big time. Has anybody gotten any
>> >> USB mouse to work with Linux? I've seen this with two
>> >> different computers. I've seen it with two different
>> >> mice. The behavior is consistent.
>> >>
>> >> Mind you, PS2 mice work fine. It's just USB that sucks.
>> >> --
>> >> Allen Brown
>> >> http://brown.armoredpenguin.com/~abrown
>> > --
>> > Bob Miller K<bob>
>> > [email protected]
>>
>>
>>
>>
>> _______________________________________________
>> EUGLUG mailing list
>> [email protected]
>> http://www.euglug.org/mailman/listinfo/euglug
>
>
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
