![]() Um, I'm hesitant to type this out as I really know very little about this area (though, incidentally, Lekensteyn above is very knowledgeable about ACPI), but, well, here goes. (2) The machine is getting old and is starting to misbehave so initially I dismissed the wonky behavior as some early impending failure sign. The current kernel shipped by CentOS 6 (2.6.32-431) also shuts down the machine as expected so you might want to try a livecd of a distro with an older kernel to see if the problem goes away. (1) Can't say for sure when this started happening, but current Arch kernels do this (didn't try LTS though), both windows xp and 7 work as expected. there isnt a bios option for wake on lan, you need to set to os and control from there 1 More posts you may like r/feedthebeast Join 2 yr. OS The wake up events will be defined by OS. BIOS Activates the following items, set wake up events of these items. If anything I'd say that this behavior may be a mix of a wonky bios and a kernel regression. Wake Up Event By BIOS Selects the wake up event by BIOS or operating system. It seems that for some systems, having "Resume by pci device pme" will cause the machine to reboot instead of shutdown, and indeed after looking into the bios setting on my desktop system I had that enabled. I have just found one downside though.I don't know if you lost interest or if you solved this already but here's a datapoint of my own: recent(1) kernels make my desktop system(2) reboot instead of shutdown, I have not bothered to look into it because I don't use it very often but after your inquiry I decided to look into my own problem. This way i'll have all of them go to standby after 2 hours idle and hopefully overnight it wont be getting TOO hot in the cupboards or use too much elecricity. System can be powered up by WOL packet when in stand-by mode but not when completely shutdown. When configured to be controller by BIOS it only works partially. if you "Standby" the pc in windows you can wake it from cliknig the mouse or pushing a key on the keyboard but you have to go into device manager and go into the properties of your mouse and keyboard and tick the box that says "allow this device to wake the computer" do that and it works for me fine, like i say regardless of what is set in the bios, agreeing that it just doesnt seem to work at all the bios wake features. When configured to be controller by OS it doesn't work AT ALL no matter what I configure in NIC driver settings in Windows. Avoid this entire range of MSI boards if WOL is important to you.I found that you can set the bios wake to anything and they wont actually affect waking from keyboard and mice in windows. Press F10 to save and exit the BIOS setup. ![]() The whole power control thing seems to be FUBAR in fact. To enable Wake on Lan in the BIOS (below for Intel motherboards): Press F2 during boot to enter the BIOS setup. I've spent over an hour trying to fix this, trying every possible permutation of relevant settings without success, updating the BIOS, changing power settings to OS controlled rather than BIOS, and setting the OS settings to wol on magic packets and wake from shutdown, disabled EUP2013. I'm in a very similar position as you farquea, with 100 new H61M-P23 boards installed.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |