On Thu, May 04, 2006 at 01:05:37AM +0200, Michael Biebl wrote: > jacob wrote: > > On Wed, May 03, 2006 at 01:03:25PM -0700, Debian Bug Tracking System wrote: > >> From: Michael Biebl <[EMAIL PROTECTED]> > >> jacob wrote: > >>> On Tue, May 02, 2006 at 03:37:05PM +0200, Michael Biebl wrote: > >>>> jacob wrote: > >>>>> Package: powersaved > >>>>> Version: 0.12.11-1 > >>>>> Severity: normal > >>>>> > >>>>> > >>>>> powersaved complains that there is no resume= boot option, when I try to > >>>>> suspend to disk. However: > >>>>> > >>>> > >>> $ cat /sys/power/resume > >>> 0:0 > >> Ok, here is the source of the problem. Your resume partition is not > >> correctly set (0:0 basically means, no resume partition). So powersaved > >> is actually working correctly (that's why I'm closing this bug). > >> The question now is, why the resume partition is not correctly set. > >> > >> > > I'm not a initrd expert, but a quick google search revealed [1]. Maybe > your problem is similar. Could be that one of the initrd scripts does > not set /sys/power/resume correctly. You could try to comment out > SUSPEND in /etc/mkinitramfs/conf.d/resume and update the initrd > (update-initramfs), maybe then /sys/power/resume is not modified by the > scripts in the initrd. >
Light finally dawns. It was something even more insidious. I was suspending before I got resume working, with a ramdisk created by yaird. Yaird doesn't properly support resume yet. When I discovered this, I installed initramfs-tools, updated my ramdisk, and suspended. It resumed properly on reboot. I hadn't rebooted since. So it never set /sys/power/resume. After a reboot, /sys/power/resume says 3:2, as it should. Thanks for your help, Michael. Hopefully, no one else follows this odd sequence, but if they do, then this bug report should help them. Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
