From: "S K" <nospamnoham@gmail.com>
To: "Zhao Yakui" <yakui.zhao@intel.com>
Cc: "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: Sun, 10 Aug 2008 21:44:50 -0700 [thread overview]
Message-ID: <514e099a0808102144n241c8e9ak255bded0a80744f1@mail.gmail.com> (raw)
In-Reply-To: <1218418431.6671.52.camel@yakui_zhao.sh.intel.com>
>> So I'm guessing this is a kernel bug.
> >From the attached acpidump it seems that there is no definition of
> _PCT,_PSS, _PPC. So acpi_cpufreq driver can't be used on your machine.
> This is a BIOS issue.
Yakui, Did you actually check if the above was true?
>
> But it is very strange that cpufreq scaling can work on Windows XP.
> Will you please try the P4 clock cpufreq driver and see whether the
> scaling can work ? In fact P4 clock cpufreq driver is already replaced
> by acpi_cpufreq driver for the latest cpu.
> Anyway please try p4 clock cpufreq driver.
What is the name of the driver? I'm not able to find any such driver
in Fedora 9 installed modules. There is only acpi-cpufreq and powernow-k8.
Also, If someone doesn't mind, can they tell me what all files I need to
replace in Fedora 9 once I get a kernel.org kernel compiled? I know
how to edit grub.conf,
and that I should replace vmlinuz, but do I need to replace initrd too?
Thanks,
SK
next prev parent reply other threads:[~2008-08-11 4:45 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 [this message]
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=514e099a0808102144n241c8e9ak255bded0a80744f1@mail.gmail.com \
--to=nospamnoham@gmail.com \
--cc=alan-jenkins@tuffmail.co.uk \
--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®