Hi,

1.  Make sure that your Interface does not get down, when Linux shuts down. Control this behavior, with the Links on your Switch or maybe there are also light that must not turn off on your interface. The rc_down_interface is perfect for this
   

2.  Have you set wake on lan with ethtools? -> I do it every boot: /usr/sbin/ethtool -s eth0 wol g
   

Ethtool currently doesn't support the tulip on board LAN. But the BIOS should enable WOL. echo -n PCI0 > /proc/acpi/wakeup reenables PCI wakeup, which is required for WOL. And the interface is confugured to not going down on shutdown.

3.  The magic packet must be sent to the broadcast address, since ARP requests do not work! -> my /sbin/wol-htpc script 
   
   

wol --ipaddr=192.168.0.255 00:13:d4:1e:94:73

Now I'm using etherwake and the packets are right.

Now I've patched my kernel with suspend2. Now after hibernating to suspend-to-ram or ACPI S4 WOL is working perfectly. Hibernating to the poweroff mode disables WOL again. Is WOL never possible if the PC is soft powered off?

Another problem: I would like to use alarm ACPI wakeup for booting the PC before the next recording starts. I've not tried this with hibernate, but with poweroff this also doesn't work. Is this the same problem?

Some strange effect is also:

--- # echo "2007-03-03 12:00:00" > /proc/acpi/alarm # cat /proc/acpi/alarm 2007-03-00 12:00:00 # ---

Thanks for another idea, Bernd

Linux usually shuts down all interfaces, when going down (init 0) ..

On Ubuntu it's in: /etc/init.d/networking -> it does an "ifconfig eth0 down" Then WOL then will never work, since the LAN-port is without power.

You may check for: martin@htpc:/etc$ ll rc?.d |grep network lrwxrwxrwx 1 root root 20 2006-06-07 20:45 S35networking -> ../init.d/networking lrwxrwxrwx 1 root root 20 2006-06-07 20:45 S35networking -> ../init.d/networking lrwxrwxrwx 1 root root 20 2006-06-07 20:45 S40networking -> ../init.d/networking

Try this: go into single user mode with "init 1" - check, if there is still power at your network port. If not, your LAN is shut down.

Martin

-----Ursprüngliche Nachricht----- Von: vdr-bounces@linuxtv.org [mailto:vdr-bounces@linuxtv.org] Im Auftrag von Bernd Juraschek Gesendet: Samstag, 3. März 2007 18:53 An: vdr@linuxtv.org Betreff: Re: [vdr] Wakeup On LAN

Hi!

Now I've patched my kernel with suspend2. Now after hibernating to suspend-to-ram or ACPI S4 WOL is working perfectly. Hibernating to the poweroff mode disables WOL again. Is WOL never possible if the PC is soft powered off?

After powering off the PC per long-pressing the power button WOL works perfectly. The normal shutdown seems to disable wakeup :-(

Greetings, Bernd

_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Bernd Juraschek schrieb:

Hi!

...

Now I've patched my kernel with suspend2. Now after hibernating to suspend-to-ram or ACPI S4 WOL is working perfectly. Hibernating to the poweroff mode disables WOL again. Is WOL never possible if the PC is soft powered off?

After powering off the PC per long-pressing the power button WOL works perfectly. The normal shutdown seems to disable wakeup :-(

You might want to try google ;) Assuming from your mail that you speak german also (even if not, it should give you pointers), this might help:

http://de.gentoo-wiki.com/Wake_On_Lan

Looks like the key points are: - you need to switch on WOL on the network card with ethtool (most probably everytime you shut down. (On Gentoo according to the Howto: Edit /etc/conf.d/local.stop like below:

# /etc/conf.d/local.stop

# This is a good place to unload any misc. # programs you started above. # For example, if you are using OSS and have # "/usr/local/bin/soundon" above, put # "/usr/local/bin/soundoff" here. /usr/sbin/ethtool -s eth0 wol g

) - you need to make sure the net interface is not switched off during shutdown. (On Gentoo :

You have to edit /etc/conf.d/rc like below:

# RC_DOWN_INTERFACE allows you to specify if RC will bring the interface # compeletly down when it stops. The default is yes, but there are some # instances where you may not want this to happen such as using Wake On LAN.

RC_DOWN_INTERFACE="no"

)

Looks reasonable from what ihave read until now :)

BTW: Thats the search i have done http://www.google.de/search?q=wake+on+lan+gentoo&start=0&ie=utf-8&am... ;)

HTH

Steffen

Hi,

Regarding waking up at a certain time: Go to the wiki in read carefully about nvram-wakeup.

This damn Siemens D1605 board is not supported by nvram-wakeup. First Siemens has some own checksum calculation and second guess-helper isn't able to guess the CMOS addresses for the alarm clock.

Thinking about using ACPI wakeup, cat /proc/acpi/alarm tells me "2007-03-00 19:03:00" with 00 for the day - regardless of the value written into. But - I've not tested this with S4 mode.

Alarm wakeup is not urgent for me because I use my router to wakeup the PC the right time. The PC safes the time into the router before it hibernats. The router uses this time to wakeup the PC per WOL.

Greetings, Bernd