this post was submitted on 18 Mar 2025
89 points (100.0% liked)

Linux Gaming

17206 readers
329 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
top 7 comments
sorted by: hot top controversial new old
[–] Willdrick@lemmy.world 1 points 6 days ago (1 children)

Does anybody know if it's possible to use this to control case fans based on sensor's temps other than the CPU ones? I've been fiddling with it for 10 minutes and can't figure it out.

I have an oversized CPU cooler and a pretty closed case (thermaltake view27). For now I'm brute forcing airflow with the 3 intake front fans but it gets loud even while idling.

Since the cooler is oversized, by default the case fans won't spin up faster even when my GPU is dumping tons of heat into the case. I'd like to set it so it takes the temps off a motherboard sensor rather than the cpu

[–] xinayder@infosec.pub 1 points 5 days ago (1 children)

You can, you can create a profile based on a sensor. I had to install the it87 driver for Linux to identify the case cooling fans I had.

[–] Willdrick@lemmy.world 1 points 5 days ago

My case fans are listed and I can see the rpm, I just couldn't figure out the "create a curve based off the temp of this other sensor" part.

[–] Thorry84@feddit.nl 4 points 1 week ago* (last edited 1 week ago) (1 children)

I've been using this for a while now and it's pretty good. For my watercooling it controls the fans and pump speed using liquidctl. Stuff plugged into the motherboard it controls directly.

However the connection between CoolerControl and liquidctl breaks all the damn time for some reason. With the latest update it's broken again. I haven't figured out exactly where the error is, because the error comes from liquidctl but I can't reproduce it using just liquidctl. So it's somewhere between CoolerControl (it's daemon) and liquidctl. Once I figure it out I'll post a bug report and it will be fixed soon I hope.

I wonder how much extra cpu load CoolerControl adds. Some manufacturer tools are known to be quite cpu intensive. I've seen the interval for CoolerControl be quite short, to react quickly to changes. But I think their clever way of splitting the UI from the actual control logic is very efficient. It probably means the cpu impact is minimal.

Excellent tool, would recommend!

[–] phrogpilot73@lemmy.world 1 points 1 week ago

I'm with you on this. The desktop app isn't connecting now, but I can log in via the web app and it appears to work.

For anyone on Bazzite there's already a ujust script for setting it up:

ujust install-coolercontrol
systemctl reboot
#reboot
sudo systemctl enable --now coolercontrold

Woah, this is the software I've been looking for! This is absolutely fantastic