kricker

The latest script in this thread takes care of that for you I believe. It has settings to not let the server sleep if there is network access or the discs are not spun down. Download the script and open it up to look at it. The settings are all in the first part of the script.

Can someone who understands all the changes and modifications please update the wiki accordingly? Maybe also add info about using bwm-ng and pm-utils and why one would need them. It has been awhile since I played around with s3 and unraid. When I came back to this thread I was overwhelmed at all the changes and additions to the original s3.sh script . I was wanting to reset mine up from scratch but now I am somewhat confused on what script would be best to use and what the bwm-ng package and pm-utils package do.

I though about s2ram, but since I don't even have a monitor hooked up to it now, it didn't really matter. I just used the monitor to get it setup.

Anyone have a clue why this may be? Most likely it's due to a bug/feature in the MB BIOS implementation of S3. Seems to be. After flipping ACPI bios settings willy nilly, it is now working....mostly. It doesn't re-post video on resume, but I don't care. It's a headless system now that its running anyhow.

Anyone have a clue why this may be?

I have got a system to wake from S3. But once it does, the shares are not accessible, nor can I telnet into it or view the webgui. It is as if the system is either hung or not re-negotiating the Ethernet link. I used the sleep script from the wiki which has a line to re-establish the dhcp. I believe it is a copy of the one from this post. After more testing it appears the system will wake from s3 properly if a monitor is attached, but not if there is no monitor attached.

http://lime-technology.com/forum/index.php?topic=4405.30 Did that not work for you?

Just tired beta 4.5.7 with the new kernel and my system still doesn't wake by magic packet. I have to manually press the power button. After waking, I see my NIC is still getting reset to wake on: d. It is set to g before I send the sleep command. Is there something going on during the process it does before sleeping that is causing this to happen? I've read some posts around the net where people are modifying certain files such as rc.local. Does either of these have any bearing here? Oddly enough I also noticed if I set eth0 to wake on "pumbg", after I wake it manually it will be set on "pumb", the g goes away.

Good notes. Hopefully one day I'll be able to use them BTW, on step 6, I am pretty sure you have to spin down the drives before sleeping or you will always end up with a parity check on resume.

Okay, I'm not quite there yet. Maybe if a new beta comes out it'll have that or newer kernel.

uuuhmmm? Is that a compile yourself kinda thing?

Linux 2.6.29.1-unRAID. root@Tower:~# uname -a Linux Tower 2.6.29.1-unRAID #2 SMP Thu Apr 23 14:17:18 MDT 2009 i686 Intel(R) Pe ntium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux root@Tower:~#

Whatever is in 4.5-beta6

As per bubbaq's earlier advice, I hooked up an old drive installed windows and set the NIC to WOL. It is working fine with windows XP. The strange thing though is that the NIC light still goes out while in standby. But, it does wake with a magic packet nicely. After confirming this, I rebooted into unRAID. I telnetted in and checked the NIC using "ethtool eth0". The NIC was set to "Wake-on: g": I stopped the RAID then executed the sleep command "echo 3 > /proc/acpi/sleep". The PC would not WOL at this point. I could still wake it with the keyboard. After I woke it using the keyboard I checked the NIC again. This time it said "Wake-on: d". I believe this means it was disabled. Did it get disabled before it went into sleep?

Is this a drive option you are setting using a WD tool? Or a BIOS option you have?

Take a look at this post here. Use the code posted there to create a WOL.py script. Edited it ad described in the post for your needs. You can then run that from XBMC a few ways; manually whenever you want to wake the NAS, you can link to it using an autoexec.py script which will run whenever XBMC is first launched, or edit the skins .xml file and add a second onclick action to the menu item that takes you to the media on the NAS <onclick>XBMC.RunScript(Q:\scripts\Wake\WOL.py)</onclick>

Is that the actual command you typed? I've tried all sorts of commands that looked similar, but that exact one doesn't look familiar. Which build of unRAID did you use that with, and do you have and mods to it?

You got the link to that?

Nooooo...... There is no package for s2ram.... what you downloaded was the source code. You have to compile it.... and for that you need a dev system, or at least a BUNCH of packages (and more than 512MB RAM if doing it under unRAID) in order to compile source. After looking thru the file I thought it might be source code, but I wasn't sure since my knowledge of Linux is still very minimal. Oh well. I guess I'll just sit back and wait a little longer. Thanks for the input.

Sorry to be such a noob, but which version of s2ram should I get. I understand unRAID is built off Slackware, but I don't see that listed on the s2ram page. I saw a mention from a forum post somewhere that they got s2ram from slacky.eu. Unfortunately, that page is in Italian. EDIT: Okay I searched for the "Suspend" package on the slacky.eu page and it led me to http://suspend.sourceforge.net/. Is that the correct package? I'm off to go read up on how to install it now. EDIT2: Okay so I renamed suspend-0.8.tar.gz (from the sourceforge link above) to suspend-0.8.tgz and from /boot I executed: installpkg suspend-0.8.tgz Then I tried to execute: s2ram and got: s2ram: command not found I'm guessing it's either the wrong package or I did not install it properly. As a side note it appears there are no "removepkg" or "pkgtool" commands available.

I don't think I'm sending my system to sleep mode properly anymore. I send it the command "echo 3 > /proc/acpi/sleep" and it goes off. My NIC lights is off, but I can see that my ATI USB remote is getting power (it has a red LED that is lit up). When I press a key on the leyboard it does come on, but it looks like a full reboot. I see the BIOS post and then the normal boot to unRAID sequence. Am I sending the wrong command for sleep?

My German is way too rusty to follow that page...care to summarizes the key bits?

I was assuming one could use something like a Bart's PE or such to set the card from windows without having to actually install windows.

In some cases, you have to use Windows to force the registers on the NIC. Boot Windows, and then go to driver options for the NIC, and select all the options there. Also go to power management in the NIC, and make sure that "allow this device to bring the computer out of standby" is enabled, and disable "allow the computer to turn off this device to save power." I know that should make a bit of difference, but some NIC drivers in Linux have some bugs when it comes to setting registers for things like WOL.... but it you do them first in Windows they will stick. Also, go to the latest unRAID beta... the .29 kernel has a number of s3 suspend improvements. My bench machine does not suspend with unRAID 4.4.2 but does splendidly with 4.5-Beta6. Great Tips. I'll try the new beta first, then see if the windows tricks do any good. With the new beta, does one still have to do all tweaks to turn it on and set the card?

Same here. The system goes to sleep, and I can see that the LAN light is still on for the NIC, but it just will not wake from a magic packet. Frustrating.