From: "J . A . Magallon" <jamagallon@able.es>
To: "James H . Cloos Jr ." <cloos@jhcloos.com>
Cc: "Michael D . Crawford" <crawford@goingware.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to Power off with ACPI/APM?
Date: Fri, 5 Jan 2001 02:16:23 +0100 [thread overview]
Message-ID: <20010105021623.C743@werewolf.able.es> (raw)
In-Reply-To: <3A54DC87.5B861B7@goingware.com> <m37l4akdn5.fsf@austin.jhcloos.com>
In-Reply-To: <m37l4akdn5.fsf@austin.jhcloos.com>; from cloos@jhcloos.com on Fri, Jan 05, 2001 at 02:10:06 +0100
On 2001.01.05 James H. Cloos Jr. wrote:
> Michael> APM gives its message first in the boot process, then later
> Michael> ACPI does. But ACPI says something like "APM already
> Michael> present, exiting", so the doc is wrong both ways you read it,
> Michael> or else ACPI doesn't succeed in the intended behavior to
> Michael> override APM.
>
> I get th eopposite behavior. If both are compiled in only ACPI works.
> (Only tested w/ 2.4.0-test kernels, though.)
>
> Either way you need the userspace daemon running to actually do
> anything. Even my notebook's key for toggling full-screen vs
> un-expanded display on the lcd does nothing unless apmd or acpid
> as applicable are running....
>
How is each of your setups, ie, what is compiled in kernel and what is
a module ? My guess is:
- ACPI+APM in kernel: ACPI wins
- APM in kernel, ACPI module; APM starts, blocks ACPI
- and so on....
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.2.19-pre6 #1 SMP Wed Jan 3 21:28:10 CET 2001 i686
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-05 1:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 20:26 How to Power off with ACPI/APM? Michael D. Crawford
2001-01-05 1:10 ` James H. Cloos Jr.
2001-01-05 1:16 ` J . A . Magallon [this message]
2001-01-05 1:23 ` J . A . Magallon
2001-01-05 1:33 ` James H. Cloos Jr.
2001-01-05 1:18 ` egger
-- strict thread matches above, loose matches on Subject: below --
2001-01-05 18:18 Michael D. Crawford
2001-01-06 3:06 ` idalton
2001-01-05 18:08 Per Jessen
2001-01-05 7:56 Grover, Andrew
2001-01-05 3:32 Michael D. Crawford
2001-01-05 9:18 ` J . A . Magallon
2001-01-05 9:23 ` Dominik Kubla
2001-01-05 9:33 ` J . A . Magallon
2001-01-05 3:00 Michael D. Crawford
2001-01-03 20:49 How to power " Michael D. Crawford
2001-01-04 20:09 ` egger
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=20010105021623.C743@werewolf.able.es \
--to=jamagallon@able.es \
--cc=cloos@jhcloos.com \
--cc=crawford@goingware.com \
--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