Mouse stopped working after a few days [SOLVED]

willy · 2007-08-31 11:47:03

Hi all,

I have some problem, as the title suggested. My mouse just stopped working after a few days booting into Arch. It's a USB mouse and it never caused any problem to me before. The red light on the mouse just turn off, I tried to plug it in and out, I tried to put another mouse and that does not solve the problem as well. I'm not sure where to start finding the source of this problem. Can anyone help me?

Last edited by willy (2007-09-13 05:42:21)

DrPike · 2007-08-31 14:41:36

maybe dmesg or lsusb gives you some details?

Does the status change between pluggin and unplugging the mouse? You an see the activity either
with 'lsusb' or 'dmesg' commands.

DrP

willy · 2007-09-02 08:28:57

Hi,
Thanks for replying. I thought I will wait for the problem to occur again before replying. After the mouse suddenly turned off, i did dmesg:

...
eth0: no IPv6 routers present
usb 3-1: USB disconnect, address 2
usb 3-1: new low speed USB device using uhci_hcd and address 3
usb 3-1: configuration #1 chosen from 1 choice
input: Microsoft Microsoft Wheel Mouse Optical as /class/input/input5
input: USB HID v1.00 Mouse [Microsoft Microsoft Wheel Mouse Optical] on usb-0000:00:10.2-1
usb 3-1: USB disconnect, address 3
usb 3-1: new low speed USB device using uhci_hcd and address 4
usb 3-1: configuration #1 chosen from 1 choice
input: Microsoft Microsoft Wheel Mouse Optical as /class/input/input6
input: USB HID v1.00 Mouse [Microsoft Microsoft Wheel Mouse Optical] on usb-0000:00:10.2-1
usb 3-1: USB disconnect, address 4
usb 3-1: new low speed USB device using uhci_hcd and address 5
usb 3-1: configuration #1 chosen from 1 choice
input: Microsoft Microsoft Wheel Mouse Optical as /class/input/input7
input: USB HID v1.00 Mouse [Microsoft Microsoft Wheel Mouse Optical] on usb-0000:00:10.2-1
usb 3-1: USB disconnect, address 5
usb 3-1: new low speed USB device using uhci_hcd and address 6
usb 3-1: device descriptor read/64, error -110
usb 3-1: device descriptor read/64, error -110
usb 3-1: new low speed USB device using uhci_hcd and address 7
usb 3-1: device descriptor read/64, error -110
usb 3-1: device descriptor read/64, error -110
usb 3-1: new low speed USB device using uhci_hcd and address 8
usb 3-1: device not accepting address 8, error -110
usb 3-1: new low speed USB device using uhci_hcd and address 9
usb 3-1: device not accepting address 9, error -110

If I try to reconnect the mouse(by plugin out and in). The same message appear for address 10. Any ideas?

mac57 · 2007-09-02 16:18:53

Do you have any other OS dual booted on this machine? This LOOKS like a hardware error to me, but the easiest way to quickly isolate that is to try it in another OS and see if the problem shows up there. Is this possible?

Also, what sort of hardware are you running this on? I used to see similar errors from a USB2.0 hard drive when I ran it against a CPU that was just too slow to keep up...

DrPike · 2007-09-02 17:53:07

Yes, I agree with mac57: it could be an hardware problem.
It easy to check either replacing the mouse with another unexpansive USB model (you can buy one at less than 10$ US) or connecting the same mouse to another PC.
If the problem persists with another USB device on your PC, you've to investigate on the USB port: did you try with another port? If you suspect a driver problem (quite unusual case to me), try to boot another LIVE distro (ubuntu, knoppix or wathever) and check the mouse activity for a while...

Best wishes,
DP

willy · 2007-09-03 00:13:39

Do you have any other OS dual booted on this machine? This LOOKS like a hardware error to me, but the easiest way to quickly isolate that is to try it in another OS and see if the problem shows up there. Is this possible?
Also, what sort of hardware are you running this on? I used to see similar errors from a USB2.0 hard drive when I ran it against a CPU that was just too slow to keep up...

I only have have Arch in this computer. It's a P4 2.8 GHz. There's vmware with winxp home in it, but I haven't turn it on for ages.

It easy to check either replacing the mouse with another unexpansive USB model (you can buy one at less than 10$ US) or connecting the same mouse to another PC.
If the problem persists with another USB device on your PC, you've to investigate on the USB port: did you try with another port? If you suspect a driver problem (quite unusual case to me), try to boot another LIVE distro (ubuntu, knoppix or wathever) and check the mouse activity for a while...

I tried connecting it to another port and I tried connecting another mouse those ports as well, all without success. I guess i could try using the Live distros, but it will take days to know the result.

Can an upgrade cause this problem? I remember doing an upgrade before this problem occurs

DrPike · 2007-09-03 08:18:00

I tried connecting it to another port and I tried connecting another mouse those ports as well, all without success. I guess i could try using the Live distros, but it will take days to know the result.
Can an upgrade cause this problem? I remember doing an upgrade before this problem occurs

So, the mouse seems to be working well!
Try to use pacman -Syu and hwd -u when the system is well upgraded: answering 'yes' to the question the hardware tool will run on your PC. And see if there are differences on usb manager.

what does the lsusb command report?

Did you also change/upgrade the kernel ?

DP

Last edited by DrPike (2007-09-03 08:30:33)

willy · 2007-09-03 10:49:36

lsusb:

Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 004 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 004 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

I tried lsusb after the mouse was turned off, it did not return anything. I do not have enough experience yet to change the kernel:), I just did pacman -Syu and hwd -u. There is another kernel update. I will let you know about the result in a few days. Thanks for the help DrPike and mac57.

DrPike · 2007-09-12 17:06:05

So, how is going now?

willy · 2007-09-13 01:15:38

Hello,

I almost forgot about it. It's working fine now, no more mouse disconnection. Thanks again for your help.

Willy

DrPike · 2007-09-13 05:26:37

Ok, in case of success is a good rule to edit your first post adding a tag [SOLVED] at
the beginning of the title. This is useful for other people looking at the same problem
you have.

So, at the end it was a matter of kernel?

DrPike

willy · 2007-09-13 05:43:21

Done.
Hmm.. not too sure, i'm not an expert in this, but after running pacman -Syu and hwd -u, everything is all fine.

Arch Linux

#1 2007-08-31 11:47:03

Mouse stopped working after a few days [SOLVED]

#2 2007-08-31 14:41:36

Re: Mouse stopped working after a few days [SOLVED]

#3 2007-09-02 08:28:57

Re: Mouse stopped working after a few days [SOLVED]

#4 2007-09-02 16:18:53

Re: Mouse stopped working after a few days [SOLVED]

#5 2007-09-02 17:53:07

Re: Mouse stopped working after a few days [SOLVED]

#6 2007-09-03 00:13:39

Re: Mouse stopped working after a few days [SOLVED]

#7 2007-09-03 08:18:00

Re: Mouse stopped working after a few days [SOLVED]

#8 2007-09-03 10:49:36

Re: Mouse stopped working after a few days [SOLVED]

#9 2007-09-12 17:06:05

Re: Mouse stopped working after a few days [SOLVED]

#10 2007-09-13 01:15:38

Re: Mouse stopped working after a few days [SOLVED]

#11 2007-09-13 05:26:37

Re: Mouse stopped working after a few days [SOLVED]

#12 2007-09-13 05:43:21

Re: Mouse stopped working after a few days [SOLVED]

Board footer