I'm experiencing the very same issue on Jaunty 64 bit on Athlon 64 x2. What really seems to have happened is that some functionalities which were built as *modules* in the 2.6.27 kernel are now built right into the kernel:
64 bit config comparison (unset values removed): config-2.6.27-11-generic:424:CONFIG_CPU_FREQ=y config-2.6.27-11-generic:428:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y config-2.6.27-11-generic:431:CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m config-2.6.27-11-generic:432:CONFIG_CPU_FREQ_GOV_ONDEMAND=m config-2.6.27-11-generic:433:CONFIG_CPU_FREQ_GOV_PERFORMANCE=y config-2.6.27-11-generic:434:CONFIG_CPU_FREQ_GOV_POWERSAVE=m config-2.6.27-11-generic:435:CONFIG_CPU_FREQ_GOV_USERSPACE=m config-2.6.27-11-generic:436:CONFIG_CPU_FREQ_STAT=m config-2.6.27-11-generic:437:CONFIG_CPU_FREQ_STAT_DETAILS=y config-2.6.27-11-generic:438:CONFIG_CPU_FREQ_TABLE=m config-2.6.27-11-generic:3392:CONFIG_X86_ACPI_CPUFREQ=m config-2.6.27-11-generic:3420:CONFIG_X86_POWERNOW_K8=m config-2.6.27-11-generic:3421:CONFIG_X86_POWERNOW_K8_ACPI=y config-2.6.28-11-generic:429:CONFIG_CPU_FREQ=y config-2.6.28-11-generic:433:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y config-2.6.28-11-generic:436:CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y config-2.6.28-11-generic:437:CONFIG_CPU_FREQ_GOV_ONDEMAND=y config-2.6.28-11-generic:438:CONFIG_CPU_FREQ_GOV_PERFORMANCE=y config-2.6.28-11-generic:439:CONFIG_CPU_FREQ_GOV_POWERSAVE=y config-2.6.28-11-generic:440:CONFIG_CPU_FREQ_GOV_USERSPACE=y config-2.6.28-11-generic:441:CONFIG_CPU_FREQ_STAT=y config-2.6.28-11-generic:442:CONFIG_CPU_FREQ_STAT_DETAILS=y config-2.6.28-11-generic:443:CONFIG_CPU_FREQ_TABLE=y config-2.6.28-11-generic:3601:CONFIG_X86_ACPI_CPUFREQ=y config-2.6.28-11-generic:3630:CONFIG_X86_POWERNOW_K8=y config-2.6.28-11-generic:3631:CONFIG_X86_POWERNOW_K8_ACPI=y But probably something did not work with some modules / kernel parts. Maybe some functions were designed to work as modules only, and they simply can't work if builtin? Experience with 3 Jaunty PCs: 1) HP Desktop with a Pentium E2160 CPU and Jaunty 32 bit -> cpufreq still available and working 2)Dell desktop with Core 2 Duo E6xxx CPU, Jaunty 32 bit -> cpufreq still available and working 3) Homebuilt Athlon 64 x2, Jaunty 64 bit -> cpufreq unavailable since Jaunty upgrade. I'm attaching a tar.gz with the output from cpuinfo, uname -a and find for the three pcs. ** Attachment added: "cpufreq_issues.tar.gz" http://launchpadlibrarian.net/27166496/cpufreq_issues.tar.gz -- cpu frequency scaling not supported after upgrading to 9.04 https://bugs.launchpad.net/bugs/365798 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
