Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16773 - [epplet-base] cpufreq applet doesn't work
Attached to Project:
Arch Linux
Opened by Pavol Klačanský (pavolzetor) - Wednesday, 21 October 2009, 19:08 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 26 January 2010, 17:40 GMT
Opened by Pavol Klačanský (pavolzetor) - Wednesday, 21 October 2009, 19:08 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 26 January 2010, 17:40 GMT
|
DetailsDescription:
hallo, cpu freq files in dir /sys/devices/system/cpu/cpu0/cpufreq I cannot scale it by applet in E17, but after executing e.g. "cpufreq-set -c 0 -f 800", the applet starts work Additional info: * cpufrequtils 005-2 * config and/or log files etc. Steps to reproduce: start system try scale CPU speed by e.g. echo > file exec cpufreq-set and try file again |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Tuesday, 26 January 2010, 17:40 GMT
Reason for closing: Fixed
Additional comments about closing: cpufrequtils 006-1
Tuesday, 26 January 2010, 17:40 GMT
Reason for closing: Fixed
Additional comments about closing: cpufrequtils 006-1
You are execute these commands as root? Are you on i686 or x86_64, can you read files on /sys/devices/system/cpu/cpu0/cpufreq/*? What values are on? What relevant modules are loaded before and after don't work/work ?
Thanks.
x86_64
I can read these files
celkom 0
-r--r--r-- 1 root root 4096 okt 24 19:37 affected_cpus
-r-------- 1 root root 4096 okt 24 19:37 cpuinfo_cur_freq
-r--r--r-- 1 root root 4096 okt 24 19:37 cpuinfo_max_freq
-r--r--r-- 1 root root 4096 okt 24 19:37 cpuinfo_min_freq
-r--r--r-- 1 root root 4096 okt 24 19:37 cpuinfo_transition_latency
drwxr-xr-x 2 root root 0 okt 24 19:44 ondemand
-r--r--r-- 1 root root 4096 okt 24 19:37 related_cpus
-r--r--r-- 1 root root 4096 okt 24 19:35 scaling_available_frequencies
-r--r--r-- 1 root root 4096 okt 24 19:35 scaling_available_governors
-r--r--r-- 1 root root 4096 okt 24 19:35 scaling_cur_freq
-r--r--r-- 1 root root 4096 okt 24 19:37 scaling_driver
-rw-r--r-- 1 root root 4096 okt 24 19:35 scaling_governor
-rw-r--r-- 1 root root 4096 okt 24 19:37 scaling_max_freq
-rw-r--r-- 1 root root 4096 okt 24 19:37 scaling_min_freq
-rw-r--r-- 1 root root 4096 okt 24 19:36 scaling_setspeed
[root@myhost pk]# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_setspeed
<unsupported>
<unsupported>
[root@myhost pk]# ps aux | grep cpufreq
root 1832 0.0 0.0 7900 940 pts/0 DN+ 19:45 0:00 grep cpufreq
I've started it after boot and after start E17 from console (as root)
And there is strange beahavior. After run that command "cpufreq-set -f 800MHz"
scaling works (by writing to file by applet)
800000
<unsupported>
What's the name of the ML? Can you post a link to your archived post? I'm interested in knowing what they think of the patch.
I'm not registred in ML, I must wait to admin control.