On 28/12/14 16:13, Bruce Dubbs wrote:
On Sun, Dec 28, 2014 at 1:35 AM, Christopher Gregory <[email protected] <mailto:[email protected]>> wrote:The issue is that systemd, and I strongly suspect the same is the case for pm-utils as well, although I can not find an exact answer for that tool, uses the kernel's native swsusp for handling suspend/hibernate/resume. This native kernel code, in order to be able to resume from a laptop/desktop being suspended to disk, which means that after you issue the pm-hibernate command in the case of pm-utils, this actually copies the entire contents of ram to your swap partition and then totally powers off your computer. The next time you restart your computer it is *meant* to resume from where you left off after going through the boot-up rotine. This does not happen unless you use an initramfs. It just plain ignores the saved suspended image and does a new boot instead. It does not do this for me. I have: menuentry 'LFS (SVN-20140604 on /dev/sda10 hibernate)' { linux /vmlinuz-3.14.3-lfs20140604 root=/dev/sda10 ro resume=/dev/sda11 } and hibernate works for me. At least it did when I last tried it from xfce. As you know, I'm not using systemd, but I am using a standard pci based disk drive, so I suspect something about that is causing the problem.
Non-systemd, but works for me as well, albeit with vbetools and a sleep hook for XScreensaver, and Nouveau crashing from time to time. :(
With or without an initramfs - I use the latter to pre-load monitor EDID data, if I'm using a cable splitter.
David -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
