Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I just backed up a 1 gb .psb file via time machin. To my g tech fw/USB/esata drive using the FireWire interface and my CPU temps went from 37 to 39 seems an ok rise but should my CPU be at 39 just copying files in the middle of the uk winter?
 
I just backed up a 1 gb .psb file via time machin. To my g tech fw/USB/esata drive using the FireWire interface and my CPU temps went from 37 to 39 seems an ok rise but should my CPU be at 39 just copying files in the middle of the uk winter?

It's a four or eight core server processor, stop complaining. 39C is fine.
 
I just backed up a 1 gb .psb file via time machin. To my g tech fw/USB/esata drive using the FireWire interface and my CPU temps went from 37 to 39 seems an ok rise but should my CPU be at 39 just copying files in the middle of the uk winter?

Thats fine.

The CPU actually has to do something when copying files, and besides 2/3C variations could very well be within the CPU bounds of error.

Mine is sitting at 26C atm with Safari, MSN and Mail open...
 
Just out of curiosity, did the update change anything in terms of the fan control?

I'm currently converting a video file (1600% CPU usage), core temps are 67 to 81° and the fan speeds remain absolutely stable at their minimum (600-1100).

Seems as if I have to install SMC fan control again since SMC reset, firmware update and the audio update did not make the fan control of my machine working again.
Any suggestions?
 
I've updated the Fan Control software as follows:

1. Minimum fan speed is 500.
2. Fan speed should return to minimum level now as a line of code was stopping it for some strange reason.
3. Permissions should be fixed, but then again, maybe not.
4. Fan speeds will ramp up quicker and then reach equilibrium slower, so less oscillations in the speed.

http://www.concorde-photos.co.uk/stuff/MP2009CPUFancontolV0.7.zip

CR.

Same strategy here and I can't recommend it enough. System remains quiet during low workload states, with the fan speed increasing more aggressively than Apple's profile under load.

I'm not sure if it's just me, but I am loving my Mac Pro again...
 
Same strategy here and I can't recommend it enough. System remains quiet during low workload states, with the fan speed increasing more aggressively than Apple's profile under load.

I'm not sure if it's just me, but I am loving my Mac Pro again...

Me too, its like having a new machine - thanks for the fan control app.
 
Mac

Smacman wrote:
I'm not sure if it's just me, but I am loving my Mac Pro again...

I've loved this machine from the start. It's run flawlessly, my best Mac experience ever. But the company... that another story altogether.

I'm still amazed this was addressed by Apple at all. I thought it was hopeless to get through to them. To influence them at all.
I'm still suspicious of them anyway though, and that will last for a long, long time.

To have the fix not wait for 10.6.3,... does anyone think that says something about urgency? Anyone think that before a company starts selling a new model that it's got to get rid of the bad press about the older model first?
Who'd want a 2010 having heard about all this? Ok, I would,... but what normal person would?
 
I've updated the Fan Control software as follows:

1. Minimum fan speed is 500.
2. Fan speed should return to minimum level now as a line of code was stopping it for some strange reason.
3. Permissions should be fixed, but then again, maybe not.
4. Fan speeds will ramp up quicker and then reach equilibrium slower, so less oscillations in the speed.

http://www.concorde-photos.co.uk/stuff/MP2009CPUFancontolV0.7.zip

CR.

Does this let you set the minimum fan speeds even below the defaults ?
Minimum 500 like you said is way below Apple min, or am I wrong ?
 
Yes.

And I'd like to know if anyone has tested USB for problems since the fix. Statements such as "Audio is fixed" is too vague, as it doesn't indicate if it's using the on-board audio chip, USB or FW audio devices. I'm just hoping for some clarification.

I finally got a chance to check out the update tonight... The fix works great for my USB audio interface. My idle temps are now 20-deg C cooler than before and the connection of the USB I/F and or playing music makes no difference to temps. :)
 
I finally got a chance to check out the update tonight... The fix works great for my USB audio interface. My idle temps are now 20-deg C cooler than before and the connection of the USB I/F and or playing music makes no difference to temps. :)
:cool: Good to hear, and thanks. :)
 
Does this let you set the minimum fan speeds even below the defaults ?
Minimum 500 like you said is way below Apple min, or am I wrong ?

500 RPM is 100 below the default 600RPM.

The CPU BOOST fan usually runs at 142.5% of the intake/exhaust speed but has a min speed of 800 that I am not altering.

