|
Bugzilla – Full Text Bug Listing |
| Summary: | powersave error message about ondemand governor/cpufreq | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Christian Deckelmann <christian.deckelmann> |
| Component: | Mobile Devices | Assignee: | Holger Macht <hmacht> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | IS&T | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Deckelmann
2005-10-05 12:25:36 UTC
To be sure: Your aim is to completely disable cpufreq? I will take care. Yes, this machine cannot do CPUFreq, it is a P4 Desktop. Unfortunately we always try to initialize it and if it fails, we throw this error. Some more checking before trying to enable the ondemand governor would be good (or maybe a "--no-cpufreq" option for the daemon which at least with "CPUFREQD_MODULE=off" gets appended in the startscript) We plan to overwork the cpufreq-interface of the powersave daemon, so I will take account of this issue when I start implementing. I added a configuration value to the daemon indicating whether cpufreq is enabled by configuration or not. Just commited to cvs, so closing... |