ACPI / cpufreq on Presario R3120
I've got a Presario with an AMD XP-M 3000+ CPU (a 32-bit K8). I can't get the acpi or powernow-k8 modules to load on the 2.6.6 kernel; loading acpi gives this message:
Quoted 1 line
acpi_processor_perf-0301 [1219]
acpi_cpufreq_cpu_init: Unsupported
address space [127, 127]
and powernow-k8 (with and without Pavel's patches) gives this:
Quoted 1 line
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version
1.20.08b - March 20, 2004)
Quoted 2 lines
powernow-k8: Too many lo freq table entries
powernow-k8: BIOS error - no PSB
I dumped the DSDT but it doesn't seem to have much info on the CPU.
The applicable section in my .config file is:
#
# CPU Frequency scaling
#CONFIG_CPU_FREQ=y
# CONFIG_CPU_FREQ_PROC_INTF is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m
# CONFIG_CPU_FREQ_24_API is not set CONFIG_CPU_FREQ_TABLE=m
#
# CPUFreq processor drivers
#CONFIG_X86_ACPI_CPUFREQ=m
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_X86_POWERNOW_K6 is not set
# CONFIG_X86_POWERNOW_K7 is not setCONFIG_X86_POWERNOW_K8=m
# CONFIG_X86_GX_SUSPMOD is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_SPEEDSTEP_ICH is not set
# CONFIG_X86_SPEEDSTEP_SMI is not set
# CONFIG_X86_P4_CLOCKMOD is not set
# CONFIG_X86_LONGRUN is not set
# CONFIG_X86_LONGHAUL is not set
Any suggestions where I should look? I'm not sure if it's a APCI or cpufreq issue -- Ken
Hi,
Quoted 1 line · Ken Hughes
I've got a Presario with an AMD XP-M 3000+ CPU (a 32-bit K8).
You have a AMD64 ?
Quoted 12 lines
I can't get the acpi or powernow-k8 modules to load on the 2.6.6 kernel; loading acpi gives this message:
Quoted 1 line
acpi_processor_perf-0301 [1219]
acpi_cpufreq_cpu_init: Unsupportedaddress space [127, 127]
and powernow-k8 (with and without Pavel's patches) gives this:
Quoted 1 line
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version
1.20.08b - March 20, 2004)
Quoted 2 lines
powernow-k8: Too many lo freq table entries
powernow-k8: BIOS error - no PSB
Then it's AMD64, not an XP-M (or else powernow-k8 would not print that it found a AMD64 or an Opteron I believe).
To be sure, what say /proc/cpuinfo ?
Going back to your problem, can you send to me an acpidmp output, or post a link to it?
wget ftp://ftp.kernel.org//pub/linux/kernel/people/lenb/acpi/utils/pmtools-20031210.tar.bz2 tar xjvfp pmtools-20031210.tar.bz2
cd pmtools-20031210/acpidmp
make
sudo ./acpidmp > acpidmp.out
bzip2 acpidmp.out
Quoted 1 line
I dumped the DSDT but it doesn't seem to have much info on the CPU.
This may be on another ACPI table, likely in SSDT.
Cheers,
Signature · 4 lines
Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.
Quoted 8 lines · Bruno Ducrot
Hi,
Quoted 1 line · Ken Hughes
I've got a Presario with an AMD XP-M 3000+ CPU (a 32-bit K8).
You have a AMD64 ?
.....
Quoted 10 lines
Quoted 5 lines
Quoted 2 lines
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version
1.20.08b - March 20, 2004)
Quoted 2 lines
powernow-k8: Too many lo freq table entries
powernow-k8: BIOS error - no PSBThen it's AMD64, not an XP-M (or else powernow-k8 would not print that it found a AMD64 or an Opteron I believe).
To be sure, what say
/proc/cpuinfo?
It's an AMD64/K8 core, but 32-bit only:
http://www.theinquirer.net/?article=14578
# cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 4 model name : AMD Athlon(tm) XP Processor 3000+ stepping : 8 cpu MHz : 797.944 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext 3dnowext 3dnow bogomips : 1576.96
Quoted 1 line
Going back to your problem, can you send to me an acpidmp output?
Attached.
Quoted 3 lines
Quoted 1 line
I dumped the DSDT but it doesn't seem to have much info on the CPU.
This may be on another ACPI table, likely in SSDT.
It's in the SSDT probably.
Ken
_______________________________________________
Cpufreq mailing list
[email protected]
http://www.linux.org.uk/mailman/listinfo/cpufreq
Quoted 16 lines · Ken Hughes
Quoted 8 lines · Bruno Ducrot
Hi,
Quoted 1 line · Ken Hughes
I've got a Presario with an AMD XP-M 3000+ CPU (a 32-bit K8).
You have a AMD64 ?
.....
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version
1.20.08b - March 20, 2004)
Quoted 2 lines
powernow-k8: Too many lo freq table entries
powernow-k8: BIOS error - no PSB
Quoted 7 lines
Quoted 4 lines
Then it's AMD64, not an XP-M (or else powernow-k8 would not print that it found a AMD64 or an Opteron I believe).
To be sure, what say
/proc/cpuinfo?It's an AMD64/K8 core, but 32-bit only:
http://www.theinquirer.net/?article=14578
What's that? Will look at amd site then.
Ok, you have that in a SSDT :
Name (_PSS, Package (0x03)
{
Package (0x06)
{
0x00000640,
0x0000F230,
0x00000064,
0x00000006,
0xE0202988,
0x00000188
},
Package (0x06)
{
0x00000320,
0x000032C8,
0x00000064,
0x00000006,
0xE0202E00,
0x00000600
},
Package (0x06)
{
0x00000320,
0x000032C8,
0x00000064,
0x00000006,
0xE0202E00,
0x00000600
}
})The last two states are *exactly* the same. Then powernow-k8 complains that there is 2 low states (which is not supported, as Paul will tell us). Then the driver fail.
Cheers,
Signature · 4 lines
Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.
Quoted 23 lines · Bruno Ducrot
Package (0x06)
{
0x00000320,
0x000032C8,
0x00000064,
0x00000006,
0xE0202E00,
0x00000600
},
Package (0x06)
{
0x00000320,
0x000032C8,
0x00000064,
0x00000006,
0xE0202E00,
0x00000600
}
})Quoted 3 lines
The last two states are *exactly* the same. Then powernow-k8 complains that there is 2 low states (which is not supported, as Paul will tell us). Then the driver fail.
We could kludge around this by doing a compare of the tables before we abort, and if they are the same, just ignore one of them. If it differs, we do what we do now.
Ideally, this should be fixed in a BIOS update though, or alternatively an ACPI fallback.
Paul ?
Dave