Posts Tagged ‘undervolting’

Too Good to Be True? My MacBook Pro: First Cool, Now Quiet

Friday, May 15th, 2009

This will be a brief coda to a couple of recent posts in which I related how I finally solved an ever-worsening (OS changes?) problem of overheating on my first generation MacBook Pro. See “What a Relief! MacBook Pro Overheating Problem Cured—Really” and “Can’t Boil Water With Vista on My MacBook Pro Anymore” for the details. The solution turned out to be undervolting—setting cpu operating voltages at values (determined by experiment) below the overly conservative ones set at the factory. A great little ambien piece of software called CoolBook enables one to do that on the Mac. A similar program (RMclock) is available for Windows.

I can report that I have encountered neither high temperatures nor computer instability since adjusting voltages lower with CoolBook. After a couple of weeks of stress-free lower temperatures, I realized that the previously necessary evil of the constant droning of the MacBook Pro’s cooling fans was no longer necessary. In my earlier efforts to control temperature I had installed a System Preferences utility called Fan Control. This allowed me to set the minimum temperature at which the fan speed would start ramping up and the rate at which it would increase with temperature. This was not a solution for sustained operation at the highest default voltage used when the cpu was running at maximum speed, but I think it did keep things cooler than what Apple’s normal fan speed algorithm did.

It may seem funny that Apple would have such high operating voltages coupled with such puny fan cooling; but I think we have reason to believe that Steve Jobs hates fan noise (I’m with you there, Steve), perhaps beyond reason. I remember buying a third-party fan that sat on top of my first Mac, the mighty one-megabyte-RAM Macintosh Plus. Word was that it was needed to prevent premature death of the convectively cooled Mac. I can imagine Steve telling the engineers to get rid of that fan noise on the MacBook Pro, or else.

The fans on my machine, even though one of them was relatively new, having been replaced under AppleCare when my original hard drive croaked (Fatal But Survivable: A Hard Drive Transplant Story), seemed to have gotten noisier over time, from overuse I suppose, so they were annoying me more. Why not get rid of Fan Control? Removing it from the System Preferences Panel wasn’t hard (Ctrl-click and make selection), but this merely put the fan speed versus temperature profile out of my control, while leaving the last one set by Fan Control in effect. I saw one unfortunate on MacUpdate warning people not to install Fan Control because it permanently changes the fan settings. This is fortunately not true, but the folks that make Fan Control should probably do a better job of letting people zithromax know how to completely uninstall it. Here is the rest of the procedure: remove the following files and folders (both on your start disk)— /Library/StartupItems/FanControlDaemon and /Library/PreferencePanes/Fan Control.prefPane.

In order to have a way of monitoring temperature and fan speed I went back to running smcFanControl, a program that only allows one to set the minimum fan speed. I used it to set the minimum speed back to 1000 rpm, down from the Fan Control minimum of 1600 rpm I’d been enduring. This is really quiet!

Having smcControl running enables me to step in to raise the fan speed if necessary. Shades of the past: yesterday I was reinstalling the iPhone SDK as part of a long battle (probably not to be related here) to be able to test my in-development iPhone app on an iPod Touch, when I noticed the smcFanControl temperature reading said 90° C, while the fans were still whirring away at less than 2000 rpm. I used smcFanControl to raise the minimum speed much higher manually, which had the desired result. When that taxing installation procedure was over, I set the fan antabuse speed back to 1000 rpm.

Now that I finally have what I thought I was getting modafinil when I bought the MacBook Pro, this should be the last I’ll have to say on the subject of temperature control and fan noise. Peace.

Can’t Boil Water With Vista on My MacBook Pro Anymore

Tuesday, May 5th, 2009

It was a little over a year ago that I got Windows Vista up and running on my first-generation MacBook Pro by means of Apple’s Boot Camp, only to discover that it ran hot—so hot that it seemed pretty worthless. I believe that post (Vista on My MacBook Pro Is Hot—Boiling Hot!) has brought this blog more visitors than any other, which I count as solid evidence that many other Mac users have encountered the same problem and have gone searching on Google for a solution.

Unfortunately, all I could offer my fellow sufferers was the knowledge that they were not alone, but now I have a solution for them, based on the same “undervolting” technique I finally discovered to solve the even greater overheating problem I had encountered running under Mac OS 10.5.6, where temperatures would climb over 115° C and cause the computer to shut down unless I exited certain programs (rendered useless) or web sites in time.

I recently wrote What a Relief! MacBook Pro Overheating Problem Cured—Really, in which I told of finding a program called CoolBook to be the answer to my overheating problems. The basic idea behind the solution is that the computer’s factory-default voltages, which essentially determine the operating temperature, are for the different cpu clock frequencies substantially higher than they need to be. CoolBook enables one to reset these voltages to lower values, thus gaining much cooler operating temperatures, most importantly for the highest frequency, where sustained heavy-duty computing can lead to overheating. Undervolting with the help of CoolBook really gave me back the full use of my MacBook Pro. I refer anyone having similar problems to that recent post. The procedure for finding the lower voltages your particular computer can live with involves a fairly lengthy trial and error period, but it only needs to be done once.

