Hi, I have been testing s2ram and suspend to disk quite thouroughly, and conclusions are that there is stil the main to do :(
s2ram I have tried to change /etc/pm/config s2ram parameters to many of that listed on http://en.opensuse.org/S2ram, but none functioned more than once - first suspend to ram was successful with every s2ram parameter (with some parameters, resuming occurred first after pressing win key several times), after the second suspend to ram resuming failed in approx 90 %. It seems to me, that the problem is not s2ram related, but to suse itself. suspend to disk With suse 10.2 final I have made approx. 15 experiments, all worked fine but the last one was alarming - in the evening, I suspended the machine to disk, on the evening resumed and was surprised, that 20 % of the battery has been consumed, and a message box telling suspend failed - this implies that the machine still consumed electricity. (for comparison - win 2000 boots although suspended to disk, if network cable is plugged in - one has to plug the cable out for the computer not to spontaneously trigger the resume - this is NOT the case in suse - I have tested it). With suse 10.1 final, s2ram -f -a3 worked fine (except for one minor problem not inhibiting the functionality), and flawless. Suspend to disk worked also smoothly, although approx 5% were extremely slow (approx. 5 - 10 min - that is not acceptable) (i did it approx 200 times). So, have a lot of energy to explore whats the problem :) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Suspend-devel mailing list Suspend-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/suspend-devel
