mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] [PATCH 2.6]: suspend to disk only available if non-modular IDE
Date: Tue, 30 Mar 2004 16:52:31 +1000	[thread overview]
Message-ID: <1080629551.12019.12.camel@laptop-linux.wpcb.org.au> (raw)
In-Reply-To: <pan.2004.03.29.21.34.45.973137@dungeon.inka.de>

Hi.

On Tue, 2004-03-30 at 07:34, Andreas Jellinghaus wrote:
> so suspend to disk does not work with scsi?
> 
> >> > -       depends on PM && SWAP
> >> > +       depends on PM && SWAP && IDE=y && BLK_DEV_IDEDISK=y
> 
> implies IDE is needed.

It is at the moment, I'm afraid. I'm hoping to get SCSI support for
suspend2 finished shortly. I did suspend a OSDL machine to SCSI in
January, but the driver lacked the power management that I needed to
reload the second half of the image and thereby be sure all was okay.

> btw: would it be somehow possible to resume after initrd phase?
> or some other idea how a generic kernel with modules in the initrd
> could use suspend to disk? or a laptop where the initrd is needed
> to setup a dm-crypt volume with the right decrypton key?

That should be doable, provided that the initrd doesn't mount anything.
Decryption is 'interesting'. The key needs to be set up in the resumed
kernel too. (Shouldn't be a problem, if you manage to suspend to it!).

Regards,

Nigel
-- 
Nigel Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6253 0250 (home)

Evolution (n): A hypothetical process whereby infinitely improbable events occur 
with alarming frequency, order arises from chaos, and no one is given credit.


  reply	other threads:[~2004-03-30  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28 19:36 Arkadiusz Miskiewicz
2004-03-28 23:37 ` [Swsusp-devel] " Nigel Cunningham
2004-03-28 23:47   ` Nigel Cunningham
2004-03-29 21:34     ` Andreas Jellinghaus
2004-03-30  6:52       ` Nigel Cunningham [this message]
2004-03-30  7:31         ` Andreas Jellinghaus
2004-03-30 22:23           ` Nigel Cunningham
2004-03-30 20:11   ` Pavel Machek
2004-03-31 22:36     ` Nigel Cunningham
2004-04-01  7:26       ` Pavel Machek

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=1080629551.12019.12.camel@laptop-linux.wpcb.org.au \
    --to=ncunningham@users.sourceforge.net \
    --cc=aj@dungeon.inka.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®