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

Re: s2disk works, but can not resume



On Thu, Feb 14, 2008 at 05:35:51PM +0100, LÉVAI Dániel wrote:
> On Wednesday 13 February 2008 23.53.55 Andrew Sackville-West wrote:
> > On Wed, Feb 13, 2008 at 09:43:00PM +0100, LÉVAI Dániel wrote:
> > > Hi!
> > >
> > > I'm trying to resume after a s2disk with the kernel boot
> > > parameter "resume=/dev/sda12" (this is my swap space). The s2disk
> > > command runs fine, no problem, but when booting the kernel, it
> > > simply ignores the resume boot parameter, and won't resume from the
> > > hibernation. I've tried to setup the default swap device in the
> > > linux kernel's config, but still no luck. I'm using uswsusp-0.7-1,
> > > linux kernel 2.6.24-4 with debian unstable.
> > >
> > > Any ideas? What other info I should provide?
> >
> > Have you checked uswsusp.conf to ensure it specifies the right
> > partition for resuming *and* have you rebuilt the initrd's since
> > installing uswsusp? I *think* but don't *know* that's what you need.
> >
> > A
> This is my uswsusp.conf, it contains the correct partition, but I think 
> that the kernel boot parameter specifies which partition shall be used 
> as swap:
> 
> # /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
> resume device = /dev/sda12
> compress = y
> early writeout = y
> image size = 971482316
> RSA key file = /etc/uswsusp.key
> shutdown method = platform
> compute checksum = y
> 
> As for the initrd image, I don't use that. I'm compiling in the sata 
> drivers, and everything else what otherwise would be in the initrd 
> image (as a kernel module).

You need the resume binary accessible in order to resume. I don't know
how you could do that without an initrd and I suspect that's the
problem. But I don't know enough about it to answer definitively.

A
 

Attachment: signature.asc
Description: Digital signature


Reply to: