From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: BlaisorBlade <blaisorblade_work-whZMOeQn8C0@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2001-(Ali chipset)mainboard with no ACPI because "from '97 and too old"!
Date: Fri, 10 Oct 2003 10:30:42 +0200 [thread overview]
Message-ID: <20031010083042.GL11391@poupinou.org> (raw)
In-Reply-To: <200310092108.15747.blaisorblade_work-whZMOeQn8C0@public.gmane.org>
On Thu, Oct 09, 2003 at 09:08:15PM +0200, BlaisorBlade wrote:
> The subject explains almost all. On my desktop, my mainboard (from 1st
> mainboards, with an AMI bios, if I don't remember badly) appears, on boot, as
> "from '97 and too old" so ACPI is disabled; see top of dmesg output (on
> kernel 2.4.22). On some older version of the patch(I've used the -ck patchset
> since kernel 2.4.20, and it included ACPI, and I've had it in the Mandrake
> 9.0/9.1 kernel) my mainboard was correctly handled and ACPI didn't create any
> problems. All required data is attached. Please address any question on Cc:
> to me, since I'm not subscribed. Thanks.
Dmesg said:
<quote>
ACPI disabled because your bios is from 97 and too old
You can enable it with acpi=force
</quote>
so reboot with kernel parameter acpi=force.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
prev parent reply other threads:[~2003-10-10 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 19:08 2001-(Ali chipset)mainboard with no ACPI because "from '97 and too old"! BlaisorBlade
[not found] ` <200310092108.15747.blaisorblade_work-whZMOeQn8C0@public.gmane.org>
2003-10-10 8:30 ` Ducrot Bruno [this message]
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=20031010083042.GL11391@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=blaisorblade_work-whZMOeQn8C0@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