[Mdlug] IBM T30/SUSE 10.0 Suspend to RAM Problems (repost word wrapped, sorry)

[Peter Bart]

On Sun, 2006-11-19 at 17:20 -0500, Jeff Hanson wrote:
> On 11/19/06, Peter Bart <peter at petertheplumber.net> wrote:
> > One of the things I'm trying to deal with is I've never gotten
> > suspend to disk to work properly. It's set in Yast to work and when I
> > suspend a popup box shows up telling me it's stopping services but then
> > the display stays on with several error messages. Over several minutes
> > the screen goes from black with the messages to almost white which
> > obscures the text. The indicator lights show that it has suspended. I
> > can also resume. I found the text displayed in /var/log/messages:
> 
> I don't see problems with those messages.  What does the lspci command
> report for devices (or "lspci -v" or "lspci -vv").  It appears to be a
> video interface or BIOS compatibility problem.  Most suspend to disk
> or suspend to RAM modes require good driver support but many
> manufactures don't provide enough hardware info.  On many systems, one
> or the other may work but often not both.  Maybe check BIOS settings
> and see if any BIOS/video caching or shadowing options are enabled.
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug

Jeff,
	What you say makes sense. lspci simply lists the devices on my machine.
I think my original question might be a dead end. I compared the suspend
to disk and ram logs and they appear identical. So the system is simply
going about shutting down, nothing remarkable about that. From the
entries into the log to the order in which they appear. The only
difference seems to be the display shuts off when I suspend to disk.
Sometimes the sound card has a hard time coming back from suspend to ram
but that's after. Even if the display is still on my laptop appears to
suspend to ram successfully. There is a difference between the two,
suspend to disk appears to wake up some of the suspended devices; sorry
it goes by very quickly; and it also wakes up the orinoco pci. Then it
writes data to swap and then the hard drive shuts down. What confuses me
is not just the screen staying on but why something to do with wifi
needs to wake up to write to swap. I think i get why data would be
written to swap for suspend to disk but not for suspend to ram, the way
the data is stored is different. I might be confused about that though.
What is interesting is that suspend to ram worked beautifully on the
same laptop, same distro but using gnome then. I use KDE now.

Regards,
-- 
Peter Bart <peter at petertheplumber.net>
http://petertheplumber.net