public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 17:55:39 +0000	[thread overview]
Message-ID: <201012301755.51589.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4D1CB713.7050304@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1140 bytes --]

On Thursday 30 December 2010 16:45:07 Bill Longman wrote:
> On 12/29/2010 11:59 PM, Mick wrote:
> > Did you try changing the default to CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND
> > ?
> 
> Yes, Mick, that was my first governor. I thought I'd try to see if it
> would behave at top speed if I set it to "performance". No luck, though.
> And I can easily change the governor. It swaps out to any of the
> installed governors with aplomb, although I have to do this manually. I
> can't change governors from gkrellm, for instance. If I change it
> manually, the new governor shows up there, but it's read-only so to speak.

Is there a plugin for gkrellm that does governors?  Can't find it on mine.


> I don't know if the idle controller has anything to do with this but
> here is what my idle controller looks like:
> 
> /sys/devices/system/cpu/cpuidle
> 08:43:14# ls -l;cat current_*
> total 0
> -r--r--r-- 1 root root 4096 Dec 30 08:43 current_driver
> -r--r--r-- 1 root root 4096 Dec 30 08:43 current_governor_ro
> intel_idle
> menu

Although different CPU my cpuidle is exactly as shown above.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-12-30 18:10 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
2010-12-30 16:45                   ` Bill Longman
2010-12-30 17:55                     ` Mick [this message]
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=201012301755.51589.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