On Mon, Nov 06, 2006 at 04:43:13PM +0100, Christian wrote: > > Did you have CONFIG_ACPI_PROCESSOR=y in 2.6.18, or did > > CONFIG_ACPI_PROCESSOR=m, CONFIG_X86_POWERNOW_K8=y work for you in 2.6.18? > > It worked with CONFIG_ACPI_PROCESSOR=m in 2.6.18-rc7. Since 2.6.19-rc1 it > doesn't work anymore with CONFIG_ACPI_PROCESSOR=m. > > user@ubuntu:~/Projekte/linux-2.6.18-rc7$ grep -i ACPI_PROCESSOR /boot/config-2.6.18-rc7 > CONFIG_ACPI_PROCESSOR=m > > user@ubuntu:~/Projekte/linux-2.6.18-rc7$ > grep -Ei "POWERNOW_K8" /boot/config-2.6.18-rc7 > CONFIG_X86_POWERNOW_K8=m > CONFIG_X86_POWERNOW_K8_ACPI=y > > +++ There's a difference in 2.6.19! CONFIG_X86_POWERNOW_K8_ACPI is gone +++ I don't understand how this was allowed. Because when I try this with a 2.6.18 tree.. (nothing changed between -rc7 and final for cpufreq) <editted a .config to match your config> $ grep ACPI_PROCESSOR .config CONFIG_ACPI_PROCESSOR=m $ grep POWERNOW_K8 .config CONFIG_X86_POWERNOW_K8=y CONFIG_X86_POWERNOW_K8_ACPI=y and then after a make oldconfig the CONFIG_X86_POWERNOW_K8_ACPI is removed as it isn't valid. Did you edit your .config by hand ? Dave -- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
