Re: acpi=force safe?

On Fri, Feb 06, 2004 at 11:16:15AM -0600, Nick Bartos wrote:

Am I to understand that the worse that could happen is that the acpi
features I compiled in (just standard and the button option) just wouldn't
work?  If that is the case then that would be fine.

Just standard mean that all the IRQ routing was done by ACPI
amongst other things.  And you need to do so if you want to receive
events from the power button.

That part of the firmware may be broken, and you may have hang on boot
(even though I think it is safe now without lapic support even on old laptops).

Really I just don't want things like kernel screw ups (which I thought I
might have had once due to acpi, but I don't remember), or other things
that affect system stability.

If I can compile in these things and force acpi on and not be any worse
off stability wise than if I didn't force it, then that willl be fine for
me.

Why not let user decide at boot time?  That easy to do so with syslinux
for example.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn