I recently started to use development and upgraded from an FC5 state. The kernel from FC5 works with processor frequency control. The last two kernels from my start with development bomb out for processor speed control.
Does this work with development kernels? Is there a modification from FC5 scripts to current development which needs completed to get this to work?
From previous tests with smp enabled kernels, the frequency control would not work. Are all development kernels smp enabled for i386 as well as 64-bit processors?
Thanks, Jim (non-Nvidia)
On Fri, Jun 02, 2006 at 07:55:57PM -0400, Jim Cornette wrote:
I recently started to use development and upgraded from an FC5 state. The kernel from FC5 works with processor frequency control. The last two kernels from my start with development bomb out for processor speed control.
Does this work with development kernels? Is there a modification from FC5 scripts to current development which needs completed to get this to work?
On my todo. I should find time to get this nailed in the next few days.
From previous tests with smp enabled kernels, the frequency control would not work. Are all development kernels smp enabled for i386 as well as 64-bit processors?
Yes.
Dave
Dave Jones wrote:
On Fri, Jun 02, 2006 at 07:55:57PM -0400, Jim Cornette wrote:
I recently started to use development and upgraded from an FC5 state. The kernel from FC5 works with processor frequency control. The last two kernels from my start with development bomb out for processor speed control.
Does this work with development kernels? Is there a modification from FC5 scripts to current development which needs completed to get this to work?
On my todo. I should find time to get this nailed in the next few days.
Thanks! I'll run the FC5 kernel until then.
From previous tests with smp enabled kernels, the frequency control would not work. Are all development kernels smp enabled for i386 as well as 64-bit processors?
Yes.
If it is the same cause, I'll hold off until then. The cpu scaling is a highly desired feature.
Jim
Dave
Hello,
On 03/06/06, Jim Cornette fct-cornette@insight.rr.com wrote:
The cpu scaling is a highly desired feature.
As it saves power consuption, is it possible to see the following line in newer kernel's config?
CONFIG_X86_CPUFREQ_NFORCE2=m
Dave, would you mind to comment regarding the issue with AMD XP-M, is it possible to be made "=m" default.
On Tue, Jun 06, 2006 at 12:40:15PM +0300, Filip Tsachev wrote:
Hello,
On 03/06/06, Jim Cornette fct-cornette@insight.rr.com wrote:
The cpu scaling is a highly desired feature.
that should be fixed in todays rawhide btw.
As it saves power consuption, is it possible to see the following line in newer kernel's config?
CONFIG_X86_CPUFREQ_NFORCE2=m
that driver is still really experimental, and given there's already more wierdo bugs that I can't make head nor tail of in bugzilla, adding something that potentially introduces instability isn't a good idea.
Dave, would you mind to comment regarding the issue with AMD XP-M, is it possible to be made "=m" default.
not without adding complexity to the startup scripts to pick the right driver. By having them non-modular the right one gets picked automatically as the kernel tries the init routine for each.
Dave
Dave Jones wrote:
On Tue, Jun 06, 2006 at 12:40:15PM +0300, Filip Tsachev wrote:
Hello,
On 03/06/06, Jim Cornette fct-cornette@insight.rr.com wrote:
The cpu scaling is a highly desired feature.
that should be fixed in todays rawhide btw.
The cpu frequency is now working again. Thanks!
Now to get on with bugs in gdm, X, sound-mixers and more.
Jim
Dave
-
Dave Jones -
Filip Tsachev -
Jim Cornette