cpufreqd 1.0 doesn't work with the new sysfs-style interface, just uses the old procfs-based one. Reproducible: Always Steps to Reproduce: 1. emerge cpufreqd 2. /etc/init.d/cpufreqd start Actual Results: * CPUFreq support has not been compiled into the kernel Expected Results: Should work both ways. Sooner or later the procfs-style interface will be dropped from 2.6 kernels (probably more sooner than later). Ugly solution: enable old-style procfs interface in 2.6.0-* while it lasts. Nice solution: we should upgrade to cpufreqd 1.0.1 which supports both methods :)
Nice solution: we should upgrade to cpufreqd 1.0.1 which supports both methods :) I decided to use the nice solution. Bumped the version to 1.0.1 I hope this resolves this bug. If not then please reopen it. Thanks for your help.
Requires additional fix in /etc/init.d/cpufreqd to allow the startup to work on sysfs-only interface. " if [ ! -e /proc/cpufreq ] ; then " should be " if [ ! -e /proc/cpufreq -a ! -e /sys/devices/system/cpu/cpu0/cpufreq ] ; then " Sorry to have missed it before.
Did you post that updwards? Do the include a init.d file that includes this fix in the next release?
Contacted author (Mattia Dongili), told me he'll fix it tonight.
Great! As soon as he fixed it and i checked in the new ebuild i'll close this bug. Thanks for your help!
I can't find acorrected ebuild or bumped package (and i think the package should get bumped as the init-script is inside the package) on cpufreqd.sf.net. Could you please check and ask him again?
Gustavo Zacarias <gustavo@zacarias.com.ar>: Could you please remind the author of cpufreqd to provide a fixed version (as he told you so)? I can't do anything on this bug if i'm not getting a corrected version from upstream.
We should probably close this since the freq interface isn't completely defined on 2.6.x kernels yet. Also it should be ~x86. Sorry for the delay.
> ------- Additional Comment #8 From Gustavo Zacarias 2003-09-17 10:47 PST ------- > We should probably close this since the freq interface isn't completely defined > on 2.6.x kernels yet. After many sysfs shuffles during 2.5., the _current_ cpufreq sysfs interface [2.6-testX] will most likely be what's in 2.6.x, too. So, can you apply the "patch" of comment #2 and push cpufreqd-1.0.1-r1, please? If not, I'll contact Mattia and ask him for the updated "upstream" release.
Created attachment 18858 [details, diff] proposed patch to be put into sys-apps/cpufreqd/files MD5 823074606ab9025af1210226fd2a626a sysfs.diff 403 updated ebuild will follow in a moment
Created attachment 18859 [details] proposed replacement ebuild MD5 3d408991f66e9b7b8ce858e30e970b54 cpufreqd-1.0.1-r1.ebuild 909
I checked in the new ebuild and the patch. I think as a long time solution it would be good to get this fixed upstream. Thanks for your submission and your help.
