Please look at the title of the article you linked to… it says it defaults to “active”. And it has been defaulting to Active for all the versions of kernel 6.5 I have run, right up until I upgraded to 6.5.9-1, at which point it now is disabled by default and must be forced on.
I am assuming that this is a change made by the Manjaro team, and I am just trying to work out if the change was made for a reason or in error.
Thanks for the advice, but it’s not what I am trying to get addressed here.
I have been running P-State for a long time, since 5.9. With the release of 6.5 I was able to remove the kernel config and it defaulted to Active as expected, but the behaviour changed with the release of kernel 6.9.5-1.
I am trying to establish if this change was made by the Manjaro team because of a bug or other issue, or if it was disabled by mistake.
Yes it should, which is why I was surprised when it stopped working as expected.
My (probable) mistake was attributing the changed behaviour to the updated kernel, not to the firmware I applied recently, though I thought I had confirmed P-State was still working after I did the firmware update, however I am unsure enough that I now have to do a bunch of testing to confirm the root cause.
I am going to roll back my firmware and confirm that is the root cause. I’ll have to roll forward again to get the security fixes in the latest AGESA back, but I really should confirm that it’s the firmware and not actually a bug in the CPPC driver in the kernel. I am also going to roll back my kernel a couple of versions to confirm that they also don’t work with the latest motherboard firmware. If CPPC/P-State works with old kernels and the latest firmware it confirms the problem is in the kernel, however if CPPC/P-State works on all kernels with the old firmware it confirms the problem is in the firmware.
I remember when PCs where rather simple affairs and there weren’t so many things to go wrong and so much validation wasn’t needed. Ah well, ups and downs.
I will report back when I have had a chance to test and confirm where the fault is.