Messages in this thread | | | Date | Sat, 24 Jan 2004 20:03:45 -0600 (CST) | Subject | acpi - forcing only button event & powerdown on? | From | "Nick Bartos" <> |
| |
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?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |