[patch] suspend: update documentation

[patch] suspend: update documentation

[Pavel Machek]

Update suspend documentation.

Signed-off-by: Pavel Machek <pavel@suse.cz>

---
commit 8972d0ff145879e53416ac77c4cd096fd3cfe227
tree f901592e816f4cfae7383f443b21a13f67a644f8
parent a6500a8820a9b271105fe92e5d3013f7c2875b44
author <pavel@amd.(none)> Tue, 12 Jul 2005 11:04:31 +0200
committer <pavel@amd.(none)> Tue, 12 Jul 2005 11:04:31 +0200

 Documentation/power/swsusp.txt |    7 +++++++
 Documentation/power/video.txt  |    9 ++++++++-
 2 files changed, 15 insertions(+), 1 deletions(-)

diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
--- a/Documentation/power/swsusp.txt
+++ b/Documentation/power/swsusp.txt
@@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
 system is shut down or suspended. Additionally use the encrypted
 suspend image to prevent sensitive data from being stolen after
 resume.
+
+Q: Why we cannot suspend to a swap file?
+
+A: Because accessing swap file needs the filesystem mounted, and
+filesystem might do something wrong (like replaying the journal)
+during mount. [Probably could be solved by modifying every filesystem
+to support some kind of "really read-only!" option. Patches welcome.]
diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt
--- a/Documentation/power/video.txt
+++ b/Documentation/power/video.txt
@@ -46,6 +46,12 @@ There are a few types of systems where v
   POSTing bios works. Ole Rohne has patch to do just that at
   http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2.
 
+(8) on some systems, you can use the video_post utility mentioned here:
+  http://bugzilla.kernel.org/show_bug.cgi?id=3670. Do echo 3 > /sys/power/state
+  && /usr/sbin/video_post - which will initialize the display in console mode.
+  If  you are in X, you can switch to a virtual terminal and back to X using
+  CTRL+ALT+F1 - CTRL+ALT+F7 to get the display working in graphical mode again.
+
 Now, if you pass acpi_sleep=something, and it does not work with your
 bios, you'll get a hard crash during resume. Be careful. Also it is
 safest to do your experiments with plain old VGA console. The vesafb
