[mythtv-users] WOL - was Backend powered off/shutdown unexpectedly!

[Simon Fisher]

Some other WOL anomalies I experience which you might find useful to know about

One of my machines will respond to a WOL unless it's had mains power removed since being shutdown. That is with the
machine running I can issue a shutdown and later send a WOL and it will awaken and boot. If the machine is disconnected
from the mains power and reconnected it won't respond to a WOL but needs physical press button to boot.

An old machine I use as a data backup destination host booted for a few minutes periodically throughout the day has a
slow NIC on the motherboard which will respond to WOL and a faster additional plug-in NIC which won't. I have both
connected cabled to the network switch. I target the MAC address of the one on the NIC for WOL, and use the other one
for all other network traffic.


Simon


> Yann Lehmann has pointed you to what I believe is the best guide to WOL for Ubuntists like you and me.
> But be aware that, in my experience, cards (and built-in network interfaces) behave in one of three
> ways:
> 
> * They don't support WoL at all.  Game over; get a card that does ...
> * They support WoL by default without you having to do anything.
> * They support WoL but only if you tell them to do so.
> 
> In my case (and I have two machines like this) they fit into the third category, and I /have to enable
> WoL each time I boot the machine/.  I have an ethtool line in one of the startup profiles (there are
> so many I forget which one) which issues the "ethtool -s eth0 wol g" command.
> 
> Occasionally I boot something else (bootable CD usually) and then when I later reboot into Ubuntu I
> have to go downstairs and switch the machine on physically.