How Well Is AMD CnQ Working For You On Linux?
Phoronix: How Well Is AMD CnQ Working For You On Linux?
One of the latest possible Linux power-related regressions I've heard about is that AMD Cool 'n' Quiet may no longer be functioning too well on Linux-based systems...
The only device with an AMD processor that I have right now is a Brazos-based netbook, and it doesn't seem to have any power management issues. If anything, it exceeds the specifications. I didn't check the power management when CnQ was disabled, though.
That said, isn't CnQ/EIST losing is relevance lately, in light of ACPI processor (C) states? If nothing is using resources, it just goes to complete sleep by itself. No need to change the frequency, so there is no performance loss.
asus f1a75-M pro
I have a f1a75-M pro in combination with AMD's A8-3870K and after enabling the powernow or any other power saving function in bios the system will locks up. No idea if this is due to the hardware or linux.
If PowerNow leads to lockups, this is almost certainly a hardware or BIOS issue. On K10 and later CPU generations, p-state transitioning is done in hardware, so there's little chance for any driver to screw up.
Originally Posted by mard0
PowerNow really did suck on K8 generation CPUs, but it's great on later CPUs.
I got the impression C'n'Q is and always has been a BIOS related thing, not OS, so i don't see why linux wouldn't use it. I guess depending on how you load the CPU, other OSes compared to windows might not use it as effectively but in the end, its how much power your system draws when idle that matters most.
I really do suspect that AMD will find a way to get proper powersaving out for their GPUs. Now that they are putting them onto the same die with the CPU, having them run on full blast all the time (and thus negating nearly all powersaving done by the CPU) is a big problem.
Originally Posted by 0xBADCODE
Since these APUs were one of the driving forces behind releasing documentation and OSS drivers (the way I undestand it, at least), having them not work properly is not a good way to proceed. So I'm guessing that proper powersaving (already written) will be released once the technical review is done.
It's really not, at least not entirely. What the BIOS needs to do for PowerNow/CnQ to work is fill the p-state table in the CPU's model-specific registers, and that's it. This table contain values for operating frequency, voltage, etc. for all states. The OS requires a driver that reads the table and instructs the CPU to switch to a certain state, depending on load, according to some governor. (BTW, if the BIOS fails to set up the p-state table correctly, you can do that from userspace before loading PowerNow drivers.) The transition between states is handled by the CPU itself, so the driver is quite simple.
Originally Posted by schmidtbag
Earlier on K8, the driver also needed to accurately do and time all the nitty-gritty low-level details of transitioning between states, and this was quite error-prone, depending on hardware.
Last edited by brent; 10-28-2012 at 12:15 PM.
I just upgraded my kernel from 3.6 to 3.7-rc3 and wondered why CnQ stopped working at all, so I looked into the boot messages and found:
powernow-k8: this CPU is not supported anymore, using acpi-cpufreq instead.
As I didn't had acpi-cpufreq compiled into the kernel the issue was found.
Not sure if I would call that a bad thing through. CPU is:
model name : AMD Athlon(tm) II X3 455 Processor
Hi brent I stumbled upon your post while searching the web for a way to fix a problem with my Laptop. I've got a MEDION E1312 with an AMD Sempron 210U and I'm using PeppermintOS 4 based on Ubuntu Kernel 126.96.36.199-generic.
Originally Posted by brent
There are no BIOS Updates availlable from OEM and with my computer your mentioned situation fits my Problem: "BIOS fails to set up the p-state table correctly".
So how do I setup p-states via userspace? Thanx in advance.