Am Mittwoch, den 23.11.2005, 15:50 +0100 schrieb Maximilian Attems: > please open a _new_ bug report, so the issue don't get lost. > > > Am Dienstag, den 22.11.2005, 12:55 +0100 schrieb Jonas Smedegaard: > > Well, I *think* it won't work as swsusp even refuses to suspend (so I > > could never try to resume): > > > > swsusp: cannot find swap device, try swapon -a > > please post to that bug report the output of: > * cat /proc/mounts > * cat /proc/swaps > * cat /etc/fstab > > aboves is a quite clear message that you are not using any > swap partition. swsusp parks your data there, so no luck without. ;)
If it had just been so easy :). I have been fiddling around with swsusp and suspend2 probably for years now (every now and then) and think I understood at least that I need some space to hibernate to :). And the "quite clear" message you are referring to might be exactly /not/ clear at all but rather misleading instead. Because I have checked of course that my swap is active and I think it might be that suspend wants to tell me that it /would not/ find the swap partition if I suspended now and rebooted because IDE stuff is compiled as modules and swsusp would not be able to resume without them. I don't know however, how early swsusp's resume is triggered during boot and I am rather surprised if an initrd could not insmod them before. But maybe that is just the "modular IDE" patch I read about in the LKML thread and that you mentioned in an earlier mail. I have opened bug #340593 and supplied the information you requested. I am CCing to [EMAIL PROTECTED] and hope this is the Right Thing. Thanks for any help, Thomas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
