All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sune Mølgaard" <sune@molgaard.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Frequency scaling, Dell Inspiron 6000
Date: Mon, 30 Jul 2007 15:26:24 +0200	[thread overview]
Message-ID: <46ADE700.6070400@molgaard.org> (raw)
In-Reply-To: <20070730004423.GA27398@srcf.ucam.org>

Matthew Garrett wrote:
> On Sun, Jul 29, 2007 at 04:03:31PM +0200, Sune Mølgaard wrote:
> 
>> The CPU of the machine is labeled as centrino compliant, but is in fact 
>> a Celeron-M, and hence does not support _Enhanced_ Speedstep. However, I 
>> clearly remember having frequency scaling working with Ubuntu kernel 
>> 2.6.15, but failing with Ubuntu 2.6.17 (possibly with some 2.6.18 code 
>> backported).
> 
> It doesn't support Speedstep at all. You were probably using p4-clockmod 
> in the past, which is a mechanism for temperature control rather than 
> any sort of useful power saving.

Hi Matthew, and thanks for answering,

This might be as you describe, as I don't know which module was used 
when it worked.

However, I got a warning dialogue window from the GNOME powernowd applet 
about frequency scaling being unavailable upon the kernel upgrade, not 
upon an upgrade of powernowd as one might suspect, if powernowd suddenly 
seized to support p4-clockmod.

If I had bought the laptop today and encountered the problems, I would 
probably reach the same conclusion as you, but IIRC powernowd doesn't 
cooperate with p4-clockmod, and it was a kernel upgrade that made it 
complain.

I stated earlier that I didn't recall if the BIOS or the kernel upgrade 
came first, but digging into my memory of events, plus my normal way of 
dealing with problems, I am now fairly sure that the kernel upgrade 
borked frequency scaling (or clockmod, which I still find unlikely), 
prompting the BIOS upgrade.

Best regards,

Sune Mølgaard

-- 
Men will wrangle for religion; write for it; fight for it; die for it; 
anything but live for it.
- Charles Caleb Colton
-
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:[~2007-07-30 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29 14:03 Frequency scaling, Dell Inspiron 6000 Sune Mølgaard
2007-07-30  0:44 ` Matthew Garrett
2007-07-30 13:26   ` Sune Mølgaard [this message]
2007-07-30 18:01     ` Matthew Garrett
2007-07-30 18:18       ` Sune Mølgaard
2007-07-30 18:22         ` Matthew Garrett
2007-07-30 18:32           ` Sune Mølgaard
2007-07-30 19:00             ` Matthew Garrett
2007-07-30 19:40               ` Sune Mølgaard

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=46ADE700.6070400@molgaard.org \
    --to=sune@molgaard.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.