Chris Cooke wrote: > Hi, > > Thanks a lot for the help, much appreciated! > >> Remember this is hibernation-specific. > > Yes, that's right - I can configure a network interface to respond to > wake on LAN using "ethtool -s eth0 wol g" and then power down the > machine with "poweroff", and the machine will then boot when I send a > Magic Packet from another machine using "ether-wake". That gives me a > fall-back position - it's at least possible now to envisage some sort > of automatic shutdown and startup system. > > However when I try the same thing but suspend or hibernate the machine > instead of powering it down, it doesn't respond to magic packets. > >> I think it's most likely to be suspend scripts unloading network >> drivers prior to hibernation. > > Ah, nice idea, thanks. I've just had a look in /etc/pm/hooks and > there is a "10NetworkManager" script there which shuts down the > network interface! I've commented out the bit which does the shutting > down, then tried ethtool and ether-wake as above, but unfortunately > the machine still doesn't respond either while suspended or while > hibernated :-( None of the other scripts in /etc/pm/hooks or > /etc/acpi/events are network-related - are there any other places I > should be looking? On Ubuntu, the equivalent of /etc/pm/hooks/50modules ends up unloading my network driver module. > > I remember reading somewhere that machines in a sleep state need a > different sort of packet to wake them up, like Phy instead of > MagicPacket? But I never did find any definite information about > that. The ethtool command in theory lets me set a number of "wol" > states - from its man page: > > wol p|u|m|b|a|g|s|d... > Set Wake-on-LAN options. Not all devices support > this. The > argument to this option is a string of characters > specifying > which options to enable. > p Wake on phy activity > u Wake on unicast messages > m Wake on multicast messages > b Wake on broadcast messages > a Wake on ARP > g Wake on MagicPacket(tm) > s Enable SecureOn(tm) password for MagicPacket(tm) > d Disable (wake on nothing). This option clears all > previous > options. > > ... however for my machine's interface it will only let me set "g" or > unset it with "d"; none of the others are possible. > Using ethtool to query the state of the interface it says "Supports > Wake-on: g". > I have no idea if the limitation is a hardware thing, or a software > bug, or what. > It'd be great to be able to resume a machine on demand with wake on > LAN but I (still) can't get it to work. "p" is permitted on mine, but I don't know that it does anything useful. I think the options are limited by the hardware (though obviously driver support is needed too).
The other limitation to look out for is that some hardware (including mine, but I'm not sure how wide=spread this is) will forget about wake-on-lan if power is lost (i.e. during blackouts or if unplugged). > However this doesn't matter as much as it could because I've found out > how to make wake alarms work - telling the machine before you sleep it > exactly when it should wake up again. Sure. _______________________________________________ Discuss mailing list [email protected] http://mail.lesswatts.org/mailman/listinfo/discuss
