LinuxQuestions.org - buggy mouse

Page 1 of 2

Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - buggy mouse (https://www.linuxquestions.org/questions/slackware-14/buggy-mouse-4175560319/)

nitecrawler

12-01-2015 11:36 AM

buggy mouse

i have a 2 button mouse with a middle scroller....and its a usb connected mouse....
it behaves weirdly on my fresh install of slackware 14.1....

after a duration of time it fails to respond and then i have to go to a virtual console and get back to my X window to get it working again.....

to be specific the right click button doesnt work after sometime and i have to switch to a virtual console and come back to my X window to get my mouse working again...

weird issue but hoping help is around....
do i need to reconfigure it?

ardvark71

12-01-2015 11:39 AM

Hi...

Not sure I can help with this but just to confirm, can this issue be duplicated using another mouse?

Regards...

nitecrawler

12-01-2015 11:52 AM

i have inserted another mouse...this time a logitech mouse now but same issues....and in my terminal lots of text is selected automatically....or my window gets selected and if i move the mouse around the window keeps moving over the screen.....

output of lssusb:

Code:

bash-4.2$ lsusb | grep Mouse

Bus 002 Device 007: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

bassmadrigal

12-01-2015 12:04 PM

What mouse driver did you select when you installed Slackware? For the longest time, I used the PS2 version, which is limited vs the imps2 driver.

Also, have you tried multiple USB ports?

nitecrawler

12-01-2015 12:12 PM

well, i strictly dont remember which driver i selected....think it was usb this time round....

and i have switched the usb ports now...

nitecrawler

12-01-2015 12:28 PM

still no luck after changing my usb port....my mouse right click button stops working after sometime and i need to switch to a virtual console and back to get it working again....

MarcT

12-01-2015 02:31 PM

Run "dmesg" as root once the mouse stops working, and see if anything relevant is logged.
I used to get this sometimes when going through a KVM switch.

nitecrawler

12-01-2015 09:40 PM

dmesg

Code:

mce: [Hardware Error]: Machine check events logged

just to add my keyboard also stops working when the usb mouse fails too.....

elcore

12-02-2015 12:08 AM

Maybe check lsmod to find out which module it's currently using.
Does it happen on huge kernel or generic? I'm using evdev driver for both mouse and keyboard, haven't seen this problem yet.

BradReed

12-02-2015 12:44 AM

Quote:

Originally Posted by nitecrawler (Post 5458014)

Code:

bash-4.2$ lsusb | grep Mouse

Bus 002 Device 007: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

Sounds like Powertop is turning off the USB port to save power. You can use powertop to stop that, or try a command like the following to turn the mouse back on.

Code:

echo 'on' > "/sys/bus/usb/devices/2-*/power/control";

MarcT

12-02-2015 07:07 AM

Quote:

Originally Posted by nitecrawler (Post 5458315)

dmesg

Code:

mce: [Hardware Error]: Machine check events logged

just to add my keyboard also stops working when the usb mouse fails too.....

Ok - Check the post above about power saving. If that's not the cause, there might be a hardware issue with the machine.

Slackware has the "mcelog" utility which can decode MCEs (Machine Check Events), but even though there's an executable rc script, Slackware doesn't seem to run it at startup.
Run it manually and see if mcelog can decode the next one:

Code:

sh /etc/rc.d/rc.mcelog start

If you do get a decode, post it up on here.

Finally, have a read of the mcelog man page ("man mcelog") for more details.

Good luck!
Marc

nitecrawler

12-02-2015 07:25 AM

@BradReed:

from powertop tunables section i got the following:

Code:

  Good          Bluetooth device interface status

>> Good          Autosuspend for USB device WebCam SC-13HDL11939N [Generic]                                            

  Good          Autosuspend for USB device EHCI Host Controller [usb1]

  Good          Autosuspend for USB device EHCI Host Controller [usb2]

  Good          Autosuspend for unknown USB device 1-1 (8087:0024)

  Good          Autosuspend for unknown USB device 2-1 (8087:0024)

                                                        

  Bad          Autosuspend for USB device USB Keyboard [SIGMACHIP]

  Bad          Autosuspend for USB device USB Optical Mouse [Logitech]

  Bad          Autosuspend for USB device Bluetooth USB Host Controller [Atheros Communications]

so whats good and whats bad?

nitecrawler

12-02-2015 09:30 AM

so i went through the documentation on powertop and changed Good to Bad for the usb listings...but still the issue persists....

now, when i check dmesg i get this output:

Code:

[70970.469987] hub 2-1:1.0: port 2 disabled by hub (EMI?), re-enabling...

[70970.469994] usb 2-1.2: USB disconnect, device number 8

[70970.654467] usb 2-1.2: new low-speed USB device number 11 using ehci-pci

[70970.733984] usb 2-1.2: New USB device found, idVendor=046d, idProduct=c05a

[70970.734003] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[70970.734008] usb 2-1.2: Product: USB Optical Mouse

[70970.734012] usb 2-1.2: Manufacturer: Logitech

[70970.736627] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input20

[70970.736804] hid-generic 0003:046D:C05A.000A: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.0-1.2/input0

BradReed

12-02-2015 09:38 PM

What does lsusb show?

Mine shows my mouse as:
$ lsusb
Bus 001 Device 003: ID 187c:0515 Alienware Corporation

Note the number after Bus ignoring leading zeroes and replace $BUS with it in the following:

echo 'on' > "/sys/bus/usb/devices/usb$BUS/power/control";

or

echo 'on' > "/sys/bus/usb/devices/$BUS-*/power/control";

Does either turn your mouse back on?

BradReed

12-02-2015 09:49 PM

Quote:

Originally Posted by nitecrawler (Post 5458465)

@BradReed:

from powertop tunables section i got the following:

Code:

                                          

  Good          Autosuspend for USB device EHCI Host Controller [usb1]

  Good          Autosuspend for USB device EHCI Host Controller [usb2]

  Good          Autosuspend for unknown USB device 1-1 (8087:0024)

  Good          Autosuspend for unknown USB device 2-1 (8087:0024)

                                                        

  Bad          Autosuspend for USB device USB Keyboard [SIGMACHIP]

  Bad          Autosuspend for USB device USB Optical Mouse [Logitech]

  Bad          Autosuspend for USB device Bluetooth USB Host Controller [Atheros Communications]

so whats good and whats bad?

I would try setting all the unknown USB devices and USB Hosts to BAD, one at a time until I found the one that was turning off the mouse.

All times are GMT -5. The time now is 07:33 AM.

Page 1 of 2

Show 50 post(s) from this thread on one page