@@ -64,7 +70,8 @@ Model                           hack (or
 ------------------------------------------------------------------------------
 Acer Aspire 1406LC		ole's late BIOS init (7), turn off DRI
 Acer TM 242FX			vbetool (6)
-Acer TM C300                    vga=normal (only suspend on console, not in X), vbetool (6)
+Acer TM C110			video_post (8)
+Acer TM C300                    vga=normal (only suspend on console, not in X), vbetool (6) or video_post (8)
 Acer TM 4052LCi		        s3_bios (2)
 Acer TM 636Lci			s3_bios vga=normal (2)
 Acer TM 650 (Radeon M7)		vga=normal plus boot-radeon (5) gets text console back

Re: [patch] suspend: update documentation

[randy_dunlap]

On Tue, 12 Jul 2005 11:05:10 +0200 Pavel Machek wrote:

| Update suspend documentation.
| 
| Signed-off-by: Pavel Machek <pavel@suse.cz>
| 
| ---
| 
| diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
| --- a/Documentation/power/swsusp.txt
| +++ b/Documentation/power/swsusp.txt
| @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
|  system is shut down or suspended. Additionally use the encrypted
|  suspend image to prevent sensitive data from being stolen after
|  resume.
| +
| +Q: Why we cannot suspend to a swap file?

Q: Why can't we suspend to a swap file?
or
Q: Why can we not suspend to a swap file?

| +
| +A: Because accessing swap file needs the filesystem mounted, and
| +filesystem might do something wrong (like replaying the journal)
| +during mount. [Probably could be solved by modifying every filesystem
| +to support some kind of "really read-only!" option. Patches welcome.]
| diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt
| --- a/Documentation/power/video.txt
| +++ b/Documentation/power/video.txt
| @@ -46,6 +46,12 @@ There are a few types of systems where v
|    POSTing bios works. Ole Rohne has patch to do just that at
|    http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2.
|  
| +(8) on some systems, you can use the video_post utility mentioned here:
| +  http://bugzilla.kernel.org/show_bug.cgi?id=3670. Do echo 3 > /sys/power/state

That attachment is weird for me.  It downloads as "attachment.cgi", but
it's a tar.gz file.  :(        (using firefox if it matters)

| +  && /usr/sbin/video_post - which will initialize the display in console mode.
| +  If  you are in X, you can switch to a virtual terminal and back to X using
| +  CTRL+ALT+F1 - CTRL+ALT+F7 to get the display working in graphical mode again.


---
~Randy

Re: [patch] suspend: update documentation

[Nigel Cunningham]

Hi.

On Wed, 2005-07-13 at 03:24, randy_dunlap wrote:
> On Tue, 12 Jul 2005 11:05:10 +0200 Pavel Machek wrote:
> 
> | Update suspend documentation.
> | 
> | Signed-off-by: Pavel Machek <pavel@suse.cz>
> | 
> | ---
> | 
> | diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
> | --- a/Documentation/power/swsusp.txt
> | +++ b/Documentation/power/swsusp.txt
> | @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
> |  system is shut down or suspended. Additionally use the encrypted
> |  suspend image to prevent sensitive data from being stolen after
> |  resume.
> | +
> | +Q: Why we cannot suspend to a swap file?
> 
> Q: Why can't we suspend to a swap file?
> or
> Q: Why can we not suspend to a swap file?
> 
> | +
> | +A: Because accessing swap file needs the filesystem mounted, and
> | +filesystem might do something wrong (like replaying the journal)
> | +during mount. [Probably could be solved by modifying every filesystem
> | +to support some kind of "really read-only!" option. Patches welcome.]

This is wrong. Suspend2 has supported writing to a swap file for a long
time (since 1.0), without requiring the filesystem to be mounted when
resuming. We just need to store the bdev and block numbers in the image
header.

Regards,

Nigel
-- 
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened. 

Re: [patch] suspend: update documentation

[Pavel Machek]

Hi!

> | diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
> | --- a/Documentation/power/swsusp.txt
> | +++ b/Documentation/power/swsusp.txt
> | @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
> |  system is shut down or suspended. Additionally use the encrypted
> |  suspend image to prevent sensitive data from being stolen after
> |  resume.
> | +
> | +Q: Why we cannot suspend to a swap file?
> 
> Q: Why can't we suspend to a swap file?
> or
> Q: Why can we not suspend to a swap file?

Thanks, fixed.

> | +
> | +A: Because accessing swap file needs the filesystem mounted, and
> | +filesystem might do something wrong (like replaying the journal)
> | +during mount. [Probably could be solved by modifying every filesystem
> | +to support some kind of "really read-only!" option. Patches welcome.]
> | diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt
> | --- a/Documentation/power/video.txt
> | +++ b/Documentation/power/video.txt
> | @@ -46,6 +46,12 @@ There are a few types of systems where v
> |    POSTing bios works. Ole Rohne has patch to do just that at
> |    http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2.
> |  
> | +(8) on some systems, you can use the video_post utility mentioned here:
> | +  http://bugzilla.kernel.org/show_bug.cgi?id=3670. Do echo 3 > /sys/power/state
> 
> That attachment is weird for me.  It downloads as "attachment.cgi", but
> it's a tar.gz file.  :(        (using firefox if it matters)

I think I actually got that file from server somehow, but it was not
exactly easy :-(.
								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.

Re: [patch] suspend: update documentation

[Pavel Machek]

Hi!

> > | Update suspend documentation.
> > | 
> > | Signed-off-by: Pavel Machek <pavel@suse.cz>
> > | 
> > | ---
> > | 
> > | diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
> > | --- a/Documentation/power/swsusp.txt
> > | +++ b/Documentation/power/swsusp.txt
> > | @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
> > |  system is shut down or suspended. Additionally use the encrypted
> > |  suspend image to prevent sensitive data from being stolen after
> > |  resume.
> > | +
> > | +Q: Why we cannot suspend to a swap file?
> > 
> > Q: Why can't we suspend to a swap file?
> > or
> > Q: Why can we not suspend to a swap file?
> > 
> > | +
> > | +A: Because accessing swap file needs the filesystem mounted, and
> > | +filesystem might do something wrong (like replaying the journal)
> > | +during mount. [Probably could be solved by modifying every filesystem
> > | +to support some kind of "really read-only!" option. Patches welcome.]
> 
> This is wrong. Suspend2 has supported writing to a swap file for a long
> time (since 1.0), without requiring the filesystem to be mounted when
> resuming. We just need to store the bdev and block numbers in the image
> header.

Uh, and then you pass something like resume=/dev/hda5@BLOCKID on
command line? Okay, that could work.

Does this look fair?

Q: Why can't we suspend to a swap file?

A: Because accessing swap file needs the filesystem mounted, and
filesystem might do something wrong (like replaying the journal)
during mount.

There are few ways to get that fixed:

1) Probably could be solved by modifying every filesystem to support
some kind of "really read-only!" option. Patches welcome.

2) suspend2 gets around that by storing absolute positions in on-disk
image, with resume parameter pointing directly to suspend header.


								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.

