Arnout Boelens wrote: > On Tuesday 31 October 2006 14:28, Michael Biebl wrote: >> Arnout Boelens wrote: >> >>> Or wrote down the wrong filename ;-). Actually, when I do a suspend to disk >>> /var/log/suspend2disk.log is not even created. Also, neither suspend to ram >>> nor >>> disk is working with kpowersave. Maybe there is the same thing wrong for >>> both? >> With such an answer, there is only wild guessing. Try to collect as much >> information as possible. Look at the log files >> (/var/log/(syslog|daemon|messages). Tell me what modifications you made >> to your kernel, which settings and packages you installed. Do you have >> special hardware. Does powersave -u/powersave -U output an error message? > > My kernel 2.6.18 is compiled from the debian source package. The only patch I > applied was the suspend2 2.2.8 patch. I made my initrd image with yaird. I > couldn't find any hints in the log files of why things don't work. One thing > that surprised me is that suspending using the "hibernate" command works fine > without powersaved installed, but with powersaved installed it doesn't work > anymore. Which changes does the powersaved package make to the hibernate (or > acpi) scrips? >
None. Must be caused by something else. It would also explain, why suspend_to_disk does not work for you. Normally, powersaved uses it's own set of scripts (in /usr/lib/powersave), but if a suspend2 enabled kernel is detected, it does not use it's own scripts but simply calls hibernate. Do you have problems with the in-kernel software suspend or uswsusp? Otherwise I'd suggest you install a stock debian kernel and see if powersaved works for you. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
