CoreCtrl vs CoreFreq

CoreCtrl is a free, open-source GNU/Linux application for controlling hardware through profiles. Profiles can launch when an associated Linux or Windows application starts, then restore their settings when it ends. You can also activate a manual profile, which takes priority over automatic profiles; only one manual profile can be active at a time. The project describes its AMD GPU controls as full, covering fans, frequency, power, sensors, and hardware and software information. CPU support is more limited: it includes a frequency-scaling governor control, a package maximum-frequency sensor, and CPU package information. Automatic profiles need an executable binary name, so they cannot be tied to scripts or interpreted-language applications. The available controls depend on the Linux kernel version and hardware. Full AMD GPU control with the amdgpu driver requires a boot parameter and reboot. CoreCtrl is free, with no paid plans stated, and the project recommends installation through a distribution package manager. It is in maintenance mode, with development focused on fixes and upkeep rather than new features or hardware support.

CoreFreq is free Linux CPU-monitoring software with BIOS-like controls for 64-bit processors. It reads frequencies, ratios, performance counters, instructions per cycle, C-states, temperature, and documented core-voltage readings. The interface shows processor features, brand and architecture strings, plus a topology map including caches. Its driver exposes controls for Turbo Boost, power management, thermal limits, prefetchers, and hardware-controlled performance states. A daemon and command-line client provide monitoring views and JSON-encoded system information. Listed architectures include Intel and AMD families, Arm A64, RISC-V RV64, and PowerPC64 LE. Requirements include Linux kernel 3.3 or newer and GNU C Library. Installation can use source builds or packages for several distributions. The project is GPL-2.0 licensed and uses shared memory between its kernel module and user-space component. Some virtual machines may hide required registers. Driver signing is required when kernel signature verification is enabled. The interface renders best in ASCII or VT100 terminals.