Does anyone have suspend (either to-RAM or to-disk) working on 9.3 Pro? If so, does it matter which filesystem is used (ext3, reiserfs, etc.)? tnx, ken -- A lot of us are working harder than we want, at things we don't like to do. Why? ...In order to afford the sort of existence we don't care to live. -- Bradford Angier
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, ken wrote:
Does anyone have suspend (either to-RAM or to-disk) working on 9.3 Pro?
Yes, me :) Both work on my IBM Thinkpad T42 here.
If so, does it matter which filesystem is used (ext3, reiserfs, etc.)?
No, that should not matter. Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz@grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCk3gvSVDhKrJykfIRAorXAJ9zqdLpyeUkOtZQO9JLyeZApdAIggCfbFDR Ez5RQflzVZgGtZPQx67aicI= =HTdQ -----END PGP SIGNATURE-----
On Tuesday 24 May 2005 12:53 pm, Lenz Grimmer wrote:
Yes, me :) Both work on my IBM Thinkpad T42 here.
If so, does it matter which filesystem is used (ext3, reiserfs, etc.)?
No, that should not matter.
Did you find anything that made a difference? 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. B-)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Brad Bourn wrote:
If so, does it matter which filesystem is used (ext3, reiserfs, etc.)? No, that should not matter.
Did you find anything that made a difference?
Sorry, not sure what you mean here.
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"? Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz@grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCk41fSVDhKrJykfIRAsENAJ9c+/a/Ovfsljl361d4vIlbK2VKBACfdq4B nzHaWZlFoomBh2gMheeicBY= =1mnt -----END PGP SIGNATURE-----
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=)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Brad Bourn wrote:
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.
Suspend-to-Disk worked out of the box, after I enabled it. For suspend to RAM, I had to add the following kernel parameter to the the grub menu.lst: acpi_sleep=s3_bios Otherwise the screen would be garbled after a resume.
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.
Have you tried using the "nv" driver instead? It might be the solution, but I am not that familar with the nVidia drivers when it comes to suspending. Also try to post your problem on the suse-laptop list - the guys are quite helpful there.
Are you using the nvidia drivers?
No, the "radeon" driver from Xorg. Using the proprietary ATI driver does not work with suspending at all :(
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.
There are a lot of things you could try. I would recommend you first start by reading /usr/share/doc/packages/powersave/README.suspend(2ram) That should get you started. Good luck! Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz@grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCk5x8SVDhKrJykfIRAl+rAJ4yqePrO6xm8shzNpd0F+2Mqr0YaQCfYi0X Lff7qrqiuvmmuQ90+XDNoD8= =bdIC -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brad Bourn wrote:
Thanks, That does make it seem video related. I'll check into it.
Good luck!
(unless anyone has got it working with binary nvidia driver <hint><hint>)
Check http://susewiki.org/index.php?title=Suspend_NVidia_HOWTO for more hints :) Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz@grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCk55ZSVDhKrJykfIRAniBAJ9vlp/5/0xEvYcpWaZZr/QFyPDuLACdEOa4 oM/wQoy19N50bI2XEjYlZtM= =owi4 -----END PGP SIGNATURE-----
Lenz Grimmer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Brad Bourn wrote:
Thanks, That does make it seem video related. I'll check into it.
Good luck!
(unless anyone has got it working with binary nvidia driver <hint><hint>)
Check http://susewiki.org/index.php?title=Suspend_NVidia_HOWTO for more hints :)
Thanks for this link - I have exactly the same problem as the original poster on my Dell 8600 - suspend to disk works with the software nv drivers, but not with the Nvidia hardware drivers. I'd given up on hardware 3d as suspend is rather more important to me :) I'll try these settings and see if they help. - Korny p.s. suspend didn't work at all in 9.2 or 9.1, but I can't remember if I ever tried it with the software nv driver... Suspend to Ram doesn't work due to some other problem I haven't had time to diagnose. -- Kornelis Sietsma e-mail: korny at my surname dot com
Kornelis Sietsma wrote:
<snip>
Check http://susewiki.org/index.php?title=Suspend_NVidia_HOWTO for more hints :)
Thanks for this link - I have exactly the same problem as the original poster on my Dell 8600 - suspend to disk works with the software nv drivers, but not with the Nvidia hardware drivers. I'd given up on hardware 3d as suspend is rather more important to me :)
I'll try these settings and see if they help.
It worked! I now have suspend to disk working with nvidia drivers - thank you. Hope it helps Ken as well. -- Kornelis Sietsma e-mail: korny at my surname dot com
Kornelis Sietsma wrote:
Kornelis Sietsma wrote:
<snip>
Check http://susewiki.org/index.php?title=Suspend_NVidia_HOWTO for more hints :)
Thanks for this link - I have exactly the same problem as the original poster on my Dell 8600 - suspend to disk works with the software nv drivers, but not with the Nvidia hardware drivers. I'd given up on hardware 3d as suspend is rather more important to me :)
I'll try these settings and see if they help.
It worked! I now have suspend to disk working with nvidia drivers - thank you. Hope it helps Ken as well.
Any idea about how to get back from suspend to ram? I can suspend OK, but can't get back, without killing the power. Suspend to disk works and I can go to standby, but the screen goes all bright. I'm running SuSE 9.3 on a ThinkPad R31.
On Wednesday 25 May 2005 14:02, James Knott wrote:
Kornelis Sietsma wrote:
Kornelis Sietsma wrote:
<snip>
Check http://susewiki.org/index.php?title=Suspend_NVidia_HOWTO for more hints :)
Thanks for this link - I have exactly the same problem as the original poster on my Dell 8600 - suspend to disk works with the software nv drivers, but not with the Nvidia hardware drivers. I'd given up on hardware 3d as suspend is rather more important to me :)
I'll try these settings and see if they help.
It worked! I now have suspend to disk working with nvidia drivers - thank you. Hope it helps Ken as well.
Any idea about how to get back from suspend to ram? I can suspend OK, but can't get back, without killing the power. Suspend to disk works and I can go to standby, but the screen goes all bright.
I'm running SuSE 9.3 on a ThinkPad R31. Try setting your bios to s3 in power management
-- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
ken wrote the following on 05/24/2005 07:52 PM:
Does anyone have suspend (either to-RAM or to-disk) working on 9.3 Pro?
if it helps, i have suse 9.2 pro, and suspend to ram works on my dell latitude d600 (but only with a hard-disk password enabled, so that a video-wakeup is 'forced' on resume) :)
If so, does it matter which filesystem is used (ext3, reiserfs, etc.)?
i dont think it should matter. i have one ext2 partition, one reiserfs and one ext3.. in my installation. (oh, and fat32) clem.
The Tuesday 2005-05-24 at 13:52 -0400, ken wrote:
Does anyone have suspend (either to-RAM or to-disk) working on 9.3 Pro? If so, does it matter which filesystem is used (ext3, reiserfs, etc.)?
In my system it crashes, even if using text mode only. It suspends ok, I suppose, but when awaking, it doesn't get to the end - another day I can copy the error messages if anybody is interested. -- Cheers, Carlos Robinson
On Thursday 26 May 2005 03:03, Carlos E. R. wrote:
The Tuesday 2005-05-24 at 13:52 -0400, ken wrote:
Does anyone have suspend (either to-RAM or to-disk) working on 9.3 Pro? If so, does it matter which filesystem is used (ext3, reiserfs, etc.)?
In my system it crashes, even if using text mode only. It suspends ok, I suppose, but when awaking, it doesn't get to the end - another day I can copy the error messages if anybody is interested.
-- Cheers, Carlos Robinson
How big is your swap? I did a test laptop today purely as a challenge from this thread. I usually make swap double the ram, I made my swap 256, (yes I know, I was testing 128MB, be weary of me I do crazy things :} ) It failed, similar to your error above, so I reloaded with a 1GB swap, and now it works. Cheers -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
The Thursday 2005-05-26 at 07:09 +0200, Chadley Wilson wrote:
In my system it crashes, even if using text mode only. It suspends ok, I suppose, but when awaking, it doesn't get to the end - another day I can copy the error messages if anybody is interested.
How big is your swap?
Two partitions 1G each. RAM is 0.75G
I did a test laptop today purely as a challenge from this thread. I usually make swap double the ram, I made my swap 256, (yes I know, I was testing 128MB, be weary of me I do crazy things :} )
In Linux, swap can be as big as you need. I have an old machine, 32Mb ram, 1 G swap. The "double the ram size" rule comes from the windows world.
It failed, similar to your error above, so I reloaded with a 1GB swap, and now it works.
The error I get is way more complex than that. I suspend from the command line, using swsusp, or the instructions in "/usr/src/linux-2.6.11.4-20a/Documentation/power/swsusp.txt": echo shutdown > /sys/power/disk; echo disk > /sys/power/state or echo platform > /sys/power/disk; echo disk > /sys/power/state All methods fails. Using the last one, in runlevel 3, I get this errors when waking up - notice that most of the errors belong to the "going to sleep" part (hand copied to paper): hda: task_no_data_intr: status=0x51 {DriveReady SeekComplete Error} hda: task_no_data_intr: error=0x04 {DriveStatus Error} ide: failed opcode was: unknown Those three messages repeat three times except that the last one says instead: ide0: friled opcode was unknown \ \ \ \ \- 'r' or 'a'? \- missing ':' - '0' ide0: reset: sucess The whole group repeated several times in what I can see of the screen, except that the 'friled' typo is only present in the last one. hda: task_no_data (same as above) hda:.... (idem) ide: failed opcode was: unknown PM: snapshotting memory swsusp: Need to copy 22021 pages swsusp: Restoring Highmem hub 2-0:1.0: resubmit --> -108 PM: Image restored sucessfully PCI: Setting latency timer of device 0000:00:1f.2 to 64 PCI: Setting latency timer of device 0000:00:1f.4 to 64 ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:00:1f.5 to 64 eth0: link down bttv: reset, reinitialize bttv: PLL: 286363 => 35468950.. Ok The keyboard works, I can switch console - but as soon as I do, I loose those error message above. Prompt does not reappear. I can press enter, the screen moves up a line, no result. I have to hard reset the PC to reboot. Remember, this is text mode, no nvidia involved (and I use the nv driver, anyhow). -- Cheers, Carlos Robinson
participants (8)
-
Brad Bourn -
Carlos E. R. -
Chadley Wilson -
Clement Twine -
James Knott -
ken -
Kornelis Sietsma -
Lenz Grimmer