[DragonFlyBSD - Bug #569] (Closed) ACPI issues (maybe)

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #569 has been updated by tuxillo.

Description updated
Category set to ACPI
Status changed from New to Closed
Assignee deleted (0)
Target version set to 4.2.x

Hi,

Apparently the Core Duo T2050 (the processor in that laptop) is 32-bit only.
Closing this one as i386 is no longer supported.

Cheers,
Antonio Huete

----------------------------------------
Bug #569: ACPI issues (maybe)
http://bugs.dragonflybsd.org/issues/569#change-12518

* Author: qhwt+dfly
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: ACPI
* Target version: 4.2.x
----------------------------------------
Hi.
Please post any bug reports to bugs@, whether it's ACPI-related or
not.

Is this bug new in 1.8?  Do you experience this problem when you
run a UP kernel?

That's how you enable some debugging features when the acpi driver is
compiled in the kernel.  However, compiling the ACPI driver in the kernel
is not supported at the moment, as some modifications to ACPI-CA code are
given as *.patch files in /sys/dev/acpica5 and those are not used when
compiled in the kernel (I believe there's a few other drivers which also
use *.patch files, but I haven't tried to see if these are not used either).
To compile an acpi driver with debugging feature enabled for an SMP kernel,
you do:
  export ACPI_DEBUG=yes CFLAGS='-O -pipe -DSMP=1'
for bourne shell users, or for *csh,
  setenv ACPI_DEBUG yes
  setenv CFLAGS '-O -pipe -DSMP=1'

Sounds like ACPI driver failed to load.  Do you have this problem
when you boot with ACPI disabled (debug.acpi.disabled="acpi" in the
boot loader)?

Cheers.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account