On 12/22/06, <b class="gmail_sendername">Peter Stuge</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Dec 21, 2006 at 04:21:18PM +0100, Shaddam Corrino IV wrote:<br>> However, I think that 2nd and subsequent soft power off/on cycles<br>> would work if the system would be put in stand-by mode in the right<br>
> way.<br><br>If the system is suspended it is not power on, but resume or wakeup.<br><br>Wake-on-USB could be done just as Wake-on-LAN but it would trigger<br>pretty often since USB host controllers are very thin devices, as
<br>opposed to a network controller.</blockquote><div><br><br>I found out that the "apmsleep -s 00:01" (with little 's') does not wake up on either network or usb. However, "apmsleep -S 00:01" does almost what I want. The apmsleep with big S does not seem to shut down hdd, but I can do that using hdparm.
<br><br>I have problem since the "apmsleep" with big S does not only wake up (correctly) on USB, but also on broadcast network packets! Disabling "wake up on network" in BIOS won't help, nor ethtool
<br><br># ethtool -s eth0 wol g<br>Cannot get current wake-on-lan settings: Operation not supported<br> not setting wol<br># dmesg | grep eth<br>eth0: Lite-On 82c168 PNIC rev 32 at ca812000, 00:A0:CC:62:2B:2A, IRQ 10.<br>
<br>Argh!<br><br><br><br></div><br></div><br><br clear="all"><br>-- <br>Thanks!<br>Shaddam IV