Your message dated Tue, 24 Mar 2009 03:32:46 +0100
with message-id <20090324023246.ga7...@stro.at>
and subject line Re: cpu-freq/user-guide.txt should mention Celeron
has caused the Debian Bug report #328528,
regarding cpu-freq/user-guide.txt should mention Celeron
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
328528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cpufreqd
Version: 1.2.3-3
Severity: wishlist

Upon seeing:
  Unable to find a CpuFreq interface in your kernel.
  Cpufreqd won't be started, please enable a CpuFreq driver in your kernel and
I try
# modprobe -l \*cpu*|sed s...@.*/@@\;s/.ko$//|xargs -n 1 modprobe
FATAL: Error inserting acpi_cpufreq 
(/lib/modules/2.6.12-1-686/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko):
 No such device
FATAL: Error inserting cpufreq_nforce2 
(/lib/modules/2.6.12-1-686/kernel/arch/i386/kernel/cpu/cpufreq/cpufreq-nforce2.ko):
 No such device
# lsmod|grep cpu
cpuid                   3076  0
cpu5wdt                 5564  0
cpufreq_conservative     7140  0
cpufreq_ondemand        6076  0
cpufreq_powersave       1664  0
cpufreq_stats           4740  0
freq_table              4516  1 cpufreq_stats
cpufreq_userspace       4508  0

I therefore have tried my best to
"enable a CpuFreq driver in your kernel"
# dlocate Cpufreq
gives nothing, so it can't be a lowercase / uppercase problem.

Anyway, if in fact it is a kernel problem, please reassign this bug there.
I only use stock kernels.
-- System Information:
Debian Release: testing/unstable
Kernel: Linux 2.6.12-1-686


--- End Message ---
--- Begin Message ---
upstream rejected with good rationale, thus closing.


--- End Message ---

Reply via email to