✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is Noctua NF-A12x25 PWM, with ARCTIC P12 PWM PST (5 Pack) as a strong alternative.

A Linux gaming PC usually inherits whatever fan behaviour the motherboard firmware felt like using: case fans that surge at menu screens, idle noise you can hear across the room, and an AIO pump locked to a profile designed around Windows software you no longer run. The fix is not a vendor suite. Between the kernel’s hwmon drivers, the CoolerControl daemon and the liquidctl project, Linux can own every fan curve and pump channel in the case, provided your hardware exposes a control path software can reach.

This guide walks that workflow end to end: how to find out which fans Linux can actually see, how to build temperature-linked curves in CoolerControl, when a USB-connected cooler needs liquidctl instead, and what to buy when your board gives software nothing to hold on to. Product specifications below are the makers’ published figures, quoted as stated, with no cooling-performance promises attached.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

Install CoolerControl, confirm your fans appear as hwmon devices, and build graph profiles that tie each fan or pump to CPU, GPU or coolant temperature. If your AIO or fan hub connects over USB rather than a fan header, liquidctl exposes its pump and fan channels, and CoolerControl can drive those too. Boards with locked-down headers need a USB fan controller instead.

How Linux sees your fans

Every software-controllable fan starts life as a hwmon device. The kernel reads the motherboard’s Super I/O chip, the part from Nuvoton or ITE that watches temperatures and drives the fan headers, and publishes sensor readings and PWM outputs that tools can read and write. Common chips are covered by in-kernel drivers such as nct6775 and it87, and running a sensor detection pass shows you exactly which channels exist on your board.

Two caveats decide most success stories. First, the Nuvoton NCT6687 fitted to many recent MSI boards is only partly handled by the stock kernel driver, and full fan control on those boards often needs the out-of-tree nct6687 module loaded instead. Second, firmware still owns the headers until you let go: set each header to PWM mode in the setup utility, because a header left in DC or automatic mode can ignore or fight the duty values software writes. Graphics card fans arrive through the amdgpu hwmon interface on AMD hardware, while NVIDIA cards expose fan control through the vendor’s Linux tooling. The older fancontrol script can hold a static configuration, but it is a blunt instrument next to a profile-based tool.

Building curves in CoolerControl

CoolerControl runs as a system daemon with a desktop application on top. The daemon applies your settings at boot and keeps applying them whether or not the window is open. Inside the app you create profiles: graphs that map a temperature source to a fan duty, so a rear exhaust fan can follow GPU temperature while the CPU cooler follows the processor package sensor.

The useful trick is the function layer. A mix function combines several sensors, for example the higher of CPU and GPU temperature, and feeds that single value into one profile, so case fans respond to whichever part is actually hot during a game. Profiles can be applied per fan or to groups, and liquidctl devices appear in the same device list as hwmon fans, so one window manages headers, pumps and hubs together. Because applied speeds latch in the hardware, keep a sane fallback curve in the firmware setup as a safety net for the moments the daemon is not running, such as early boot or a live USB session.

Pumps, displays and liquidctl

Some coolers never touch a fan header for control. USB-connected AIOs and fan hubs are invisible to hwmon, and that is the gap liquidctl fills: it talks to the device directly and exposes pump speed, fan channels and coolant temperature. Its supported list includes NZXT Kraken X and Kraken Z families, Corsair Hydro Platinum and Pro XT coolers, the Commander Pro, Commander Core and Commander Core XT fan controllers, and Aquacomputer units such as the Octo and Quadro.

Coolant temperature is the real prize. Radiator fans and pump speed should react to the temperature of the liquid, which rises and falls far more smoothly than a spiking CPU core sensor, and liquidctl is what makes that reading available on Linux. CoolerControl can then draw a curve against it like any other sensor. Support is strictly per model, so run a device listing first and confirm your exact cooler or controller appears before planning a build around it. Lighting and LCD features vary by device and are the least complete part of the support picture.

When the board gives you nothing

Some boards expose sensors but no writable PWM outputs, and compact boards may offer only two headers for a case full of fans. Three routes out exist. Splitters and daisy-chain cables such as ARCTIC’s PST system let several fans share one header’s signal, as long as the combined draw stays inside the per-header current rating printed in the board manual. A USB fan controller carries its own channels and sidesteps the board entirely, which is also the cleanest fix when a hub is already part of the build. Standalone manual controllers with a physical dial remain a last resort: simple and dependable, but they cannot react to temperature on their own.

Hardware that plays along

The five products below cover each control path in this guide: standard PWM fans for headers, a dual-tower air cooler, a USB-controlled AIO, and a controller that adds channels when the board runs out.

Noctua NF-A12x25 PWM

Noctua NF-A12x25 PWM

Noctua NF-A12x25 PWM

Check price on Amazon

Noctua’s 120 mm flagship is the reference point for header-driven case and radiator duty, with a wide PWM range and a supplied Low-Noise Adaptor that caps the top speed for near-silent builds.

Specs:

  • Size: 120 x 120 x 25 mm
  • Speed: 450 to 2,000 RPM via PWM, 1,700 RPM maximum with the Low-Noise Adaptor
  • Airflow: 102.1 cubic metres per hour, maker-stated
  • Static pressure: 2.34 mm H2O, maker-stated
  • Acoustical noise: 22.6 dB(A), maker-stated
  • Bearing: SSO2, with a Sterrox liquid-crystal polymer impeller
  • Connector: 4-pin PWM

ARCTIC P12 PWM PST (5 Pack)

