Attaching eGPU silently exchanged sensor sources for curves - almost overheated the water loop
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
The report describes temperature sources being reassigned when an eGPU is attached after Fan Control starts. Begin by locating how configured curves identify and resolve temperature sensors, then trace how newly discovered sensors affect those references. Done means existing curves keep their intended sensor or clearly warn when that sensor changes.
Written by the indexing model from the issue text.
Description
Adding an eGPU after FanControl has been started can result in an exchanged temperature sensor as the source for configured curves without any warning. Internal GPU temperature was exchanged against external GPU in my case.
Hardware is RTX3090 interal and RTX3080 eGPU via TB4.
The temperature source should be configured via some unique ID, e.g. its name + ID, so it can not be substituted, if a new temperature sensor appears in the system. A warning would also be helpful, if sensors change.
- 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
-
bug settings ui
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DewaldOosthuizen/py-tray-command-launcher#162 ·
Maintainers usually reply within 1 day
-
area/ui-parity type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#140 ·
Maintainers usually reply within 1 day
-
needs: triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
accessibility good first issue hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenChemistry/avogadrolibs#3184 ·
Maintainers usually reply within 1 day
-
accessibility area:ui bug needs-repro P3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Raaif-Yousuf/Wingman#827 ·
Maintainers usually reply within 1 day