The issue I have is it makes the clock run fast in OSX which screws up almost everything. How did you get yours to work? If it helps I'm on a custom DSDT and absolutely everything works on 10.6.5 (everything include sleep and WOL)
I've never had the dreaded clock issue on any of the three machines I've built...
My current board is a Gigabyte P55A-UD4P, and I'm not even running a custom DSDT. I'm using the latest Chameleon v2.0-RC5 (r650), multi-beast v 2.5.1 with the following kexts:
EvOreboot.kext, fakesmc.kext, JMicron36xSATA.kext, Legacy889HDA.kext, LegacyAppleRTC.kext, NullCPUPowerManagement.kext and NVEnabler 64.kext.
My smbios.plist is set to MacPro5,1 and looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>SMfamily</key>
<string>MacPro</string>
<key>SMproductname</key>
<string>MacPro5,1</string>
<key>SMboardproduct</key>
<string>Mac-F221BEC8</string>
<key>SMserial</key>
<string>G8031889GWR</string>
<key>SMbiosversion</key>
<string>Asylum.Design.MachIX</string>
<key>SMcputype</key>
<string>1793</string>
</dict>
</plist>
My com.apple.Boot.plist looks like this (32-Bit Kernel)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>arch=i386</string>
<key>GraphicsEnabler</key>
<string>Yes</string>
<key>Timeout</key>
<string>1</string>
<key>Legacy Logo</key>
<string>Yes</string>
<key>EthernetBuiltIn</key>
<string>Yes</string>
</dict>
</plist>
I have disabled sleep on mine, as it's just not that important to me... I can turn it off if I don't want to pay the electric company... the thing boots in 4 spins of the Apple menu anyway... lol (thank you SSD drive).
I was using the official Realtek Gigabit Ethernet driver, but reverted to the open source SL1000 kext as it just worked better for me.
I have speed-step disabled completely in the bios, so I'm running full-bore all the time... and have never had any clock issues that I'm aware of.
The only thing I've had an issue with is my bluetooth adapter ($4.95 from Fry's) causes it to kernal panic... I'm sure it's the POS adapter I'm using, I just haven't had a chance to try another adapter yet.
Last edited: