My first thought was to simply start broadcasting WOL magic packets over the network, but my Raspberry Pi is not waking up. So I'm assuming it either doesn't support WOL, or I haven't properly configured it.

While I wouldn't be suprised if the pi's operating consumption is comparable to many desktop's waiting-for-wake-on-lan consumption, it would be an interesting question if there is enough public information available about the SOC to do clock throttling and achieve a lower power idle state.
– Chris StrattonAug 3 '12 at 0:01

3

I am using RampBMC on my Pi and I can tell you this. Using the xbmc remote app on the iPhone has a shut down feature. When I tell it to shut down it does. IT DOESN'T REBOOT. The screen goes blank and the only thing lit up on the Pi is the red power lite. Thats it. It may have power to it but it is not running XBMC. I am also interested in a WOL option. I want to be able to put a piece of double sided tape on my Pi and stick on the back of my TV and never have to touch it. The XBMC iPhone app also has WOL option by the way.
– user13657Mar 22 '14 at 14:53

@AlexChamberlain Yes, but once the OS is halted you can't get it back without rebooting.
– JivingsAug 3 '12 at 9:37

2

@Jivings Can you reboot using the WoL support in the LAN chip?
– Alex ChamberlainAug 3 '12 at 9:38

12

Its not just the Pi, going to sleep also puts external HDDs to sleep which can mean significant power savings or simply prolong the life of HDD.
– MrchiefDec 29 '12 at 4:10

2

Ok, so the new RaspBmc spins down external HDD after 20 minutes of inactivity - sweet! You can also configure the time period to anything like. So I guess WOL takes a back seat for now! :)
– MrchiefJan 1 '13 at 4:16

4

I think what people fail to realize is that the Raspi does not have an 'ON' button, so this would come in handy to turn on a Raspi has been turned 'off'
– pukOct 10 '13 at 1:14

@Jivings : how to boot after it has been halted ?
– user1648Sep 27 '12 at 8:32

5

You are wrong. Just issue a 'poweroff' command from the console while power is attached and it will turn off. Now it is connected to the power supply, but it is not on. There's plenty of software that turns the device off through a similar soft-off method. WoL would then theoretically turn it back on.
– OctopusDec 3 '14 at 18:36

I'm facing the same issue for a long time. But I use a trick to WOL my Raspberry Pi's (I use several RPi's in the museum where I work).
I tackled the issue using an inexpensive ethernet power relay.

Here is my trick:
I connect an ETH002 board (from Devantech) to the network. Power of the RPi is connected through the output NC (Normally Closed) of a relay.
As the relay is normally closed, when main power is switched ON, both systems start up.

When I send a "sudo halt" command to the RPi, this goes off.
To wake it again, I send the following command to the relays board (assuming the Relay 1 is in use):

//deactivate relay 1

PacketSender\PacketSender.exe -txw 500 IPaddress 17494 "21 01 00"

// wait some seconds...

//reactivate relay 1

PacketSender\PacketSender.exe -txw 500 IPaddress 17494 "20 01 00"

where IPaddress is the IP address of the relays board and port 17494 by default.

-- PacketSender is a very good freeware, Thanks to the developer --

Doing so, I completely switch off the RPi and power it on again.
e.g when there is an evening event in the museum. Looks like WOL.

So why would one have to have a BIOS just to have a clock? Lots of stuff have clocks, and even RTCs without BIOS... And why would one need a clock to WOL? All it would take to WOL: Logic to short 2 pins when the ETH firmware detects WOL packages. If the ethernet controller firmware could run in a low power state, and had access to both GPIO 5 and 6, then it would be no problem... raspberrypi.stackexchange.com/a/19754/24295
– svin83Jul 12 '18 at 19:01

Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).