I mainly wanted Vista on my Mac in order to test the Vista-compatibility of the Windows versions of my science education programs, OnScreen Particle Physics and OnScreen DNA. Having done that, and not having a new version to test, I could easily live without Vista; and the overheating problems encountered under 10.5.6 were much more serious for me. Nonetheless, it was an ongoing irritation in the back of my mind that Apple’s promise of being able to run Windows with Boot Camp was really a false one so long as the temperature went up so high under normal use. Thus it was natural to ask if I could apply the same undervolting procedure under Vista to eliminate the heating problem there as well.

Of course, CoolBook was no help for running Vista, since it is a Mac program, but a Google search for undervolting led me to a Windows solution. If you Google with the search string “undervolting guide,” you will find The Undervolting Guide, which tells you everything you need to know to undervolt under Windows. There is a free downloadable program called RMclock that allows you to reset the default voltages, just as CoolBook does for the Mac. The guide is written under the assumption that you have no previous information about temperature or the lower voltage limits at which your computer can operate stably. It leads you through a procedure similar to what I outlined in my post on Mac undervolting. Since I had already gone through this under Mac OS X and couldn’t see any reason why the lower-limit voltages would depend on the operating system, I assumed my results would still hold under Vista. The whole procedure seems a lot easier on the Mac side, so I would recommend anyone trying to cool down Vista on a Mac to determine lower-limit voltages under the Mac OS. Be sure to write down the lower-limit voltages you have found before booting into Windows to set voltages there.

I went directly to the RMclock instructions in the guide, skipping the parts dealing with stressing the computer at different voltages. You need to follow the RMclock instructions closely, as the procedure is considerably more complicated than what it is for CoolBook, there being several steps to go through before you reach the point of actually setting voltages. Things look quite a bit different too. Instead of showing the frequencies in physical units of MHz, RMclock shows “multipliers,” which are presumably the factors by which some reference frequency (unspecified) is multiplied to obtain the actual frequency. I just made the reasonable assumption that the maximum multiplier corresponded to the maximum frequency (2.004 GHz in my case) and set the voltage to what I had previously determined was sufficient under Mac OS X for my MacBook Pro. For the other multipliers I scaled accordingly, but chose voltages on the conservative side, i.e, a little higher, just to be safe. For keeping the maximum temperature down, it’s really only the top frequency voltage setting that matters much anyway. Lowering the other voltages below that used for the highest frequency just gives you a lower average temperature and longer battery life.

Did it work? Yes, I can run the most complex simulations of OnScreen DNA at a “cool” 80° C, instead of the previous 100° C. Undervolting has made it comfortable for me to run Vista on my MacBook Pro, so I don’t feel cheated anymore. Maybe I’ll actually use Vista for something other than testing my software now.

What a Relief! MacBook Pro Overheating Problem Cured—Really.

Friday, April 17th, 2009

Just in case anyone has arrived here desperate for a solution to MacBook overheating, let me put it in this first sentence: CoolBook is what you need. I last wrote about the ever-worsening tendency of my first-generation MacBook Pro to go into a runaway heating mode back on November 22 of last year in an optimistically titled post called New Firefox Cures Overheating? I knew better than to be confident that something as simple as a browser upgrade could have taken care of my overheating problems, but I wanted so much to believe it. The Firefox upgrade probably did alleviate overheating associated with Firefox, but before long it became obvious that it was only a small part of the problem.

Since my lonely corner of the blogosphere receives several visits daily from unfortunates with the same overheating problems (I can tell from the logs of their visits: Google search terms), I’ve felt bad that all I was really offering them was the knowledge that they were not alone, even if Apple has never said anything about the problem. My computer got a slight amount of symptomatic relief by using the Fan Control utility, which goes into the System Preferences panel. With Fan Control, I was able to control the fan speed versus temperature profile to some degree, but the maximum fan speed, no matter what temperature it kicks in at, is no match for a true runaway heating episode.

The overheating problem only got worse for me with the 10.5.6 OS upgrade. Some apps became completely unusable. For example, Winclone, a great program for backing up your Boot Camp Windows partition to a compressed file on your Mac partition, thus allowing you to have a Windows backup on your Time Machine drive, would reach 100° C before 5% of the Windows partition had been read! The temperature never reached a plateau, and the high temperature caused a shutdown the one time I decided to let it keep going and hope for the best. I tried reverting back to an earlier version of Winclone, which had never caused a problem before, but that didn’t help.

The funny thing was that the runaway heating often seemed to be associated with periods where one might expect the computer to be cooly twiddling its thumbs. For example, EPSON Scan, the software that runs my excellent Epson Perfection 2450 Photo Scanner, would operate at a reasonable temperature when actually scanning, but once I clicked to tell it that, yes, I wanted it to scan another page, it seemed to go into a rage for some reason, and I heard, not the purr of a resting Mac, but the ever loudening buzz of the cooling fans, which were vainly trying to get it to cool down. Click to begin the next scan, and the temperature would drop. Similar odd behavior was observed with the Microsoft Office upgrade installer. Once the installation, which occurred coolly enough, had finished, the fans would start to buzz; and quitting the installer was the only way to bring the temperature back down.

There were also certain websites that would cause both Safari and Firefox to get a fever that ramped up rapidly and could only be stopped by jumping to another site. This could happen on certain sites without any video or anything I’d seen associated with the problem before. A web site featuring high school athletic event schedules was one such innocuous looking site with pyromaniacal pages.

At some point a few weeks ago Safari became completely useless, as it would invariably start up the runaway heating ramp within seconds after launch. How can it happen that a program permanently changes its behavior? I don’t know, but reinstalling with a freshly downloaded copy of Safari 3.2 did not help. Ordinarily I wouldn’t have tried the Safari 4 beta, but I had nothing to lose at that point, so I installed it, and it ran normally. I believe running Safari 4 instead of its formerly stable predecessor actually caused an overall lowering of the average temperature at which my MacBook Pro ran, but it by no means cured the overheating problem. I was pretty well resigned to having it indefinitely until the day before yesterday, when I got my hopes up again.

I can’t remember how I came across CoolBook, but I downloaded and installed it yesterday, and it has really solved my problem. Hopefully it has no undiscovered side effects. How does CoolBook work? In a word: undervolting. CoolBookController (to use the program’s full name) allows you to scale down the operating voltages assigned to different frequencies, thus allowing the computer to run at a cooler temperature without reducing the computing power, which depends on the frequency. Apple has set a default table of these voltage and frequency pairs that is quite conservative. Chips vary, and Apple must have chosen the voltages so that almost no cpus will be unstable for any frequency. This makes life easier for Apple, from the warranty standpoint no doubt, but in the case of the laptops it sells, it makes for a lot of unnecessarily high operating temperatures. So why doesn’t Apple do a chip-by-chip calibration to minimize the number of hot MacBooks? Well, it probably took me at least two hours to get CoolBook all set up for my MacBook Pro. First, it takes a while to figure out what to do, though everything you really need can be found in the instructions.

Then it’s just a matter of trial and error to determine what is the lowest voltage you can use with a given frequency on your machine. A utility called CPUTest is provided to verify cpu stability for the voltage/frequency combination you choose. This utility evidently does uninterrupted heavy-duty computations until it catches an error or until you decide it’s run long enough to call it a successful combination. The documentation recommends running the test for at least ten minutes; so you can see how an hour can easily be used up. In my experience, failures usually occurred in the first minute or so though.

I followed the recommendation to determine the maximum frequency at which my machine could run without trouble at the lowest voltage setting of 0.95V. Following the result reported in the documentation I tried 1.837 GHz for this voltage and got an immediate black-screen shutdown. i should have known mine couldn’t match that. I cut the trial frequency way down and worked my way up. I found 1.503 GHz was the highest stable frequency. Apple’s default frequency for the lowest voltage is 1.0 GHz.

Here are the frequency/voltage pairs that my formerly hot MacBook Pro ended up with (original Apple voltage settings in parentheses):  1.503 GHz, 0.95 V (1.1125 V); 1.67 GHz, 0.9625 V (1.1625 V); 1.837 GHz, 1.0125 V (1.2125 V); 2.004 GHz, 1.0875 V (1.2625 V).

How much difference do the lower voltage settings make? A very big difference in operating temperature for my machine. It has cool (58° C) and silent operation during times of cpu-loafing such as the computer is experiencing while I type this piece. During the stress of the CPUTest, I saw the temperature reach 98° C for the 2.004 GHz frequency, but it stopped there, and I know from experience it would only have been stopped by a computer shutdown at 115° C using the Apple default voltage.

The fix of the overheating problem still doesn’t explain why the computer thinks it needs to go to to maximum frequency for no apparent reason. CoolBook’s cpu-frequency monitor allows you to see what the current frequency is. Sure enough, it goes to the maximum 2.004 GHz on that baseball schedule page. I think I may just now have seen the culprit though. That page has one of those continually scrolling stock-ticker-like message things, which perhaps eats up computer cycles somehow. If that’s it, it doesn’t even have to be visible to cause the effect.

I also see that gathering permissions info in Disk Utility throws it into the highest frequency mode, as I would have expected from previous temperature rise observations. Why is that, I wonder? Quitting Disk Utility in midstream had no immediate effect on the computing frequency though. It’s stuck there at the highest frequency, though no running program is doing anything I’m aware of. I think this must really be an OS X issue. Fortunately, instead of being in the upper nineties, the temperature is around 70° C. That’s still high enough to cause an annoying fan noise though. Already complaining!

Anyway, the $10 I spent on CoolBook was nothing for the amount of relief it has brought. I’d have spent ten times that much to be guaranteed a solution to the overheating problem, which was ongoing and had become quite limiting, witness my not being able to run Winclone. This time, there really has been a solution. I successfully made a backup with Winclone yesterday at around 70° C. Unless Apple breaks CoolBook with its next update (and the danger of that will give me pause), I’m set for being a normal Mac user for the foreseeable future. CoolBook is evidently the creation of Magnus Lundholm and is found on a web site with an se domain. Hats off to the guy in Sweden!