Modprobe of cpufreq modules fails

Modprobe of cpufreq modules fails

[Uli Brueggemann]

Hi,

I'm running a Core 2 Duo system. With different kernels (up to 2.6.23.1 or
2.6.24-rc2) I cannot modprobe acpi_cpufreq or speedsteep-centrino or ...
So I always get the report "no such device".

Kernel configuration:

CONFIG_ACPI=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROC_EVENT=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_DOCK=m
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_FUJ02B1 is not set
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=m
CONFIG_ACPI_SBS=m

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
# CONFIG_CPU_FREQ_DEBUG is not set
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

(I've also tried ondemand or userspace)

According to dmesg there should be no problem:

Initializing CPU#0
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000
0000e3bd 00000000 00000001 00000000
monitor/mwait feature present.
using mwait in idle threads.
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0000e3bd
00000000 00000001 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... disabled
Freeing SMP alternatives: 8k freed
ACPI: Core revision 20070126
CPU0: Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz stepping 02
Booting processor 1/1 eip 2000
Initializing CPU#1
Calibrating delay using timer specific routine.. 4246.30 BogoMIPS
(lpj=212315)
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000
0000e3bd 00000000 00000001 00000000
monitor/mwait feature present.
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0000e3bd
00000000 00000001 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz stepping 02
Total of 2 processors activated (8496.22 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs

Can someone help?

Best

Uli

Re: Modprobe of cpufreq modules fails

[Jarod Wilson]

[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]

Uli Brueggemann wrote:
> I'm running a Core 2 Duo system. With different kernels (up to 2.6.23.1 or
> 2.6.24-rc2) I cannot modprobe acpi_cpufreq or speedsteep-centrino or ...
> So I always get the report "no such device".

You definitely want acpi-cpufreq, not speedstep-centrino... The 'no such
device' message usually indicates that upon querying your BIOS ACPI
tables, acpi-cpufreq found no valid frequency scaling information, which
suggests either freq scaling is disabled in the BIOS or your BIOS has
busted ACPI (in which case a newer BIOS for your board, if available,
might help).

Also, you can boot with the added parameter 'cpufreq.debug=7' to get a
bit more info spit out in dmesg about what's going on when you try to
load acpi-cpufreq. Could give some further insight into what went wrong
and/or verify what I suggested above.

-- 
Jarod Wilson
jwilson@redhat.com



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

[-- Attachment #2: Type: text/plain, Size: 147 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq

Modprobe of cpufreq modules fails

[Uli Brueggemann]

Hi Jarod,

thanks for your answer. I start to understand a bit.

Anyway cpufreq.debug=7 leads to

cpufreq-core: trying to register driver acpi-cpufreq
cpufreq-core: adding CPU 0
cpufreq-core: initialization failed
cpufreq-core: adding CPU 1
cpufreq-core: initialization failed
cpufreq-core: no CPU initialized for driver acpi-cpufreq
cpufreq-core: unregistering CPU 0
cpufreq-core: unregistering CPU 1

So it seems that the mainboard (Jetway) is not the right one. I have not
found any BIOS setting which would help. Also the latest BIOS update has not
solved the problem. Why does the initialization fail? Any other reason?

So this finally leads to my question: how to detect the right mainboard/BIOS
before buying?

Uli



On Nov 12, 2007 4:04 PM, Jarod Wilson < jwilson@redhat.com> wrote:

> Uli Brueggemann wrote:
> > I'm running a Core 2 Duo system. With different kernels (up to 2.6.23.1or
> > 2.6.24-rc2) I cannot modprobe acpi_cpufreq or speedsteep-centrino or ...
> > So I always get the report "no such device".
>
> You definitely want acpi-cpufreq, not speedstep-centrino... The 'no such
> device' message usually indicates that upon querying your BIOS ACPI
> tables, acpi-cpufreq found no valid frequency scaling information, which
> suggests either freq scaling is disabled in the BIOS or your BIOS has
> busted ACPI (in which case a newer BIOS for your board, if available,
> might help).
>
> Also, you can boot with the added parameter 'cpufreq.debug=7' to get a
> bit more info spit out in dmesg about what's going on when you try to
> load acpi-cpufreq. Could give some further insight into what went wrong
> and/or verify what I suggested above.
>
> --
> Jarod Wilson
> jwilson@redhat.com
>
>
>