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

Oct 29, 2007 7:23 PM in response to ergophobe

Well, I'm having the same issue (and others). Are they by any chance plugged into a USB hub? Possibly a USB-1 hub? I was pulling my hair out as none of my printers or scanners work either, but realized the common trait would be that they are all plugged into older powered USB hubs. All the devices plugged into USB2 compliant hubs work fine. Coincidence?

Oct 30, 2007 2:17 PM in response to ergophobe

I'm having the same issue. About once every 15 times I put the machine to sleep when I go to wake it up the built-in keyboard and trackpad don't work. I can plug in an external keyboard and that will work as will my bluetooth mouse. I then need to restart the machine, some times multiple times before the keyboard will start to work again. I have not hand any problems till installing leopard. I did the standard update install. The only special thing I have is a wacom tablet but I updated the drivers on that and I haven't even plugged it in yet.

Oct 30, 2007 4:10 PM in response to ergophobe

I have seen this same problem. Often when a new window opens or I click on a text field the keyboard doesn't respond. I have no peripherals connected. I thought it might be a sticking control key but pressing control keys doesn't fix it. The keyboard does start working eventually but there is no buffer of keys just what I type after it "wakes up". Seems to happen in all applications and is becoming annoying.

If anyone has found a work around better than just waiting I would love to hear it.

Oct 30, 2007 5:15 PM in response to ergophobe

Adding my voice to the choir. I am seeing this too. Very frustrating. Doesn't happen all of the time, but enough to be a serious nuisance.

Poked around with the USB Probe tool after this happened (with external mouse) and it says the keyboard & trackpad appear to be suspended. None of the logs seem to show any issues. I tried this with hibernate (aka safe sleep) enabled and disabled and have reproduced it in both cases.

Oct 31, 2007 12:00 AM in response to j.r.w.

Ok looks like I might have figured this out. On my 17" G4 laptop I used sidetrack, it looks like the software made the migration over to the new laptop and is seriously incompatible with Leopard. There are 4 things to look for and remove if they exist:
/System/Library/Extensions/SideTrack.kext
/Library/PreferencePanes/SideTrack.prefPane
/Library/StartupItems/SideTrack
/Library/LaunchDaemons/com.ragingmenace.SideTrack.Daemon.plist

The sidetrack website has more information:
http://www.ragingmenace.com/index.html

AAron

Oct 31, 2007 8:46 AM in response to aglimme

I don't use sidetrack, so if that is one issue it can't be the only one.

Saw a post on a similar thread asking whether people were using VMWare, since maybe there is an issue with their kext. Since there are PowerPC based users on this thread I doubt that is the issue, but I will try uninstalling this. The problem has been getting worse for me and now is doing it almost every time I susend/resume. Argh...

Oct 31, 2007 9:51 AM in response to j.r.w.

FYI, uninstalling Parallels and VMWare's Fusion (I was using both) doesn't help.

However another scrub of the System log did reveal something peculiar. Sort of a mess to post but in case anyone from Apple is watching this, I am attaching. This is coming up right after I resume wake from suspend.


Oct 31 09:33:25 jwilcox-mbp kernel[0]: AppleYukon2: 00000000,00000000 sk98osx_dnet - recovering from missed interrupt
Oct 31 09:33:28 jwilcox-mbp kernel[0]: AppleUSBHub::setPowerState(0x3ef9a00, 2 -> 4) timed out after 10724 ms
Oct 31 09:33:28 jwilcox-mbp kernel[0]: USBF: 124.693 ControlTransaction: control packet 1 error 0xe0004057
Oct 31 09:33:31 jwilcox-mbp kernel[0]: USBF: 127.693 AppleUSBUHCI[0x3dca000]::DeviceRequest - dmaCommand (0x3f27900) already had memory descriptor (0x557e400) - clearing
Oct 31 09:33:31 jwilcox-mbp kernel[0]: USBF: 127.694 AppleUSBUHCI[0x3dca000]::DeviceRequest - buffer dmaCommand (0x3f27800) already had memory descriptor (0x3f51580) - clearing
Oct 31 09:33:31 jwilcox-mbp kernel[0]: USBF: 127.694 ControlTransaction: control packet 1 error 0xe0004057
Oct 31 09:33:32 jwilcox-mbp kernel[0]: AppleYukon2: 00000000,00000000 sk98osx_dnet - recovering from missed interrupt
Oct 31 09:33:46 jwilcox-mbp login[228]: USER_PROCESS: 228 ttys000
Oct 31 09:33:48 jwilcox-mbp kernel[0]: USBF: 144.696 AppleUSBUHCI[0x3dca000]::DeviceRequest - dmaCommand (0x3f27800) already had memory descriptor (0x5467280) - clearing
Oct 31 09:33:48 jwilcox-mbp kernel[0]: USBF: 144.696 AppleUSBUHCI[0x3dca000]::DeviceRequest - buffer dmaCommand (0x3f27900) already had memory descriptor (0x5469780) - clearing
Oct 31 09:33:48 jwilcox-mbp kernel[0]: USBF: 144.696 ControlTransaction: control packet 1 error 0xe0004057
Oct 31 09:33:48 jwilcox-mbp kernel[0]: USBF: 144.696 AppleUSBUHCI[0x3dca000]::DeviceRequest - dmaCommand (0x3f27900) already had memory descriptor (0x601fc00) - clearing
Oct 31 09:33:48 jwilcox-mbp kernel[0]: USBF: 144.696 AppleUSBUHCI[0x3dca000]::DeviceRequest - buffer dmaCommand (0x3f27800) already had memory descriptor (0x601b680) - clearing
Oct 31 09:33:48 jwilcox-mbp kernel[0]: USBF: 144.696 ControlTransaction: control packet 1 error 0xe0004057
Oct 31 09:33:49 jwilcox-mbp kernel[0]: USBF: 144.798 AppleUSBHub[0x3f4b800]::SuspendPort - expected port to be suspended for conversion, but it is not!!

Nov 1, 2007 3:04 PM in response to DaveKinahan

Probably too early to call it a solution but I tried this yesterday around noon and have not suffered the issues since. I disabled the wake on lid opening, basically just to see if the keyboard would be able to wake the system because I wanted to know if it was dead when it suspended or during the wake process. Since then I haven't run into any issues, so it may be somehow related to lid-waking.

Try it if you like, no guarantees. To disable wake on lid opening type the following command in the terminal: "sudo pmset -a lidwake 0"

To reenable this later, just use: "sudo pmset -a lidwake 1"

With lid-wake disabled, you wake the mac by hitting keys on the keyboard. If you do try it, let me know if you still see failures so I know if this is working or just a fluke.

Nov 2, 2007 6:25 AM in response to ergophobe

I have the same problems with occasionally waking from sleep, the keyboard stays in a sleep mode. I have found that by triggering the ambient light sensor several times, my keyboard will come back for several minutes.

It tends to lose the keyboard after a few minutes though (when it re-loses the keyboard, is generally when I switch apps or use spaces)


Although it isn't a solution, it does help.

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.