CRYSTALIDEA Forums

By any chance can we have all the temperature sensors listed in Mac Fan Control for the Retina MBPs. Seems disappointing that it only supports 11, when other software, such as iStat Menus and others read 25.

Attached iStat Menus as an example.

loadbang
Which sensors do you need?

It seems Macs Fan Control is not working properly (for me and a lot of my friends) in the newest version of Yosemite. Upon startup, the Macs Fan Control comes up and reads: "New version of the program is available. Please visit our website for the newest version."

Below that are two buttons: Continue and Exit. The Continue button has a countdown on it, and when it reaches 0, I may then click continue to enable Macs Fan Control - and that's the only way to re-enable it each time.

I looks at the crystalidea site for a "newest version" but the version I am running IS the newest version as far as I can tell.

Any ideas what can be done in this situation? I LOVE Macs Fan Control. Can this work again in Yosemite?

My Computer: Late-2008 2.8 GHz Intel Core 2 Duo with 512GB Samsung SSD (Trim enabled) and 8GB RAM OS 10.10.1

Beta version URL is:
http://www.crystalidea.com/downloads/ma ... l_beta.zip

Thank you so much - now I understand - what you guys are referring to as the "Beta" version, actually IS the newest version. Maybe instead of calling it a Beta Version (which often refers to an OLD or previous version), you could re-label the "old" version as works on: OS 10.6, 10.7, 10.8, and 10.9. And then below that, provide a link for the "Newest" version which can be labeled "Beta Version for OS 10.10 Yosemite". Would this make things less confusing for people trying to download the "latest" version? Hope my suggestion helps!! Thanks for making such an awesome Fan Control App - this app has saved MANY a computer for me!

hello,

new comer on forum.

i have been running macs fan control for over 2 years on a macbook pro 17 inches 2.8 core2duo. The MAGIC of it was that you could set speed on both fans at 1100 tr/min, which was magically silent, and perfectly working.

the update of macs fan control of this last days set the minimum speed at 2000 tr/min. So the macbook makes constant noise now. !!!!!!!!!!!!!!!!!

what is the purpose of changing that WHEN IT WAS WORKING FINE.

i am so disappointed.

and i will simply look for an other app.

i am sorry but the new setting kills the only interest of this app.

MFC is not able to change minimum speed

Maybe instead of calling the newest version the Beta Version (which often refers to an OLD or previous version), could you re-label the "old" version as: "Compatible With: OS 10.6, 10.7, 10.8, and 10.9"

And then below that, provide a link for the "Newest" version which can be labeled "Beta Version. Version 1.2.0 beta 2 for OS 10.10 YOSEMITE".( Or at least SOMETHING to signify that this is the LATEST and NEWEST version). I believe this would make things WAY less confusing for people trying to download the "latest" version? Hope my suggestion helps!! Any thoughts on the matter? Anyone???

Last login: Mon Dec 29 19:58:10 on ttys000
Justins-MBP:~ juzMBP$ /Users/juzMBP/Downloads/runTest/runTest ; exit;
Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
MacBookPro9,2
ioctl CTLIOCGINFO: No such file or directory
logout

[Process completed]

I am running Macs Fan Control 1.2.0 beta 2 but suddenly I am receiving notifications that I need to update my version. I do not see any newer version on your site. Is this a glitch? If not, can you show me where on your site to download the latest version please?

Thank you.

Latest beta not working here. When opening the app, it doesn't launch, and Console says:

"com.apple.xpc.launchd: (com.crystalidea.MacsFanControl.128684[482]) Service exited due to signal: Segmentation fault: 11"

and

"ReportCrash[468]: Saved crash report for MacsFanControl[482] version 1.2.0.0 (???) to /Users/Username/Library/Logs/DiagnosticReports/MacsFanControl_2015-01-02-052020_My-MacBook-Pro.crash"

I did uninstall previous Fan control software, reboot, and reset SMC before trying to install Macs Fan Control. The stable 1.1.12.3 works fine. What should I try next with the Beta?

the beta does not work on mac mini late 2012. the normal version works just fine. do you know why?

Sorry, I'm aware of this problem. Will fix it within a week

i cant get the beta2 to run, simply quits, yet I'm sure I've had it running.

Using Yosemite in Dark mode, hence using the beta.

Trashed all preferences and anything to do with the app, but no difference.
Logs show a crash because of segmentation fault.

Running on iMac 27" i7 + Fusion Drive
10.10.1

any ideas?

mrelwood wrote:Latest beta not working here. When opening the app, it doesn't launch, and Console says:

"com.apple.xpc.launchd: (com.crystalidea.MacsFanControl.128684[482]) Service exited due to signal: Segmentation fault: 11"

and

"ReportCrash[468]: Saved crash report for MacsFanControl[482] version 1.2.0.0 (???) to /Users/Username/Library/Logs/DiagnosticReports/MacsFanControl_2015-01-02-052020_My-MacBook-Pro.crash"

I did uninstall previous Fan control software, reboot, and reset SMC before trying to install Macs Fan Control. The stable 1.1.12.3 works fine. What should I try next with the Beta?

Same here on Mac mini '12 (like themoto also said). I could provide the crashlog if needed.

It's been a few weeks. Are there any updates to the situation? Thanks!

Some points: MacPro 5.1 OSX 10.9.5

- i have to restart the Mac,- because App does not open.
- always asking for a update,- wich guides to a downgrade.
- CPU load rises up to 8% after some time. Only restart it, solves it to 0.7% - 0.9%

No news about the new beta or fix the current one... are you still alive?

Quetzlacoatl
Yes, we're alive. Lots of work, sorry. We don't forget about MFC development. Stay in touch in beta topic.

I'm able to perform the first command:

sudo chown -R root:wheel macsfancontrol.kext

Trying the second command:

sudo kextload macsfancontrol.kext

I get this in my terminal session:

runTest/macsfancontrol.kext failed to load - (libkern/kext) not loadable (reason unspecified); check the system/kernel logs for errors or try kextutil(8).