Re: [patch] suspend: update documentation

[Nigel Cunningham]

Hi.

On Wed, 2005-07-13 at 08:51, Pavel Machek wrote:
> Hi!
> 
> > > | Update suspend documentation.
> > > | 
> > > | Signed-off-by: Pavel Machek <pavel@suse.cz>
> > > | 
> > > | ---
> > > | 
> > > | diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
> > > | --- a/Documentation/power/swsusp.txt
> > > | +++ b/Documentation/power/swsusp.txt
> > > | @@ -318,3 +318,10 @@ As a rule of thumb use encrypted swap to
> > > |  system is shut down or suspended. Additionally use the encrypted
> > > |  suspend image to prevent sensitive data from being stolen after
> > > |  resume.
> > > | +
> > > | +Q: Why we cannot suspend to a swap file?
> > > 
> > > Q: Why can't we suspend to a swap file?
> > > or
> > > Q: Why can we not suspend to a swap file?
> > > 
> > > | +
> > > | +A: Because accessing swap file needs the filesystem mounted, and
> > > | +filesystem might do something wrong (like replaying the journal)
> > > | +during mount. [Probably could be solved by modifying every filesystem
> > > | +to support some kind of "really read-only!" option. Patches welcome.]
> > 
> > This is wrong. Suspend2 has supported writing to a swap file for a long
> > time (since 1.0), without requiring the filesystem to be mounted when
> > resuming. We just need to store the bdev and block numbers in the image
> > header.
> 
> Uh, and then you pass something like resume=/dev/hda5@BLOCKID on
> command line? Okay, that could work.
> 
> Does this look fair?
> 
> Q: Why can't we suspend to a swap file?
> 
> A: Because accessing swap file needs the filesystem mounted, and
> filesystem might do something wrong (like replaying the journal)
> during mount.
> 
> There are few ways to get that fixed:
> 
> 1) Probably could be solved by modifying every filesystem to support
> some kind of "really read-only!" option. Patches welcome.
> 
> 2) suspend2 gets around that by storing absolute positions in on-disk
> image, with resume parameter pointing directly to suspend header.

And a block size. (It affects the interpretation of the block number).

Apart from that, yes.

Regards,

Nigel
-- 
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened. 

[patch] suspend: update documentation

[Pavel Machek]

This updates documentation for suspend-to-disk and RAM. In particular
modular disk drivers trap is documented.

Signed-off-by: Pavel Machek <pavel@suse.cz>

--- a/Documentation/power/swsusp.txt
+++ b/Documentation/power/swsusp.txt
@@ -27,13 +27,11 @@ echo shutdown > /sys/power/disk; echo di
 
 echo platform > /sys/power/disk; echo disk > /sys/power/state
 
-
-Encrypted suspend image:
-------------------------
-If you want to store your suspend image encrypted with a temporary
-key to prevent data gathering after resume you must compile
-crypto and the aes algorithm into the kernel - modules won't work
-as they cannot be loaded at resume time.
+. If you have SATA disks, you'll need recent kernels with SATA suspend
+support. For suspend and resume to work, make sure your disk drivers
+are built into kernel -- not modules. [There's way to make
+suspend/resume with modular disk drivers, see FAQ, but you should
+better not do that.]
 
 
 Article about goals and implementation of Software Suspend for Linux
@@ -328,4 +326,10 @@ init=/bin/bash, then swapon and starting
 usually does the trick. Then it is good idea to try with latest
 vanilla kernel.
 
+Q: How can distributions ship a swsusp-supporting kernel with modular
+disk drivers (especially SATA)?
 
+A: Well, it can be done, load the drivers, then do echo into
+/sys/power/disk/resume file from initrd. Be sure not to mount
+anything, not even read-only mount, or you are going to lose your
+data.
diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt
--- a/Documentation/power/video.txt
+++ b/Documentation/power/video.txt
@@ -104,6 +104,7 @@ HP NX7000			??? (*)
 HP Pavilion ZD7000		vbetool post needed, need open-source nv driver for X
 HP Omnibook XE3	athlon version	none (1)
 HP Omnibook XE3GC		none (1), video is S3 Savage/IX-MV
+HP Omnibook 5150		none (1), (S1 also works OK)
 IBM TP T20, model 2647-44G	none (1), video is S3 Inc. 86C270-294 Savage/IX-MV, vesafb gets "interesting" but X work.
 IBM TP A31 / Type 2652-M5G      s3_mode (3) [works ok with BIOS 1.04 2002-08-23, but not at all with BIOS 1.11 2004-11-05 :-(]
 IBM TP R32 / Type 2658-MMG      none (1)
@@ -122,16 +123,21 @@ IBM TP X30			s3_bios (2)
 IBM TP X31 / Type 2672-XXH      none (1), use radeontool (http://fdd.com/software/radeon/) to turn off backlight.
 IBM TP X32			none (1), but backlight is on and video is trashed after long suspend
 IBM Thinkpad X40 Type 2371-7JG  s3_bios,s3_mode (4)
+IBM TP 600e			none(1), but a switch to console and back to X is needed
 Medion MD4220			??? (*)
 Samsung P35			vbetool needed (6)
-Sharp PC-AR10 (ATI rage)	none (1)
+Sharp PC-AR10 (ATI rage)	none (1), backlight does not switch off
 Sony Vaio PCG-C1VRX/K		s3_bios (2)
 Sony Vaio PCG-F403		??? (*)
 Sony Vaio PCG-N505SN		??? (*)
+Sony Vaio PCG-GRT995MP		none (1), works with 'nv' X driver
 Sony Vaio vgn-s260		X or boot-radeon can init it (5)
+Sony Vaio vgn-S580BH		vga=normal, but suspend from X. Console will be blank unless you return to X. 
+Sony Vaio vgn-FS115B		s3_bios (2),s3_mode (4)
 Toshiba Libretto L5		none (1)
-Toshiba Satellite 4030CDT	s3_mode (3)
-Toshiba Satellite 4080XCDT      s3_mode (3)
+Toshiba Portege 3020CT		s3_mode (3)
+Toshiba Satellite 4030CDT	s3_mode (3) (S1 also works OK)
+Toshiba Satellite 4080XCDT      s3_mode (3) (S1 also works OK)
 Toshiba Satellite 4090XCDT      ??? (*)
 Toshiba Satellite P10-554       s3_bios,s3_mode (4)(****)
 Toshiba M30                     (2) xor X with nvidia driver using internal AGP
diff --git a/kernel/power/process.c b/kernel/power/process.c
--- a/kernel/power/process.c
+++ b/kernel/power/process.c
@@ -83,7 +83,7 @@ int freeze_processes(void)
 		yield();			/* Yield is okay here */
 		if (todo && time_after(jiffies, start_time + TIMEOUT)) {
 			printk( "\n" );
-			printk(KERN_ERR " stopping tasks failed (%d tasks remaining)\n", todo );
+			printk(KERN_ERR " stopping tasks timed out (%d tasks remaining)\n", todo );
 			break;
 		}
 	} while(todo);
diff --git a/kernel/power/swsusp.c b/kernel/power/swsusp.c
--- a/kernel/power/swsusp.c
+++ b/kernel/power/swsusp.c
@@ -967,7 +967,7 @@ int swsusp_check(void)
 	if (!error)
 		pr_debug("swsusp: resume file found\n");
 	else
-		pr_debug("swsusp: Error %d check for resume file\n", error);
+		pr_debug("swsusp: Error %d checking for resume file\n", error);
 	return error;
 }
 

-- 
Boycott Kodak -- for their patent abuse against Java.

Re: [patch] suspend: update documentation

[Randy.Dunlap]

On Fri, 6 Jan 2006, Pavel Machek wrote:

