Closed candre23 closed 4 months ago
Hello @candre23! Very cool setup! 👍
So, first of all, the core numbering is by design, so you are all good there. I suppose one could argue that on a dual-CPU machine each CPU should start at 1, but that's a different issue.
Regarding the temps not displaying, I was able to duplicate your scenario and I think this might be a bug. Try the following:
Gadgets\@Resources
folder and open the file CpuMeter.lua
with Notepad++ or your preferred editor. -- get the 0-based physical core index from the logical core map table
nCoreIndex = tCoreMap[nCoreIndex + 1]
nCoreIndex = tCoreMap[(nCoreIndex % nLogicalCoresPerSkin) + 1]
I think this should resolve the error. Let me know how it goes. I'll fix this is the next release.
Yep, that fixed it. Temps are displaying correctly for both CPUs now. Thanks!
Awesome! Thanks a bunch. That fix isn't actually correct, by the way, but it was the simplest thing that I could do with one line of code. The proper fix will be in the next release, so keep an eye out. :-)
P.S.: Very cool screenshot! That's a keeper! :D
I've got HWinfo set up to pass all the relevant values and I have them mapped in the hwinfo.inc file. CPU0 is displaying temps correctly, but all temps display as "0C" for CPU1. I've reloaded the gadget, rebooted the machine several times, and verified that the temps are reading correctly in hwinfo itself. The only other weird thing is that the core numbers for CPU1 don't start at 1. They pick up where CPU0's cores leave off. Is this correct behavior, or part of the issue I'm having?
Relevant section of the hwinfo index:
Relevant section of the mapping file:
What I'm seeing: