comment? uh... well...
i personally would not (do not) use acpi for anything other than the bare essentials - battery/ac power switching, and hyperthreading on my 8887. (and behind-the-scenes stuff out of my control, such as irq switching and whatnot.) i would much rather use apm, as it's a more mature project, but i don't want to give up hyperthreading.
acpi4linux is still very much a work-in-progress. there are many aspects of it that are still unstable - sleep states, for one. i mean, the acpi4linux project releases with datestamps instead of version numbers. (not a very good argument, i know, but datestamps are much more often seen on changing code such as CVS) using unstable features poses a risk of causing problems. not physical problems, but i would not be surprised to see a hard drive completely eat all its data while switching sleep modes - it's been reported more than a couple times. i have been using this particular linux install for almost two years - even going so far as to transfer my hard drive and install from my old dell laptop into my new sager. (old one was pentium3, new one is pentium4 - p4 supports all p3 instructions and more, no need to recompile or reinstall) there is too much time and work put into this install - configs that would take forever to completely set up again, mp3's and ogg's, videos, saved texts and writings. basically, years' worth of important information built up that i really cannot afford to lose.
not only that, but i also don't take this laptop anywhere at all. i have no use for sleep at all - just turn it on when i use it, turn it off when i'm done.
supposedly, acpi is a lot better in 2.5 (and subsequently, will be in 2.6), supporting all sleep states and more. however, 2.5 itself is unstable, so it's trading one risk for another.
obviously, everyone controls their own computer. it's each person's choice whether or not to use sleep now, under 2.4. many people use software suspend without any problems at all. that's fine; more power to them. however, using unstable code always poses a little danger factor - and that's a risk i'm just not willing to take.
... was that a good enough comment?
or by comment, did you mean just tell you how to do it? well, like i mentioned before, i do not and have never used it. i can point you in the right direction, though...
you need to patch your kernel with the swsusp patch. check it out here:http://fchabaud.free.fr/English/defa...p&FILE2=Swsusp
read the docs, patch your kernel, etc. sorry, but i really can't tell you much more than that. i've never even touched that patch before...
but be ready for instability. i'll close with Con Kolivas' warning about the patch:
*BROKEN AND WILL EAT YOUR HARD DISK!*
(take it with a grain of salt, though. it b0rks when used on a ck kernel, but normally it's a little less volatile.)