The 'g' in Supports Wake-on: pumbg indicates that wake-on-lan by using a 'magic packet' is indeed supported. Next, you need to make sure that wake-on-lan support is enabled in the BIOS (although, this does not seem to be necessary for my motherboard). In addition, you need to tell your network card to enable wake-on-lan:

# ethtool -s eth0 wol g

When you run `sudo ethtool eth0` again you will see that "Wake-on: d" (disable; wake on nothing) has changed to "g" (wake on magic packet)

Since after rebooting Wake-on will be reset, you will want to add this setting somewhere in your boot up.

Ubuntu 10.04/12.04

To make this setting permanent edit /etc/network/interfaces, in the auto eth0 section (or you might have an auto lo section) add at the end:

ethernet-wol g

Other Linux

To make this setting permanent edit /etc/rc.local:

# nano -w /etc/rc.local

Add ethtool -s eth0 wol g above the 'exit 0' line.

Now turn off you mythbox and send it a 'magic packet'.

Sending 'magic packet' to wake up your mythbox

You will need a wake-on-lan client to send 'magic packets' over your network. First, determine the MAC address of the machine you want to power on:

# ifconfig

Turn off your mythbox and from another computer execute the following command (replacing the MAC address with the one you just found). I used a wake-on-lan client from Sourceforge.

$ wol 00:4F:49:07:0B:5F

If all went well, your mythbox will boot up now! There are other clients for Windows, Mac OS X and iPhone as well.

Via Python one-liner

Maybe not as clean, but works on all systems where Python is available, replace the '\x00\x1A\x92\x9D\x69\x85' with the numbers of your backend's MAC address:

Send automatically from a frontend

By adding one or two scripts into a remote frontend, it will automatically start the backend, and then wait until the backend is ready to accept a client connection. Ideally the frontend and backend would boot concurrently, however that's difficult to arrange without building a special environment (e.g. to boot rapidly from flash memory), so the practical solution is simply to use an /etc/init.d script in the frontend, and wait while the frontend and backend boot serially.

The purpose of the first script is to issue the WOL packet as early as possible. If the overall bootup time is not considered to be an issue, this script can be omitted and the wakeonlan command can be issued from the script which runs from the user's auto-started sessions (called mythfestart.sh, further down). These scripts use 'wakeonlan' from Ubuntu package repos, but wol or ether-wake would work just as well.

After the above script has been placed in /etc/init.d/ (and marked executable with chmod +x ..), it can be made to run at bootup by issuing:

sudo update-rc.d wol defaults

Now we need a script which waits until the backend is ready to accept client connections, before starting mythfrontend. That way, the frontend will start cleanly without any error panels such as "no UPnP backends found", etc. This script can be added to the user's autostarted sessions (in place of the normal 'mythfrontend' script).

Wake-on-LAN supported but just won't wake up

At this writing, the Marvell Gigabit Ethernet controller on the Asus A8V and some other motherboards, using skge driver under Debian Etch may not wake at all while connected at Gigabit speeds to a Gigabit switch. The same hardware may wake correctly when shutdown with Windows in a dual-boot system.

A variety of workarounds have been suggested, from modifying the halt binary to using the NIC at 100 Mbps speeds, to placing calls to ethtool in various startup/network/shutdown scripts, but the simplest path to solution is probably to disable the motherboard network controller in BIOS and replace with a known-good PCI Gigabit NIC (such as the US Robotics 7902 Gigabit NIC).

Wake On LAN, Fedora 11 and Realtek RTL8111/8168 (etc)

This chip seems to be pretty common, along with a lot of problems getting WOL to work...
I suspect this will apply to the following NICs chips

this stops the r8169 module loading after reboot, this is the one that ships with the kernel, and WOL won't work (except for physical activity), which means it will happily use your shiney new r8168 module instead.

It also appears to be necessary to place the following lines into /etc/init.d/halt

/usr/sbin/ethtool -s eth0 wol g # This sets the WOL options on the NIC you may wish to use different ones
sleep 10 # Apparently this is necessary

The above lines need to be the penultimates ones, just above

exec $command $HALTARGS

General remarks

Some motherboards allow a large set of events to wake-up the machine via ACPI. These can be toggled via /proc/acpi/wakeup. Examples of ACPI wakeup events related to Wake-on-LAN:

'LAN0', 'LANC' - The ethernet card

'P0P2', 'PCI0' - The PCI bridge may need to be allowed to wakeup your machine before WOL works. You can find out which is your PCI bridge by matching the first column of lspci output with the last column of cat /proc/acpi/wakeup.

'NOTE:' Using /proc/acpi/wakeup is a legacy system. It is in the process of being split into /sys/devices/[..]/power/wakeup per device. Use echo enabled > power/wakeup on each device node you want to use to wake up the machine. Shortcuts may be available, like /sys/class/net/eth0/device/power/wakeup for your eth0 network device..