> The vicious cpufreq widget uses > /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq, which seems to > be gone in 3.10, and the new cpuinfo_cur_freq is root:root 0400 :/
Concerning root:root 0400 ownership, the workaround I would suggest would be to install the 'sysfsutils' package and then to make entries in /etc/sysfs.conf to manually set file mode and ownership, such as: -------------------- mode devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq = 0440 mode devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq = 0440 ... owner devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq = root:adm owner devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq = root:adm ... -------------------- Another confusing thing is that I'm using Debian's 3.10 kernel, but for some reason scaling_cur_freq and cpuinfo_cur_freq both exist on my system. (Not sure why that is.) # uname -r 3.10-1-amd64 # ls -1 /sys/devices/system/cpu/cpu0/cpufreq/ affected_cpus bios_limit cpuinfo_cur_freq cpuinfo_max_freq cpuinfo_min_freq cpuinfo_transition_latency related_cpus scaling_available_frequencies scaling_available_governors scaling_cur_freq scaling_driver scaling_governor scaling_max_freq scaling_min_freq scaling_setspeed stats -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
