-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-06-30 07:10, Takashi Iwai wrote:
At Mon, 29 Jun 2015 22:49:58 +0200, Carlos E. R. wrote:
Not always, I think.
... when you're lucky :) In most cases the workaround is needed for both.
Typically a problem is a bug (or a lack) of the suspend/resume code, and most kernel drivers use the same function for S3 and S4 in some level.
I know that some machines work fine on hibernate but fail on suspend. And I have seen machines with totally broken suspend; my old desktop stopped the internal fan and the cpu went terribly hot, because it remained powered. In that machine I had to disable suspend to ram. It was a bios bug, I found out later. On a laptop, the USB sockets may remain powered during suspend to ram, so that hacks needed to restart a certain device on wake up might not be not needed on suspend, but it would be on hibernate. However, loading/unloading whatever module on all cases, works always. It just makes things a bit slower. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWScEEACgkQja8UbcUWM1xcVAD/bDiLFomQB8eC3N2ewuK0fPB6 +XtwB4EYKd9YPM5elIUA/2M3d7LwP3saBfIWe2qyDk/a9t1wa2JmTwQ0eGSYnxO7 =KEC1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org