2.5.64 - cpu freq not turned on

2.5.64 - cpu freq not turned on

Post by CaT » Fri, 07 Mar 2003 17:30:23



There was a 2.5.x kernel that allowed me to use cpufreq with it but the
recent ones just give me this message:

cpufreq: Intel(R) SpeedStep(TM) for this chipset not (yet) available.

Now I know it worked before cos I noticed it and played about with the 8
speed steps I had available to me (and I thought I only had 2).

What information is needed about my chipset to make the code detect it
properly?

(not on cpufreq ml btw)

--
"Other countries of course, bear the same risk. But there's no doubt his
hatred is mainly directed at us. After all this is the guy who tried to
kill my dad."
        - George W. Bush Jr, 'President' of the United States
          September 26, 2002 (from a political fundraiser in Huston, Texas)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.64 - cpu freq not turned on

Post by Dominik Brodowsk » Sat, 08 Mar 2003 01:40:15


Hi,


> There was a 2.5.x kernel that allowed me to use cpufreq with it but the
> recent ones just give me this message:

> cpufreq: Intel(R) SpeedStep(TM) for this chipset not (yet) available.

> Now I know it worked before cos I noticed it and played about with the 8
> speed steps I had available to me (and I thought I only had 2).

Actually, SpeedStep is (so far, Banias isn't out to the public market yet)
only 2 states. What you had running was probably the p4-clockmod driver for
Intel Pentium 4 processors. But that does only throttle the CPU, which
causes (at best) linear energy saving while real "speedstep" is much better
than that. You can see what cpufreq driver is loaded by cat'ting
scaling_driver in the cpufreq sysfs directory for that cpu.

This directory moved in 2.5.64 - and that's why you probably think there was
some regression (in fact, there is, but patches to fix that are on their
way...) - the sysfs interface to cpufreq is now in
/sys/devices/sys/cpu0/cpufreq/          or
/sys/class/cpu/cpufreq/cpu0/cpufreq/

Quote:> What information is needed about my chipset to make the code detect it
> properly?

lspci -- maybe it's a ich4-m southbridge, then the attached patch (also sent to
Linus a few moments ago) might help.

        Dominik

diff -ruN linux-original/arch/i386/kernel/cpu/cpufreq/speedstep.c linux/arch/i386/kernel/cpu/cpufreq/speedstep.c
--- linux-original/arch/i386/kernel/cpu/cpufreq/speedstep.c     2003-03-06 21:56:18.000000000 +0100

 #include <asm/msr.h>

