30198 Views 1 … 6 7 8 9 10 Previous Next 148 Replies Latest reply: Jun 26, 2008 11:01 AM by darrelld Go to original post
I have the same issue with my six weeks old MacBook Pro 15" 2,4. Before upgrading to 10.5.1 I had to restart to be able to use the keyboard after freeze. The freeze occurred after sleep. Now with 10.5.1 installed the keyboard freezes everytime I have to fill text into a form in a browser and in a lot of other occations too, like several times during typing this message. The keyboard wakes up after a couple of seconds, thogh, but it's a REAL pain in the **! Please, Apple - solve this!!!
I called Apple Care regarding the same issue on my Macbook. I waited on hold for 40 minutes for an apple tech to tell me that they are aware of the problem, and are working on a fix. Until then he suggested not putting my computer to sleep and shutting it down when it's not in use. He said the issue was related to coming out of sleep mode. I have found the issue to not necessarily correspond to waking from sleep. So, apparently they're aware of the issue. This isn't leopard "beta" is it. Shouldn't key compatibility things like this be tested before releasing an operating system. I mean it only took me a couple of days to discover the issue on my computer.
My first Mac too. We're off to a good start :S
Robert Ruef wrote:
I called Apple Care regarding the same issue on my Macbook. I waited on hold for 40 minutes for an apple tech to tell me that they are aware of the problem, and are working on a fix. Until then he suggested not putting my computer to sleep and shutting it down when it's not in use. He said the issue was related to coming out of sleep mode.
Sorry to hear you are also having these problems. At least it is good news that they are now aware of the problem. Let's hope a software fix will be released soon.
it´s driving me crazy. after a few days with working trackpad and keyboard, i am now back where i started. re-installing qt 7.3 was no permanent fix. I put the computer into my bag a few days ago and unpacking it hours later, keyboard and trackpad were gone again.
Today I was going to downgrade to Tiger using the original dvd, but that was ´not possible´ said the installer. also, after the reboot in the installer (in 10.4) the trackpad and keyboard weren't working either, so I guess the problem is not just in leopard? (but I suspected that all along, my problems started in Tiger after I connected a friend's iPod)
Stuck with a half working MacBook Pro I am starting to get very annoyed. it's been close to a month now for me. Please Apple do something....! And do it fast!
At least this sounds like an Apple Technician ACKNOWLEDGES that it is a KNOWN ISSUE (he knew about it...and had a solution).
Now the Apple developers need to get on it and get a hotfix out. End of story. Oh, and Apple needs to public ally acknowledge it -- in this forum or elsewhere for "upcoming bug fixes."
Thanks for the tip, WiRaCoCha, but my MBP is still having issues after disabling safe sleep.
The "sudo update_prebinding -force -root /" tip mentioned on AppleInsider also did absolutely nothing (surprise, surprise). Occasionally my keyboard now goes out without the trackpad dying, so that would appear to eliminate the speculated division between machines with dying trackpads and keyboards and machines with only dying keyboards, as I've gotten both. (Not cool!)
Of interest: I use HardwareGrowler to notify me whenever a USB device is connected or disconnected. I definitely received notification when the keyboard/trackpad device is "disconnected," meaning that both became non-responsive. Sometimes I'll get a "disconnect" message immediately followed by a "connect" message, but being able to monitor the problem certainly won't make it disappear instantly.
I did not get this notification on occasions when only my keyboard decided to not work.
I don't know if disabling Safe Sleep improved anything, but one time so far I was able to revive my keyboard (while the trackpad still responded) without rebooting by simply sleeping and waking the machine (closing and opening the lid).
I had no such issues with Mac OS X 10.4.10, as others noted, and I had no problems with my trackpad and keyboard until yesterday. Who knows why that is...
The following are types of Console log messages related to "USB" that I have seen since the first reboot after my trackpad and keyboard first stopped working yesterday. Please note that they are out of context (i.e. there might be some other console message, such as those related to going in and out of sleep, that are not super-explicitly related to these problems - I hope).
Example of a rapid connect/disconnect process that results in a permanent failure, after which I had to reboot. This has recurred.
11/26/07 8:11:05 PM kernel USBF: 6636. 9 [0x42bbe00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of hub @ location: 0x5d000000)
11/26/07 8:11:06 PM kernel USBF: 6637.680 [0x42bbe00] The IOUSBFamily has successfully enumerated the device.
11/26/07 10:25:56 PM kernel USBF: 12818.689 [0x42bbe00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of hub @ location: 0x5d000000)
11/26/07 10:26:00 PM kernel USBF: 12822.532 [0x42bbe00] The IOUSBFamily was not able to enumerate a device.
A USB Spec. violation? Uh oh... This has not recurred.
11/26/07 6:31:10 PM kernel USBF: 640.930 USB Device Apple Internal Keyboard / Trackpad is violating Section 9.3.5 of the USB Specification -- Error in GetConfigDescriptor( wLength = 4)
This may be related to the above (note "GetFullConfigDescriptor"). This has not recurred.
11/26/07 10:27:56 PM kernel USBF: 2.119 CSRHIDTransitionDriver[0x4350b00](IOUSBCompositeDevice) GetFullConfigDescriptor(0) returned NULL
A message that appeared *before* entering hibernation (after disabling Safe Sleep, which, again, may not matter). I did not see this before disabling Safe Sleep.
11/27/07 4:39:02 PM kernel USBF: 15091.627 AppleUSBEHCI[0x416a000]::SuspendUSBBus - port 4 was NOT already suspended (as it should have been) PROBLEMS AHEAD
That's all I got. If the console text looks spammy, I apologize, just trying to help.
Message edited by Joe Kohlmann for length.
I have a macbook.. My keyboard stopped working after installing leopard, so I'm sure that Leopard is the problem.
I did a safe reboot, (restart and hold the shift key)
My keyboard worked in SAFE mode. I have nothing plugged in except the power.
I then restarted the usual way, and the keyboard worked again.
Try it. Maybe this will be a workaround until Apple finally decides there's a problem.
Similar problem here, though it really felt like a hardware issue to me ... but it only started happening after I installed Leopard. On startup, most of the left half of my keyboard will become unresponsive, while the right half works fine. Even odder, the caps lock and num lock keys resting state will be reversed; that is, when the machine reaches the login box, they keys are both lit, even though I haven't touched them.
This has happened to me twice. Both times I was able to restart by using an external mouse, and restarting miraculously fixed the problem.
Do people think it's a hardware issue after all? It seems odd that a reboot would even temporarily cure an intermittent hardware issue -- those typically start and stop seemingly at random.
A very stupid thought - has anyone with an MBP observed what state the keyboard backlight(s) are in when the keyboard is unresponsive? This occurred to me since it seems to be the OS device driver that controls the illumination level, but this could also be a dead end if the state remains unchanged based on whether or not the OS believes the keyboard is connected.
I might try this myself sometime soon. Anything to get a handle on this until Apple fixes it...
Hello! I've got a similar problem!
Bought a new MBP an upgraded to Leopard. A few days later when i startet it up, keyboard an trackpad were dead. I downgraded to 10.4.10 but when installing it the computer sayd: no keyboard connected. So i brought it to the apple shop, where they put a new top case into the computer. After this, my computer worked fine on 10.4.10. But yesterday when I startet the machine up, exact the same problem occured. The difference to other cases is, the keyboard doesen't work at all, it's not a intermittent problem. Is it possible that the installation of leopard a few weeks ago, damaged any hardware?
additional i installed a canon printer driver yesterday (pixma 4500). Heard about other people that have the same problem after this...
If anyone has some idea, i'd be glad about...thx
keyboard backlighting is OFF when keyboard is unresponsive.
Another note: the iSight continues to work when keyboard is unresponsive, but no surprise, given that it's on a completely different USB bus.
I spent 40 minutes on the phone with Apple. The tech walked me through booting from DVD, running Apple Hardware Test, Disk Utility (repair disk/permissions), zapping PRAM. I gave the tech the exact USB error and also referred him to this thread.
Apple is sending me out a box for a repair.
I was having the same kind of instability with Leopard until I did an erase and install and manually moved my files back over. While this is an absurd choice for the less savvy computer user, it's the only choice which has cleared up all of my issues, keyboard, airport, etc.
Since this option fixed my issues, I suggest creating a new user and logging in there to see whether that fixes the problem. If not, you'll probably need to wait for Apple or do an erase and install.
What I find distressing, and very unlike Apple's reputation, is that an upgrade and install option wasn't thoroughly tested on the MBP or was and released anyway. This is clearly not a hardware issue since BootCamping into Vista showed ZERO issues with the keyboard.... but of course created the problem of moving to mac in the first place; disliking Windows.
I still have a few scenarios to test, such as sleeping and heading to a different Wi-fi Access Point, but I'll follow-up on those and post later this weekend.