From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9851] New: cpufreq is not works with Intel Celeron 420
Date: Wed, 30 Jan 2008 07:05:10 -0800 (PST) [thread overview]
Message-ID: <bug-9851-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=9851
Summary: cpufreq is not works with Intel Celeron 420
Product: Power Management
Version: 2.5
KernelVersion: 2.6.24
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: sanarin@nikiet.ru
Hardware Environment: Intel G33 chipset, Intel Celeron 420
Problem Description: I got Intel G33-based motherboard and 2 processors - Intel
Core 2 Duo E6300 and Intel Celeron 420. Then I put E6300 into motherboard,
cpufreq works fine. But with Celeron 420 and same hardware ans software,
spufreq is not works. I tried ACPI Processor P-States driver and Pentium 4
clock modulation driver. Both drivers are not works with Celeron 420. If I use
p4-clockmod, I got following message : "Unknown p4-clockmod-capable CPU. Please
send an e-mail to <cpufreq@lists.linux.org.uk>". ACPI Processor P-States driver
simple not works. No any error messages.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-01-30 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 15:05 bugme-daemon [this message]
2008-06-02 15:32 ` [Bug 9851] cpufreq is not works with Intel Celeron 420 bugme-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-9851-3570@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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.