From: Jarod Wilson <jwilson@redhat.com>
To: cpufreq@lists.linux.org.uk
Cc: Emmanuel Andreu <emmanuel.andreu@gmail.com>
Subject: Re: Unknown p4-clockmode capable CPU
Date: Mon, 25 Feb 2008 09:02:01 -0500 [thread overview]
Message-ID: <200802250902.01276.jwilson@redhat.com> (raw)
In-Reply-To: <47C25A7C.3020305@gmail.com>
On Monday 25 February 2008 01:04:44 am Emmanuel Andreu wrote:
> Hello,
>
> Cpufreqd tells me at syslog :
> Feb 24 22:57:23 underworld kernel: [ 247.512000] p4-clockmod: Unknown
> p4-clockmod-capable CPU. Please send an e-mail to
> <cpufreq@lists.linux.org.uk>.
> My CPU is a Celeron M 530, that works "fine" (a little bit slowly !!) on
> Vista, but that doesn't get recognized yet, neither by p4-clockmod, nor
> by all the lm-sensors stuff. Laptops running this CPU (most "low cost
> long battery-life" recent laptops, in my case the Lenovn 3000 N200
> 0769-A42) will have to run with full speed CPU and sometimes overheat
> problems, for now).
>
> Hope my little report will help, best regards,
Something that new hopefully works with acpi-cpufreq instead of the ancient
and crappy p4-clockmod. Have you tried acpi-cpufreq instead?
--
Jarod Wilson
jwilson@redhat.com
prev parent reply other threads:[~2008-02-25 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 6:04 Unknown p4-clockmode capable CPU Emmanuel Andreu
2008-02-25 14:02 ` Jarod Wilson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802250902.01276.jwilson@redhat.com \
--to=jwilson@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=emmanuel.andreu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox