linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Misha Nasledov <misha@nasledov.com>
Cc: Nigel Cunningham <ncunningham@clear.net.nz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: APM Suspend Problem
Date: Fri, 28 Nov 2003 18:20:05 -0800	[thread overview]
Message-ID: <20031129022005.GE8039@holomorphy.com> (raw)
In-Reply-To: <20031129021712.GA13798@nasledov.com>

On Fri, Nov 28, 2003 at 02:49:28PM -0800, William Lee Irwin III wrote:
>> apmd is running, though I don't know if it's the one doing it.
>> It also seems to be dependent on CONFIG_APM.

On Fri, Nov 28, 2003 at 06:17:12PM -0800, Misha Nasledov wrote:
> Yeah, like I said, if I boot back into 2.4.21 it'll work just fine. I know it
> worked in -test2 and -test3 but somewhere between then and -test9 it stopped
> working. It might've been after -test3.. I haven't really looked into using
> ACPI as APM is supposed to work perfectly on my laptop and I don't want to
> complicate things.. I wish I knew more about kernel hacking so that I could
> look into this problem.

I haven't used the CONFIG_SOFTWARE_SUSPEND needed for ACPI much; AIUI
it's still prototypical in various ways (or whatever the right way to
phrase that is), and I'm a bit too overextended to help out with it now.

There is an oddity I forgot to report: it doesn't suspend when I close
the lid if I still have the power plugged in. Also, I tried the suspend
button, and it works perfectly fine here for both suspend and resume on
a standard LTC issue Stinkpad T21, again with the power cord proviso.


-- wli

  reply	other threads:[~2003-11-29  2:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27  6:20 APM Suspend Problem Misha Nasledov
2003-11-27 11:46 ` Felipe Alfaro Solana
2003-11-27 20:22   ` Misha Nasledov
2003-11-27 22:58 ` Benjamin Herrenschmidt
2003-11-27 23:33   ` Misha Nasledov
2003-11-28 21:28 ` William Lee Irwin III
2003-11-28 21:50   ` Misha Nasledov
2003-11-28 21:50     ` William Lee Irwin III
2003-11-28 22:27       ` Nigel Cunningham
2003-11-28 22:49         ` William Lee Irwin III
2003-11-29  2:17           ` Misha Nasledov
2003-11-29  2:20             ` William Lee Irwin III [this message]
2003-11-29  2:35               ` Nigel Cunningham
2003-11-29  5:38               ` Shawn Willden
2003-11-29  5:46                 ` William Lee Irwin III
2003-11-29  9:57                   ` Misha Nasledov
2003-11-29  7:36                 ` Misha Nasledov
2003-12-01 20:24             ` Pavel Machek
2003-12-02 21:44 ` john stultz
     [not found] <WnPi.57n.5@gated-at.bofh.it>
     [not found] ` <WsPg.Xi.35@gated-at.bofh.it>
     [not found]   ` <WAWd.BP.7@gated-at.bofh.it>
2003-11-28 21:12     ` Michael Schierl
2003-11-29  1:02 pZa1x
2003-11-29  1:14 ` pZa1x
2003-11-29  8:22   ` Russell King
2003-11-29 11:26     ` pZa1x
2003-12-01 21:07       ` Russell King
2003-12-06 21:46         ` pZa1x
2003-12-07 17:06           ` Russell King
     [not found] <15Eea-Id-23@gated-at.bofh.it>
     [not found] ` <15Eea-Id-25@gated-at.bofh.it>
     [not found]   ` <15Eea-Id-27@gated-at.bofh.it>
     [not found]     ` <15Eea-Id-21@gated-at.bofh.it>
2003-12-25 19:17       ` Michael Schierl

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=20031129022005.GE8039@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=misha@nasledov.com \
    --cc=ncunningham@clear.net.nz \
    /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;
as well as URLs for NNTP newsgroup(s).