> This updates documentation for suspend-to-disk and RAM. In particular
> modular disk drivers trap is documented.
>
> Signed-off-by: Pavel Machek <pavel@suse.cz>
>
> --- a/Documentation/power/swsusp.txt
> +++ b/Documentation/power/swsusp.txt
> @@ -27,13 +27,11 @@ echo shutdown > /sys/power/disk; echo di
> +. If you have SATA disks, you'll need recent kernels with SATA suspend
> +support. For suspend and resume to work, make sure your disk drivers
> +are built into kernel -- not modules. [There's way to make
> +suspend/resume with modular disk drivers, see FAQ, but you should
> +better not do that.]

(drop "better", or say "but you probably shouldn't do that.")

What recent kernels have SATA suspend/resume support?
Not from kernel.org AFAIK.

-- 
~Randy

Re: [patch] suspend: update documentation

[Pavel Machek]

On Pá 06-01-06 08:46:19, Randy.Dunlap wrote:
> On Fri, 6 Jan 2006, Pavel Machek wrote:
> 
> > This updates documentation for suspend-to-disk and RAM. In particular
> > modular disk drivers trap is documented.
> >
> > Signed-off-by: Pavel Machek <pavel@suse.cz>
> >
> > --- a/Documentation/power/swsusp.txt
> > +++ b/Documentation/power/swsusp.txt
> > @@ -27,13 +27,11 @@ echo shutdown > /sys/power/disk; echo di
> > +. If you have SATA disks, you'll need recent kernels with SATA suspend
> > +support. For suspend and resume to work, make sure your disk drivers
> > +are built into kernel -- not modules. [There's way to make
> > +suspend/resume with modular disk drivers, see FAQ, but you should
> > +better not do that.]
> 
> (drop "better", or say "but you probably shouldn't do that.")

Second variant applied.

> What recent kernels have SATA suspend/resume support?
> Not from kernel.org AFAIK.

Andrew merged it to -mm tree after getting notebook with SATA. I'm not
sure if it is in kernel.org just now or not, it probably did not make
it into 2.6.15.
								Pavel
-- 
Thanks, Sharp!

Re: [patch] suspend: update documentation

[Randy.Dunlap]

On Fri, 6 Jan 2006, Randy.Dunlap wrote:

> On Fri, 6 Jan 2006, Pavel Machek wrote:
>
> > This updates documentation for suspend-to-disk and RAM. In particular
> > modular disk drivers trap is documented.
> >
> > Signed-off-by: Pavel Machek <pavel@suse.cz>
> >
> > --- a/Documentation/power/swsusp.txt
> > +++ b/Documentation/power/swsusp.txt
> > @@ -27,13 +27,11 @@ echo shutdown > /sys/power/disk; echo di
> > +. If you have SATA disks, you'll need recent kernels with SATA suspend
> > +support. For suspend and resume to work, make sure your disk drivers
> > +are built into kernel -- not modules. [There's way to make
> > +suspend/resume with modular disk drivers, see FAQ, but you should
> > +better not do that.]
>
> (drop "better", or say "but you probably shouldn't do that.")
>
> What recent kernels have SATA suspend/resume support?
> Not from kernel.org AFAIK.

Ah, now I see that it's merged.  Great.

Thanks,
-- 
~Randy

[patch] suspend: update documentation

[Pavel Machek]

This updates documentation for swsusp / suspend-to-RAM. Parts by Rafael.

Signed-off-by: Pavel Machek <pavel@suse.cz>

diff --git a/Documentation/power/swsusp.txt b/Documentation/power/swsusp.txt
index b28b7f0..96bbe61 100644
--- a/Documentation/power/swsusp.txt
+++ b/Documentation/power/swsusp.txt
@@ -27,19 +27,18 @@ echo shutdown > /sys/power/disk; echo di
 
 echo platform > /sys/power/disk; echo disk > /sys/power/state
 
+. If you have SATA disks, you'll need recent kernels with SATA suspend
+support. For suspend and resume to work, make sure your disk drivers
+are built into kernel -- not modules. [There's way to make
+suspend/resume with modular disk drivers, see FAQ, but you probably
+should not do that.]
+
 If you want to limit the suspend image size to N bytes, do
 
 echo N > /sys/power/image_size
 
 before suspend (it is limited to 500 MB by default).
 
-Encrypted suspend image:
-------------------------
-If you want to store your suspend image encrypted with a temporary
-key to prevent data gathering after resume you must compile
-crypto and the aes algorithm into the kernel - modules won't work
-as they cannot be loaded at resume time.
-
 
 Article about goals and implementation of Software Suspend for Linux
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -333,4 +332,19 @@ init=/bin/bash, then swapon and starting
 usually does the trick. Then it is good idea to try with latest
 vanilla kernel.
 
