This discussion is archived
102871 Views 359 Replies Latest reply: Jan 7, 2008 4:50 AM by eriatarka
Currently Being ModeratedDec 13, 2007 3:58 PM (in response to LOUDSYSTEM)I've gone almost an entire week without having my keyboard lock up by doing the
- turn off Spaces (virtual desktops & switcher) and reboot (as mentioned by someone else)
- open and shut the laptop normally as I use it throughout the day but when I'm done for the night, I now do a full shutdown/power off.
Whether it is simply related to going into and coming out of sleep many times, or if Spaces was part of the problem, I haven't really tried to determine, but this usage pattern seems to be working for me while I await the fix.
YMMV.MacBook Pro, Mac OS X (10.5.1), MacBookPro3,1 (Model Identifier)
Currently Being ModeratedDec 13, 2007 7:09 PM (in response to Snaka)More confirmation that it might be a sleep/deep sleep problem.
I'd been turning the MBP off at night, or whenever I was going to be away awhile, and I hadn't had any keyboard issue in weeks. Was starting to think it had miraculously resolved, or I was just imagining it.
Today I decided to calibrate my battery, which means using it down to auto-sleep, and then letting it sit for 5+ hours.
When I plugged the power in and started back up (neat safe restore screen, BTW) I began having dead-keyboard issues almost instantly. Shut down/restarted, and it's fine again.
Would be nice if, until there's a fix, maybe APPLE COULD SUGGEST THIS TO PEOPLE.
(I have Spaces on all the time and am a rabid Space-switcher, so I don't think it's Spaces.)Macbook Pro 2.2 15", Mac OS X (10.5.1)
Currently Being ModeratedDec 13, 2007 8:52 PM (in response to engr2law)yes, this happens to me in both leopard and windows bootcamp.MacBook Pro - 2.4 core 2 duo, 4 gb ram, Mac OS X (10.5.1)
Currently Being ModeratedDec 13, 2007 8:55 PM (in response to Darren 2007)
To disable safe sleep, run the two following commands in Terminal:
$ sudo pmset -a hibernatemode 0
$ sudo nvram "use-nvramrc?"=false
When done, restart your computer. Now delete the file "/private/var/vm/sleepimage" to free up a good chunk of hard drive space (the amount of RAM you have installed). With safe sleep disabled, a total power loss (i.e., removing your battery without the AC adapter connected) will wipe out whatever was in RAM at the time. Safe sleep is a nice feature, but since I don't switch out my battery and it's never fallen out before, the time I save makes it worth disabling for me (not to mention the fact that it seems to solve the keyboard problem).
I tried this and so far (24 hours) it has been working. I did not delete the sleepimage file, but did run the two commands.
This may be a decent temp solution. I will report back again in a few days.
Entering Day 2 of no keyboard problems thanks to Joebadiah and his terminal commands.
It worked for a while... but today the problem returned. So much for a decent temp solution. I did reboot holding the Command-Option-P-R keys to flush the PRAM. Hopefully that holds for a bit longer. MacBookPro G4 Tower iPod Nano, Mac OS X (10.5)
Currently Being ModeratedDec 14, 2007 5:50 AM (in response to gcgrey)So .... I disabled spaces and still had the problem - rebooted and all was fine. Since then I re-started spaces with no problems. Have come to the conclusion that it is nothing to do with spaces ....
As far as I can see it is something to do with some combination of the use of external keyboard/mouse/other device (USB and/or - possibly - Bluetooth or firewire), sleep/wakeup and then reverting to internal keyboard use. I use an external mouse/keyboard/display at work and then revert to the internal keyboard when at home. I have not had any further problems over the past couple of days.
All I can suggest for now is that if you use external devices always attach/detach them with the mac awake and if you get into the keyboard problem reboot with no external devices attached and go from there.macbook pro, Mac OS X (10.5.1)
Currently Being ModeratedDec 14, 2007 10:02 AM (in response to FelipeSunol)http://www.macosxhints.com/article.php?story=20071130115912235
THIS MIGHT ME A SOLUTION
I've run across this a few times and knew it was a software issue. Once booted into single user mode, the keyboard would stop responding.
The solution is to start the system up normally and open International in System Preference. Under Input Menu, select a new keyboard layout, then select US again. This worked right away for me.Mac Mini, Mac OS X (10.5.1)
Currently Being ModeratedDec 14, 2007 12:53 PM (in response to Galen Bennett)I reset the PMU around 3 days ago and haven't had a reoccurrence since.
Try it!15" MacBook Pro (2.2 GHz Intel Core 2 Duo), Mac OS X (10.5.1)
Currently Being ModeratedDec 14, 2007 3:17 PM (in response to Amberdine)I never have Spaces on, shut down the MBP every night and I've had this problem with the initial Leopard release and the last update. At first I only had the occasional "1st key typed dead" thing (a real pain, thought I couldn't type anymore ...) and now I'm getting the complete keyboard freeze-up every day or so. This has never happened on my Xeon desktop (Leopard), and never on the Mac Book Pro when booted into Vista. I'm beginning to have a different attitude toward those Apple ads - my MBP is more compatible with Vista than Leopard.2.4 GHz Core 2 Duo, Mac OS X (10.5.1)
Currently Being ModeratedDec 15, 2007 9:16 AM (in response to Gus Bird)I'm suffering from the same issue as well. I've got a MacBook Pro 2.4ghz.
Nearly every time it sleeps the keyboard becomes unresponsive when it wakes.
As a recent Microsoft switcher the whole Leopard experience has been a real disappointment. As someone who because of my work was forced to deal with Vista early on I'm afraid Apple are just as guilty of Microsoft of putting out an OS without getting it's basic functionality working. Every new OS is going to have issues but some of the Leopard issues are simply unacceptable. Given the quite justified stick many Apple users give Microsoft it's very disappointing.
More annoying is Apple's attitude. I guess because of their marketing image of an OS that just works it's easier for them to simply ignore issues with their OS.
Now if only my SMB's would work as well.
I'm seriously considering going back to 10.4.
Apple need to pull their finger out, the last thing they need is to earn a reputation like Microsoft in that users are best advised steering clear of their OS's until SP2 at the earliest.MBP 2.4ghz, Mac OS X (10.5.1)
Currently Being ModeratedDec 15, 2007 2:12 PM (in response to LOUDSYSTEM)Same problem here, It happend within the first 4 days I bought my macbookpro, it had been fine for a few weeks but tonight it is really bad. It stopped working 7 TIMES!!!! in less than half an hour!!!
I hope apple comes with a solution very very soon!
Message was edited by: Ellen Andriesmacbookpro, Mac OS X (10.5.1)
Currently Being ModeratedDec 15, 2007 2:38 PM (in response to LOUDSYSTEM)To update...this showed up for me a few days ago.
For fun, I called Applecare today and was given a case number. The tech support person claimed that this problem had never been reported before. He expressed surprise that there was a 250+ message long thread on discussions.apple.com describing the same thing we were talking about.
We did the usual reset PRN thing. I'm sure this won't work but I thought I'd humor the tech. Now that I have a case number I'll call them back and pester them some more the next time it happens....MacBook Pro - 2.4 Intel Core 2 Duo - 4 GB Ram, Mac OS X (10.5.1)
Currently Being ModeratedDec 15, 2007 5:52 PM (in response to Adam Wolkoff)As I mentioned, I did a re-start and have not had the keyboard problem of having to wait to type. My mouse is not as jumpy as it was either. Which makes me think that the issues have something to do with the sleep patern. Except I have only done the re-start once. My space bar still squeaks, would anyone know if there are dampners under the keys, or is there a way of tightening the keys. I am afraid if I take it in to apple they will want to replace the keyboard and send it off! Has anyone ever had a single key replaced? ThanksPowerbook G4, Mac OS X (10.4.10)
Currently Being ModeratedDec 15, 2007 9:28 PM (in response to LOUDSYSTEM)Just to add to this. After going through apple care on the phone, I brought my macbook pro (less than 30 days old) to the geniuses at the apple store. they said it was a known problem with leopard and macbook hardware on ALL machines with Leopard and that there is no current fix for it. Their only "fix" is to revert my laptop back to Tiger and then I wait for the Leopard fix. My computer became basically useless after a while - I sometimes had to wait for 2-3 minutes to type. Needless to say, as I write this on my old but trustworthy PC (with XP), I am not a happy new mac user. The guy at the store was super nice, but not much he can do. I asked about a reset on my Applecare warranty but they said they do not do that. I will try and get this though. My personal opinion is that this is an ENORMOUS flaw in the system and worthy of a major recall or compensation for current owners. Obviously not something apple wants given what it would do the sales, but I am really surprised it is not being talked about more in the press.macbook pro 15", Mac OS X (10.5.1)
Currently Being ModeratedDec 16, 2007 1:57 AM (in response to gioux)Hi there
after almost ten years of windows I finally bought a MBP and I was full of expectations, it is on the way, coming tomorrow. Naturally I started surfing in the Mac world and I found good and bad stuff as usual, but this "cheap keybord problem" is really disappointing me, so I decided to send back the new MPB without opening the box.I hope many others costumers gonna take this decision.
Currently Being ModeratedDec 16, 2007 1:59 AM (in response to LOUDSYSTEM)Sigh.
Yet another MBP keyboard sufferer.
No VMWare here. I do have Parallels installed but haven't run it in weeks.
Debilitating. Embarrassing. Pervasive.
Please fix this bug, Apple.MacBook Pro 2.4, Mac OS X (10.5.1)