Hello all.

I am happy to announce that I have been able to suspend to disk and
resume successfully from inside the graphics environment.  I am using
the "SuSEfied" kernel of the day, 2.6.16, dated April 8, 2006 (64-bit). 
I did not patch it with the suspend patches (perhaps the "SuSEfied"
kernel already has them?).  A few days ago, I described in another
posting how the 'swsusp' command fails when invoked from inside a
graphics environment with the nVidia driver loaded.

This time I issued 'echo disk > /sys/power/state' (as root, but from
within the graphics environment) and the system suspended.  It resumed
fine.  As I said, I am using the 64-bit kernel 2.6.16 (as described
above) and nVidia's 1.0-8756 64-bit driver .  The system seems to run
fine after resuming.  One thing *I think* I observed is that the
usability of the vertical scroll bar of the mousepad does not return
after resume unless I try to scroll a web page.  To be honest, I don't
think that suspend to disk on this machine saves much time over a normal
shutdown and reboot, unless many applications are open.  I am not sure
why 'swsusp' fails with the nVidia driver as I described a couple of
days ago.

Encouraged by this success, I decided to try suspend to RAM.  Again as
root and from within the graphics environment I issued 'echo mem >
/sys/power/state' and the machine suspended to RAM (the machine shut
down and the two power lights blinked).  Only the mouspad and the power
switch could awaken the machine (not the keys in the main keyboard). 
The machine resumed fine and for a few seconds everything was back, but
the hard disk began to run like crazy (the hard disk activity light was
on constantly), the system could respond to the 'ps' command but *not*
the 'top' command and eventually the machine locked up; the caps-lock
LED began to blink.  I repeated my attempt to suspend to RAM several
times with identical results.

After this near success, I decided to hack with the DSDT.  I believe I
went through the necessary steps by the book. I went to the
http://acpi.sourceforge.net web site, where I downloaded the closest
DSDT I could find.  That was for an R3455.  (Here is the direct link:
http://acpi.sourceforge.net/dsdt/view.php?manufacturer=Compaq&name=Presario+R3455EA
.)   I unzipped the file, compiled it with iasl ('iasl -sa
Compaq-Presario_R3455EA-F.34-original.asl') and copied the output file,
'DSDT.aml', to '/etc/DSDT.aml'.  Then, I modified the appropriate entry
for the DSDT table in the '/etc/sysconfig/kernel' file to point to that
path ('/etc/DSDT.aml').  Finally, I remade mkinitrd (which informed me
that it recognized the DSDT) and rebooted.  Suspend to RAM behaved
exactly the same.

At least, I tried...   One thing I observed was that the DSDT I
downloaded was geared towards an F34 BIOS, while my BIOS is F35.  Maybe
I should try the DSDT for a Pavilion.

CF

-- 
Running 64-bit Linux on AMD64


_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/

Reply via email to