On Mon, Jul 31, 2006 at 07:04:07AM -0700, Zwane Mwaikambo wrote: > On Mon, 31 Jul 2006, Tomasz Torcz wrote: > > > On Sun, Jul 30, 2006 at 10:45:13AM -0700, Zwane Mwaikambo wrote: > > > > > CONFIG_X86_ACPI_CPUFREQ > > > > I had this one =y. After setting =n, cpufreq-nforce2 (=m) works again. > > > > powernowd: PowerNow Daemon v0.96, (c) 2003-2005 John Clemens > > powernowd: Found 1 cpu: -- 1 thread (or core) per physical cpu > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: No > > such file or directory > > powernowd: cpu0: 1228Mhz - 1753Mhz (7 steps) > > Hi Tomasz, > > Could you also please test Bert's patch which propogates error > return values with your previous configuration? Bert's patch works. With CONFIG_X86_ACPI_CPUFREQ=y and cpufre-nforce2=m I have working cpufreq (like in 2.6.17 and before). -- Tomasz Torcz "Never underestimate the bandwidth of a station [email protected] wagon filled with backup tapes." -- Jim Gray
Attachment:
pgpyDWYaV8SN9.pgp
Description: PGP signature
- References:
- 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: bert hubert <[email protected]>
- Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: Tomasz Torcz <[email protected]>
- Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: Zwane Mwaikambo <[email protected]>
- Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: Tomasz Torcz <[email protected]>
- Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: Zwane Mwaikambo <[email protected]>
- 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- Prev by Date: Re: [ltp] Re: Generic battery interface
- Next by Date: Re: [2.6.18-rc2-mm1] libata ate one PATA channel
- Previous by thread: Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- Next by thread: Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- Index(es):
 |