I have installed Leopard without any problem, but I have noticed a problem that recurred twice: my MBP no waking up from sleep when one or more firewire HDs are attached.
Is anyone having the same issue and is there a fix?
I don't have com.apple.AutoWake.plist, but the computer appears to work fine so far. Perhaps you'd only have that if you scheduled your computer to wake up at a certain time?
I too have a PowerMac G5 and Apple Studio Display and since upgrading to 10.5 cannot awaken my Mac from its sleep, no matter how it fell asleep or for how long. I have tried the suggestions to correct it, but alas, still nothing and a painful reset required to get back up and running.
I have disabled auto-sleep by setting the energy saver to never, but this is not a good thing, it costs me more money and impacts on the environment.
It's really frustrating and I do feel that Apple should offer some support in these situations. OK, I know that Applecare exists and there is 'free' support for the initial ownership of new hardware, but when they release a new OS which we all pay for, that then seriously disrupts the usability of our machines, they should be offering support and making statements somewhere. Of course, they won't want to make statements as it will put others off purchasing the new OS until the problems are solved, although I fear looking at the threads about similar problems with 10.4 they might not do this for quite some time.
Now I know why I stuck with 10.3.9 for so long...
And I completely forgot there was no longer support for Classic, thus losing two of my most used apps - oops...
You know, I got the can't find preferred network dialogue when I first logged on after the upgrade and it suggested my preferred network.
I didn't really think about it until now as I'm actually connected by ethernet cable so it didn't really matter. But I have now just had another look and my machine isn't even recognising my Airport card anymore... What on Earth is happening?
I have the first series 15" MacBook Pro, and my machine would not go completely asleep. The light on the latch comes on at a low level (like when Energy Saver dims the screen), but it never started to pulse. The only way to get the machine back was to power it off by holding the power button. When I powered it on, it would try to wake from hibernation, then immediately reboot. I tried reseting the SMC and deleting com.apple.PowerManagement.plist, but what finally worked for me is deleting the sleepimage file.
(As RP Daley notes, the com.apple.PowerManagement.plist file is in Library/Preferences/SystemConfiguration/).
If you have an Intel Mac and deleting the PowerManagement file doesn't work, you can try deleting the hibernation file at /var/vm/sleepimage. You can't browse to it in the Finder, so select Go -> Go to Folder... and enter /var/vm and press return. Or, on a Terminal command line enter:
I found the file and deleted it, but this did not fix the problem.
When my computer is asleep for more than a few minutes it sometimes but not always wakes up with a "letterboxed" blue screen, and I have to unplug the power to reboot. Others have reported some connection to the number of external drives attached...I have two FW drives. When they are disconnected, the problem seems to go away, but I'll have to wait and see about that.
so it seemed to have worked, but when I just woke up my mbp after about 2 hours of sleep, the screen popped right up and it looked like it woke up just fine, but then when I tried to work on it, it was completely locked up. I managed to check istat before it competely went down and it had my cpu at like 75% use when only mail was open??? Any ideas?
Thanks a lot Sonicjay.
Your post solved the problem for me too. I haven't had any freeze from wake since yesterday.
So far so good. And I hope those of you who are still in trouble will find a solution soon, for it was a very annoying bug.
Regards
D.
Well, it worked for me temporarily...I'm starting to have the issue again. When I powered off and back on, the crash report referenced the video card, so I'm thinking maybe a driver update is in order. I'll call Apple back on it tonight or tomorrow and see what else they have to say.
it only worked temporarily for me also. I called apple and they had me re-install leopard but this time select the option "archive and install." I have had no more problems since.
Ditto here. My PB worked fine for a day or so after the fix, then I crashed it again by unplugging the USB hub while it was sleeping. After that the crashes were as frequent as before.
I scheduled my Mac Pro to wake up at 7am this morning, and it did it no problem. One thing that has crossed my mind is the SMB connections.. The new Shared list of nearby computers (including Win machines) is great, but connecting to them is still very problematic, and has caused a couple hangs. I'm thinking that the times that I had trouble waking from sleep were after sessions where I connected to my windows server..not positive on this yet, but I'm investigating it. I'm mildly considering a clean install to eliminate any upgrade weirdness, but really don't want to do that if possible. I'll keep you all posted.
I have Leopard installed on four Macs, one G4, one G5 iMac, one MacBook Intel, and one iMac Intel. Three of the four wake from sleep normally, but the iMac Intel will not wake from a computer generated sleep. (It even goes to sleep sooner than I have selected in Energy Saver) If it does wake, it takes nearly a minute, and I get spinning beach ball and sluggish performance, and generally am forced to restart. In the discussion group, many have had this problem. One solution was to remove a preference file called, "com.apple.PowerManagement.plist", trash it and restart. I do not have that file in the Library / Preferences folder nor in my user / Library / Preference folder. It appears that many have this problem.
I just took my MBP to the Genius Bar for this very issue. The "PowerManagement.plist" fix above didn't work for me. No matter how it goes to sleep, it will not wake up. The technician then booted my MBP from their network drive (which was cool, i've never seen it done before - they plug their ethernet cable to the machine and hold down the N key, so it booted from the same drive that all the other macs in the store boot from.) Anyway, we tried to do a sleep from there and all we got was the beach ball - it didn't even go to sleep! It just hung. He said it looked like a hardware issue - my response was how can an OS install cause a hardware issue!
Since its under warranty, I had to leave my MBP with them and they'll "replace some parts" and ship it back to me in a week or so. I'm lucky that I have a G5 at home, and also backed up all my data from the MBP before this whole fiasco. If it is indeed some kind of hardware problem, I feel bad for everyone whose machine is out of warranty!
This marks the last time I EVER install an OS on release day! No matter how cool Steve Jobs keynotes are...
