[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [NOT SOLVED, BUT PROGRESS] Failure to boot after failed resume from s2something



On (16/07/09 20:55), Andrew Reid wrote:
| On Thursday 16 July 2009 12:36:57 John wrote:
| >
| > So my questions are:
| >
| > 1) How does one get rid of an old s2disk/hibernate setting that
| > demands to run "PM: Starting manual resume from disk"?
| > 2) Can update-initramfs be instructed to ignore that old setting?
| > 3) Ideally, can this problem be addressed from within the busybox:
| > (initramfs)
| > into which one is dumped when trying to do it the wrong way/
| 
|   Have you tried booting with "noresume"?  The theory on this 
| is that this should entirely bypass the resume process, so it
| won't matter what's in your resume partition.

Hi, Andrew,

Thanks for taking the trouble.

I have indeed tried "noresume," and it fails in the same old
way. Apparently the problem is built into initrd.img-(uname -), since
two of my kernels fail in the same way, and only the one whose
initrd.img-(uname -).bak was saved. I now fear to touch that one,
since it's all that keeps the machine bootable.

|   I dimly recall setting the resume partition in the initramfs.conf
| process somewhere, but can't seem to find documentation about that
| now.

I've looked at that documentation, without finding anything
helpful. /etc/initramfs-tools.conf.d/resume is set to the proper resume
partition. I can s2ram successfully from the one working kernel, but
of course can't experiment with the others because they won't boot.

Thanks for your efforts.

-- 
JohnRChamplin@columbus.rr.com
====================================================
GPG key 1024D/99421A63 2005-01-05
EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63
gpg --keyserver subkeys.pgp.net --recv-keys 99421A63

Attachment: signature.asc
Description: Digital signature


Reply to: