[Bug 9851] New: cpufreq is not works with Intel Celeron 420

[Bug 9851] New: cpufreq is not works with Intel Celeron 420

[bugme-daemon]

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.

[Bug 9851] cpufreq is not works with Intel Celeron 420

[bugme-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=9851


protasnb@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |protasnb@gmail.com




------- Comment #1 from protasnb@gmail.com  2008-06-02 08:32 -------
Dmitry,
Can you provide dmesg and dmidecode with the failing processor?
Thanks.


-- 
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.