public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Cc: imorgan@webcon.ca
Subject: Re: Q: swsusp with S5 instead of S4?
Date: Mon, 2 May 2005 23:49:32 +0200	[thread overview]
Message-ID: <20050502214932.GA4650@elf.ucw.cz> (raw)

[now cc-ed l-k, sorry for duplicate]

Hi!

> works just fine, in terms of general computing anyways, after resume.
> 
> However, some of the ancilary functions, such as LCD brightness, RF kill
> switch, and volume mute button do not work after resuming.
> 
> Figuring that some hardware parameters were not being restored, I verified
> that by forcing a cold boot (boot up to GRUB, issue the 'halt' command to
> power off, then power on again and let the kernel resume from swsusp),
> everything works perfectly again just as it should because the BIOS takes
> care of the initialisation then, which it normally skips after a 
> soft-off/S4.
> 
> Asside from trying to figure out exactly what hardware parameteres are not
> being saved/restored, I'm happy to let the BIOS initialise those things.
> But, I need a way to perform a normal power-off/S5 after swsusp instead of a
> soft-off/S4 so that I don't have to go though the double-grub-boot process
> every time. Can this be done?

echo shutdown > /sys/power/disk should do that. If it does
not... well, see what is different in those two codepaths...

							Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.


             reply	other threads:[~2005-05-02 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 21:49 Pavel Machek [this message]
2005-05-30 19:53 ` Q: swsusp with S5 instead of S4? Ian E. Morgan
2005-05-30 21:35   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2005-05-02 21:13 Ian E. Morgan
2005-05-30 23:48 ` Jim Crilly
2005-05-31 14:35   ` Ian E. Morgan
2005-05-31 17:14     ` Jim Crilly

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=20050502214932.GA4650@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=imorgan@webcon.ca \
    --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