+Q: How can distributions ship a swsusp-supporting kernel with modular
+disk drivers (especially SATA)?
+
+A: Well, it can be done, load the drivers, then do echo into
+/sys/power/disk/resume file from initrd. Be sure not to mount
+anything, not even read-only mount, or you are going to lose your
+data.
+
+Q: How do I make suspend more verbose?
+
+A: If you want to see any non-error kernel messages on the virtual
+terminal the kernel switches to during suspend, you have to set the
+kernel console loglevel to at least 4 (KERN_WARNING), for example by
+doing
 
+	echo 4 > /proc/sys/kernel/printk
diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt
index 912bed8..0cd8822 100644
--- a/Documentation/power/video.txt
+++ b/Documentation/power/video.txt
@@ -104,6 +104,7 @@ HP NX7000			??? (*)
 HP Pavilion ZD7000		vbetool post needed, need open-source nv driver for X
 HP Omnibook XE3	athlon version	none (1)
 HP Omnibook XE3GC		none (1), video is S3 Savage/IX-MV
+HP Omnibook 5150		none (1), (S1 also works OK)
 IBM TP T20, model 2647-44G	none (1), video is S3 Inc. 86C270-294 Savage/IX-MV, vesafb gets "interesting" but X work.
 IBM TP A31 / Type 2652-M5G      s3_mode (3) [works ok with BIOS 1.04 2002-08-23, but not at all with BIOS 1.11 2004-11-05 :-(]
 IBM TP R32 / Type 2658-MMG      none (1)
@@ -120,18 +121,24 @@ IBM ThinkPad T42p (2373-GTG)	s3_bios (2)
 IBM TP X20			??? (*)
 IBM TP X30			s3_bios (2)
 IBM TP X31 / Type 2672-XXH      none (1), use radeontool (http://fdd.com/software/radeon/) to turn off backlight.
-IBM TP X32			none (1), but backlight is on and video is trashed after long suspend
+IBM TP X32			none (1), but backlight is on and video is trashed after long suspend. s3_bios,s3_mode (4) works too. Perhaps that gets better results?
 IBM Thinkpad X40 Type 2371-7JG  s3_bios,s3_mode (4)
+IBM TP 600e			none(1), but a switch to console and back to X is needed
 Medion MD4220			??? (*)
 Samsung P35			vbetool needed (6)
-Sharp PC-AR10 (ATI rage)	none (1)
+Sharp PC-AR10 (ATI rage)	none (1), backlight does not switch off
 Sony Vaio PCG-C1VRX/K		s3_bios (2)
 Sony Vaio PCG-F403		??? (*)
+Sony Vaio PCG-GRT995MP		none (1), works with 'nv' X driver
+Sony Vaio PCG-GR7/K		none (1), but needs radeonfb, use radeontool (http://fdd.com/software/radeon/) to turn off backlight.
 Sony Vaio PCG-N505SN		??? (*)
 Sony Vaio vgn-s260		X or boot-radeon can init it (5)
+Sony Vaio vgn-S580BH		vga=normal, but suspend from X. Console will be blank unless you return to X. 
+Sony Vaio vgn-FS115B		s3_bios (2),s3_mode (4)
 Toshiba Libretto L5		none (1)
-Toshiba Satellite 4030CDT	s3_mode (3)
-Toshiba Satellite 4080XCDT      s3_mode (3)
+Toshiba Portege 3020CT		s3_mode (3)
+Toshiba Satellite 4030CDT	s3_mode (3) (S1 also works OK)
+Toshiba Satellite 4080XCDT      s3_mode (3) (S1 also works OK)
 Toshiba Satellite 4090XCDT      ??? (*)
 Toshiba Satellite P10-554       s3_bios,s3_mode (4)(****)
 Toshiba M30                     (2) xor X with nvidia driver using internal AGP
@@ -156,6 +163,9 @@ VBEtool details
 ~~~~~~~~~~~~~~~
 (with thanks to Carl-Daniel Hailfinger)
 
+This is not a generic solution. For some machines, you'll have better
+luck with setting parameters on kernel command line.
+
 First, boot into X and run the following script ONCE:
 #!/bin/bash
 statedir=/root/s3/state

-- 
Thanks, Sharp!