Open FlashLightning67 opened 5 months ago
If I knew exactly what's the issue, I would address it in LHM directly.
Ah my bad.
I'm not sure if such a jank solution is within the scope of this project, but could some sort of functionality be added to just open and close CPU-Z whenever sensors aren't detected, as an opt in feature for users with motherboards with this issue? This can be done to an extent with task scheduler, but this issue crops up at weird times and having fan control do it whenever there is a problem could be helpful
Hi, I have submitted a fix has been submitted (as a Pull) against LibreHardwareMonitor to address this issue. See Pull 1438 if you are interested. I have copied the net8.0 files (LibreHardwareMonitorLib.dll and LibreHardwareMonitorLib.xml) that I compiled with VS2022 community edition over the top of my FanControl ones and it's working on my rig with an IT8655E chip. If you have a different ITE chip, then you could try the code modification shown in the pull against your chipset, at your own risk.
I don't know how long it will take until the fix is rolled into LHM for release to all, and then subsequently into FanControl.
This is great, I added your changes to the IT8665E chip and it has fixed this issue. Hopefully it'll get merged into LHM and the fix for both chips will eventually make its way into FanControl.
I compile LHM myself, unless exception, from the latest commit. So your changes should be in the next FanControl release.
Certain motherboards have an issue with LHM where it doesn't accurately report the RPM as shown here However, this issue is oddly resolved by opening certain monitoring software, such as CPU-Z or CPUID HWMonitor. This issue, of course, translates to fan control as well, making these motherboards (mostly ASUS it seems) unusable.
While the root issue is with LHM, they don't seem to be able to fix it. Is it possible for fan control to incorporate a solution that could cause LHM to start working, similar to what CPU-Z manages to somehow do?