yesterday I went about to get hibernate, or suspend-to-disk (swsusp2) to work. Basically followed the Software Suspend HOWTO (http://www.suspend2.net/HOWTO
After successfully patching the kernel (18.104.22.168), recompile with filewriter and swapwriter compiled in the kernel and editing the hibernate.conf I gave it a try by typing 'hibernate'. System hibernated but rebooted normal (i.e. without resuming). dmesg complained about not finding the resume2= in lilo.conf so I appended resume2=swap:/dev/hda6 and ran lilo. No problem so far. Reading about possible data loss I copied the init.d/hibernate-cleanup.sh script to /etc/rc.d/rc.hibernate-cleanup (running Slackware-current) and added an entry in /etc/rc.d/rc.S to fire up that script during boot after the file systems are mounted but before swap is mounted.
Then I rebooted, and EVIL struck: immediately after the boot screen (with the manufacturer's brand logo) instead of seeing lilo's menu, I get a black screen with only LI in the left most corner, and there it hangs forever... aaaarrrggghhhhhhhh
I thought cleaning out swap would do the trick (suggested in the howto), so after booting knoppix cd I tried mkswap /dev/hda6 to no avail. Mounting /dev/hda7 (root) and running the hibernate-cleanup script to manually wipe out the swap also didn't help.
Reiserfsck /dev/hda7 (root partition) indicates loads of errors. Will fixing with fsck lead to data loss?
When I inspected lilo.conf, I found that the append="resume2=swap:/dev/hda6" entry was not there anymore.
PLEASE, anyone, what should I do to prevent further harm or data loss, or to further diagnose the exact problem?
Apologies for the long mail, but I am in despair to get my laptop running again without the necessity to reinstall Slack (that's the beauty of linux; never reinstall, it's always fixable.... isn't it?)