I'm using the stock suspend with SLED 10 (which seems to be almost the same RPM as in Suse 10.1 - suspend-20060406-9.8).
S2RAM reports the following on my machine:
This machine can be identified by:
sys_vendor = "Sony Corporation"
sys_product = "VGN-A190(UC)"
sys_version = "C0003EL3"
bios_version = "R0030F1"
I would like to report a limited amount of success using s2ram and standard suspend-to-disk on this machine. Limited because, perhaps one time out of five, the machine just hard locks when it wakes up from a suspend to disk or ram. I am using the proprietary ATI drivers ( 8.27.18) and suspend is still relatively stable.
I have noticed a few other problems with suspending:
1. Suspend to ram still uses battery at about 50% the normal rate, even when suspended! The laptop also stays very warm when suspended.
2. Both suspends take a long time to wake up from (and aren't very fast at suspending). It take perhaps 30 seconds to resume from ram and more from disk.
3. Even after resuming from RAM the disk sometimes doesn't come online immediately. I can run some commands but commands that access the disk like 'ls' stall the machine for 10-20 more seconds until I hear the disk spin up and everything goes back to normal.
I have some questions that I hope someone can help me with:
1. Is it normal for s2ram to use so much battery when suspended or is this specific to my machine?
2. Might the battery usage during s2ram have to do with my display driver? Maybe its not powering down properly?
3. Is it possible that upgrading to the new version, as explained by Pavel below, could fix these issues?
4. Would it be useful to just upgrade the suspend user tools or do I have to also update the kernel?
thanks,
Sheer
On 7/31/06, Pavel Machek <[EMAIL PROTECTED]> wrote:
Hi!
> I have invented an installation procedure for SUSE 10.1 that allows the user to
> integrate s2disk (s2both) with powersaved and put the resume binary into the
> initramfs image created by mkinitrd.
>
> The instruction is appended and the scritpt and patches referred to in it are
> attached. Some file paths are hardcoded, but I don't think it's a big deal.
>
> Comments welcome.
Looks good to me, but I did not try it. (I guess you have just saved
some work for Stefan -- we'll probably want to use s2disk for suse10.2
:-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
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
------------------------------------------------------------------------- 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
