On Tue, 6 Mar 2007 13:48:54 +0100
Michael Meskes <[EMAIL PROTECTED]> wrote:

> I tracked the problem down some. It works nicely IF I make sure my
> initrd is updated. Given that I do not run the newest kernel image on my
> system (because that 2.6.20 version I tested sometimes froze the system
> after resume) the initrd was not automatically updated. It seems my
> system worked fine with uswsusp 0.5 only because that was the version
> with which the initrd was created.

Thank you very much for tracking this down!
 
> I think if you'd add the option "-k all" to your call this should be
> done automatically. 

Hmm, yes I thought about doing that, it seemed the most sensible thing
to do. The initramfs maitainers, however, think it is a 'polite
conservative setting' to only update the newest one automatically...

But not breaking suspend is even more polite, ... I'll think about it some more.

grts Tim

Attachment: signature.asc
Description: PGP signature

Reply via email to