I know there is no warranty on motherboards.
I looked through the BIOS of PC1 (DZ68BC 0028 BIOS, i5-2500K, 730 SSD) and saw that Wake-on-LAN was set to "Power on - Normal boot." The other relevant settings -- "Deep S4/S5" and "Wake system from S5" -- were disabled by default. I disabled Wake-on-LAN because it's not one of my use cases. I also disabled Wake-on-LAN on PC2 (DH67CL 0160 BIOS, i5-2500K, Samsung SSD).
Soon thereafter PC1 sometimes refused to start by pressing the power switch. I had to press and hold the power switch to start it. So I went back and re-enabled Wake-on-LAN. So far I have not seen the power switch strangeness again. However, PC2 does not have the strangeness.
DH67CL BIOS release notes has an entry in 0132 BIOS ("Fixed issue with monitor sleep states") and an entry in 0151 BIOS ("Fixed issue where the monitor will not remain in sleep state after waking from S3"), which could explain why PC2 has no Wake-on-LAN strangeness.
To my questions:
- The Intel page http://www.intel.com/content/www/us/en/support/boards-and-kits/desktop-boards/000006002.html Configuring Wake-On LAN for Intel® Desktop Boards explains that Wake-on-LAN is only useful for remote management, e.g. AMT. Is the above DZ68BC behavior a bug or am I missing something?
- The BIOS explanation for "Deep S4/S5" is: "If enabled, system will use less power while in S4/S5 sleep states, but will wake from S4/S5 only via power button or RTC alarm." Does this mean that pressing the keyboard would no longer wake the system if "Deep S4/S5" is enabled?
- DZ68BC BIOS release notes has an entry in 0036 BIOS ("Fix issue with Wake up system from S5 setting" happened") and an entry in 0035 BIOS ("Fixed issue where monitor will not remain in sleep state after wake from S3"). Is there any way to know if either of these would fix my issue?
UPDATE: Since no one answered, I thought I'd roll the dice. I reverted the BIOS settings to default and then used Express BIOS to move to 0035, 0036, 0037, 0039, and then 0042, doing each one in order as Intel personnel have often recommended. 0037 took so long I thought the board was bricked. 0042 added a message about the Marvell controller having no virtual disk even though I have the Marvell type set to AHCI and always have because I do not use it. Then I disabled Wake-on-LAN and shut it down. Now, power-on is even worse, as I have to hold the power switch in for about five seconds to start it.
In regard to the first question, yes, the behavior if the DZ68BC board it is a bug, because regardless if the wake-on-LAN is enable or disable, the board should turn on when pressing the power key without holding it.
Did you restore the BIOS to defaults and try it again?
For the second question, according to the information we have, in order to wake the PC from S4/S5 states, you need to press the power key, the keyboard and mouse will not work, they will only work with S1, S2 or S3 states.
For you third inquiry, since you already try the BIOS update to all those versions and the problem got even worse, that indicates that it seems to be a problem with the BIOS or the board itself.
Since the board is now retired and discontinue, certain options like a new BIOS released will not be available, since Intel is not developing any software solutions for this board anymore, let me apologize for that and for any type of inconvenience.
Just in case, if you have the proof of purchase for the board, and it shows that it was purchased less than 3 years ago, the board will be under warranty and we can replace it for you.
If you are interested in the replacement, please get in contact directly with us through chat, email, phone or online support, you just need to select boards on product type and you will get those options:
http://www.intel.com/content/www/us/en/support/contact-support.html# @12 http://www.intel.com/content/www/us/en/support/contact-support.html# @12
Any questions, please let me know.
Yes, I used F9 a few times to go back and forth between defaults, but nothing changed. And I knew that Intel left the motherboard business, so I wasn't expecting any more BIOS updates.
Yes, that is correct.
So, if you tried the BIOS update and restore the BIOS to defaults and the problem remains, then, the problem will be the board itself.
Normally we recommend to try different BIOS versions, but you did that too, so, it seems to be a defective board.
Any questions, please let me know.