Bug 164535

Summary:	More options for the power-management module
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Marco Michna <mmichna>
Component:	YaST2	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED WONTFIX	QA Contact:	Stanislav Visnovsky <visnov>
Severity:	Enhancement
Priority:	P5 - None
Version:	Beta 9
Target Milestone:	---
Hardware:	All
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	Component Test	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	140732

Description Marco Michna 2006-04-07 16:06:10 UTC

If your processor is not capable of frequency scaling then you just get a nice warning in the syslog. It would be much better if this message would be integrated into the YaST module and let the user choose if he/she want to set CPUFREQ_ENABLED=no in /etc/powersave/cpufreq.

Comment 1 Jiri Srain 2006-07-24 11:00:52 UTC

Thomas, how can I determine whether CPU supports frequency scaling?

Comment 2 Marco Michna 2006-10-22 18:46:55 UTC

Renni! Wake up!

Comment 3 Thomas Renninger 2006-10-23 08:46:23 UTC

check whether /sys/devices/system/cpu/cpu*/cpufreq directory exists.
We also had dbus option for that, but that likely changed and is not what you want?
Be aware that this should be checked after the powersaved/hal started and the cpufreq modules have been tried to be loaded. Since 10.2 there will be cpufreq modules loaded at installation time by linuxrc, but not all are tried there, hal (that's the service loading the cpufreq modules now Holger, right?), should do that more reliable.

Comment 4 Holger Macht 2006-10-23 09:01:40 UTC

The YaST module won't contain any CPUFreq settings anymore in the near future due to the pm redesign. So Jiri, feel free to close this bug as WONTFIX.