From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org
Subject: Re: How to Power off with ACPI/APM?
Date: Fri, 05 Jan 2001 03:00:46 +0000 [thread overview]
Message-ID: <3A5538DE.92066D9A@goingware.com> (raw)
> 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....
Nope. If they're both in the kernel, APM wins.
When I built with both ACPI and APM, and then APM ran first. ACPI started up in
the kernel, commented that APM was already there, and exited.
Many folks have given me tips on getting power off to work, I'll screw around to
see if I can get it to go. But I guess the fact that ACPI exits if APM is
enabled is a real bug.
I know it's hip, cool and efficient to use modules but I often start by
hardwiring things into the kernel because I may not have stuff set up right yet
to load the modules after getting the new kernel. Just saying Y instead of M
often makes things work without further trouble.
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set
--
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com
Tilting at Windmills for a Better Tomorrow.
-
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 reply other threads:[~2001-01-05 6:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 3:00 Michael D. Crawford [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-05 18:18 How to Power off with ACPI/APM? 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-04 20:26 Michael D. Crawford
2001-01-05 1:10 ` James H. Cloos Jr.
2001-01-05 1:16 ` J . A . Magallon
2001-01-05 1:23 ` J . A . Magallon
2001-01-05 1:33 ` James H. Cloos Jr.
2001-01-05 1:18 ` egger
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=3A5538DE.92066D9A@goingware.com \
--to=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