Mac OS X on x86 Hardware 2008–2024 Technical Archive
InfiniteMac OSx86 › Leopard 10.5 › Real-time clock running very fast on P6T/i7
3,509 reads · 2009-07-13
Note Leopard 10.5 ASUS P5K / P5Q

Real-time clock running very fast on P6T/i7

I recently installed iDeneb 1.3 and updated it to 10.5.7 on my Asus P6T-based system. The full information can be found on my website. It includes detailed history of what I did. Unfortunately, there seems to be a massive issue with the…

Primary Author
@petrilli Published 2009-07-13
Collection
Leopard 10.5
Archival Footprint
3,509 historical reads · 0 curated field notes (from 3 dispatches) · 2009-07-13
Credited Voices (1)
@petrilli (3)

I recently installed iDeneb 1.3 and updated it to 10.5.7 on my Asus P6T-based system. The full information can be found on my website (blog.am ber.org/2009/07/12/its-alive/). It includes detailed history of what I did.

Unfortunately, there seems to be a massive issue with the real-time clock (RTC). After searching the internet and this forum, the few mentions of it all revolve around fixing busratio=20 in the kernel boot. I've done that, even manually setting it on start. Unfortunately, the system seems to run entirely too fast for the clock.

For example. I rebooted this system at 5:15p and made sure that NTP updated the clock to match what is on all my other machines (and cell phone). It is now 13 minutes later, and the clock is now 15 minutes ahead. Within an hour, it will be 10-15 minutes ahead and continue to go.

If I open the Date & Time Preferences panel, then it will reset the clock to the correct time (via NTP), however it seems to quickly get out of control.

Does anyone have any clues as to what might be causing this? The system is running bone-stock configuration and no overclocking has been done.

Author Updates & Technical Revisions

Follow-up dispatches by @petrilli

Author Update #1 @petrilli 2009-07-13

Addition bit of info

Note that this machine seems to have no issues when it's running with Linux or FreeBSD or Windows XP. As of 6:10p, it's now at 6:24p.

Author Update #2 @petrilli 2009-07-13

Someone pointed me to a resolution around the FSB clock rate. If you install the latest Chameleon v2 software, it automatically detects and compensates.

Problem resolved.

Sources & Contributor Provenance (1 credited usernames · Thread #3366)
UsernameDossier ContributionDispatchesActive Window
@petrilliPrimary Author32009-07-13