On Tuesday 24 May 2005 02:24 pm, Lenz Grimmer wrote:
Did you find anything that made a difference?
Sorry, not sure what you mean here. Did it just work? Did you have to do ANYTHING to get it to work aside from just enable it? That is all I have done so far.
I have an new 64-bit HP laptop zv5000 I think. It will suspend, but when renewing, it reboots back to normal startup and cleans the disk.
"Cleans the disk"? Please elaborate. Does it simply do a "normal" bootup instead of resuming? What do you mean by "clean"?
I went to yast and enabled both suspend to disk and suspend to ram. When I go back to my desktop and right click the plug/battery icon, on the context menu is the options for suspending to disk or ram. They both act the same. I will see the dialog box in the middle of my desktop giving my percentage written to ram or disk. Then I will see my screen go blank followed by very bright psychedelic patterns for a split second then power off (if suspend to disk) or suspend (if suspend to ram). Then by hitting the power button again to bring back, I'll see the suse screen, then text mode showine the progress of the reading back to ram, and then it (seems like when it tries to init the video card) reboots again. This time it doesn't see the suspended state/flag/boot sector/grub option/etc. and boots normally causing fsck to run and see the disk messy (I assume from the suspend) and cleans it up. Don't know the exact messages, but they are the same as if you just shut off the machine and not init 6 it properly. I am using the binary video driver for nvidia with the options nvidia NVreg_Mobile=0 option set in modules.conf file. Are you using the nvidia drivers? Any insight you may have from ANY tweak that you needed to do aside from simply enabling it, gotchas, common problems, lack of support for certain things, etc. would be greatly appreciated. Thanks is advance. B=)