$ zgrep PSTATE /proc/config.gz
CONFIG_X86_INTEL_PSTATE=y
CONFIG_X86_AMD_PSTATE=m # why not y?
$ lscpu | grep "cppc"
# nope
$ sudo modprobe amd_pstate
# That works
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 550 MHz - 4.21 GHz
available cpufreq governors: conservative ondemand userspace powersave performance schedutil
current policy: frequency should be within 550 MHz and 4.21 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 2.55 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.21 GHz.
AMD PSTATE Nominal Performance: 142. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 68. Lowest Non-linear Frequency: 1.72 GHz.
AMD PSTATE Lowest Performance: 22. Lowest Frequency: 550 MHz.
This path fixed, but why does CONFIG_X86_AMD_PSTATE show m instead y ?
Thanks!
[omano@omano-nvme ~]$ cpupower frequency-info
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 131 us
hardware limits: 550 MHz - 4.43 GHz
available cpufreq governors: conservative ondemand userspace powersave performance schedutil
current policy: frequency should be within 550 MHz and 4.43 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.37 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.43 GHz.
AMD PSTATE Nominal Performance: 135. Nominal Frequency: 3.60 GHz.
AMD PSTATE Lowest Non-linear Performance: 66. Lowest Non-linear Frequency: 1.76 GHz.
AMD PSTATE Lowest Performance: 21. Lowest Frequency: 550 MHz.
All good here with latest 5.18 kernel it loads fine on boot now with proper parameters. Great to have it back as my CPU clocks higher (respecting my bios settings) with this amd-pstate driver, it only goes to defaults with acpi-cpufreq.
VeraCrypt is funky due to the update. See error message below.
I get it when it says itâs not a problem to the end user, and it still works fine AFAIK but since itâs on community repository, I consider it relevant.
/build/wxwidgets/src/wxWidgets-3.2.0/src/common/sizer.cpp(2288): assert "CheckSizerFlags(!((flags) & (wxALIGN_RIGHT | wxALIGN_CENTRE_HORIZONTAL | wxALIGN_BOTTOM | wxALIGN_CENTRE_VERTICAL)))" failed in DoInsert(): wxALIGN_RIGHT | wxALIGN_CENTRE_HORIZONTAL | wxALIGN_BOTTOM | wxALIGN_CENTRE_VERTICAL will be ignored in this sizer: wxEXPAND overrides alignment flags in box sizers
DO NOT PANIC !!
If you're an end user running a program not developed by you, please ignore this message, it is harmless, and please try reporting the problem to the program developers.
You may also set WXSUPPRESS_SIZER_FLAGS_CHECK environment variable to suppress all such checks when running this program.
If you're the developer, simply remove this flag from your code to avoid getting this message. You can also call wxSizerFlags::DisableConsistencyChecks() to globally disable all such checks, but this is strongly not recommended.
Truecrypt was working perfectly fine and reliable for those being happy with the limited encryption security level truecrypt provided. All newer alternatives have their own issues.
