public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandall <eric@sandall.us>
To: Pavel Machek <pavel@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Suspend to ram with 2.6 kernels
Date: Fri, 08 Sep 2006 15:24:37 -0700	[thread overview]
Message-ID: <4501EDA5.5020406@sandall.us> (raw)
In-Reply-To: <20060907193333.GI8793@ucw.cz>

Pavel Machek wrote:
> On Wed 06-09-06 19:35:50, Eric Sandall wrote:
>> Hello LKML,
>>
>> I am having a problem with suspend-to-ram (have been for a while, but
>> suspend-to-disk has been working fine for me, so I never really bothered
>> to report it until now).
>>
>> Suspend-to-disk and resuming from it works fine (using `echo -n disk >
>> /sys/power/state`).
>>
>> Suspend-to-ram works fine (using `echo -n mem > /sys/power/state`), but
>> resuming does not. When I lift up the lid of my laptop (Dell Inspiron
>> 5100) it seems to power back up (the power light changes from blinking
>> to solid), but my screen stays blank and keys such as capslock do not
>> toggle their LED.
> 
> See suspend.sf.net, use provided s2ram program.

Thanks! The key (mentioned in the documentation there) is to disable
framebuffer (ATI video card). First time I've had suspend-to-RAM working
on this machine. ;)

Suspending works with `s2ram -f`, no other options needed, from X.

# s2ram -i
This machine can be identified by:
    sys_vendor   = "Dell Computer Corporation"
    sys_product  = "Inspiron 5100                   "
    sys_version  = ""
    bios_version = "A23"

Though you may want to rename the /usr/sbin/suspend command to something
other than 'suspend' as, at least for me, it is a shell command which
puts the current shell in the background.

The HOWTO *does* mention:
[Warning: some shells have "suspend" built in command, so specifing
exact path like ./suspend is more important than usual.]

Though I still believe it'd be a good idea to pick a non-conflicting name.

-sandalle

-- 
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric@sandall.us                  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/



  reply	other threads:[~2006-09-08 22:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07  2:35 Suspend to ram with 2.6 kernels Eric Sandall
2006-09-07 19:33 ` Pavel Machek
2006-09-08 22:24   ` Eric Sandall [this message]
2006-09-09 19:16     ` Pavel Machek
2006-09-11 10:13   ` Andreas Steinmetz
2006-09-11 20:27     ` Rafael J. Wysocki
2006-09-11 22:28       ` Andreas Steinmetz
2006-09-11 23:59         ` Matthew Garrett
2006-09-12 11:05           ` Andreas Steinmetz
2006-09-12 12:46             ` Matthew Garrett

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=4501EDA5.5020406@sandall.us \
    --to=eric@sandall.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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