Idle temps are barely effected when running at 500 vs 600RPM!
 
Yes.

And I'd like to know if anyone has tested USB for problems since the fix. Statements such as "Audio is fixed" is too vague, as it doesn't indicate if it's using the on-board audio chip, USB or FW audio devices. I'm just hoping for some clarification.

I have quad 2.66 and E-MU 0202. It's fixed.

The idle temp for the machine is 39C. (CPU from iStat) I used to run at 69-71C with audio. Now it's something like 42C.
 
I'll try it out :eek:
How do you remove it just in case ?

Very easy,

Three files in:

/Library/PreferencePanes
/Library/Startup Files/FanControlDaemon <-- Delete the folder

Restart and thats it IIRC.

I think there is a file in Preferences too if you want too look for it.

Intake: 954
Exhaust: 953
BOOSTA: 1360
Heatsink Temp: 45C
Core Temps: 70C

Lovely!
 
Interesting. With BOOST A running at 800 instead of 856 rpm the "fridge sound" is gone. Completely eliminated all resonance from the machine, it used to make this RRRRRRRRRmmmmmmmmmRRRRRRRRRRRRmmmmmmmmRRRRRRRRRRRRmmmmmmmmRRRRRRRRRRRRRRRmmmmmmmm pulsating noise which I got used to by now...
 
Unfortunately, I still have to use Leopard right now, so the fix that Apple have just released doesn't work for me because it covers only Snow Leopard.

can you try this?


save copies of your AppleHDA.kext and IOPlatformPluginfamily.kext from System/Extensions


then install these with Kexthelper:

http://krull.se/audiofix.zip

it will do exactly the same as Apple's update but it will (hopefully) work on leopard.
 
They wrote a new audio and io driver, something a little bit outside my abilities. I did some attempts to use other audio drivers and that solved the issue but then sound did not work properly :p


Anyway Id like someone with leopard to try what I mentioned in my last post, if that works at least I can have a Leopard fix to release :p
 
Hey everyone on the thread. First of all thanks to everyone for bringing this to my and apple's and countless other MP 09 user's attention. I have been following the thread for the past month and ran the same diagnostics and encountered the same problems as everyone else (of course).

I am glad that there is a fix (which I have confirmed as working on my machine as well). What I am not glad about is the fact that it took so long for Apple to respond in light of such hard evidence. Also, confounding is the fact that the response came so swiftly after a little media light was shed on the matter. It is indicative of Apple's priorities to say the least.

Here is my biggest problem with all of this:
Apple let its power users suffer unnecessary wear and tear on their machines, pay higher utilities at the hands of their machines, and (this is the biggest issue for me) lose countless hours of productivity *read money* due to this "bug" or flaw. I feel like there should be recompense beyond just a silent fix. The machines were effectively lemons for almost a year, not operating as advertised or expected and apple makes no acknowledgement of this issue?

So while I am happy that it is fixed, and indeed I can tell the difference, I am still very upset over this problem. Anyone else?
 
Hey everyone on the thread. First of all thanks to everyone for bringing this to my and apple's and countless other MP 09 user's attention. I have been following the thread for the past month and ran the same diagnostics and encountered the same problems as everyone else (of course).

I am glad that there is a fix (which I have confirmed as working on my machine as well). What I am not glad about is the fact that it took so long for Apple to respond in light of such hard evidence. Also, confounding is the fact that the response came so swiftly after a little media light was shed on the matter. It is indicative of Apple's priorities to say the least.

Here is my biggest problem with all of this:
Apple let its power users suffer unnecessary wear and tear on their machines, pay higher utilities at the hands of their machines, and (this is the biggest issue for me) lose countless hours of productivity *read money* due to this "bug" or flaw. I feel like there should be recompense beyond just a silent fix. The machines were effectively lemons for almost a year, not operating as advertised or expected and apple makes no acknowledgement of this issue?

So while I am happy that it is fixed, and indeed I can tell the difference, I am still very upset over this problem. Anyone else?

Honestly I think this is a bit of an overreaction. Using myself as an example, playing audio while maxing out my quad core CPU led to a CPU temperature of about 60-65C. This is well within the operational parameters, and I'm not at all concerned about any loss of my Mac Pro's useful life. By the time my Mac Pro's CPU fails, it will probably have been sold two or three times.

As far as loss of productivity is concerned, can you provide actual examples of lost revenue? This is an impossible case to make against Apple.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.