I picked up an open box 1.83 macbook pro from an apple reseller. I tried it out in the store checked for any pixel or other issues saw none so I got it. I saved a few hundred because the box had been open. I have had it for a week heat seems to be hot but undercontrol. It is running at 22 degrees c. I have seen it at 40. The only issue is the whine. It is very faint and quit. I can't hear it now but have heard it before in a quiet room. I downloaded quietMBP and set at 40 the whine is gone. The questions is should I take it back due to the whine issue. Is the whine issue a major problem that will damge the machine and cause a service call. I can live with the whine but don't want it to develop into a more serious problem. Any advice.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
1.83 week 12 Macbook pro
- Thread starter tim2006
- Start date
- Sort by reaction score
Whatever the legitimacy of the whine being "within spec" or not, I SERIOUSLY doubt it will actually cause any damage. It's just noisy power circuitry.
If that were a problem, half the desktops on earth would die from it.
I'd say if you have to be in a quiet room and paying attention to even notice, and it's not bothering you, just ignore it. You probably wouldn't have even thought anything of it if you hadn't read all the complaints here.
If that were a problem, half the desktops on earth would die from it.
I'd say if you have to be in a quiet room and paying attention to even notice, and it's not bothering you, just ignore it. You probably wouldn't have even thought anything of it if you hadn't read all the complaints here.
tim2006 said:
WOW!!! When booting cold, the lowest temp I have seen is 35C. Are you sure those temps are correct?
ummm, that can't be. Not even my iBook G4 has been that cool in the 7 months that I have had it. Even my iBook has broken 73C when at 100% processor utalization.
the whine seems to be related to the CPU idle cycles. I dont have a whine now, but when i turn off bluetooth and airport, i get the whine. If it really annoys you that much, do something which uses up a small amount of CPU time. Bluetooth peripherals use up just enough of the CPU to get rid of the whine. If that isnt an option, there are programs which are written to constantly address a small part of the CPU, or you could send one instance of "yes > /dev/null" in terminal.
Unless you're talking about surface temperature that is RIDICULOUSLY cool. Are you using Temperature Monitor? If so, maybe you're looking at the SMART temperature reading, which would be the hard drive. The SMART reading is the default number it shows, and unlike "CPU Core 1" or "CPU Core 2" (which are obviously the processor), it doesn't need an admin password to read it so it's all you'll see if you don't give it one. If this is the case, that's still cool, but at least possible.tim2006 said:
If it really is the processor core temperatures... no. That's seriously not even warm to the touch, and I don't think it's physically even possible unless you woke it from sleep in a cold room about 30 seconds before and it hasn't had time to warm up yet. I don't think even the Apple //c had a processor that ran that cool. 22C is cool room temperature, and that's DEFINITELY physically impossible--the processor is by definition drawing some power, so unless you're in an unheated room deep in the Southern Hemisphere, air cooling simply cannot make it that cool. It's thermodynamically impossible.
So either the number you're talking about isn't really the processor temp, there's something wrong with the software you're using to measure it, or the processor's internal temp sensor is off. The Core Duo's internal sensor being off is rather unlikely, but even if it were it's nothing to worry about--the MacOS doesn't use that number for anything, it has a sensor on the motherboard that it uses to decide when the fan is necessary. There's currently no software that can read that, but it's probably fine, or the fan would be running full blast all the time.