…finally fixes MacBook Core 2 Duo support. The only reason this was broken to begin with was a typo on Apple’s part.
On November 8, Apple released the new MacBooks with a Core 2 Duo CPU. Typically, Apple takes weeks (sometimes even months) until they publish the developer specifications. With the MacBook, it only took two days. This enabled me to quickly slip in support in the 1.5.2 release.
Or so I thought. According to Apple, the new MacBook had a model identifier of MacBook1,2. It did seem peculiar that they didn’t call it the MacBook2,1, but I figured changes were maybe not notable enough to warrant such a major bump. In any case, I added 1,2 to MenuTemperature’s list, and released it. Over the next few weeks, though, I got reports that it wouldn’t work.
A quick web search confirmed my suspicion: there is no such thing as a MacBook1,2 (the results don’t represent the query), but there certainly is a MacBook2,1. The first person to report it received a replacement file from me, but never responded whether or not it worked. trac might be to blame, in that its notification of ticket changes is quite lacking.
In any case, 1.5.3 is now out, and hopefully, I actually get positive reports of it working now. Meanwhile, Apple still has yet to fix their specifications. Yes, I did send in a report.
Others' Thoughts
Comment on October 10th, 2008 at 2:23 pm
Running on PowerBook G4 Aluminum, 1.25Ghz. OSX 10.4.11. I get the error “No working temperature sensors found. MenuTemperature was unable to find a sensor (ID: PowerBook5,2)” I guess this model has no sensors installed
Comment on October 14th, 2008 at 12:14 pm
Hello, I tried your tool, but unfortunately I get an error “No working temperature sensors found. MenuTemperature was unable to find a sensor (ID: PowerMac3,4)” I have an upgraded g4 digital audio with a ziff from PowerLogix (1.8 ghz) It would be nice to read out the temperatures. thanks.
Your Own Thoughts
I'd love to hear your input. Just try to stick to a few rules:
Before you comment for the first time (or, after you have deleted cookies), you will have to answer a little challenge to prove that you are not a spammer.
Comments are written in Markdown.