Can't wake Lion over wifi (or ethernet) using iPad and home sharing.

Rayced wrote:

LexSchellings wrote:

A firmware update (WiFi Firmware Update 1.0 for iMac) just came out today.

That only affects a bunch of models made in 2009. I don't think that's gonna solve this issue.

Meanwhile I've managed to get through it dumping (once again…) the preference file /Library/Preferences/SystemConfiguration/com.apple.PowerManagment.plist then let the system make it again by opening and editing the power managment pref pane. Now it works if I put to sleep mode the computer, I don't know yet if it's gonna work when the computwer goes automatically in sleep mode (I still have to test it) after the proper time I've set in the preferences.

As I thought the wake on demand feature stop working as the computer goes to sleep by itself.

Just to add, I have a late 2009 iMac and if my computer goes to sleep by itslef (via power settings) I cannot reach it from my apple TV. In fact, I can be watching a movie on the Apple TV and all the sudden I lose my home share. My only solution to that small problem was to make the HD sleep period longer than the buffering time of the apple TV.

Perhaps the EFI update will help you...

I have also tried putting a fresh com.apple.PowerManagment.plist in the Library but this didn't work for me.

Trying the Dark Wake edit of the com.apple.Boot.plist. Will let you all know if it works for me although. I'm apprehensive of changing things in the the system that aren't user options as I don't have the knowledge to know if this isn't having further knock on effects with other settings. If anyone can tell me what side effects this may have to my system, i'd appreciate it.

The darkwake 0 works for me, so I'm really pleased about this. The question I have is, what is the side effects of using this? will it effect my system elsewhere? and what is the differnece between darkwake 0 and darkwake 1?

At the moment though I have wake over WAN working again with the apple remote and a VPN client. Also I was under the impression that the mac would wake fully but the screen stays off unless I use VPN (which is what I wanted as there's no need for my screen to be on if I'm just serving media to my AppleTV's)

Cheers MirkoW

Ok spoke too soon, MacPro back in coma mode!

you should set the "darkwake" to "1". READ the link that Mirkov gave, read it completely.

LexSchellings, how about instead of the patronising capitalised READ comments, why don't you give the solution or constructive help, instead of wasting everyone's time?!

If you had read the post yourself, you would have seen that it doesn't mention anywhere to change the "darkewake' to 1 and in fact the defualt setting for OSX Lion is 1 so it would just put me back to the exactly how the system was in the first place.

because it IS the solution. In Lion the deafult value is 0.

Added: In mIrkow's entries the 1 is mentioned several times...

Are you reading a different post to the rest of us? Please be my guest and link to the part that specifically says to add a string that reads:

<key>Kernel Flags</key>

<string>darkwake=1</string>

It clearly says

<key>Kernel Flags</key>

<string>darkwake=0</string>

Within the link at the bottom of Mirkov's post it also states that this string is to be added to the boot.plist and will DISABLE the darkwake which will resolve the Mac not waking over the network!

the above string isn't present and you have to add it. At No point does it mention you have to put the following!

<key>Kernel Flags</key>

<string>darkwake=1</string>

This would be pointless as the defualt for Lion is already darkwake=1, that's why it isn't in the original boot.plist.!!

So in other words, your fix for this problem is to include a string in the boot.plist telling Lion to do absolutely nothing different?

This maybe YOUR solution not THE solution.

No sir, as I said it is fully explained by mirkov's link. Test in your and everybody's mac in System Information/ hardware section/ power and look at "PrioritizeNetworkReachabilityOverSleep": you will see the default 0. After you change the 0 to 1, you will see the 1, and you do not even have to restart.

And, btw, it is not my solution.

Thanks but i'm not sure what has this got to do with darkwake string? This, as you have pointed out, is the "PrioritizeNetworkReachabilityOverSleep" which is located in the com.apple.PowerManagement.plist and not the com.apple.Boot.plist, where the darkwake string is placed?

The "PrioritizeNetworkReachabilityOverSleep" was an unrelated question ask at the bottom of the link. And if you look at my posts you will see that I have already tried this with no results which is why I went on to try the darkwake work around suggested by Mirkov, to which I directed my questions.

I'm bumping up my last question:

Do other users experience the same behavior as I do when letting the mac sleep by itself rather then manually switching it to sleep?

To be more clear: if I switch the mac to sleep mode via apple menu or using the power button, it'll wake on demand, otherwise if I let it go to sleep mode by itself (ie when is elapsed the time specified in the preferences for energy saving) it'll not be able to wake up on demand.

If that's the common problem, do users started to experience it after 10.3 upgrade or were they experiencing it also under older Lion's versions?

Thanks.

Again, no sir.

you came in this thread with a "solution" for Jonathan, and then hacked the thread with your own problem. Darkwake has nothing to do with the problem and should not be used at all.

@ LexSchellings: I'm confused, I thought this was a forum for people to help with solutions to mac problems, admittedly my solution didn't work and by sharing in the trouble shooting that I had done, in the hope of enabling others to save time by trying the same, or not as their preference leads them. My questions about darkwake where in context to the solution to this thread as it was offered as a solution by Mirkov. So as for hacking the thread with my own problem? The problem I have is identical to Johnathans as most others on this thread, hence the reason we are all here? So I'm not sure how this would class as hacking the thread, by your own definition anyone with a question other than Johnathan is hacking the thread.

@ Rayced: I have had no issues with wake on demand with either manual sleep or timed sleep until i installed 10.7.3 from 10.7.2 and likewise with airport firmware 7.6.1 from 7.6.