|
Release Notes |
When using a MacBook Pro of the "Early 2011" model series (having identification codes beginning with "MacBookPro8"), the system might return invalid hardware information: Apple computers of the model series MacBook Pro 13-inch (Early 2011), MacBook Pro 15-inch (Early 2011), and MacBook Pro 17-inch (Early 2011) are originally shipped with a special release of Mac OS X, known as version 10.6.6 Build 10J3210, and the firmware version MBP81.88Z.0047.B04. Both components appear to be immature, not supporting all aspects of the MacBook Pro computers correctly yet. The systems might return incorrect information about technical details of the processor package and contain invalid entries in their System Management data. Applications such as Hardware Monitor or Temperature Monitor depend on the operating system to respond correctly on hardware information requests. The following details could be display incorrectly: number of processor cores per processor package, system bus clock frequency, bus widths of memory chips, onboard devices, available expansion slots. This list might not be complete.
Workaround: There is no known workaround. Apple might or might not resolve these problems with future versions of Mac OS X and the MBP81 firmware. It is Apple's policy not to comment on any technical details of Intel-based computers.
When running monitoring utilities of other vendors which also access S.M.A.R.T. features of hard drives, Hardware Monitor and Temperature Monitor can be blocked from accessing S.M.A.R.T. readings: Certain low-quality monitoring applications of third-party vendors are known to reserve exclusive access to the S.M.A.R.T. interfaces of hard drives. When running such applications, neither Hardware Monitor, nor Temperature Monitor, nor other applications, like Apple's Disk Utility or System Profiler, can access any S.M.A.R.T. features until the misbehaving application is quit. S.M.A.R.T. sensors or probes show a value of "---", the Drive Overview window shows "S.M.A.R.T. status: not available".
Workaround: Either disable S.M.A.R.T. monitoring in the third-party application, or contact its vendor to have the problem resolved. It is bad practice to use exclusive access to the S.M.A.R.T. interfaces of hard drives.
After waking from sleep mode, the Main Logic Board Air Inlet sensor of some Power Macintosh G5 Dual Core systems shows negative or no readings: When a dual core PowerMac G5 wakes from sleep mode, the temperature reading of the air inlet sensor may show incorrect values.
Workaround: This is a known defect in specific versions of Mac OS X Tiger. This particular sensor is not correctly woken up by the operating system. We have made Apple aware of this problem and hope they will resolve it in future versions of Mac OS X. In the meantime, you can restart the computer to reset the sensor hardware, or disable data acquisition for this sensor in the preferences of the application.
Computers of the model series "iMac (Late 2006)" may show unusually high readings for the CPU A Current Sensor: When you are using an Apple iMac with model identification "iMac5,1", the values displayed for the current (amperage) sensor of the CPU appear to be too high and inconsistent with CPU power readings.
Workaround: This is a known problem with the System Management Controller (SMC) used in this particular model series. (Other iMac series are not affected by this problem.) It is unknown if Apple will release an SMC firmware update to fix this problem. You might like to disable data acquisition for this sensor in the preferences section of the application.
In certain configurations, the entry "Logitech LCD Manager" may not be displayed in the list of LCD devices, even if a Logitech product with LCD support is connected to the computer (Hardware Monitor only): Although you have attached a Logitech LCD product and installed the Logitech driver software, no device entry for this product appears in the preferences panel of Hardware Monitor. The display does not work and cannot be configured.
Workaround: The Logitech LCD Manager software does not start reliably under specific circumstances. In this case, applications are not able to see or connect to the respective LC displays. Not only Hardware Monitor, but all applications trying to use LCD-enabled Logitech devices are affected by this problem. Try the following to start the LCD Manager manually:
Logitech might resolve this problem in future versions of their driver software.