public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: cpufreq@lists.linux.org.uk
Cc: "Alex Villací­s Lasso" <avillaci@ceibo.fiec.espol.edu.ec>,
	linux-acpi@vger.kernel.org
Subject: Re: About p4-clockmod breakage/removal
Date: Tue, 13 May 2008 20:48:00 -0400	[thread overview]
Message-ID: <200805132048.00653.lenb@kernel.org> (raw)
In-Reply-To: <48246C3E.7010608@ceibo.fiec.espol.edu.ec>

On Friday 09 May 2008, Alex Villací­s Lasso wrote:
> In a somewhat old computer I use at home, I have a Pentium 4 CPU running 
> at 1.7GHz. On this computer, acpi-cpufreq does not work (modprobe fails 
> with -ENODEV), only p4-clockmod. Lately this means I have to compile my 
> own kernel to get speed throttling on my computer.
> 
> Recently, patch ed9cbcd40004904dbe61ccc16d6106a7de38c998 (Revert 
> "speedstep-lib.c: fix frequency multiplier for Pentium4 models 0&1") 
> broke clock speed reporting. It now reports I have a max speed of 13.80 
> GHz instead of 1.7GHz. I only wish my CPU were that fast... Reverting 
> this patch fixes the problem for me. However, since I suscribed 
> yesterday to this list, I see talk about removing p4-clockmod altogether 
> from the tree. Maybe my real problem is that acpi-cpufreq does not work 
> even though it should, but I have yet to find a way to make the module 
> print the information that is supposed to be displayed through dprintk() 
> messages. What else can I do to debug acpi-cpufreq on my machine?

Assuming this is a laptop with a batter,
I'd certainly be interested if you could run BLTK
and measure any benefit to p4-clockmod (I've never
been able to)

http://www.lesswatts.org/projects/bltk/

Re: acpi-cpufreq
Verify that you're running the latest BIOS,
and look in BIOS SETUP for any options related
to CPU power management, Speed Step, EIST, P-states etc,
and enable if present.

If that doesn't do it, then open a bug here
complaining that acpi-cpufreq doesn't load:

http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI

and attach the output from acpidump -- which will tell
us if the underlying BIOS support is present.
My guess is that it is not.

-Len

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2008-05-14  0:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48246C3E.7010608@ceibo.fiec.espol.edu.ec>
2008-05-14  0:48 ` Len Brown [this message]
2008-05-14  0:56   ` About p4-clockmod breakage/removal Matthew Garrett
2008-05-14  3:35     ` Len Brown
2008-05-14  9:15       ` Matthew Garrett
2008-05-14 15:18         ` Len Brown
2008-05-14 23:11           ` Matthew Garrett
2008-05-14 11:18     ` Pavel Troller
2008-05-14 17:22       ` Len Brown
2008-05-15  1:55         ` Henrique de Moraes Holschuh
2008-05-14 11:36     ` Thomas Renninger
2008-05-14 11:42       ` Matthew Garrett
2008-05-14 12:49         ` Thomas Renninger
2008-05-14 12:56           ` Matthew Garrett
2008-05-14 15:28         ` Len Brown

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=200805132048.00653.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=avillaci@ceibo.fiec.espol.edu.ec \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=linux-acpi@vger.kernel.org \
    /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