- Joined
- Aug 3, 2013
- Messages
- 14
- Mac
- Classic Mac
- Mobile Phone
I have a GA-H87N-WIFI motherboard and am running 10.9. Mostly the machine is working quite well now. You can see more about how it's set up here.
I'm experiencing a bizarre problem. I need to access services on the MacOS on demand (primarily samba shares), but the machine will sometimes go to sleep for lack of activity. This is a good thing as it saves power. I can wake the machine without trouble by using the USB keyboard. The problem arises when I try to use the network to wake the machine. This is built into MacOS via the Wake on Demand function, so long as you have a sleep proxy on the network (I do, in the form of an AppleTV 2). This does not work. Even if I try to ssh in (or I try sending new commands to an ssh connection that was open when it went to sleep), the machine stays asleep.
Needless to say I have Wake on LAN enabled in the BIOS (and Erp is disabled) and "Wake for Ethernet network access" enabled under System Preferences->Energy Saving.
To rule out any malfunction in the Bonjour services that support Wake on Demand (what I initially thought was messed up), I tried sending magic Wake on LAN packets to the machine. This also fails to work.
It gets stranger. When I boot Linux, I can see (via ethtool) that wake on lan is enabled in the network card. And if I then shut down the machine, I can indeed use magic packets to wake the machine. However, if I then boot MacOS and immediately shut down the machine without logging in, this no longer works. If I then manually power up and run only the bios setup utility and power down with no changes, I can again use magic packets to wake the machine.
And there's more: when I am in what I assume is S3 ACPI state (sleep mode) under MacOS, I do not see any lights on the ethernet card. By contrast, when the machine is in S5 state (soft power off), the ethernet card is periodically blinking (this is the case regardless of whether or not wake on lan is working while the machine is shut down -- which depends upon whether I've just shut down from macOS or not).
From what I can surmise then, MacOS must be telling the network card to disable wake on LAN while also telling it to power down more during sleep states than it normally does during shutdown states. Both these behaviors are contrary to the stated goals of Apple, which is to support Wake On Demand (which is also what I need).
I'm quite puzzled as to what's going on, but thinking now that it must have to do with the hackintosh ethernet drivers. For the record, although I have both Atheros and Intel drivers installed on my machine (as there are 2 ethernet ports, from apparently different manufacturers, on the motherboard), I'm using en0 and this is the Intel one (evidence below).
Any help would be much appreciated as I'm starting to lose hair over this...
I'm experiencing a bizarre problem. I need to access services on the MacOS on demand (primarily samba shares), but the machine will sometimes go to sleep for lack of activity. This is a good thing as it saves power. I can wake the machine without trouble by using the USB keyboard. The problem arises when I try to use the network to wake the machine. This is built into MacOS via the Wake on Demand function, so long as you have a sleep proxy on the network (I do, in the form of an AppleTV 2). This does not work. Even if I try to ssh in (or I try sending new commands to an ssh connection that was open when it went to sleep), the machine stays asleep.
Needless to say I have Wake on LAN enabled in the BIOS (and Erp is disabled) and "Wake for Ethernet network access" enabled under System Preferences->Energy Saving.
To rule out any malfunction in the Bonjour services that support Wake on Demand (what I initially thought was messed up), I tried sending magic Wake on LAN packets to the machine. This also fails to work.
It gets stranger. When I boot Linux, I can see (via ethtool) that wake on lan is enabled in the network card. And if I then shut down the machine, I can indeed use magic packets to wake the machine. However, if I then boot MacOS and immediately shut down the machine without logging in, this no longer works. If I then manually power up and run only the bios setup utility and power down with no changes, I can again use magic packets to wake the machine.
And there's more: when I am in what I assume is S3 ACPI state (sleep mode) under MacOS, I do not see any lights on the ethernet card. By contrast, when the machine is in S5 state (soft power off), the ethernet card is periodically blinking (this is the case regardless of whether or not wake on lan is working while the machine is shut down -- which depends upon whether I've just shut down from macOS or not).
From what I can surmise then, MacOS must be telling the network card to disable wake on LAN while also telling it to power down more during sleep states than it normally does during shutdown states. Both these behaviors are contrary to the stated goals of Apple, which is to support Wake On Demand (which is also what I need).
I'm quite puzzled as to what's going on, but thinking now that it must have to do with the hackintosh ethernet drivers. For the record, although I have both Atheros and Intel drivers installed on my machine (as there are 2 ethernet ports, from apparently different manufacturers, on the motherboard), I'm using en0 and this is the Intel one (evidence below).
Any help would be much appreciated as I'm starting to lose hair over this...
Code:
$ system_profiler|awk '/^Ethernet Cards/{c=15;next}c-->0'
ethernet:
Type: Ethernet Controller
Bus: PCI
Vendor ID: 0x8086
Device ID: 0x153b
Subsystem Vendor ID: 0x1458
Subsystem ID: 0xe000
Revision ID: 0x0004
BSD name: en0
Kext name: AppleIntelE1000e.kext
Location: /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleIntelE1000e.kext
Version: 2.5.4
.
