Hello,
today I dealt with the problem Chris mentions in
http://mail.lesswatts.org/pipermail/discuss/2008-February/000157.html
I found a solution in my case (I use 8139too). The very condition
which determined the WOL being activated or not depending on halt or
hibernate, is the eth interface being put to down. That's usually done
by the rc scripts at halt time.
In order to get the WOL activated with a magicpacket, then, I had to (for eth0):
- ethtool -s eth0 wol g
- ifconfig eth0 down
If I don't do any of those steps, I don't have wol. I added a
scriptlet in my hibernating system, the file
/etc/hibernate/scriptlets.d/wol, with the next contents. Please have
in mind that I have a special configuration with a bridge (br0). I had
to call the rc scripts; if I did ifconfig eth0 down and then up, the
route tables lost the gateways.
#-------- start of wol file --------
#Ethernet WakeOnLan
function setwol
{
/usr/sbin/ethtool -s eth0 wol g
/etc/init.d/net.br0 stop
ifconfig eth0 down
}
function resumelan
{
/etc/init.d/net.br0 start
}
AddSuspendHook 01 setwol
AddResumeHook 01 resumelan
#-------- end of wol file --------
Best regards,
Lluís.
_______________________________________________
Discuss mailing list
[email protected]
http://mail.lesswatts.org/mailman/listinfo/discuss
