umm, my mouse stop working and i have to un/plug it in

Devboy · 08-21-2004, 02:25 AM

It's a pain 3times now, when i have left my pc the mouse just doesnt work i have to unplug it and plug it in! anyone know how i can fix this?

i have a Microsoft usb optical intellie mouse.

frob23 · 08-21-2004, 04:33 AM

How about some console messages (/var/log/message should contain them) concerning the mouse? As well as a "uname -a"?

We violently need more information to even begin considering to help.

Devboy · 08-21-2004, 05:59 AM

Console messages for what? the mouse just stops working when the pc is lef idle, i unplug it plug it in and its fine untill left idle :S.

Code:

$ uname -a
FreeBSD 127.0.0.1 4.10-STABLE FreeBSD 4.10-STABLE #1: Tue Aug 17 10:03:27 BST 2004     devboy@127.0.0.1:/usr/obj/usr/src/sys/GENERIC  i386
$

frob23 · 08-21-2004, 07:03 AM

console messages for the mouse... the ones that appear (on the console coincidentally) when you plug in the mouse... also the ones that might be appearing when ums disconnects.

Obviously, you are not running at the console or you would see them... you will most likely find a record of them in /var/log/messages and/or in the output of dmesg.

Devboy · 08-21-2004, 07:18 AM

ahh, that would be:

Code:

Aug 21 08:01:42 127 /kernel: ums0: at uhub0 port 1 (addr 2) disconnected
Aug 21 08:01:42 127 /kernel: ums0: detached
Aug 21 08:01:42 127 moused: unable to open /dev/ums0: Device not configured
Aug 21 08:01:45 127 /kernel: uhub0: port error, restarting port 1
Aug 21 08:01:46 127 /kernel: ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1
Aug 21 08:01:46 127 /kernel: ums0: 5 buttons and Z dir.
Aug 21 08:17:48 127 /kernel: ums0: at uhub0 port 1 (addr 2) disconnected
Aug 21 08:17:48 127 /kernel: ums0: detached
Aug 21 08:17:48 127 moused: unable to open /dev/ums0: Device not configured
Aug 21 08:17:50 127 /kernel: uhub0: port error, restarting port 1
Aug 21 08:17:51 127 /kernel: ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1
Aug 21 08:17:51 127 /kernel: ums0: 5 buttons and Z dir.
Aug 21 10:44:33 127 /kernel: ums0: at uhub0 port 1 (addr 2) disconnected
Aug 21 10:44:33 127 /kernel: ums0: detached
Aug 21 10:44:33 127 moused: unable to open /dev/ums0: Device not configured
Aug 21 10:44:40 127 /kernel: uhub0: device problem, disabling port 1
Aug 21 10:44:41 127 /kernel: uhub0: port error, restarting port 1
Aug 21 10:44:42 127 /kernel: ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1
Aug 21 10:44:42 127 /kernel: ums0: 5 buttons and Z dir.
Aug 21 10:44:42 127 /kernel: ums0: at uhub0 port 1 (addr 2) disconnected
Aug 21 10:44:42 127 /kernel: ums0: detached
Aug 21 10:44:42 127 moused: unable to open /dev/ums0: Device not configured
Aug 21 10:44:45 127 /kernel: uhub0: port error, restarting port 1
Aug 21 10:44:46 127 /kernel: ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1
Aug 21 10:44:46 127 /kernel: ums0: 5 buttons and Z dir.
Aug 21 13:10:28 127 /kernel: ums0: at uhub0 port 1 (addr 2) disconnected
Aug 21 13:10:28 127 /kernel: ums0: detached
Aug 21 13:10:28 127 moused: unable to open /dev/ums0: Device not configured
Aug 21 13:10:30 127 /kernel: uhub0: port error, restarting port 1
Aug 21 13:10:31 127 /kernel: ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1
Aug 21 13:10:31 127 /kernel: ums0: 5 buttons and Z dir.
Aug 21 13:14:04 127 /kernel: ntfs_strategy: ntfs_readattr failed

frob23 · 08-21-2004, 09:08 AM

I have done a lot of reading on this issue and wish I could say I found a good solution. The problem seems to have existed for a while and it likely still does exist. If you want, you may be interested in looking at the following:

http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/32713

This is a PR report detailing the issue back in 4.4 -- it has been suspended for feedback because they are not sure the issue still exists. You may want to submit feedback saying you believe it does and detail your problem.

Now -- trying some temporary solutions ... because obviously knowing it is a problem isn't fixing it for you.

Is this only an issue after the computer has been idle for a while? [1]

[1] NO: then the original PR definitly relates to your problem and you'll probably want to jump on the official mailing lists for further help.

[1] YES: Do you have the computer configured to suspend (sleep) after a certain amount of time? [2]

[2] NO: Have you enabled ACPI -- I believe it is off by default for 4.x but that might have changed for 4.10? [3]

[3] YES: Turn off ACPI (either at boot or by rebuilding the kernel to not include it) -- does the problem go away? [4]

[4] NO: Contact the mailing lists and describe what is going on.

[4] YES: Good.

[3] NO: Contact the mailing lists and describe what is going on.

-- This describes, roughly, the order I would go about approaching this. It might be incomplete or completely off base. But this is what I am guessing at from here.