No CPU temperature in iStat with 0.7

[Xardas220]

Hi,

just updated to 0.7. I have no CPU temperature in iStat anymore. I'm on MacOS 11.5.1, OC 0.7.0. Is this known or do I have a wrong setting? There is the new function to use the internal temperature and stuff, but I want to use the one in iStat.

Thanks,

Xardas

[trulyspinach]

Hi,
This is interesting, I did not change anything in SMCAMDProcessor. As you can probably see the source code for it have not been changed for a while.
Did you changed your SMBios somehow? It will break whatever the SMC key iStat use to display package temperature.

[Xardas220]

Hi,
nope, I changed nothing only the two .kext's. These are also the same in name and were replaced with the old ones. I booted from a USB-Drive that is exact like the boot-folder on my EFI-drive, with the difference that 0.7 is on the USB-drive.

1. I booted again from the internal (old SMCAMD..) and the temp is there.
2. Replaced the new SMCAMD.. with the old on the USB-drive, the temp works again also.

So the reason must be 0.7 but I don't know how that can be. So you said, the code is the same for some time now.

[trulyspinach]

Can you kextstat | grep SMCAMD when the temp doesn't show just to verity if SMCAMDProcessor is correctly loaded?
If not maybe OC's log can help diagnostic the problem.

Thanks

[Xardas220]

Here the screenshot of kextstat. Also a screenshot of the missing CPU-temp but the CPU-temp of the internal reading. Normal there is the CPU-temp on the menu bar of iStat left from "MEM".

[trulyspinach]

Seems like it loaded without problem, I was thinking if the 0.7 cause it failed to load. I am out of idea for now and I can't really test it at the moment. If the previous version works fine for you maybe you can stick to it until this is fixed.

[Xardas220]

Seems like it loaded without problem, I was thinking if the 0.7 cause it failed to load. I am out of idea for now and I can't really test it at the moment. If the previous version works fine for you maybe you can stick to it until this is fixed.

Mh, that‘s weird. I‘ll use the older version and wait for a bug fix. Thanks for the fast reply! :)

[Schaefers]

I just updated AMDRyzenCPUPowerManagement.kext to 0.7 and for me the temps in iStat Menus are still showing fine.

[Xardas220]

I just updated AMDRyzenCPUPowerManagement.kext to 0.7 and for me the temps in iStat Menus are still showing fine.

Have you done both SMC and power management? Or only power management?

[Schaefers]

I just updated AMDRyzenCPUPowerManagement.kext to 0.7 and for me the temps in iStat Menus are still showing fine.

Have you done both SMC and power management? Or only power management?

Only power management.

[Xardas220]

I just updated AMDRyzenCPUPowerManagement.kext to 0.7 and for me the temps in iStat Menus are still showing fine.

Have you done both SMC and power management? Or only power management?

Only power management.

I updated both. Maybe thats the problem. I‘ll try tomorrow.

[trulyspinach]

@Xardas220 Please let me know if 0.7 works good with some older version SMCAMDProcessor for you.

[henkiewie]

The same thing happened here.

Only restoring the previous SMCAMDprocessor.kext brought back the temperature in iStat.

[trulyspinach]

@henkiewie does the previous SMCAMDProcessor.kext works fine with 0.7?

[henkiewie]

@trulyspinach Yes it does for me. See the second screenshot.

[trulyspinach]

Thanks, then I am guessing maybe the source code changed at some point either accidentally by myself or some pull requests that caused the problem. I’ll look into this soon.

For now I believe the workaround would be to use the previous version of SMCAMDProcessor.

[Jacobax]

same here
OC0.7.2. Stats shows no temperature
the previous version works fine with OC0.7.1

[lwndow]

wanted to add my experience. added both 0.7 kexts (no previous install) and had no CPU temp (Aorus B550 Master). swapped the 0.6.4 SMCAMD in and it was registering again. big sur, 11.5.2, macpro7,1, OC 0.7.2

[VisualEhrmanntraut]

Thanks, then I am guessing maybe the source code changed at some point either accidentally by myself or some pull requests that caused the problem. I’ll look into this soon.

For now I believe the workaround would be to use the previous version of SMCAMDProcessor.

@trulyspinach According to GitHub, these are the two files changed for SMCAMDProcessor between 0.6.4 and 0.7: