From: "W. Brown" <wbrownab@comcast.net>
To: cpufreq@www.linux.org.uk
Subject: Re: speedstep won't load even with acpi tables
Date: Tue, 05 Oct 2004 19:12:59 -0400 [thread overview]
Message-ID: <41632A7B.5080508@comcast.net> (raw)
In-Reply-To: <20041005215350.GA1299@dominikbrodowski.de>
Ah, thanks Dominik, that was an easy fix.
I incorrectly assumed that that was a helper for the cpu specific
module. I was going by the Gentoo Power management guide
<http://www.gentoo.org/doc/en/power-management-guide.xml> which says to
configure:
<M> ACPI Processor P-States driver
and
<*> CPUFreq driver for your processor
It goes on to say...
"Compile your kernel, make sure the right modules get loaded at startup
and boot into your new ACPI-enabled kernel." They didn't explain what
the "right modules" are though. My bad.
Will
Dominik Brodowski wrote:
>Hi,
>
>You already got speedstep up and running using the ACPI cpufreq driver:
>
>
>
>>>acpi 4684 0 - Live 0xe09cc000
>>>
>>>
>
>
>
>>>CONFIG_X86_ACPI_CPUFREQ=m
>>>
>>>
>
>
>
>>>#cpu
>>>non-fatal
>>>acpi
>>>
>>>
>
>you load it _before_ speedstep-centrino, even. disabling it should allow you
>to load the (faster) speedstep-centrino module...
>
>
>
>>>Oct 5 12:30:29 shake cpufreq: CPU0 - ACPI performance management activated.
>>>Oct 5 12:30:29 shake cpufreq: *P0: 1700 MHz, 21000 mW, 100 uS
>>>Oct 5 12:30:29 shake cpufreq: P1: 1400 MHz, 17500 mW, 100 uS
>>>Oct 5 12:30:29 shake cpufreq: P2: 1200 MHz, 15000 mW, 100 uS
>>>Oct 5 12:30:29 shake cpufreq: P3: 1000 MHz, 12500 mW, 100 uS
>>>Oct 5 12:30:29 shake cpufreq: P4: 800 MHz, 10000 mW, 100 uS
>>>Oct 5 12:30:29 shake cpufreq: P5: 600 MHz, 7500 mW, 100 uS
>>>
>>>
>
>... with which you should get 10uS latencies instead of 100 uS.
>
> Dominik
>
>
>
prev parent reply other threads:[~2004-10-05 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4162DCE2.4030008@comcast.net>
2004-10-05 21:21 ` speedstep won't load even with acpi tables Jeremy Fitzhardinge
2004-10-05 21:53 ` Dominik Brodowski
2004-10-05 23:12 ` W. Brown [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=41632A7B.5080508@comcast.net \
--to=wbrownab@comcast.net \
--cc=cpufreq@www.linux.org.uk \
/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