Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mouse and Keyboard stop working since Upgrade to Leopard

I upgraded to Leopard on Friday. Twice today, I've had problems with the mouse/keyboard freezing me out of my MBP. I never had this issue prior to upgrading. The first time today, both the KB and mouse quit. Later in the day, just the KB. Both times were after periods of inactivity. I don't remember the exact scenario leading up to it, but in both cases, a reboot fixed it. I don't have enough detail to (in my mind) justify a trip to the genius bar, but maybe someone else out there has seen this and solved the mystery?

Cheers...

MacBook Pro, Mac OS X (10.5)

Posted on Oct 29, 2007 7:00 PM

Reply
31 replies

Nov 2, 2007 12:18 PM in response to j.r.w.

Hi all,

Just adding in on this.

I am having this problem too.

I am using a Logitech wireless mouse hooked up to the keyboard USB. This happens frequently after the Mac goes idle. I have plugged a wired apple mouse into the keyboard when this happened and the wired mouse was unresponsive as well. New batteries in the wireless. Pushing the mouse resets doesn't help. Forcing the mac to sleep and re waking it brings the mouse to life - usually. This is a new problem since I installed Leopard.

How do you report this to Apple and has anyone done so?

Dan

Nov 5, 2007 5:38 PM in response to ergophobe

I think I have an idea that may help to explain the problem a little better. I remember reading in this thread that Sidetrack might cause this problem, and not knowing what it was did a search for it. I knew that I had not installed sidetrack, but when I landed on the website for it, I noticed that the same people also made MenuMeters which is something that I do use. After removing MenuMeters my problem seems to have dissappeared.

My guess is that there is something wrong with the method that the software developer uses to access hardware with its programs that makes it incompatible with Leopard. Hopefully this method is something created by this software developer and is not something in wide use, or else this problem may be more widespread and hard to track if there are many software developers that use this method to access hardware.

Nov 6, 2007 8:58 PM in response to ergophobe

Greetings,

I think I may be seeing the same thing. I have a brand new (purchased 10/27 - this is my first Mac, I am a Unix/Linux refugee) 24 inch, 2.8GHz iMac and although the keyboard and mouse are working, after the Mac wakes back up, other usb things (external disk for Time Machine and LaserJet) stop working. The only way to get the Mac to see these devices again is to reboot. I've also had the machine completely lock up on me a couple of times now (so hard that I have had to unplug the Mac's power to get it back).

The only additional data I can provide at this point is that my problems all began last night after I:

(1) Added the external usb drive (500GB Iomega, usb 2.0 high-speed)
(2) Turned on Time Machine
(3) Installed the IntelliPoint driver for my Microsoft usb wireless mouse (not necessary, I just installed it for better control over acceleration. MS says that the IntelliPoint SW is good with 10.5). I've uninstalled this but it hasn't helped.

Before this, everything worked great.

To confuse things even more... The MS wireless mouse and stock Apple keyboard are connected to a very old USB 1.0 powered hub and I have had no problems with them at all - it's the stuff plugged directly into the Mac that isn't working.

I am seeing this error, "control packet 1 error 0xe0004057", in the usb logs quite a bit. I am also seeing the Mac apparently try to communicate with disconnected devices (e.g. if I disconnect my printer, the Mac seems to think it's still connected and tries talk to it - at least that's what it looks like on cursory inspection.) Again at first glance, it looks like the Mac isn't recognizing usb connect/disconnect events - but I can't tell if the port isn't detecting them, or if it is and the driver/whatever isn't handling it correctly...

...And of course, I could be completely wrong.

At first I thought it might be a HW problem, but since it does seem to work correctly at boot, and since I've now read this thread, I'm leaning toward SW now.

Anyway, right now I've just unplugged the offending devices and put the printer on ethernet - but I'd really like a solution to this problem. I may try re-installing Leopard when I have time and see what that does.

Thanks,
Mark

Nov 11, 2007 3:25 PM in response to juxor

I agree... I too am having major issues. I do not use wireless mice with My MacBook Pro laptop I do use a Microsoft USB Laser Mouse. As I type this response I have to use my MBP Trackpad for my mouse since My USB mouse keeps powering down and I have to repeatedly unplug the USB device from my laptop and then plug it back in to allow it to work for about 15 mins before disabling again. But I do notice it only happens with the mouse, all my USB external HD's remain connected. I've used MS Laser mouses on this laptop with Tiger without any problems but since I upgraded I've had nothing but USB mouse issues since and apple does not seem to have any fixes as I've been calling them about this. They tell me to get a new driver. But this MS Laser USB mouse is an OEM device that uses a basic driver that is in the OS. So how can I get a new driver if there is none? Apple should have fixed this bug before releasing this OS. (Uhhh mouse just disabled again! Grrrrrrr)

Nov 16, 2007 2:01 AM in response to ergophobe

I upgraded to Leopard over a week ago but this randomly started happening on my Powerbook G4 yesterday. It would get to the point where the display dims so it can go to sleep and then the build in trackpad and keyboard stopped working.

I have come up with a temporary solution - tell the display it is not allowed to go to sleep and disable the dim display before sleep function. I also told my hard drive it was not allowed to sleep either. Obviously not good in the long run, but seems to work for now and hopefully it will be fixed in the 10.5.1 update which should be out soon.

I am going to go to the Apple store on Sat and see if they can do anything with it.

I ran disk verification and permissions verification and it said it was all fine EXCEPT:
Warning SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

I went to look for this file and could only find the ARDAgent.app so do not know what has happened there. Hopefully they will be able to fix this on Sat, but maybe this is the cause of the keyboard/mouse problem. Has anyone else run the disk utility verifications?

Nov 17, 2007 3:03 AM in response to j.r.w.

Unfortunately JRW's solution did not work for me. Even after the update to 10.5.1 I'm still suffering problems. Only with the internal keyboard/mouse, strangely enough not with the USB attached mouse or the Bluetooth keyboard.

Apple, please solve this. I'm being laughed at by the same people that used to look jealously at my MBP...

Nov 21, 2007 12:12 PM in response to ergophobe

I started having the same problem with my MBP after upgrading to Leopard. For me, it happens that about 50% of the time when I open my laptop in the morning, the keyboard & mouse are unresponsive. The only solution is to force a reboot. As previous posts note, errors of the type:

Nov 21 09:48:25 tybalt kernel[0]: AppleUSBHub::setPowerState(0x690b400, 2 -> 4) timed out after 11060 ms
Nov 21 09:48:25 tybalt kernel[0]: USBF: 84850. 65 AppleUSBUHCI[0x65c2000]::DeviceRequest - dmaCommand (0x694c480) already had memory descriptor (0x7c7a780) - clearing
Nov 21 09:48:25 tybalt kernel[0]: USBF: 84850. 65 AppleUSBUHCI[0x65c2000]::DeviceRequest - buffer dmaCommand (0x694c680) already had memory descriptor (0x9c7d880) - clearing
Nov 21 09:48:25 tybalt kernel[0]: USBF: 84850. 65 ControlTransaction: control packet 1 error 0xe0004057
Nov 21 09:48:25 tybalt kernel[0]: AFPSleepWakeHandler: waking up
Nov 21 09:48:28 tybalt kernel[0]: USBF: 84853. 65 AppleUSBUHCI[0x65c2000]::DeviceRequest - dmaCommand (0x694c680) already had memory descriptor (0x9033d80) - clearing
Nov 21 09:48:28 tybalt kernel[0]: USBF: 84853. 65 AppleUSBUHCI[0x65c2000]::DeviceRequest - buffer dmaCommand (0x694c480) already had memory descriptor (0xe33d480) - clearing
Nov 21 09:48:28 tybalt kernel[0]: USBF: 84853. 65 ControlTransaction: control packet 1 error 0xe0004057

fill the system log when this happens.

I tried reinstalling Quicktime 7.3. It seemed to work, for a few days at least, but today the problem occured again.

Next I will try j.r.w.'s ~solution~ of disabling wake upon opening the lid.

Nov 23, 2007 1:37 AM in response to RonL

Neither the Quicktime installation nor the wakeonlid options worked for me.

Fact is that - unlike reports on Apple Insider and the like - both my keyboard AND trackpad are stuck. External devices, both my USB MightyMouse and my Bluetooth Apple Keyboard DO remain operational...

Apple please solve this. Quickly that is!

Nov 23, 2007 6:02 AM in response to marktd

I have the (exact) same problem with my 24" Alu iMac. (4GB,500GB)

Keyboard and mouse are working, after the Mac wakes back up (only sometimes), other usb things stop working. ...Only way to get the USB Devices back is to reboot.

I also have random application crashes. Apps stop working even force quit will not work.

I´m using Time Machine, Adobe PS CS1, vmWare Fusion, eyeTV, Final Cut Studio 5.1 and others

Dec 1, 2007 11:48 AM in response to ergophobe

I think this is a Leopard bug. I just saw it happen. I filed a bug report with Apple. Here is my description. My setup was pretty generic. Let me know if there is any additional information I should include.

Summary:
The Bluetooth Mighty Mouse disables the keyboard and trackpad.

Steps to Reproduce:
1) Put computer to sleep
2) Wake computer by moving mouse
3) Try to use trackpad

Expected Results:
Trackpad should be usable
Keyboard should be usable

Actual Results:
Both trackpad and keyboard were unusable
Trying to disable bluetooth resulted in message that no input would be possible

Regression:
N/A

Notes:
Only way to solve problem was reboot, while turning of Mighty Mouse.
New (Nov. 2007) Macbook with 10.5 preinstalled. Upgraded to 10.5.1. No anti-virus software.
Was just unplugged from USB hub - no input devices were on USB bus.

PS. I will also add a link to this thread...

Mouse and Keyboard stop working since Upgrade to Leopard

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.