Jump to content

S3, WOL, no network


rmons

Recommended Posts

I'm new to unRaid and this is my first post. I just completed the setup of my first server and it has gone quite smoothly. The forums and wiki pages for unRaid have been incredibly useful but I have one thing that I can't find a solution for so I thought I would ask.

 

I noticed the "s3,WOL,no video" thread here and followed it hoping that there would be a mention and solution to my problem which is I no longer have network access to or from my unRaid server after it wakes up. Actually I also have the "no video" problem but I can forgive that if networking would work after waking up since I plan to run it as a headless server anyway.

 

I'm running a box with an Asus M4A785-M motherboard and Sempron processor. To keep things simple I'm using the onboard video and ethernet. I have updated the BIOS to the latest version and have searched for sleep and wakeup related settings and everything seems to be set correctly.

 

It goes to sleep fine and wakes up fine using the wolcmd.exe mentioned here on the forums. But unfortunately once it wakes up, I don't have any network access to the box. I can't ping the IP. I can't ftp to the IP. It doesn't appear to be on the network any longer. The lights on the ethernet port blink and appear to be active but I can't telnet to it or anything.

 

Any ideas would be greatly appreciated.

 

Edit Monday, June 14, 2010

Success!

I got this to work following the suggestions here. For my mobo and onboard NIC the key was adding the following statement to my sleep/wake script:

 

/etc/rc.d/rc.inet1 restart

 

I found that I didn't need to reset the WoL setting of g, my NIC maintained that after waking. It also woke up in 1000Mb/s mode so I didn't need to add that statement either.

 

Just by adding the above statement was enough to resolve my network access issue after waking.

 

Thanks again everyone that helped direct me to this statement and the great sleep/wake scripts offered here on the boards.

 

Cheers!

 

 

Link to comment

Thanks for the suggestion bubbaQ. I installed WinXP and the Realtek drivers for the motherboard but it hasn't helped.

 

I could see all of the settings for the NIC under Windows. I checked them to be sure that they were set as I would expect them. Rebooted into linux/unRaid and when I suspend/resume I still don't have any network access. *sigh*

Link to comment

Thanks for the suggestion bubbaQ. I installed WinXP and the Realtek drivers for the motherboard but it hasn't helped.

 

I could see all of the settings for the NIC under Windows. I checked them to be sure that they were set as I would expect them. Rebooted into linux/unRaid and when I suspend/resume I still don't have any network access. *sigh*

Are you running any commands to re-establish network connectivity after waking the server back up?

 

Most people here have a script of commands that put the server to sleep, and it, when awakened, runs the remainder of the script to re-establish connectivity.

 

Something like these:

ethtool -s eth0 speed 1000

ethtool -s eth0 wol g

 

as an alternative, you could probably just invoke the same script as used when initially setting up the networking:

like this using the "restart" argument.  It will stop the networking and re-start it:

/etc/rc.d/rc.inet1 restart

 

You might still need the two ethtool commands after the restart, to re-enable the wake-on-lan and reset the speed.  In that case, you need to run three commands upon restart.

Joe L.

Link to comment

Take a look through this thread. It's a bit long, but useful reading, and has a very useful script (that Joe L. mentioned) to handle going into and coming out of S3 sleep.

 

In particular, if you are using DHCP to get an address for your unRAID box you may need to force a DHCP renewal when it comes out of sleep as well as resetting the speed.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...