iMac after 10.6.8 update no more Wake for network access!!

Same here... iMac (late 2009)

I connect through a ssh linux server to the iMac (in ssh), but after the update (10.6.8), when the iMac is asleep for some time, the network card just goes down. No problem waking it up from bluetooth keyboard/mouse, but will not wake up on network access anymore.

If someone find a fix other then removing the sleep mode, it will be appreciate.

Tastolini,

Can you tel me if in SystemPreference->EnergySaver you have the "Start up automatically after a power failure" option turn on? If so, can you try to uncheck it and test if your system now wake from sleep on network access. Look like it work for me, but I am still in testing mode to find where the conflict is.

In the end it didn't work for me either (turn off "Start up automatically after a power failure" ) 😟

I will continue testing, but this weekend I'm away, so i'll be back on this problem monday...

Let me know if you find a solution.

I have the same problem with my year old Mac Pro. Worked fine with 10.6.7 but ever since I upgraded to 10.6.8 I have been unable to wake through either screen sharing or file sharing. Both are still checked on in my system preferences, as is "Wake for network access". I tried unsetting and resetting to no avail. File and screen sharing both work fine if the machine is already awake. I have a static IP address assigned to the Mac Pro and will try changing that tomorrow to see if that helps.

If anyone can track this down I'd appreciate an update.

Note: my "Start up automatically after a power failure" has always been off (and still is)

MacPro5,1. OS X (10.6.8)

OK. I did some network sniffing for my screen sharing situation. My laptop tries to establish a TCP connection on the vnc-server port. My Time Capsule then intercepts this and broadcasts the expected WOL magic packet that SHOULD wake up the Mac Pro. It's got the correct ID and everything. It looks like the network traffic makes sense. But the Mac Pro ignores the wake over LAN magic packet and doesn't wake.

So it looks as if the problem is with the Mac Pro receiving the WOL, NOT the laptop broadcasting stuff wrong or a Time Capsule issue.

I'm still stumped, but I'm going to keep on digging.

OK. I fixed the problem, for me at least. My time capsule wasn't even showing a light on for the ethernet port, the card in my mac pro was clearly powered down which would explain why the magic packets go missing.

10.6.8 contained a modified version of /System/Library/Extensions/IONetworkingFamily.kext, more specifically /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/Intel82574L. kext.

I replaced IONetworkingFamily.kext with the version that was present before the 10.6.8 update and my WOL now works once more.

So I'm pretty sure right now that 10.6.8 broke my WOL and I'm also pretty sure I fixed it but I'm not sure what other issues I'm causing as a result.

I have no idea how I get a reaction from Apple given that I have no "support credit" but surely they should support a customer with regressed software. Anyone got any ideas?

I have the same problem with a 2010 Mac Pro. Ever since 10.6.8 the network card goes down totally when the machine sleeps, and the system can't be woken over the network. I've stopped the machine from going to sleep while I try to raise the issue with Apple tech support.

I can confirm this works also. Thanks!

GeekyPaul wrote:

OK. I fixed the problem, for me at least. My time capsule wasn't even showing a light on for the ethernet port, the card in my mac pro was clearly powered down which would explain why the magic packets go missing.

10.6.8 contained a modified version of /System/Library/Extensions/IONetworkingFamily.kext, more specifically /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/Intel82574L. kext.

I replaced IONetworkingFamily.kext with the version that was present before the 10.6.8 update and my WOL now works once more.

So I'm pretty sure right now that 10.6.8 broke my WOL and I'm also pretty sure I fixed it but I'm not sure what other issues I'm causing as a result.

I have no idea how I get a reaction from Apple given that I have no "support credit" but surely they should support a customer with regressed software. Anyone got any ideas?

The solution propose by GeekyPaul is working, and look stable (No syslog error). And the wake for network access work fine now 🙂

Thanks

GeekyPaul wrote:

I replaced IONetworkingFamily.kext with the version that was present before the 10.6.8 update and my WOL now works once more.

It didn't work for me (on my mid 2010 mac pro) - the network interface failed to be visible on restart, and when I replaced the original kext file the system then didn't boot at all, not even into single user mode. I can't see how these two facts can be related, but I thought I'd mention it anyway.

I should just have waited for Lion :/

Not the same here (MacPro 4,1): the solution proposed by GeekyPaul disabled network at all. I must restore 10.6.8 IONetworkingFamily.kext so I still looking for a workaround and hope Apple will patch this issue because for now I won't upgrade to Lion (I need to use some PPC apps) and won't regress to 10.6.7 (because 10.6.8 seems to have better graphic performance, and turning back it's not so simple as upgrade).

Borgo: I initially had the same problem as you - the older IONetworkingFamily.kext caused networking to stop working entirely. I believe this was because I restored it to the desktop before copying it, so the permissions got broken. I managed to screw the system up a bit trying to fix this and ended up restoring from a time machine backup. The backup I used had been taken with the older kext in place, and the system now wakes from network as it should, so I think GeekyPaul's solution is correct, but possibly a bit tricky to implement properly.

OK, I'll try again when I turn back... now I'm away from my MacPro, can't wake it up 😉

OK, I tried with time machine and all went right.

The previous try I first set owners and permissions as they were, and then did a repair, but it didn't work. With time machine it seems all right (network is OK, didn't try wol yet but guess it's OK too).