--Thank you for letting us know.
My definition of successful suspend includes a successful resumption
(resume). Otherwise, if you have to reboot, why bother suspending?
I, too, have been able to suspend both to disk and to RAM, even from
inside KDE, without unloading the nVidia driver, but upon resuming, the
keyboard and display got bungled up. However, I observed that after
resuming, sometimes the processor ran "pedal to the metal" (judging from
the fans), while some other times, under 64-bit SuSE 9.3, the computer
responded to pings (although I had "lost" the keyboard and display)!
So, I think we are close to having successful suspends (according to my
definition) on this laptop, in 64 bits.
CF
Gregory Gulik wrote:
Ok, I tried to do the suspend to RAM after exiting from X by going to
init mode 3 then unloading the nvidia driver.
Once I did that the suspend worked!
But, the resume resulted in a blank screen and an apparently hung
machine. I had to do a hard reboot to recover.
Constantine 'Gus' Fantanas wrote:
Earlier, I remember nVidia claiming on its web site that its drivers
supported suspend to disk but not suspend to RAM. So much for the
fabled nVidia support for Linux (by their own admission). It's
better than others' Linux support, but NOT great!
_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
