That canned response doesn't apply, as the problem is not in the kernel itself, but in the configuration Ubuntu is using to compile the kernel.
The fix is simple: in the kernel config, change CONFIG_X86_POWERNOW_K8=y and CONFIG_X86_ACPI_CPUFREQ=y to CONFIG_X86_POWERNOW_K8=m and CONFIG_X86_ACPI_CPUFREQ=m respectively. Confirmed in Trusty Tahr. Boy this guy's been around. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/355232 Title: acpi-cpufreq/powernow-k8 should not be built-in into the kernel image Status in “linux” package in Ubuntu: New Status in “linux” source package in Lucid: In Progress Bug description: Binary package hint: linux-image-generic acpi-cpufreq is not a module anymore and is directly included in the kernel. I think it is a bad decision because it is now very difficult to use phc to undervolt a processor : we need to compile the whole kernel with acpi-cpufreq as a module instead of just compile the module. http://www.linux-phc.org/index.php I am using ubuntu jaunty. Do you think we can have it back as a module for the final release ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp