Jump to content

Mavericks AMD Clover installation time/clock runs fast.

mikey1953

By mikey1953,
in OSx86 10.9 (Mavericks)

 Share
11 posts in this topic

Recommended Posts

mikey1953
mikey1953
Posted
Posted

I have had my AMD (see signature) Mavericks 10.9.4 installation up and running for a while now. I initially used Chameleon, and had no issue with the time/clock running fast, no issues at all. I switched to Clover, and now the clock gains about an hour per day. Opening Date & Time in System Preferences successfully corrects it, of course. I read how to enter a custom boot flag in Clover Configurator. My CPU speed is 3.7 GHz, with a multiplier of 18. So I entered BusSpeedkHz=205555 in CC. The clock still runs fast. Geekbench 32-bit runs ok, Geekbench 64-bit crashes and forces a restart. I didn't have these problems with Chameleon.  Any suggestions before I switch back to Chameleon?

mikey1953
mikey1953
Posted
  • Author
Posted

Thanks for the input, but the problem can't be the busratio. I cloned the HDD first and kept Chameleon as the bootloader on the clone,  and I have a HDD of a previous installation of 10.6.8 and Chameleon. When booting in verbose mode, both clearly show the CPU speed, the multiplier, and the bus speed and it is the same in both. That is where I got the info that I entered in CC. Both of those installations are stable, neither have the time/clock issue, and that busratio is reported and works in SL and Mavericks using Chameleon.  Why would the busratio change when using Clover instead of Chameleon? Why would it change when using Mavericks instead of Snow Leopard? I don't see how it could or would. 

ameris_cyning
ameris_cyning
Posted
Posted

Thanks for the input, but the problem can't be the busratio. I cloned the HDD first and kept Chameleon as the bootloader on the clone,  and I have a HDD of a previous installation of 10.6.8 and Chameleon. When booting in verbose mode, both clearly show the CPU speed, the multiplier, and the bus speed and it is the same in both. That is where I got the info that I entered in CC. Both of those installations are stable, neither have the time/clock issue, and that busratio is reported and works in SL and Mavericks using Chameleon.  Why would the busratio change when using Clover instead of Chameleon? Why would it change when using Mavericks instead of Snow Leopard? I don't see how it could or would. 

 

Its the most common reason why that happens, thats why I always start there first.

 

Secondly, what kernel are you using? The latest one released by Broyna has corrections for timer issues.

 

Thirdly, have you tried booting with -cpuEFI?

 

Fourthly, do you have VoodooTSCsync.kext installed?

mikey1953
mikey1953
Posted
  • Author
Posted

ok, I appreciate your attention...

I believe I am using the latest Bronya kernel for 10.9.4/AMD : Darwin Kernel Version 13.3.0: Fri Aug 22 21:44:24 MSK 2014; root:xnu-2422.110.17_by_bronya/BUILD/obj/RELEASE_X86_64

But that shouldn't be the problem, because the same kernel worked fine for 4 months under Chameleon!

No, I haven't tried the -cpuEFI flag...

I assume you mean VoodooTSCSyncAMD.kext? This issue is with my AMD, not my Intel. ( I have both platforms, per my signature). I read about it, but all sources say it is for older AMD cpus, and isn't needed for Phenom II cpus K8 or newer. Mine is K10.

 

Once again, I never had these problems using Chameleon - and the ONLY thing I changed was switching from Chameleon to Clover.

 

Why would I need the VoodooTSCSyncAMD.kext under Clover and not Chameleon?

Why would everything be fine with Chameleon on both 10.6.8 and 10.9.4?

 

So, I think I'll try the -cpuEFI flag first.

 

I will report back, thanks.

ameris_cyning
ameris_cyning
Posted
Posted

ok, I appreciate your attention...

I believe I am using the latest Bronya kernel for 10.9.4/AMD : Darwin Kernel Version 13.3.0: Fri Aug 22 21:44:24 MSK 2014; root:xnu-2422.110.17_by_bronya/BUILD/obj/RELEASE_X86_64

But that shouldn't be the problem, because the same kernel worked fine for 4 months under Chameleon!

No, I haven't tried the -cpuEFI flag...

I assume you mean VoodooTSCSyncAMD.kext? This issue is with my AMD, not my Intel. ( I have both platforms, per my signature). I read about it, but all sources say it is for older AMD cpus, and isn't needed for Phenom II cpus.

 

Once again, I never had these problems using Chameleon - and the ONLY thing I changed was switching from Chameleon to Clover.

 

Why would I need the VoodooTSCSyncAMD.kext under Clover and not Chameleon?

Why would everything be fine with Chameleon on both 10.6.8 and 10.9.4?

 

So, I think I'll try the -cpuEFI flag first.

 

I will report back, thanks.

 

Just making suggestions.

 

Clover and Chameleon are two completely different bootloaders. Dont expect the two to work just alike.

