hallo Stefan Seyfried wrote: > Hi, > > (taking suspend-devel into cc:) > > On Fri, Dec 08, 2006 at 02:39:47PM +0100, IOhannes m zmoelnig wrote: >> hi. >> >> i found that my hp-pavilion notebook is not in the s2ram whitelist. >> >> umlautg:/home/zmoelnig# s2ram -i >> This machine can be identified by: >> sys_vendor = "Hewlett-Packard " >> sys_product = "Pavilion zv5200 (PR976EA#ABD) " >> sys_version = "F.34" >> bios_version = "F.34" >> See http://en.opensuse.org/S2ram for details. >> >> suspend to ram works fine, if i just pass the "-f" flag ("s2ram -f") > > Only from X or also from text console?
iirc, it only managed to make it work from X. this is: my first attempts following the suggestions (e.g. booting with init=/bin/sh and trying from there) where not very successfull. however, i haven't tried with my patched kernel yet. i'll do that when i find the time and give you more information on this. > >> there is one problem however: after resume, the harddisk does not start >> again. i fixed this by applying the attached patch to my 2.6.18-kernel. > > If this is still necessary with 2.6.19, how about reporting it to the > kernel list? It has, however nothing to do with s2ram as we are just > doing the video stuff :-) i am aware of this. i just added this information (and my kernel hack) to my report, in order to make it as complete as possible. personally, i don't favour incomplete (bug-) reports very much. i haven't tried 2.6.19 yet; i have also heard rumours, that the "am" or "mm" patchset to the kernel fixes my problem. >> the only remaining problem is, that after i resume from suspend2ram into >> X, my virtual-terminals (Ctrl-Alt-F1..Ctrl-Alt-F6) seem to be fu**ed up >> (cursor has vanished; scrolling does not work anymore; however >> everything else works fine); the laptop is equipped with an nvidia-card >> GeForce4 420 GO) and i am running the proprietary drivers from nvidia; >> probably the problem is here ... > > They are notorious for fscking up the console, so this is something > you'd probably need to report to nvidia. i thought so. i am not sure yet how problematic this behaviour will be for me on the long run. > > But maybe just posting the card after resume by means of s2ram options > would also make it work better. See http://en.opensuse.org/S2ram for an > explanation on how to use them. i will have a look, thanks for the hint. > >> s2disk works fine too (here there are no problems with the terminals) > > This hints at some problems the X driver has with the uninitialized card > after resume from RAM (after s2disk, the card is initialized by the BIOS). i found one more potential problem: with a patched version of the suspend-tools (to accept my laptop), i put my notebook into sleep mode with s2both. there it stayed for 1 week (or so), with the power chord connected (so it was still in s2ram mode). resume did not work properly (it booted, but the card did not get initialized properly). so i guess it is not "all fine" yet. one more thing: would it be possible to add a "--force" flag to the "s2both" utility, just like with "s2ram" ? mf.adrs IOhannes ------------------------------------------------------------------------- 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
