Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zen Monitor has swapped Node labels for Tdie and Tctrl #28

Closed
KeithMyers opened this issue Jun 18, 2020 · 4 comments · Fixed by KebabLord/zenmonitor-ng#2 · May be fixed by #32
Closed

Zen Monitor has swapped Node labels for Tdie and Tctrl #28

KeithMyers opened this issue Jun 18, 2020 · 4 comments · Fixed by KebabLord/zenmonitor-ng#2 · May be fixed by #32

Comments

@KeithMyers
Copy link

Zen Monitor has swapped Node labels for Tdie and Tctrl.
Screenshot of Zenmonitor_1 41

@KeithMyers
Copy link
Author

+1 bump

@KeithMyers
Copy link
Author

+100 bump

@KeithMyers
Copy link
Author

Was hoping I could attract the developer back to this issue in Zen Monitor. The problem lies with Zen Monitor as the labels for Tdie and Tctl are NOT swapped in ZenPower driver.

~$ sensors
zenpower-pci-00c3
Adapter: PCI adapter
SVI2_SoC:     +1.10 V  
Tdie:         +64.4°C  (high = +95.0°C)
Tctl:         +91.4°C  
Tccd1:        +89.2°C  
SVI2_P_SoC:   16.27 W  
SVI2_C_SoC:  +14.43 A  

enp3s0-pci-0300
Adapter: PCI adapter
temp1:            N/A  

zenpower-pci-00cb
Adapter: PCI adapter
SVI2_Core:    +1.29 V  
Tdie:         +62.4°C  (high = +95.0°C)
Tctl:         +89.4°C  
SVI2_P_Core: 178.02 W  
SVI2_C_Core: +138.22 A

HonsW added a commit to HonsW/zenmonitor that referenced this issue Aug 9, 2020
swap value and order of tDie and tCtl to reflect order of zenpower driver and fix ocerman#28
@KeithMyers
Copy link
Author

Thanks for the fork and pull request for fixing the label swap issue. Now I have the correct temps listed for my Threadripper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant