Powernow-k8 bios error no psb

powernow-k8 bios error no psb

powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version ) powernow-k8: BIOS error - no PSB or ACPI _PSS objects. (c) Advanced Micro Devices, Inc. * Your use of this code is "No PSB or ACPI _PSS objects\n"); pr_err("Make sure that your BIOS is up to date. PSB BIOS structure" error from the powernow-k8 module.. I'm guessing I'm at the mercy of MSI for a BIOS update but I'm doubtful I'll get one.

Thematic video

Computer Can't Enter BIOS? - How to Force It

Powernow-k8 bios error no psb - congratulate

powernow-k8: BIOS error - no PSB

Joined
Aug 15,
Messages
5,
Rumors has it that the linux kernel hasn't sorted this one properly out yet .
So i will not blame it on the bios just yet since it works with windows systems.

PSB is Power State Block that BIOS sends through ACPI to a processor driver that
supports Cool n Quiet or AMD Powernow for cpuspeed transistion by means of
p-state registers .
P-States (processor performance states), each of which represents a combination
of processor voltage and frequency. PST is the table of all the p-states supported.

AMD's PowerNow CnQ enabled software/driver has to be installed on systems
The software/driver receives a Performance State Block (PSB) from the
motherboard BIOS.
The PSB is nothing more than information about the supported P-States of the
processor in use.

Current windows operating systems actually support the P-States and only require
a small extra driver that handles the transition from one P-State to the next.
To do that, it takes an ACPI compliant P-State object from the BIOS containing all
the necessary information on supported and possible P-States.

P-State transition always occurs in three steps:
first, the voltage is adjusted to accommodate the change in clock speed.
Then the speed is adjusted.
Finally, the voltage is adjusted to the speed defined in the respective P-State.

Do you have Cool and Quiet preoperly enabled in the bios ??
Looks like there is two options here
BIOS is not sending the PSB
or your linux kernel cpudriver doesnt translate it or see it coming .

My 2 cents worth..
-- this is the version of the PCC specification the driver adheres to The following is a brief discussion on some of the fields exported via the /sys filesystem and how their values are affected by the PCC driver: scaling_available_frequencies: scaling_available_frequencies is not created in /sys. No intermediate frequencies need to be listed because the BIOS will try to achieve any frequency, within limits, requested by the governor. A frequency does not have to be strictly associated with a P-state. cpuinfo_transition_latency: The cpuinfo_transition_latency field is 0. The PCC specification does not include a field to expose this value currently. cpuinfo_cur_freq: A) Often cpuinfo_cur_freq will show a value different than what is declared in the scaling_available_frequencies or scaling_cur_freq, or scaling_max_freq. This is due to "turbo boost" available on recent Intel processors. If certain conditions are met the BIOS can achieve a slightly higher speed than requested by OSPM. An example: scaling_cur_freq : cpuinfo_cur_freq : B) There is a round-off error associated with the cpuinfo_cur_freq value. Since the driver obtains the current frequency as a "percentage" (%) of the nominal frequency from the BIOS, sometimes, the values displayed by scaling_cur_freq and cpuinfo_cur_freq may not match. An example: scaling_cur_freq : cpuinfo_cur_freq : In this example, the nominal frequency is MHz. The driver obtains the current frequency, cpuinfo_cur_freq, as 54% of the nominal frequency: 54% of MHz = MHz Nominal frequency is the maximum frequency of the processor, and it usually corresponds to the frequency of the P0 P-state. related_cpus: The related_cpus field is identical to affected_cpus. affected_cpus : 4 related_cpus : 4 Currently, the PCC driver does not evaluate _PSD. The platforms that support PCC do not implement SW_ALL. So OSPM doesn't need to perform any coordination to ensure that the same frequency is requested of all dependent CPUs. 3. Caveats: The "cpufreq_stats" module in its present form cannot be loaded and expected to work with the PCC driver. Since the "cpufreq_stats" module provides information wrt each P-state, it is not applicable to the PCC driver.