The Linux GPU control panel that was missing
LACT gives Linux users a single place to inspect and tune AMD, Nvidia, and Intel graphics hardware. It reports the card, firmware, memory, hardware units, PCIe details, Vulkan support, thermals, clocks, power use, and throttling. Historical charts can be configured and exported to CSV. Depending on the GPU and driver, users can also set power caps, power states, fan curves, clock limits, voltage behavior, and profiles that activate when a process or GameMode starts.
The breadth is valuable because Linux GPU control is fragmented. One setting may live in sysfs, another in a vendor library, and another behind a kernel option. LACT translates those interfaces into a consistent GTK application while keeping configuration work in a separate system service. The daemon does not require an X11 or Wayland session, so settings can survive outside the desktop and the service can run headlessly from a YAML file.
Version 0.10.0, released August 12, 2026, shows that the project is still widening that surface. It added Nvidia PowerMizer and voltage-boost controls, more Blackwell and GDDR6X or GDDR7 temperature readings, AMD GTT memory display, improved resume handling, and commands for temporarily detaching a GPU before virtual-machine passthrough. It also introduced a graphical service setup flow, replacing the old instruction to copy a systemctl command.
Installation is easy, privileged control is not trivial
LACT has first-class packages across far more distributions than most hardware utilities. Arch users can install it from official repositories, Fedora has a Copr, Debian and Ubuntu users get release packages, and packages also exist for NixOS, Gentoo, Solus, openSUSE Tumbleweed, and atomic Fedora variants. A Flatpak is available for Bazzite and other systems, while a service-only Docker path and source builds cover narrower cases.
Installing the interface is only part of setup. Changing hardware settings requires lactd, a root-level system service. Version 0.10.0's wizard makes enabling it friendlier, and new Polkit checks protect administrative actions such as profile hooks. The normal package uses a Unix socket owned by either the wheel or sudo group. Systems with different group conventions may need an explicit admin_user or admin_group in /etc/lact/config.yaml.
AMD tuning adds another layer. Overdrive is disabled in the driver by default. LACT can enable it on standard Debian, Fedora, and Arch setups by writing a modprobe configuration and rebuilding initramfs, or the user can add amdgpu.ppfeaturemask=0xffffffff to kernel boot options. Nonstandard initramfs layouts need manual work. Any tool adjusting clocks, voltages, power, and fans deserves conservative changes plus a known recovery route. LACT documents how to recover from a bad overclock, which is reassuring, but does not remove the risk.
Support depends on the exact GPU and driver
LACT's hardware matrix is the page to read before installing. Modern AMD cards have the widest configuration support, though details vary by kernel and firmware. RDNA4 needs a recent kernel, with zero-RPM fan configuration requiring a newer one still. RDNA3 firmware controls its own curve, which prevents choosing the temperature sensor. Old Polaris cards have a driver-side bug where returning to automatic fan control can break fan behavior and produce coil whine. Integrated GPUs may expose only basic controls.
Nvidia support generally starts with Maxwell, but LACT requires the proprietary driver and CUDA libraries. Locked clock ranges depend on generation, and clock offsets require sufficiently recent drivers to appear or behave well. The latest release improves Blackwell sensing, but the matrix still recommends a current driver. Users who deliberately run Nouveau or another open-only setup should stop here.
Intel support is useful for monitoring and bounded clock adjustment, not full overclocking. Arc discrete cards can expose a power limit, although the maximum may be reported incorrectly, and fan control is not available in the driver. Issue #1107 follows experimental fan support that required a patched kernel and exact curve rules. Battlemage users may also need to force GTK's OpenGL renderer to avoid Vulkan-related interface corruption.
Laptops are an important exception. If a fan is wired to the system controller rather than the GPU, LACT cannot monitor or control it. The project explicitly directs those users to a whole-system fan tool such as CoolerControl. That is a hardware boundary, not a missing checkbox that LACT can fix.
Operational rough edges and safety boundaries
Current reports show why per-machine testing matters. Issue #1151 describes an AMD Radeon 660M where LACT fails to apply power settings even though writing the relevant sysfs controls manually works. Issue #1116 reports an RX 7900 XTX fan curve that does not apply automatically after boot until another setting is submitted. These reports concern particular hardware and software combinations, not every installation, but a fan or power profile should be verified after reboot and resume before it is trusted.
Remote management needs even more care. The daemon can listen on TCP and the GUI can connect from another machine, but the README states that this connection has no authentication or encryption. It is disabled by default for good reason. Keep it on a trusted isolated network, bind it narrowly, or put it behind your own authenticated encrypted tunnel. Exposing the port directly would hand sensitive hardware control to anyone who can reach it.
Health and the decision
LACT was pushed on August 14, 2026, two days after its latest release. GitHub listed 91 open issues and pull requests combined, while a separate search found 78 issues and 13 pull requests. New reports were receiving hardware-specific discussion in August, and the release changelog credits several contributors across features, fixes, packaging, and maintenance. This is active development around a difficult compatibility surface, not a neglected utility.
For a supported Linux desktop GPU, LACT is the best-balanced starting point: approachable enough for normal users and deep enough for headless administration and metrics. Its excellent documentation makes limitations visible. Read that matrix, protect the daemon, and validate settings after every driver, kernel, or LACT upgrade.