No sensors for iMac12,1 after update

[Steven]

Hi
I had the previous version installed and upgraded to Macs Fan Control 1.1.12.2, since then I can no longer see and select all of the sensors for my Mid 2011 iMac 21.5" (see attached screenshot). I'm running MacOS 10.9.4

Obviously in this instance for the CPU I would like to select either the cpu or it's heat sink sensor.

I hope there's an easy solution, the fan speeds were driving me nuts after adding an SDD as a supplement to the internal HDD, so your software was fantastic.

Kind regards
Paul

[Steven]

Please try doing the following:

1. Quit MFC
2. run these 3 commands in Terminal (this will clear MFC preferences on your mac)

killall MacsFanControl
rm ~/Library/Preferences/com.crystalidea.macsfancontrol.plist
killall -u `id -u -n` cfprefsd

3. Please post technical information from Diagnostics tab from Preferences dialog.

[eborus]

Still no change to the sensor list, here's the diagnostics.

[Steven]

It looks like MFC fails to get temperature (value -1 in techinfo) for your sensors.

Try to terminate any other apps that are reading temperatures and reset SMC (http://support.apple.com/kb/HT3964)

[Datisit]

I have the exact same issue running Windows 7. Is resetting the SMC a probably fix for this problem?

[Steven]

Datisit
Do you own the same iMac? Trying to reset SMC won't harm anyway

[Datisit]

Hi Steven,

Actually no, I have an iMac 12,2. Only the ambient and the HDD temps are being registered. That's after two SMC resets.

Macs Fan Control 1.2.0 beta 2
iMac12,2
Intel(R) Core(TM) i5-2500S CPU @ 2.70GHz[100]
Windows 7 x64

Fans:
ODD-min{1150}curr{1559}max{2908}mode{1,1560}
HDD-min{1100}curr{1289}max{5500}mode{0}
CPU-min{940}curr{1422}max{2744}mode{1,1425}


TempSensors:
TA0P (Ambient) - 40.7461
TA0V () - 41.8203
TA0p () - 44.5
TC0H (CPU Heatsink) - -1
TC0P (CPU Proximity) - -1
TC0c () - 36
TC0h () - 32.375
TC0p () - 36.375
TC1c () - 38
TC2c () - 36
TC3c () - 39
TCGc () - 38
TCSc () - 36
TCXc () - 39.0312
TG0D (GPU Diode) - -1
TG0H (GPU Heatsink) - -1
TG0d () - 45.25
TG0h () - 43.125
TG0p () - 44
TH0O () - -1
TH1O () - -1
TL0P (LCD proximity) - -1
TL0V () - -1
TL0p () - 42.3125
TL1P () - -1
TL1V () - 38.8633
TL1p () - 42.0625
TL1v () - -1
TL2V () - -1
TLAV () - -1
TLBV () - -1
TLCV () - -1
TO0P (Optical Drive) - -1
TO0p () - 36.75
TPCD () - 47
TS0P () - -1
TS0V () - -1
TS0p () - 36.5
TS2P () - -1
TS2V () - -1
TS2p () - 35.875
Tm0P (Mem Controller) - -1
Tm0p () - 36
Tp1P () - -1
Tp1p () - 40.5
Tp2H () - -1
Tp2h () - 48.875
Tp3H (PSU Primary) - -1
Tp3h () - 39.875


Disk drives:
ST31000528AS - 42

What do you think?

[Steven]

Do you have this problem only under Windows or Mac as well?

[Datisit]

Nope - the mac client works perfectly - not that I use OS X, I just downloaded it now to check.

[Steven]

Datisit
Try running the latest beta 1.2
http://forums.crystalidea.com/viewtopic.php?f=11&t=1093

with specifying /inpout32 command line parameter (use alternative way to access SMC on Windows)

Also try to quit Bootcamp.exe process before running MFC.

[Datisit]

I'm actually already running that version - you can see it on the log file output I posted before.
Can you explain what you mean by 'with specifying /inpout32 command line parameter (use alternative way to access SMC on Windows)'

Thanks

[Steven]

Code: Select all

"C:\Program Files (x86)\Macs Fan Control\MacsFanControl.exe" /inpout32

[Datisit]

Ah that did it! - All the temperatures are being accurately displayed now.

[Steven]

Datisit
if you try again without that command line switch - the issue is back again?

[Datisit]

I've run it again without the other command.
The temperatures are still being read. Everything seems normal.

[eborus]

Still having problems. We have multiple user accounts on this iMac and need to have a copy of Macs Fan Control in the startup items for each user as there seems to be no way to make it a system wide startup process.

One user, not the administrator, can see all of the sensors in her copy of MFC whereas I cannot. Screenshots attached - obviously I would like to set the CPU fan using a CPU sensor, any ideas?

Kind regards

[Steven]

eborus
Thanks for the report. I'll try to create a multiple-user environment, in order to reproduce the issue.
Is there any other difference between accounts except that non-admin account is workins fine?

Running a system wider process is a todo feature: http://forums.crystalidea.com/viewtopic.php?f=11&t=898

[Datisit]

Hi there Steven,

I'm having to bring this up again as I am having the same problems as before on version 1.2.1. The command line alteration is have no affect this time too.
Any other suggestions?

Just to confirm, no sensors are appearing other than Ambiant and HDD.

Thanks,

Datisit

[Steven]

Datisit
again, on Windows? And OK for mac?

[Datisit]

Sorry for the late reply, the sensors seem to be recognised sometimes and sometimes not. At the moment, the CPU sensor is not being seen by the OSX or the W7 client. This causes the fan to run at full speed.

Thanks,
Datisit