getting system to wake up with WoL
Currently running Slackware 14.2 with a custom built kernel 4.4.162 and the following NICs
Intel Corporation Ethernet Connection (2) I218-V Intel Corporation I211 Gigabit Network Connection (rev 03) I've turned on WoL on my ASUS X99 Deluxe-II motherboard and am able to get WoL working while dual booted into Windows 10 so I know the hardware is working and ready for WoL. after switching back to Linux however, I can get the system to suspend, but it won't wake up without physical interaction (pressing power or key). I've used 'ethtool' to check the status and turn on WoL Code:
Supports Wake-on: pumbag |
Quote:
Also consider adding the following to rc.local: Code:
# Do not set wol to all supported options. Just 'g'. |
Quote:
|
Quote:
Is the system that sends the WOL magic packet on the same subnet as the Slackware system? That is, does the Slackware system have the correct IP address assigned? WOL is UDP and will only work on the same subnet. Also, there once was (and might still be) a quirk with some NICs on Linux systems that the magic packet has to be sent to the reversed MAC address. For example: Code:
MAC address=AA:BB:CC:DD:EE:FF |
WOL is an SBo package. Do you have it istalled?
|
Quote:
Quote:
|
Quote:
What do you see on the target machine if you run the command as root, /usr/bin/ethtool eth0 ? This is the output from a machine that works for me. Quote:
|
Quote:
Code:
ettings for eth1: |
The only thing I see, is a speed difference between our set ups.
This is just me guessing now. Either there is something wrong with your ethernet card that is not obvious, or the power supply is not responding to the signal the ethernet card to turn on. Have you had a look through your BIOS/UEFI settings for any possible problem? Is it possible to try another ethernet card? |
This is from the Arch wiki on WOL.
Quote:
The entire article. -->https://wiki.archlinux.org/index.php/Wake-on-LAN |
Quote:
Code:
tcpdump -v -i eth1 ether proto 0x0842 Quote:
|
As this is a desktop rather than a laptop, try a different approach. Do not suspend. Instead power down and then attempt awaken the system.
If the system awakens then start looking into ACPI configs. |
Quote:
|
The NIC must have standby power to receive and see the magic packet.
I am guessing your testing with Windows was with that OS in suspend mode rather than powered down. As your testing with suspend mode succeeds, power down from the Windows side. Send the WOL magic packet. If the system fails to awaken, then check the BIOS power management (ACPI) options. If the system awakens then you must already have standby power configured in the BIOS. Many modern motherboards have a single LED to indicate when the system is using standby power. If you have your systems connected through a switch, the respective LED on the switch will remain on when a connected system is powered down but using standby power. |
I remember once I had to add
Code:
/usr/sbin/ethtool -s eth0 wol g |
All times are GMT -5. The time now is 09:15 PM. |