public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: S K <nospamnoham@gmail.com>
Cc: Zhao Yakui <yakui.zhao@intel.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Fri, 08 Aug 2008 09:41:34 +0100	[thread overview]
Message-ID: <489C06BE.2020309@tuffmail.co.uk> (raw)
In-Reply-To: <514e099a0808072153w2e944037gbfbdf8e9156d7df0@mail.gmail.com>

S K wrote:
> Hi,
>
> I already did the cpufreq.debug thing and it was using the
> smi_speedstep driver instread of the acpi_speedstep (or whatever is
> the right name).
>
> Alan already told me this is likely an ACPI issue. So, I already sent
> the acpidump in a prev email (Aug 3rd 08). I'm don't have access to my
> home machine right now. Will send it again later if you can't get my
> prev email from the archives.
>   

I could be completely wrong though!

I'd not heard of speedstep_smi before (now I look, it doesn't seem to be
an option in the cpu frequency scaling Kconfig menu?).

I assumed the error messages you had about SMI were just flack.  I
thought  acpi-cpufreq was the only option on recent machines - and that
a quad core  probably counts as recent.  The error messages could be due
to Fedora scripts unconditionally loading several different modules, to
find one that works.

I'm not sure how you can answer Zhao's question if you don't already
know.  I expect Fedora C7 does try loading acpi_cpufreq (as well as
speedstep_smi).  Whether your machine actually supports acpi_cpufreq is
the question we're trying to answer.  (This is where looking at Windows,
or BIOS settings, would help).

Alan

  reply	other threads:[~2008-08-08  8:41 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 10:00 cpufreq doesn't seem to work in Intel Q9300 S K
2008-08-03 10:31 ` none
2008-08-04  5:06   ` S K
2008-08-07  9:35     ` S K
2008-08-07 19:24       ` Alan Jenkins
2008-08-08  1:32       ` Zhao Yakui
2008-08-08  4:53         ` S K
2008-08-08  8:41           ` Alan Jenkins [this message]
2008-08-08 10:10             ` S K
2008-08-08 10:43               ` S K
2008-08-08 12:30                 ` Thomas Renninger
2008-08-08 18:23                   ` S K
2008-08-09 18:59                     ` Thomas Renninger
2008-08-09 19:30                       ` Thomas Renninger
2008-08-10  8:28                       ` S K
2008-08-11  1:33                         ` Zhao Yakui
2008-08-11  4:44                           ` S K
2008-08-11  5:24                             ` Zhao Yakui
2008-08-11  5:24                               ` S K
2008-08-11  7:00                                 ` Alan Cox
2008-08-11 10:55                               ` Andi Kleen
2008-08-11 13:15                                 ` S K
2008-08-11 13:23                                   ` Andi Kleen
2008-08-12  5:43                                     ` S K
2008-08-11 11:22                             ` Arjan van de Ven
2008-08-11 11:38                               ` Alexey Dobriyan
2008-08-11 11:53                                 ` Matthew Garrett
2008-08-11 14:02                               ` Adrian Bunk
2008-08-11 14:07                                 ` Matthew Garrett
2008-08-11 14:12                                   ` Arjan van de Ven
2008-08-11 14:11                                 ` Arjan van de Ven
2008-08-11 16:03                                   ` Adrian Bunk
2008-08-11 16:20                                     ` Arjan van de Ven
2008-08-11 16:28                                       ` Adrian Bunk
2008-08-11 16:44                                         ` Arjan van de Ven
2008-08-12 19:27                                           ` Adrian Bunk
2008-08-11 19:33                                   ` Dominik Brodowski
2008-08-11 23:58                                     ` Arjan van de Ven
2008-08-12 19:03                                       ` Dominik Brodowski
2008-08-12 19:59                                         ` Arjan van de Ven

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=489C06BE.2020309@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nospamnoham@gmail.com \
    --cc=yakui.zhao@intel.com \
    /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