Terry Lambert wrote:
> Have you applied the most recent ACPI patches, and turned on
> debugging output (at least "hw.acpi.verbose=1") to see if it
> fixes the problem (and if it doesn't, at least report what's
> going on)?

It looks like the author of the ACPI code has already replied
to your post; apply the patch he suggests, and turn on the
debugging he suggests.  He knows far mor about ACPI than the
rest of us.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to