Attention: This would require truecrypt to be uninstalled.
On Arch side there is currently no fix to use truecrypt afterwards (has been removed from repos), the AUR version is not working either.
On Arch side there is currently no fix to use truecrypt afterwards (has been removed from repos), the AUR version is not working either.
Thanks, worked using Pamac (UI).
@Zesko Well “cppc” is enabled in config and the applied patch should fix the issue. Did you test the latest 5.18.12-2 build of the kernel?
Who needs that outdated software?
Which CPU do you have Zen3? Then CPPC should be listed. On Zen2 doesn’t (I haven’t it listed on 5.18.10 on my Zen2).
Let’s check:
$ uname -r
5.18.12-2-MANJARO
$ zgrep CPPC /proc/config.gz
CONFIG_ACPI_CPPC_LIB=y
$ zgrep PSTATE /proc/config.gz
CONFIG_X86_INTEL_PSTATE=y
CONFIG_X86_AMD_PSTATE=m
$ lscpu | grep "cppc"
# nope
$ sudo modprobe amd_pstate
modprobe: ERROR: could not insert 'amd_pstate': No such device
$ inxi -C
CPU:
Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP cache: L2: 3 MiB
Speed (MHz): avg: 2304 min/max: 2200/3600 cores: 1: 2580 2: 2333 3: 2052
4: 2187 5: 2002 6: 2540 7: 2979 8: 2506 9: 2080 10: 2008 11: 1992 12: 2398
I am using Zen2
But Kernel 5.18.10 works fine.
Some new Zen3 processors such as Cezanne provide the MSR registers directly while the X86_FEATURE_CPPC
CPU feature flag is set. amd-pstate
can handle the MSR register to implement the fast switch function in CPUFreq
that can reduce the latency of frequency control in interrupt context. The functions with a pstate_xxx
prefix represent the operations on MSR registers.
If the X86_FEATURE_CPPC
CPU feature flag is not set, the processor supports the shared memory solution. In this case, amd-pstate
uses the cppc_acpi
helper methods to implement the callback functions that are defined on static_call
. The functions with the cppc_xxx
prefix represent the operations of ACPI CPPC helpers for the shared memory solution.
https://www.kernel.org/doc/html/latest/admin-guide/pm/amd-pstate.html
Same, then you need shared mem set to kernel Parameter. Full MSR Support don’t work on Zen2 Hope later because shared memory sucks…
I measured acpi_cpufreq
and amd_pstate
in power consumption test, but both consumed about the same amount of watts per hour.
I would stick default acpi_cpufreq
for Zen 2 and do not notice any difference when using Desktop PC, but not Notebook.
Well, I won’t hold 5.18 updates back only cos of AMD-Pstate changes. If upstream wants to fix it, well - fine. Else it is what it is …
The patched kernel didn’t fix the amd_pstate
issue on my side.
Pls check if revision 3 fixes the remaining issues: Rebuild Kernel · manjaro-kernels/linux518@732c1c0 · GitHub
truecrypt is the orginal.
Germany BSI Security Evaluation of VeraCrypt
Created: 2020-12-27 Updated: 2022-01-02
https://sourceforge.net/p/veracrypt/discussion/general/thread/1a04e8bf82/?limit=25#ed5f
“The inherited code base has not been cleaned up, moreover, the
development still follows questionable coding practices.”
Revision 3 is now also in testing. Please check if that fixes the issue with pstate on AMD GPUs within 5.18 kernel series …
$ uname -r
5.18.12-3-MANJARO
$ 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!
It needs to be a module to work, Y means built into the kernel.
[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
.
it’s ok now
uname -a
Linux mjro 5.18.12-3-MANJARO #1 SMP PREEMPT_DYNAMIC Sun Jul 17 14:33:15 UTC 2022 x86_64 GNU/Linux
nvidia-smi
Sun Jul 17 21:26:07 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.57 Driver Version: 515.57 CUDA Version: 11.7 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA GeForce ... Off | 00000000:07:00.0 On | N/A |
| 0% 51C P8 16W / 201W | 129MiB / 4096MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 696 G /usr/lib/Xorg 122MiB |
| 0 N/A N/A 856 G xfwm4 2MiB |
+-----------------------------------------------------------------------------+
cpupower frequency-info
analyse du 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
limitation matérielle : 550 MHz - 4.65 GHz
régulateurs disponibles : conservative ondemand userspace powersave performance schedutil
tactique actuelle : la fréquence doit être comprise entre 550 MHz et 4.65 GHz.
Le régulateur "schedutil" est libre de choisir la vitesse
dans cette plage de fréquences.
current CPU frequency: Unable to call hardware
current CPU frequency: 2.95 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.65 GHz.
AMD PSTATE Nominal Performance: 132. Nominal Frequency: 3.70 GHz.
AMD PSTATE Lowest Non-linear Performance: 62. Lowest Non-linear Frequency: 1.73 GHz.
AMD PSTATE Lowest Performance: 20. Lowest Frequency: 550 MHz.
sudo turbostat
turbostat version 21.05.04 - Len Brown <lenb@kernel.org>
CPUID(0): AuthenticAMD 0x10 CPUID levels
CPUID(1): family:model:stepping 0x19:21:0 (25:33:0) microcode 0x0
CPUID(0x80000000): max_extended_levels: 0x80000023
CPUID(1): SSE3 MONITOR - - - TSC MSR - HT -
CPUID(6): APERF, No-TURBO, No-DTS, No-PTM, No-HWP, No-HWPnotify, No-HWPwindow, No-HWPepp, No-HWPpkg, No-EPB
CPUID(7): No-SGX
RAPL: 234 sec. Joule Counter Range, at 280 Watts
/dev/cpu_dma_latency: 2000000000 usec (default)
current_driver: acpi_idle
current_governor: menu
current_governor_ro: menu
cpu7: POLL: CPUIDLE CORE POLL IDLE
cpu7: C1: ACPI FFH MWAIT 0x0
cpu7: C2: ACPI IOPORT 0x414
cpu7: cpufreq driver: amd-pstate
cpu7: cpufreq governor: schedutil
cpufreq boost: 1
Thanks a lot @philm to apply the patches to the 5.18.12 Kernel its nice to see its work now again
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.