From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 91141] acpi-cpufreq cannot be loaded.
Date: Mon, 02 Mar 2015 03:09:34 +0000 [thread overview]
Message-ID: <bug-91141-12968-8htYi084r5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-91141-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=91141
--- Comment #11 from Zhang Rui <rui.zhang@intel.com> ---
(In reply to Brett Johnson from comment #9)
> The BIOS supports it and all is enabled.
I mean there is no BIOS support for acpi-cpufreq driver, i,e, the _PSS control
method.
> As I stated above, multiple P4's
> worked under the 2.6 kernels. Under p4-clockmod I can manually change the
> processor frequencies as seen by cpuinfo_cur_freq. Manual changes don't
> help, though. Since p4-clockmod isn't used anymore, does acpi-cpufreq
> support P4's? Or is there another kernel module supposed to do this?
Unlike bug #73781, which has _PSS method in BIOS and the problem can be fixed
in kernel, for your machine, you can only use p4-clockmod instead of
acpi-cpufreq driver, even in 3.x kernels.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-03-02 3:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 4:00 [Bug 91141] New: acpi-cpufreq cannot be loaded bugzilla-daemon
2015-01-12 4:24 ` [Bug 91141] " bugzilla-daemon
2015-01-12 4:38 ` bugzilla-daemon
2015-01-13 0:06 ` bugzilla-daemon
2015-01-13 0:08 ` bugzilla-daemon
2015-01-13 0:09 ` bugzilla-daemon
2015-01-13 0:09 ` bugzilla-daemon
2015-01-13 0:11 ` bugzilla-daemon
2015-01-13 0:45 ` bugzilla-daemon
2015-01-13 3:01 ` bugzilla-daemon
2015-01-21 1:47 ` bugzilla-daemon
2015-03-02 3:09 ` bugzilla-daemon [this message]
2015-04-16 1:54 ` bugzilla-daemon
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=bug-91141-12968-8htYi084r5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).