From: Sebastian Henschel <shensche-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: "Polevoy, IgorX" <igorx.polevoy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: enabling ACPI on RH 8
Date: Mon, 7 Apr 2003 10:20:20 +0200 [thread overview]
Message-ID: <20030407082019.GA13268@enigma.daemon.sh> (raw)
In-Reply-To: <DFDDBBFBAF6C634BAE34B5F175A29F0227F405-DFHDMA+VBDpRVdoAopKfxth3ngVCH38I@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
hello...
Received at 2003-04-06 / 18:28 by Polevoy, IgorX:
> I'm trying to enable ACPI on Linux RH 80 (kernel 2.4.18-14) and to run
> acpid.
> I succeeded to re-compile and re-boot the kernel with all the
> ACPI support options selected, however there is no
> /proc/acpi created (or other signs of ACPI driver is up).
>
> How do I enable it?
dunno what redhat uses, but:
check the boot parameters of your kernel, for instance in
/etc/lilo.conf:
- look for the line which conains the "append" keyword and replace "apm=on"
with "apm=off" and "acpi=off" with "acpi=on".
- save lilo.conf and rerun lilo with "/sbin/lilo".
if you are running grub it is quite similar, look for the aforementioned
parameters and change them.
the important thing is to _not_ have "acpi=off". acpi usually overrides
apm if both are "on" (either explicitly or implicitly).
if this does not help, please send the output of "dmesg" after a fresh
reboot to the list.
> Has it anything to do with the fact that the APM support is currently
> enabled ?
well, compiling both, acpi and apm, into your kernel is usually no
problem.
hth,
sebastian
--
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-07 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 15:13 enabling ACPI on RH 8 Polevoy, IgorX
[not found] ` <DFDDBBFBAF6C634BAE34B5F175A29F0227F405-DFHDMA+VBDpRVdoAopKfxth3ngVCH38I@public.gmane.org>
2003-04-07 8:20 ` Sebastian Henschel [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 8:09 Polevoy, IgorX
[not found] ` <DFDDBBFBAF6C634BAE34B5F175A29F0227F406-DFHDMA+VBDpRVdoAopKfxth3ngVCH38I@public.gmane.org>
2003-04-08 9:57 ` Mattia Dongili
2003-04-09 14:54 Polevoy, IgorX
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=20030407082019.GA13268@enigma.daemon.sh \
--to=shensche-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=igorx.polevoy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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