mikey1953
mikey1953
Posted
  • Author
Posted

I understand that they are two completely different bootloaders. All sources say that Clover is supposed to be better, though. I do appreciate your suggestions... I can't wrap my head around why if Clover is supposed to be superior, it has introduced a problem that didn't exist before in Chameleon.

I have experimented with different bus ratios, and the resulting info I enter as a custom flag in Clover.

 

Now, CPUID in Windows shows a cpu speed of 3716.36, multiplier of 18.5, bus speed of 200.864. I tried that info in CC, clock still runs fast.

AIDA64Extreme shows a cpu speed of 3716, multiplier of 18.5, bus speed of 201. I tried that in CC, clock still runs fast.

 

Now, in my system.log, it shows: FSB Detection: from BIOS calculated Mult_N2 18, cpuFreq 3700000000. That means BusSpeedkHz=205555, which is in CC in the config.plist that I uploaded earlier, and is the config file I am currently booted into.

 

As far as the two working alike, what I would expect is that the clock runs accurately in both ! LOL ! My main concern is if this will affect my DAW timing.

I will try the -cpuEFI flag, and/or the TSCsync kext. I'll report back, thanks again.

mikey1953
mikey1953
Posted
  • Author
Posted

I have tried everything. No luck. I have a feeling I have run into unknown issues with the combination of Mavericks, Clover, and AMD. There were no issues whatsoever with Mavericks, Chameleon, and AMD. I  ran every kext and cache utility. I have  tried TechTool, Drive Genius, DiskWarrior. Every combination of busspeeds and kexts and flags.

Spent hours googling.

I guess if it ain't broke, don't fix it. I guess I shouldn't have tried.

Everyone was saying Clover is superior. Well, A Chameleon in hand is worth a Clover in the bush. And the grass isn't greener.

I'm going back to Chameleon. My first love.

Thanks for the suggestions. 

mikey1953
mikey1953
Posted
  • Author
Posted

Ok now. In my last reply on this  post (that I have since deleted) I thought the problem was solved, so I marked it solved. However, after leaving the computer on for a day, the clock is fast again. But not near as fast as it was.

And, I discovered that my Intel was doing the exact same thing. I use Clover on the Intel, and boot into Mavericks rather than Yosemite, when I use my DAW because my MBox 2 Pro (firewire) is not supported under Yosemite (yet).

 

So, I found myself getting really mad and frustrated. After a shower and some hot cocoa, I decided to look for a solution elsewhere....

 

I guess it was easy to get hung up on the idea that since it is a Hackintosh machine, the problem must be with the busratio, or the bootloader, or the config.plist, or the chameleon.boot.plist, or the fact that one computer is an AMD. We were barking up the wrong tree.

 

Voila! I found the true problem and solution!

 

It is a bug in Mavericks that Apple knows about, but hasn't addressed yet.

 

I found the answer on the Apple Support Communities forum :

 

"  Tim JervisJan 26, 2014 5:21 PM 
Re: Clock runs slow when I leave iMac on all the timein response to JDW1

I have had a similar problem, the clock was running slow on a Mavericks MacBook Pro I look after. After trying out several leads, one solution that worked was to change the value of the "Set date and time automatically" field in the System Preferences -> Date & Time -> "Date & Time" tab. Editing the text in the field from (in my case) "Apple Europe (time.euro.apple.com.)" to "time.euro.apple.com" fixed the problem for me.

 

It appears that the text in this field gets written almost verbatim into the /etc/ntp.conf file, which is then used to look up the time servers. Not only does "time.euro.apple.com." lead nowhere (due to the trailing "."), but Mavericks will even add "Apple" and "Europe" into the file. The end result is the time system appears unable to get a time fix, and so the clock time drifts, uncorrected.

 

If you are in Japan, you might want to try "time.asia.apple.com" in that field. The key thing is to avoid the trailing ".". Just change the text in the field an close window.

 

I should add that this wasn't the only step I took to debug my slow clock issue. Other steps included deleting and re-creating the /etc/ntp.conf file and exploring the "pacemaker" process. However, I don't think these steps were necessary in the end and simply adjusting the text in the field above should suffice. I could be wrong.

 

Needless to say you might have a different issue and this might not help. Good luck!

 

Tim  ".

 

So - The only thing I needed to do was correct the entry in the "set date and time automatically" field to > (time.apple.com)   

I entered the new information yesterday, and all appeared well. Then, I left the computer on all night. Then checked it this morning. 

The clock  is accurate. All is well !

 

In summary, the problem is not AMD, or the boot loader, or the busratio . There is no problem with the TSCSync. The problem is a bug in Mavericks and how it writes to the /etc/ntp.conf file.

 

HAPPY CAMPER!!! GOOD HACK !!! :)

 Share
Go to topic listing
×
×
  • Create New...