FanControl not accessing GPU temperatures when running as a service
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- backend
Research direction
Start by comparing how GPU temperature sensors are accessed when FanControl runs as an application and as a service, using the Radeon RX 7700XT report as a reproduction case. Check whether GPU, Hotspot, and Memory readings remain available to fan curves in service mode, and identify the cause of the difference. Done means GPU temperature changes affect the configured case fans while the service is running.
Written by the indexing model from the issue text.
Description
I have been trying to use the max function to create curves for my case fans that will respond to both increases in CPU temp and GPU temp. This works fine when I have FanControl actually open and running as an application, but when I restart (after saving the config), FanControl no longer responds to changes in GPU temperatures. While the app is open, I can run a GPU stress test and hear the case fans ramp up, and I can run a CPU stress test and also hear the case fans ramp up, exactly as I wanted. When FanControl is running as a service, I can run a CPU stress test and hear the case fans ramp up, but when I run a GPU stress test, they do not change their speed. I have FanControl set to start service on boot, and toggling the start app on user log on and start minimized does not solve this problem. Opening fancontrol after I boot and then closing it and keeping it running as a service also does not fix this problem. I can only get it to properly work when I have fancontrol actually open as an app, and not running in the background. This occurs for all of my GPU sensors (GPU, Hotspot, Memory).
I'm using a Radeon RX 7700XT. I don't have another GPU to test this with, so it may be specific to my GPU. I have the latest drivers installed.
- Dominant language
- No language data
- Stars
- 21.1k
- Forks
- 619
- Avg merge
- 11h 52m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Rem0o/FanControl.Releases
-
bug next version
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Rem0o/FanControl.Releases#4220 · 1 comment ·
-
Difficulty 3/5 Half a day Newbie friendliness 35/100
Rem0o/FanControl.Releases#4228 · 1 comment ·
-
Difficulty 3/5 Half a day Newbie friendliness 55/100
Rem0o/FanControl.Releases#4225 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 12/100
Rem0o/FanControl.Releases#4224 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Rem0o/FanControl.Releases#4222 · 14 comments ·
All issues in Rem0o/FanControl.Releases
Similar issues
-
area/linq bug package/core triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug engine
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
frostney/GocciaScript#1746 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
omegaup/omegaup#10353 · 1 comment ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EmbarkStudios/cargo-deny#910 ·