http://bugzilla.novell.com/show_bug.cgi?id=905988 --- Comment #27 from Paul Tannington <paul.pgp-7@gmx.com> --- (In reply to Benjamin Poirier from comment #26)

Thank you for this explanation. Is it correct then to say that you used the same procedure to shut down the system in both the "turn off" and "power off" cases (i.e. "(KDE) Leave -> Turn off computer")? The difference is only that in the second case you also unplugged the computer (or shut off the power supply).

Yes, that is correct. "Turn off" (computer in standby mode) retains the wol setting on restart. After "Power off" (power disconnected) and restart the wol setting reverts to "ug".

If that is correct, then it rules out power off scripts fiddling with wol settings. It seems likely that the nic retains wol settings so long as it has power and looses them otherwise. The next thing to check is whether they are somehow initialized in a different way in 13.2 compared to 13.1.

When you test the 13.1 kernel using the instructions in comment 15, please also test the reboot, "turn off" and "power off" cases to see if the behavior is the same.

OK. However prior to that, a few observations. "Something" has changed, as I was previously using openSUSE 13.1, 3.11.10-21 kernel on this same hardware with suspend/resume working correctly. To try to eliminate my own (software) setup I booted, from a "power off" condition, with the "live" version of openSUSE 13.2 (openSUSE-13.2-KDE-Live-x86_64.iso Last modified: Thu, 30 Oct 2014 15:16:32 GMT). Ethtool reported wol as "ug". There was an immediate restart after suspend to ram, although for some reason this did not complete. I repeated that using a USB stick on which I still had a copy of V13.1 (openSUSE-13.1-KDE-Live-x86_64.iso Last modified: Wed, 06 Nov 2013 15:56:17 GMT). Ethtool reported wol as also being "ug"! When suspended to ram the nic (as indicated by the connected router) had dropped down to 10M and was still active, but there was no (unwanted) restart. Manual resume also failed to complete, I'm guessing that has something to do with the live environment and can be ignored. I appreciate you efforts on this, but I don't see any other bug reports about this behaviour. 13.2 has been released for about a month now and I believe the realtek nic is fairly common still. Whilst I'm quite happy to provide information where able, please don't forget that I have a work-around for this problem coutesy of Takashi Iwai from Comment # 10 - I don't know that it is worth pursuing, but you are the judge of that :) -- You are receiving this mail because: You are on the CC list for the bug.