From: "S K" <nospamnoham@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Zhao Yakui" <yakui.zhao@intel.com>,
"Thomas Renninger" <trenn@suse.de>,
"Alan Jenkins" <alan-jenkins@tuffmail.co.uk>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Mon, 11 Aug 2008 22:43:38 -0700 [thread overview]
Message-ID: <514e099a0808112243r78a79e3ck19a1440962b5cb0@mail.gmail.com> (raw)
In-Reply-To: <20080811132332.GR9038@one.firstfloor.org>
Wow! Didn't mean to start a "tech war" here (point's at the long
thread arguing the use of p4-clockmod).
>> It works in Windows XP, so I'm not sure if it's only a BIOS issue.
>
> On Windows platform drivers sometimes provide a replacement DSDT
> that might enable cpufreq. If that's the case there's nothing
> we can do really on the Linux side. You might be able to extract
> that DSDT from somewhere and supply it to Linux as a replacement
> DSDT, but that's not a supported configuration in the kernel.
I don't remember installing any special driver for Windows XP.
Since you claim that as a possibility, is there something that I can look
for to check if this is the case?
The reason I'm questioning this so much is because I plan to contact
Shuttle tech support and try to get them to fix this if it really is a BIOS
issue. But I need valid points to make sure they don't pass on the
blame and slip away. They do seem to release BIOS updates now and then
so I'm hoping I can coax them to release one.
>> If it's not that simple, then care to impart some knowledge?
>
> If you can't get your BIOS to provide the necessary methods
> then useful Linux cpufreq won't work. It's that simple.
> p4-clockmod aka throttling might work, but it doesn't actually
> save energy and often causes severe performance problems.
I definitely don't want to use anything that will have a drastic
effect on performance.
Thanks,
SK
next prev parent reply other threads:[~2008-08-12 5:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 10:00 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
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 [this message]
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=514e099a0808112243r78a79e3ck19a1440962b5cb0@mail.gmail.com \
--to=nospamnoham@gmail.com \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=andi@firstfloor.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
--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
all inboxes | Powered by JetHome®