Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[sapnho]

I am posting this here out of sheer desperation for I haven't been able to get a solution on quite a few hardware forums. So I thought, let's go where the experts are! And it does have a quite important MC background anyway.

I have all my music stored away on a ethernet wired server. The server's mainboard is a simple VIA ME 6000 and it does what it is supposed to do - except wake up on Lan from either standby or hibernate mode. Now the strange thing: It WoLs perfectly from a shutdown! But whatever I have tried I can't get this machine to wake up from hibernate or standby.  However, this is an important element of my whole setup because when a user turns on a local jukebox, the server is being fired up as well. Needless to say that the convenience factor is severely reduced when this takes two minutes instead of 10 seconds! The function seems to work for many other users with the same mobo and the WoL function works fully on other computers in my network.

Could those of you who have WoL working just help me with things I may have missed?

As a sign of my desperation, I promise a bottle of champagne to the one tip which makes this thing work - shipped to wherever you would like to enjoy it! (exchangable for beer or wine if you fancy... )

[KingSparta]

I somtimes wonder why people even use standby or hibernate

the only thing i can use is turn off the monitor due to some software I run on it.

I have never found that standby or hibernate work all that well anyway. some devices refuse to function after a standby or hibernate (like usb or firewire drives). they sometimes disconnect and the only way to get them back is re-boot

[Dutch Peter]

Is there a special reason why you want your machines to go into standby?
I have read it in your post.
I agree with KingSparta, but maybe you ahve special requirements.

Dutch Peter

[sapnho]

The reason is that I want the machine to wake up very quickly. As it only serves as a fileserver, the hibernate or standby has never been a problem. I used to wake it up via IR in the past and it was never an issue.

I use standby on my jukeboy every day and it works like a charm.

[JimH]

I wonder if the hibernate state also powers off the network device.  The device can probably be set to ignore OS attempts to power it off.

[sapnho]

The strange thing is that WoL out of shutdown works. I wonder what the system differences are between shutdown and hibernate in terms of the network device. Shutdown should theoretically be the most powered-down state.

[akak718]

Power management has come a long way from where it was a few years ago. In my experience, cheap chipsets often do a bad job on implementation. Companies like VIA and SIS are cheap, but you  get what you pay for. I've had a lot of success with Intel chipsets on both Intel and Asus motherboards. The one and only VIA (its an Asus motherboard) chipset I ever had works poorly.

Hmm, that is very strange that it would work after shutdown but not after hibernate. From a hardware standpoint, those two states are identical. The only difference is that a hibernate file is stored on your harddrive that windows uses to restore the previous memory contents. But the hardware knows nothing about that.

The first thing you should do is make sure you have the latest BIOS for your motherboard. From your post, it sounds liek your network device is integrated on the motherboard. It is BIOS responsibility to properly save and restore device settings on power state transitions. Once that is done, go through your BIOS setup menu and look for setting to enable WoL. For Shutdown and hibernate modes, BIOS is in (almost) complete control.

For standby (and to a lesser degree hibernate), your best bet is to make sure you have the latest drivers for your network device, then make sure it is set up from within windows. From device manager, open the properties page for your network device. There shoud be a "Power Management" tab with a checkbox that says "Allow this device to bring the computer out of standby." Realize that this setting will ONLY affect "standby" and has nothing to do with the "hibernate" or "shutdown" states.

I hope that helps. I work for a large computer hardware company and have a good bit of experience with this stuff in general, but not with your specific hardware. Let me know if anything is unclear or you have any other questions.

-Lou

[Mastiff]

sapnho, get yourself a PCI NIC. They are cheap, and it will probably work a lot better.

But the thing with setting up power management can actually affect hibernation as well. Don't ask me why, but I just now tested it on a computer here, and it does.

[sapnho]

sapnho, get yourself a PCI NIC. They are cheap, and it will probably work a lot better.

If I can wake up from shutdown, the basic mechanism seems to work. Other people with the same board manage to wake up from hibernate as well. Does anybody here have the VIA EPIA ME 6000?

[gpvillamil]

I think the point is, why bother to have the server go into standby at all? Why not just leave it on all the time?

The VIA motherboard + chipset you mention is a pretty low power unit, if I am not mistaken.

[GHammer]

If I can wake up from shutdown, the basic mechanism seems to work. Other people with the same board manage to wake up from hibernate as well. Does anybody here have the VIA EPIA ME 6000?

Have you went to the MS Knowledge Base?

Article ID : 815304 is one that may apply.

Are you certain that ACPI or APM is setup the same in the BIOS for all the machines?

[sapnho]

sapnho, get yourself a PCI NIC. They are cheap, and it will probably work a lot better.

I may consider this after all. I just wonder why would an external card make it work but not the internal one?

[Mastiff]

I have no idea. But I have experienced it myself (with an old NForce 1 chipset mobo with built-in NIC), so it's always worth a shot.

[sapnho]

Mastiff,

pm me where you want the bottle to be sent to! It works!

Heaven knows why but I put in a D-Link PCI NIC, updated that driver (it didn't word with the original one)...and a miracle occured.

Thanks very very much!

[Mastiff]

No problem. Even though they say everything in a computer is 0 and 1, I do firmly believe that there are some 0,5's as well. That was one of them!

[Shady Bimmer]

Two notes:

1) standby and hibernate are two different states.  Standby is typically more usefull for battery-powered devices such as laptops.

2) As already indicated hibernate from a hardware perspective is the same a a shutdown.  If poweron from poweroff works correctly, but poweron from hibernate does not then the NIC driver would be the first place I'd look.  Many NIC drivers do not handle restoring a previous state from a hibernate - the most significant difference between shutdown and hibernation.

Hardware device drivers have many responsibilities - including initialization of hardware that is typically in an unknown state.  Being able to also initialize to an arbitrary saved state may in fact require additional coding. . .though technically the OS should provide the layer of abstraction to remove this requirement.

Everything is indeed 0 and 1, but how those bits are handled depends on many, many factors.

[sapnho]

I also have the suspicion that a driver problem is probably at the root of the problem but whatever I tried, it just didn't work. I am using another EPIA Board (12000) where everything works as it should with the build-in NIC so EPIA is not the issue.

But whatever...it works now with the new PCI NIC...