From mboxrd@z Thu Jan 1 00:00:00 1970 From: "W. Brown" Subject: Re: speedstep won't load even with acpi tables Date: Tue, 05 Oct 2004 19:12:59 -0400 Sender: cpufreq-bounces@www.linux.org.uk Message-ID: <41632A7B.5080508@comcast.net> References: <4162DCE2.4030008@comcast.net> <1097011299.4909.11.camel@localhost> <20041005215350.GA1299@dominikbrodowski.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20041005215350.GA1299@dominikbrodowski.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk Content-Type: text/plain; charset="us-ascii"; format="flowed" To: cpufreq@www.linux.org.uk 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 which says to configure: 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 > > >