I made some interesting discoveries tonight: Once I was able to get the
hot-plugged mouse to be recognized by unplugging my printer and
plugging it back into the other USB port, but this only worked once.
The next workaround I found was to put the computer to sleep, and upon
waking up the mouse came back. But this too only worked once. Now that
I've unplugged it and plugged it in again, it's not being recognized
(I'm still getting the MakeDevice error in the console) and I won't
have my mouse back until I reboot. Does this mean anything to anybody?
Thanks,
Josh
On Oct 13, 2004, at 12:32 PM, Rich Kubota wrote:
Hi Josh,
this is weird that the device doesn't respond if the device is
hot-plugged. The error indicates that the device is not responding.
The failure is occurring while USB is trying to make the SetAddress
request to the control endpoint.
I think that to understand why this is happening, we would need to see
a trace when the SetAddress call fails.
At 1:13 AM -0400 10/13/04, Josh Bronson wrote:
I bought a mini optical USB scroll mouse made by Fantasy for my
iBook. Unfortunately, it only works if it's plugged in when I start
the computer. If I plug it in after it's started or if I unplug it
while it's working and then plug it back in, the computer doesn't
respond to it, and the following is appended to system.log:
This did not happen with my old optical USB mouse made by Logitech.
Is this possible to fix?
Thanks,
Josh
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
