You can define ACPI_DEBUG in the environment before building the kernel,
or when manually building the module, or in /etc/make.conf.
> I've stumbled on the ACPI_DEBUG issue in the module load as well.
> The ACPI_DEBUG definition only propogates to the opt_acpi.h file
> in the base kernel. The
I've stumbled on the ACPI_DEBUG issue in the module load as well.
The ACPI_DEBUG definition only propogates to the opt_acpi.h file
in the base kernel. The acpi module build doesn't seem to carry
forward the ACPI_DEBUG flag. As a workaround, I just wack the define
into the opt_acpi.h file in the
In message <[EMAIL PROTECTED]>, Georg-W Koltermann さんいわ
く:
>Hi,
>
>I finally got around to hook up a serial console and capture the error
>message. This is with ACPI_DEBUG enabled in the kernel config, but
>ACPI is still loaded as a module, not configured statically.
>
>acpi0
Hi,
I finally got around to hook up a serial console and capture the error
message. This is with ACPI_DEBUG enabled in the kernel config, but
ACPI is still loaded as a module, not configured statically.
acpi0: on motherboard
ACPI-0294: *** Error: Method execution failed, AE_NOT_EXI
* Georg-W Koltermann ([EMAIL PROTECTED]) wrote:
> Hi,
>
> I CVSuped yesterday and still see the problem that was discussed in
> this thread, i.e. immediate reset during kernel initialization when
> ACPI is enabled on an HP Omnibook 6100. The error message flies by so
> quickly that I cannot even
Hi,
I CVSuped yesterday and still see the problem that was discussed in
this thread, i.e. immediate reset during kernel initialization when
ACPI is enabled on an HP Omnibook 6100. The error message flies by so
quickly that I cannot even read it.
Has there been any progress towards a solution?
