On Mon, December 29, 2014 5:13 am, Bruce Dubbs wrote: > On Sun, Dec 28, 2014 at 1:35 AM, Christopher Gregory < > [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. > > -- Bruce
Hello Bruce, Thank you for this feedback. I was going to ask you when you got back home if you could test this. As I was not able to find anything that stated that pm-utils behaved like this, it left me wondering. I am also wondering if it is some kind of conflict between Upower-0.99.2 and pm-utils. The only way that it did work correctly for me was to patch the kernel. I am going to be building a straight systemV system as I want to see for myself how that reacts to hibernate and also see if I can use that to try and pinpoint exactly what the issue may be. Also I want to see if a few other oddities that I have found are specific to my laptop or if they are caused by updated libraries or some other weirdnes with systemd. It seems that I get the most unusual of errors that others do not seem to get. Now that I have built things numerous times and have scripts for just about everything I know that the systems are being built the same way. I wish that I had thought to test pm-utils without having upower installed first, or for that matter to test the native systemd hibernate. It has been on my list of things to check for a while now. Regards, Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
