How to configure cpufreqd - Revision history

Wyrfel at 22:35, 17 January 2006

2006-01-17T22:35:42Z

2006-01-15T20:13:55Z

2006-01-15T20:12:28Z

2006-01-14T11:59:37Z

2005-07-20T09:19:12Z

2005-07-10T15:24:24Z

2005-07-10T15:23:27Z

2005-07-10T15:06:31Z

2005-07-10T13:44:51Z

spelling corrections

2005-07-10T13:44:01Z

proposal of in-kernel alternative to cpufreqd

← Older revision		Revision as of 22:35, 17 January 2006
Line 1:		Line 1:
−	{{NOTE\|Make sure you have the appropriate kernel modules loaded, such as ''cpufreq_powersave'', ''cpufreq_userspace'', and ''cpufreq_ondemand'' (see above note).}}	+	{{NOTE\|Make sure you have the appropriate kernel modules loaded, such as <tt>cpufreq_powersave</tt>, <tt>cpufreq_userspace</tt>, and <tt>cpufreq_ondemand</tt> (see above note).}}

	In Debian, all you have to do is:		In Debian, all you have to do is:

@@ Line 6: / Line 6: @@
 And in most cases it will work out of the box.
-This is the default Debian config, but works well out of the box:
+This is the default Debian config, but works well out of the box. Notice that the syntax for the config file has changed in cpufreqd-2.0.0, where you need to close [] sections with tags like [/Profile] or [/Rule].
   # this is a comment

← Older revision		Revision as of 20:12, 15 January 2006
Line 1:		Line 1:
−	~~{{NOTE\|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling\|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}~~
−
	{{NOTE\|Make sure you have the appropriate kernel modules loaded, such as ''cpufreq_powersave'', ''cpufreq_userspace'', and ''cpufreq_ondemand'' (see above note).}}		{{NOTE\|Make sure you have the appropriate kernel modules loaded, such as ''cpufreq_powersave'', ''cpufreq_userspace'', and ''cpufreq_ondemand'' (see above note).}}

← Older revision		Revision as of 11:59, 14 January 2006
Line 1:		Line 1:
	{{NOTE\|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling\|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}		{{NOTE\|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling\|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}

		+	{{NOTE\|Make sure you have the appropriate kernel modules loaded, such as ''cpufreq_powersave'', ''cpufreq_userspace'', and ''cpufreq_ondemand'' (see above note).}}

	In Debian, all you have to do is:		In Debian, all you have to do is:

@@ Line 3: / Line 3: @@
 In Debian, all you have to do is:
- apt-get install cpufreqd
+:{{cmdroot|apt-get install cpufreqd}}
 And in most cases it will work out of the box.

← Older revision		Revision as of 15:24, 10 July 2005
Line 1:		Line 1:
−	{{NOTE\|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling\|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons.}}	+	{{NOTE\|See the [[How_to_make_use_of_Dynamic_Frequency_Scaling\|Dynamic Frequency Scaling HOWTO]] on how to avoid using cpu frequency scaling daemons by using the kernel builtin ondemand governor.}}

@@ Line 1: / Line 1: @@
 In Debian, all you have to do is:
   apt-get install cpufreqd
@@ Line 105: / Line 108: @@
   cpu_interval=0-100
   profile=hi_boost

← Older revision		Revision as of 15:06, 10 July 2005
Line 106:		Line 106:
	profile=hi_boost		profile=hi_boost

−	~~Remark: in recent Linux kernels there is the ondemand scaling governor. Using that one, you'll probably not need any~~ cpu ~~speed utilities any more. Additionally, you may change between "ondemand" and "performance" or "powersave"~~ scaling ~~governors by using ACPI events via acpid. That way, your CPU time probably won't get wasted as cpufreqd and assorted utilities do~~.	+	See [[How_to_make_use_of_Dynamic_Frequency_Scaling]] on how to avoid using cpu frequency scaling daemons.

← Older revision		Revision as of 13:44, 10 July 2005
Line 106:		Line 106:
	profile=hi_boost		profile=hi_boost

−	Remark: in recent Linux kernels there is the ondemand scaling governor. Using that one, you'll probably not need any cpu speed utilities any more. Additionally, you may change between "ondemand" and "performance" or "~~poewrsave~~" scaling governors by using ACPI events via acpid. That way, your CPU time probably won't be wasted as cpufreqd and assorted utilities do.	+	Remark: in recent Linux kernels there is the ondemand scaling governor. Using that one, you'll probably not need any cpu speed utilities any more. Additionally, you may change between "ondemand" and "performance" or "powersave" scaling governors by using ACPI events via acpid. That way, your CPU time probably won't get wasted as cpufreqd and assorted utilities do.

← Older revision		Revision as of 13:44, 10 July 2005
Line 105:		Line 105:
	cpu_interval=0-100		cpu_interval=0-100
	profile=hi_boost		profile=hi_boost
		+
		+	Remark: in recent Linux kernels there is the ondemand scaling governor. Using that one, you'll probably not need any cpu speed utilities any more. Additionally, you may change between "ondemand" and "performance" or "poewrsave" scaling governors by using ACPI events via acpid. That way, your CPU time probably won't be wasted as cpufreqd and assorted utilities do.