Clock running fast

[hiroo]

i'm not sure if this was happening before, but after the new 10.4.8, my clock is running fast. the clock as in the real time AM/PM clock in the menubar. so the clock on the computer gets progressively ahead of the actual time.

 

if i open the date and time pref panel, ntp will update the clock but it will start drifting again.

 

i'm starting this thread to see if we can track down this problem.

 

any suggestions for workarounds, like some way to set the ntp daemon to reset the clock every 5 minutes?

 

beyond that, any clues for how to fix this for real, as it, the clock runs at the speed it should?

[Rammjet]

If you are running 10.4.8 with the Semthex kernel, you need to set your FSB speed at startup.

 

At boot or in the boot.plist (under Kernel Flags) you need to set fsb (frequency)

 

Type fsb=xxx (where xxx is a number like 133, 166 or 200)

 

fsb is a frequency

fsb (freq) = fsb (speed) / 4

 

To find your fsb (speed):

 

(OSX) System Profiler -> Hardware -> Bus Speed (fsb speed)

(Win) PC Wizard -> Mainboard -> Chipset -> freq and speed avail

 

So, if your FSB (speed) is 800, then FSB (freq) = 800 / 4 = 200. You would set fsb=200 at boot or in boot.plist.

[hiroo]

i've done a ton of searching and can't find an exact format for how to enter this into the Boot.plist.

 

I'm using the semthex kernel and a Conroe C2D E6600 so i think my FSB is 266Mhz

 

My boot.plist says:

<key>Kernel Flags</key>

<string></string>

 

do I put the fsb=266 in between the string tags?

[fireshark]

yes supposedly

[hiroo]

is there any way to confirm if the fsb value has been taken correctly?

 

i put in fsb=292 (forgot that i put in a slight overclock) and the clock appears to be running ok now. but is there any other way to confirm it more directly?

[jonokti]

you probably overclock the fsb unless you are using core2 and adjusted the multiplier just match it to the fsb like in your bios. And even if you changed the multiplier just match the fsb you should correct.