SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
Last edited by nitecrawler; 12-01-2015 at 11:42 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
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....
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.
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.
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
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.
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.
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 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
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.