Ok, apparently it is my fault...
I traced the failure to
if (cpufreq_driver) {
spin_unlock_irqrestore(&cpufreq_driver_lock, flags);
return -EBUSY;
}
(cpufreq_register_driver in drivers/cpufreq/cpufreq.c)
Turns out I was modprobing acpi-cpufreq before modprobing cpufreq-k7.
This worked in previous kernels and apparently, not in this one.
If I do not modprobe acpi-cpufreq, it works.
Thiago
On 9/9/06, Thiago Galesi <[email protected]> wrote:
> >
> > CONFIG_X86_POWERNOW_K7_ACPI=y
> > ..
> > CONFIG_ACPI_PROCESSOR=m
>
> Does it start working again if you change ACPI_PROCESSOR=y ?
No. nothing changes
--
-
Thiago Galesi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]