+#ifndef PCI_DEVICE_ID_INTEL_82801DB_12
+#define PCI_DEVICE_ID_INTEL_82801DB_12  0x24cc
+#endif

 /* speedstep_chipset:

 #define SPEEDSTEP_CHIPSET_ICH2M         0x00000002
 #define SPEEDSTEP_CHIPSET_ICH3M         0x00000003
-
+#define SPEEDSTEP_CHIPSET_ICH4M         0x00000004

 /* speedstep_processor

        switch (speedstep_chipset) {
        case SPEEDSTEP_CHIPSET_ICH2M:
        case SPEEDSTEP_CHIPSET_ICH3M:
+       case SPEEDSTEP_CHIPSET_ICH4M:
                /* get PMBASE */
                pci_read_config_dword(speedstep_chipset_dev, 0x40, &pmbase);

        switch (speedstep_chipset) {
        case SPEEDSTEP_CHIPSET_ICH2M:
        case SPEEDSTEP_CHIPSET_ICH3M:
+       case SPEEDSTEP_CHIPSET_ICH4M:
                /* get PMBASE */
                pci_read_config_dword(speedstep_chipset_dev, 0x40, &pmbase);

        switch (speedstep_chipset) {
        case SPEEDSTEP_CHIPSET_ICH2M:
        case SPEEDSTEP_CHIPSET_ICH3M:
+       case SPEEDSTEP_CHIPSET_ICH4M:
        {
                u16             value = 0;

 static unsigned int speedstep_detect_chipset (void)
 {
        speedstep_chipset_dev = pci_find_subsys(PCI_VENDOR_ID_INTEL,
+                             PCI_DEVICE_ID_INTEL_82801DB_12,
+                             PCI_ANY_ID,
+                             PCI_ANY_ID,
+                             NULL);
+       if (speedstep_chipset_dev)
+               return SPEEDSTEP_CHIPSET_ICH4M;
+
+       speedstep_chipset_dev = pci_find_subsys(PCI_VENDOR_ID_INTEL,
                              PCI_DEVICE_ID_INTEL_82801CA_12,
                              PCI_ANY_ID,
                              PCI_ANY_ID,
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.64 - cpu freq not turned on

Post by CaT » Sat, 08 Mar 2003 02:30:11



> > Now I know it worked before cos I noticed it and played about with the 8
> > speed steps I had available to me (and I thought I only had 2).

> Actually, SpeedStep is (so far, Banias isn't out to the public market yet)
> only 2 states. What you had running was probably the p4-clockmod driver for
> Intel Pentium 4 processors. But that does only throttle the CPU, which

Ahhh. I have a P3 though.

Quote:> causes (at best) linear energy saving while real "speedstep" is much better
> than that. You can see what cpufreq driver is loaded by cat'ting
> scaling_driver in the cpufreq sysfs directory for that cpu.

Not there.

Quote:> This directory moved in 2.5.64 - and that's why you probably think there was
> some regression (in fact, there is, but patches to fix that are on their
> way...) - the sysfs interface to cpufreq is now in

2.5.63 doesn't turn speedstep on for me either.

Quote:> > What information is needed about my chipset to make the code detect it
> > properly?

> lspci -- maybe it's a ich4-m southbridge, then the attached patch
> (also sent to Linus a few moments ago) might help.

Didn't apply the patch cos I don't see that in the lspci output:

00:00.0 Host bridge: Intel Corp. 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
00:07.0 Bridge: Intel Corp. 82371AB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 03)

The rest are sound, cardbus etc.

--
"Other countries of course, bear the same risk. But there's no doubt his
hatred is mainly directed at us. After all this is the guy who tried to
kill my dad."
        - George W. Bush Jr, 'President' of the United States
          September 26, 2002 (from a political fundraiser in Huston, Texas)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.64 - cpu freq not turned on

Post by Ducrot Brun » Sat, 08 Mar 2003 13:30:11



> Didn't apply the patch cos I don't see that in the lspci output:

> 00:00.0 Host bridge: Intel Corp. 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
> 00:01.0 PCI bridge: Intel Corp. 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
> 00:07.0 Bridge: Intel Corp. 82371AB PIIX4 ISA (rev 02)
> 00:07.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01)
> 00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01)
> 00:07.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 03)

PIIX4EM southbridges are still in reverse-engeenering process.

Im also wondering why Intel still make this old stuff under NDA?

Cheers,

--
Ducrot Bruno
http://www.poupinou.org        Page profaissionelle
http://toto.tu-me-saoules.com  Haume page
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. [2.5.64] kexec for 2.5.64 available

Eric,

I have a patch set available for kexec for 2.5.64.  I haved checked it
on a 1-way system, the 2-way test is pending an fsck of a partition that
was unfortunately eaten earlier today.

The patches are available for download from OSDL's patch lifecycle
manager (PLM):

Patch Stack for kexec for 2.5.64:

        kexec base for 2.5.64 (based upon 2.5.63 version)
        http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1656

        kexec hwfixes for 2.5.64 (based upon 2.5.63 version)
        http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1657

        kexec usemm change (allowed 2-way to previously work for me):
        http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1658

        optional change to defconfig to CONFIG_KEXEC=y
        http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1659

The patches are also available (with matching kexec-tools-1.8 --
unchanged from the 2.5.63 version) here:
http://www.osdl.org/archive/andyp/kexec/2.5.64/

Regards,
Andy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. IBM selling Pre-loaded Linux desktops

3. 2.5.64-mm4 looking good (Re: Oops in 2.5.64bk3)

4. ftp options

5. Oops: 2.5.64 check_obj_poison for 'size-64'

6. IPMASQ! RAM & UART, do they matter?

7. nanosleep() granularity bumps up in 2.5.64 (was: [PATCH] settimeofday() not synchronised with gettimeofday())

8. What NFS speeds can I expect?

9. [BUG] nanosleep() granularity bumps up in 2.5.64 (was: [PATCH] settimeofday() not synchronised with gettimeofday())

10. Complete support PC-9800 for 2.5.64-ac4 (11/11) SCSI

11. (0/5) Brlock removal (2.5.64)

12. 2.5.64: nfs module unknown symbols

13. 2.5.64-mm2->4 hangs on contest