All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jim Carter <jimc@math.ucla.edu>
Cc: linux-kernel@vger.kernel.org, hare@suse.de, seife@suse.de
Subject: Re: Disc driver is module, software suspend fails
Date: Tue, 29 Mar 2005 00:19:22 +0200	[thread overview]
Message-ID: <20050328221922.GD1389@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0503271623150.5513@xena.cft.ca.us>

Hi!

> > There's another feature that enables you to start resume manually with
> > some echo to /sys... Perhaps it needs to be documented better, I'm
> > looking for a patch ;-).
> 
> But how can it resume from a swap device for which it has no driver?

You insmod driver for your swap device, then you echo device numbers
to /sys... then initiate resume.

> Even if you copied the needed module(s) onto the swap device, the kernel
> needs the modules to be loaded before it can read anything.  The driver 
> would be there if resuming happened after the initrd loaded it.  But
> I wasn't able to make that actually work.

It should be possible, suse 9.3 does that...
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2005-03-28 22:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25  6:54 Disc driver is module, software suspend fails Jim Carter
2005-03-25  8:14 ` Pavel Machek
2005-03-25 10:54   ` Stefan Seyfried
2005-03-28  0:27   ` Jim Carter
2005-03-28 22:19     ` Pavel Machek [this message]
2005-03-30  1:38       ` Jim Carter
2005-03-30  9:06         ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2005-04-10 23:14 Jim Carter
2005-04-13 10:07 ` Pavel Machek
2005-04-14 17:53   ` Jim Carter
2005-04-14 20:42     ` Pavel Machek
2005-05-04  1:11       ` Jim Carter
2005-05-04  9:14         ` Pavel Machek
2005-03-23  6:19 Jim Carter
2005-03-23 10:17 ` Pavel Machek
2005-03-23 22:34   ` Jim Carter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050328221922.GD1389@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=hare@suse.de \
    --cc=jimc@math.ucla.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seife@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.