From: "Nick Bartos" <spam99@2thebatcave.com>
To: linux-kernel@vger.kernel.org
Subject: acpi - forcing only button event & powerdown on?
Date: Sat, 24 Jan 2004 20:03:45 -0600 (CST) [thread overview]
Message-ID: <57099.192.168.1.12.1074996225.squirrel@mail.2thebatcave.com> (raw)
I have a little linux distro I made that I use for a fair amount of
routers/servers. They use several different motherboards, and it seems to
me that in every recent release, the acpi in the kernel fixes support for
one board while breaking another.
I have tried forcing acpi on before, but I really don't like to do that as
I am thinking it would have side effects (one of the boards is on a
blacklist for acpi=ht, and when I do acpi=force it says that I am
overriding acpi=ht).
Really all I use on all of these systems is the acpi button event (for a
nice way to cleanly shutdown a headless router/server by tapping the power
button), and the acpi powerdown feature. I would think these two features
are simple enough that forcing them on wouldn't cause any problems like
system instability, even if there were hardware issues with them (but then
I really don't know anything about acpi...).
Is there a way to force acpi on, but only for the couple of things I need
(disabling the rest if it is a good idea), so I don't get into trouble
later?
I don't care too much for the idea of making a distro where I am bypassing
kernel autodection on things (as it is most likely done a certain way for
a reason, and I am no kernel developer), but I would like to be assured
that when I upgrade these machines, the two functions I use will continue
to work.
Am I asking too much or is this doable?
next reply other threads:[~2004-01-25 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 2:03 Nick Bartos [this message]
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AE587@hdsmsx402.hd.intel.com>
2004-01-28 21:43 ` Len Brown
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=57099.192.168.1.12.1074996225.squirrel@mail.2thebatcave.com \
--to=spam99@2thebatcave.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
all inboxes | Powered by JetHome®