Hi Garrett, Thanks for the quick reply.
> Solaris does not officially support wake-on-lan. > Sometimes it happens to > work "by accident", but most of the time you can't > count on it. > Wake-On-Lan is something we need to spend some time > figuring out, but > its confounded by the fact that there is no good > standard for how to > wake up a system that doesn't require special help > from routers or > switches. (The details of this require an > understanding of how switches > and gear works, along with ethernet ARP and IP > details, so I won't go > into it. Most devices require a special "wakeup" > packet to be sent to > them, and generating that packet can be ... m... > challenging.) > Hmm, I thought WoL is a BIOS feature, and OS simply got an event. But I have no expertise in this area. I do get a simply Ruby script I can issue the magic packet to that system and trigger resume. Get back to the topic, the situation is the same if I wake up the system from power button or in the case keyboard or mouse if I enable PS2 KB/MS S3-S5 option in BIOS. Another interesting finding, if I enable "RING" as a wake up event in BIOS, the system resume successfully immediately before fully suspended. Jan 14 21:35:28 nas genunix: [ID 535284 kern.notice] System is being suspended Jan 14 21:35:34 nas genunix: [ID 122848 kern.warning] WARNING: Unable to suspend device mouse at 2. Jan 14 21:35:34 nas genunix: [ID 537702 kern.warning] WARNING: Device is busy or does not support suspend/resume. Jan 14 21:35:34 nas /sbin/dhcpagent[95]: [ID 967406 daemon.warning] refreshing state on rge0 Jan 14 21:35:34 nas /sbin/dhcpagent[95]: [ID 778557 daemon.warning] configure_v4_lease: no IP broadcast specified for rge0, making best guess Jan 14 21:35:34 nas /sbin/dhcpagent[95]: [ID 732872 daemon.error] dhcp_bound_complete: cannot add default router 192.168.123.1 on rge0: File exists Jan 14 21:35:35 nas genunix: [ID 583038 kern.notice] System has been resumed. Jan 14 21:35:36 nas gnome-session[799]: [ID 702911 daemon.warning] WARNING: Could not ask power manager to suspend: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. -- This message posted from opensolaris.org
