From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Core i7 M620 power management problem
Date: Thu, 30 Dec 2010 07:59:19 +0000 [thread overview]
Message-ID: <201012300759.32175.michaelkintzios@gmail.com> (raw)
In-Reply-To: <AANLkTimkMXNZGePNsF6hC9_38Cd0n6Rnrr9X1RArd3ax@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1659 bytes --]
On Thursday 30 December 2010 02:56:05 Bill Longman wrote:
> On Wed, Dec 29, 2010 at 4:22 PM, Paul Hartman
> <paul.hartman+gentoo@gmail.com<paul.hartman%2Bgentoo@gmail.com>
> > In my kernel config on my i7, in the cpufreq sections I have this:
> >
> > #
> > # CPU Frequency scaling
> > #
> > CONFIG_CPU_FREQ=y
> > CONFIG_CPU_FREQ_TABLE=y
> > # CONFIG_CPU_FREQ_DEBUG is not set
> > CONFIG_CPU_FREQ_STAT=y
> > # CONFIG_CPU_FREQ_STAT_DETAILS is not set
> > # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
> > # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> > CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
> > # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
> > CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
> > CONFIG_CPU_FREQ_GOV_POWERSAVE=y
> > CONFIG_CPU_FREQ_GOV_USERSPACE=y
> > CONFIG_CPU_FREQ_GOV_ONDEMAND=y
> > CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
> >
> > #
> > # CPUFreq processor drivers
> > #
> > # CONFIG_X86_PCC_CPUFREQ is not set
> > CONFIG_X86_ACPI_CPUFREQ=y
> > # CONFIG_X86_POWERNOW_K8 is not set
> > # CONFIG_X86_SPEEDSTEP_CENTRINO is not set
> > # CONFIG_X86_P4_CLOCKMOD is not set
> >
> >
> > I can send you my entire .config if you want to compare.
>
> Yes, mine is quite similar:
>
> # CPU Frequency scaling
> #
> CONFIG_CPU_FREQ=y
> CONFIG_CPU_FREQ_TABLE=y
> CONFIG_CPU_FREQ_DEBUG=y
> CONFIG_CPU_FREQ_STAT=y
> CONFIG_CPU_FREQ_STAT_DETAILS=y
> CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
> # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
Did you try changing the default to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND ?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-12-30 8:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 17:13 [gentoo-user] Core i7 M620 power management problem Bill Longman
2010-12-29 17:40 ` Paul Hartman
2010-12-29 18:35 ` Stefan G. Weichinger
2010-12-29 18:48 ` Bill Longman
2010-12-29 19:55 ` Stefan G. Weichinger
[not found] ` <AANLkTik3UmVwYwejLmV=trDN+W7443eY4yQRfn3=_m4e@mail.gmail.com>
2010-12-29 20:51 ` Bill Longman
2010-12-30 0:22 ` Paul Hartman
2010-12-30 2:56 ` Bill Longman
2010-12-30 7:59 ` Mick [this message]
2010-12-30 16:45 ` Bill Longman
2010-12-30 17:55 ` Mick
2010-12-30 18:13 ` Bill Longman
2010-12-30 0:43 ` Mick
2010-12-30 3:16 ` Bill Longman
2010-12-30 8:21 ` Mick
2010-12-30 17:10 ` Bill Longman
2010-12-30 8:59 ` Stefan G. Weichinger
2010-12-30 16:25 ` Bill Longman
2010-12-30 17:54 ` Bill Longman
2010-12-30 22:44 ` Stefan G. Weichinger
2010-12-31 1:22 ` Bill Longman
2010-12-31 10:59 ` Mick
2011-01-01 11:16 ` Stefan G. Weichinger
2011-01-01 20:10 ` Bill Longman
2011-01-01 23:50 ` Bill Longman
2011-01-02 0:34 ` Mick
2011-01-02 4:39 ` Bill Longman
2011-01-02 11:59 ` Mick
2010-12-30 3:51 ` Bill Longman
2010-12-29 19:57 ` Stefan G. Weichinger
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=201012300759.32175.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.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