On Tue, Jun 10, 2008 at 01:51:34PM +0200, psycheye wrote: > > One could argue that removing /proc/acpi now may break other programs > > and that it would be nice to have it enabled in the kernel for some more > > time. > doing: cpufreq-get I see: > No cpufreqd socket found > > (but in /var/run there's the pid about cpufreqd)
you need a unix socket, not a pid file :) you can enable this feature in the config file (see also man cpufreqd.conf) > so, if I try to set cpu clock with cpufreq-selector (cpufreq-selector -c 0 -c > 1 -f 800) the command run, but the cpu clock doesn't change :-/ oh, this is not from the cpufreqd package and actually conflicts with what cpufreqd thinks the current frequency is. > So, I don't understand if "No cpufreqd socket found" is about the bug of > package or other errors. no, unrelated. This bug is about the /proc/acpi directory not being available in recent debian kernels. > What I will do? see above. Enable the unix socket and try again. cheers -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
