Arch Linux

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!
Tasklist

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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
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
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 22 October 2009, 15:06 GMT
Please provide more information if any, like relevant log and kernel messages.

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.
Comment by Pavol Klačanský (pavolzetor) - Saturday, 24 October 2009, 10:14 GMT
as root
x86_64
I can read these files
Comment by Pavol Klačanský (pavolzetor) - Saturday, 24 October 2009, 17:58 GMT
[root@myhost pk]# ls -l /sys/devices/system/cpu/cpu0/cpufreq/
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)
Comment by Pavol Klačanský (pavolzetor) - Sunday, 25 October 2009, 09:40 GMT
[root@myhost language]# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_setspeed
800000
<unsupported>
Comment by Pavol Klačanský (pavolzetor) - Monday, 26 October 2009, 18:27 GMT
I think, this is problem of applet in E17, in GNOME applet it works, I will investigate it
Comment by Andrea Scarpino (BaSh) - Tuesday, 27 October 2009, 11:03 GMT
  • Field changed: Summary (cpufreq proc files have no write permissions → [epplet-base] cpufreq applet doesn't work)
  • Task reassigned to Eric Belanger (Snowman)
this is related only to cpufreq E17 applet. assigned to epplet-base maintainer
Comment by Pavol Klačanský (pavolzetor) - Tuesday, 27 October 2009, 20:12 GMT
I've sent patch to e17 devel list.
Comment by Eric Belanger (Snowman) - Tuesday, 27 October 2009, 20:36 GMT
can you attach a copy of the patch here?
Comment by Pavol Klačanský (pavolzetor) - Tuesday, 27 October 2009, 20:57 GMT
no problem
Comment by Eric Belanger (Snowman) - Tuesday, 27 October 2009, 21:23 GMT
Sorry, I forgot to also ask this:
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.
Comment by Pavol Klačanský (pavolzetor) - Tuesday, 27 October 2009, 21:34 GMT Comment by Pavol Klačanský (pavolzetor) - Saturday, 31 October 2009, 09:00 GMT
latest patch
Comment by Eric Belanger (Snowman) - Saturday, 31 October 2009, 09:34 GMT
It's the same as the other one. Did you sent the wrong one?
Comment by Pavol Klačanský (pavolzetor) - Saturday, 31 October 2009, 09:48 GMT
sorry, It's right
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 26 January 2010, 07:17 GMT
is this still an issue?
Comment by Pavol Klačanský (pavolzetor) - Tuesday, 26 January 2010, 15:54 GMT
no, they have applied my patch :-)

Loading...