| Summary: | xfce4-cpufreq-plugin do not work with certain processors | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Georges Eckenschwiller <paiiou> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | stormi-mageia |
| Version: | 2 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Georges Eckenschwiller
2013-01-22 22:44:46 CET
Are you sure it comes from xfce4-cpufreq-plugin? Maybe this computer doesn't support this kind of functionality. Can you test with another cpu frequency display/adjustment tool? Keywords:
(none) =>
NEEDINFO I did not find other indicator, compatible gtk. But, the peculiarity of the computer is that it is not really the processor which allows the change of frequency, but it is the chipset which changes the frequency of the bus (if I understood well) motherboard : MSI KT4V It's important to find out if it's possible at all to adjust the frequency from a linux system for this motherboard and how. Then we can know if it's a xfce4-cpufreq-plugin issue or another issue (kernel, buggy ACPI, ...).
You could try cpufreq in command line.
# cat /proc/cpuinfo # to check current CPU frequency
# urpmi cpufreq # if not installed already
# vim /etc/sysconfig/cpufreq : set MAX_FREQ={put here half your max freq, in Hz}, and set GOVERNOR=performance
# service cpufreq restart
# cat /proc/cpuinfo # to check new CPU frequency
# put /etc/sysconfig/cpufreq back to previous values
Since mageia 3, it is to cpupower who is used. cpupower frequency-info gives (extract) pilote : nforce2 limitation matérielle : 1.29 - 1.84 GHz tactique actuelle : userspace fréquence actuelle : 1.29 GHz => cpupower et powernowd work well. => I think that it is effectively xfce4-cpufreq-plugin that does not show the values. The drop-down list of processors remains grey. This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |