|
Bugzilla – Full Text Bug Listing |
| Summary: | CPUFREQ default policy not set to userspace | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michael Stather <kontakt> |
| Component: | Mobile Devices | Assignee: | Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | behlert |
| Version: | Alpha 1 | ||
| Target Milestone: | Beta 3 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Stather
2005-10-04 14:50:20 UTC
I think you misunderstood this. We want to get rid of "userspace" completely, as soon as the kernel governor works for all setups. We do not want to make userspace default. Do you have the 10.0 bug # at hand? Oh, ok I misunderstood this :( The bug I originally files was #118735 It has been marked as a duplicate of #113615 I will try to implement something to fall back automatically to userspace (or at least issue a loud honking warning at boot :-) but it is not ready yet. Sorry for the inconvenience. I'll keep this open as an enhancement, so it will stay on my radar. If ondemand does not work, powersaved now automatically tries the userspace governor, so we should get a working setup if at all possible. |