ARCTIC P12 PWM PST (5 Pack)

ARCTIC P12 PWM PST (5 Pack)

Check price on Amazon

ARCTIC’s value route to a full case of controllable fans. The PST connector shares one header’s PWM signal down a chain of fans, and the fans stop completely below a 5 percent PWM signal for silent idle desktops.

Specs:

  • Size: 120 x 120 x 25 mm per fan
  • Speed: 200 to 1,800 RPM, with fan stop below a 5 percent PWM signal
  • Airflow: 56.3 CFM, maker-stated
  • Static pressure: 2.2 mm H2O, maker-stated
  • Bearing: fluid dynamic
  • Connector: 4-pin PWM with PST sharing cable
  • Pack contents: five fans

Thermalright Peerless Assassin 120 SE

Thermalright Peerless Assassin 120 SE

Thermalright Peerless Assassin 120 SE

Check price on Amazon

A dual-tower air cooler whose two PWM fans plug straight into the CPU fan header, where CoolerControl or the firmware can run them. Six heat pipes and a 155 mm height cover most mid-tower gaming builds.

Specs:

  • Design: dual tower, six 6 mm AGHP heat pipes
  • Fans: two TL-C12C 120 mm PWM fans, 1,550 RPM maker rating
  • Fan airflow: 66.17 CFM, maker-stated
  • Noise: 25.6 dB(A) maximum, maker-stated
  • Height: 155 mm
  • Sockets: AMD AM4 and AM5, Intel LGA 1700, 1200, 115X and 1851

Corsair iCUE H100i Elite Capellix XT

Corsair iCUE H100i Elite Capellix XT

Corsair iCUE H100i Elite Capellix XT

Check price on Amazon

This 240 mm AIO routes its fans through the included Commander Core controller over USB, which is exactly the arrangement liquidctl understands: the controller’s fan channels can follow a curve while the pump reports its speed back to the system.

Specs:

  • Radiator: 240 mm, 277 x 120 x 27 mm
  • Fans: two AF120 RGB Elite PWM fans, 550 to 2,100 RPM
  • Fan airflow: up to 65.57 CFM, maker-stated
  • Fan static pressure: up to 2.68 mm H2O, maker-stated
  • Controller: iCUE Commander Core included, six fan and six RGB channels
  • Sockets: Intel LGA 1700, 1200, 115X and 2066, AMD AM5 and AM4
  • Warranty: 5 years, maker-stated

Corsair iCUE Commander Core XT

Corsair iCUE Commander Core XT

Corsair iCUE Commander Core XT

Check price on Amazon

A standalone USB controller for builds that have outgrown their motherboard headers. It adds six independently controlled PWM channels plus temperature probe inputs, and liquidctl lists it among its supported devices for fan control.

Specs:

  • Fan ports: six 4-pin PWM, individually controllable
  • RGB ports: six channels with automatic fan-type detection
  • Temperature inputs: two probe connectors
  • Connection: internal USB 2.0 header, SATA power
  • Model: CL-9011112-WW

How to choose

Start from the control path, not the fan. Inventory what Linux can already see: run a sensor scan, note which headers report both a fan speed and a writable PWM channel, and check whether your Super I/O chip needs the out-of-tree NCT6687 module. If everything you own hangs off headers, CoolerControl alone finishes the job.

Next, match the curve input to the heat source. CPU coolers follow the package sensor, case fans usually serve the graphics card better through a mix function, and radiator fans on a USB AIO should follow coolant temperature through liquidctl. Finally, count headers against fans before buying: PST chains and splitters stretch a small board, but a USB controller is the tidier answer once you pass four or five fans, and it keeps working if you change boards later.

Who should skip this

Skip the project if your firmware curves already behave and you never hear your PC; the gain here is control, not magic. Laptop owners get nothing from this guide, since embedded controllers in portables rarely expose hwmon fan outputs at all. Owners of sealed AIOs with a fixed-speed pump and no USB connection also have nothing to tune beyond the header their radiator fans sit on. And if your priority is synchronised lighting effects across a full vendor ecosystem, the Windows suites still do that one job more completely than the Linux tooling covered here.

FAQ

Why does CoolerControl not list my fans?
Usually the chip driver is missing or the header is in the wrong mode. Run sensor detection, load the out-of-tree NCT6687 module if your board uses that chip, and set the header to PWM mode in the firmware setup.

Can I control an AIO pump without Windows?
Yes, when the cooler appears in liquidctl’s supported device list or when the pump sits on a motherboard header as a plain PWM device. Coolers with neither path keep their factory pump behaviour.

Is it safe to let a daemon set fans at boot?
CoolerControl’s daemon applies profiles early and the hardware latches the last setting if the daemon stops. Keep a reasonable fallback curve in the firmware setup so the machine is never left without one.

CoolerControl or the classic fancontrol script?
fancontrol writes a static configuration and leaves it. CoolerControl adds mixed sensor functions, per-device profiles and liquidctl hardware in one interface, which is why it is the better fit for a gaming PC with a GPU and an AIO.

Final verdict

Fan control is one of the places where Linux no longer asks you to settle. CoolerControl turns hwmon headers into proper mixed-sensor curves, liquidctl brings USB pumps and controllers into the same picture, and the hardware above gives every control path a sound option, from a single Noctua on a header to a Commander Core XT running the whole case. Check your chip, pick the path your hardware exposes, and the firmware’s idea of a fan curve stops being your problem.

Explore Our Guides & Free Tools