Clover Memory issue and SMbios

I have been using Chimera for quite sometime and consider myself pretty knowledgable with it so I decided to try clover. I have everything working correctly with clover except the memory speed. I have tried so many different ways to have clover recognize my correct ram speed but have failed. I don't normally post but I can not find the solution. If anyone could help that would be awesome. I hear a lot of people say that 1333 ram speed is a bug that clover has and its actually running at correct frequency but my geekbench scores say otherwise. I am getting around 1400 with Chimera and only 1100 with clover. Another thing I cannot do is change the smbios to imac12.2 from imac13.2 because clover automatically gives you a smbios. I normally wouldn't care but my overclocking does not work with imac13.2 only with imac12.1 and imac12.2 I tried... I will put my Config as attachment if anyone wants to help me mess with it my specs are in my profile.

XMP was enabled in my bios as profile 1. 1867 speed
XMP. Yes/No both and 1 and 2 does nothing
xmp turned off in my bios and no in clover does nothing

smbios. True and False tired both...
tried trust did not work...
With Clover
I must be missing something here are the some pics and my config







With Chimera






My Plist
<?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>ACPI</key>
<dict>
<key>DSDT</key>
<dict>
<key>Debug</key>
<false/>
<key>DropOEM_DSM</key>
<false/>
<key>Fixes</key>
<dict>
<key>AddDTGP_0001</key>
<true/>
<key>AddHDMI_8000000</key>
<true/>
<key>AddIMEI_80000</key>
<true/>
<key>AddPNLF_1000000</key>
<true/>
<key>DeleteUnused_400000</key>
<true/>
<key>FIX_ACST_4000000</key>
<true/>
<key>FIX_ADP1_800000</key>
<true/>
<key>FIX_RTC_20000</key>
<true/>
<key>FIX_S3D_2000000</key>
<true/>
<key>FixAirport_4000</key>
<true/>
<key>FixDisplay_0100</key>
<true/>
<key>FixFirewire_0800</key>
<true/>
<key>FixHDA_8000</key>
<true/>
<key>FixHPET_0010</key>
<true/>
<key>FixIPIC_0040</key>
<true/>
<key>FixLAN_2000</key>
<true/>
<key>FixRegions_10000000</key>
<true/>
<key>FixShutdown_0004</key>
<true/>
<key>NewWay_80000000</key>
<true/>
</dict>
<key>Name</key>
<string>DSDT.aml</string>
<key>ReuseFFFF</key>
<false/>
</dict>
<key>DropTables</key>
<array>
<dict>
<key>Signature</key>
<string>DMAR</string>
</dict>
<dict>
<key>Signature</key>
<string>SSDT</string>
<key>TableId</key>
<string>CpuPm</string>
</dict>
<dict>
<key>Signature</key>
<string>SSDT</string>
<key>TableId</key>
<string>Cpu0Ist</string>
</dict>
</array>
<key>HaltEnabler</key>
<true/>
<key>SSDT</key>
<dict>
<key>DropOem</key>
<false/>
<key>EnableC6</key>
<true/>
<key>Generate</key>
<dict>
<key>CStates</key>
<true/>
<key>PStates</key>
<true/>
</dict>
</dict>
</dict>
<key>Boot</key>
<dict>
<key>DefaultVolume</key>
<string>Yosemite Clover</string>
<key>Fast</key>
<true/>
<key>Legacy</key>
<string>PBR</string>
<key>Log</key>
<false/>
<key>Secure</key>
<false/>
<key>XMPDetection</key>
<integer>1</integer>
</dict>
<key>Devices</key>
<dict>
<key>Audio</key>
<dict>
<key>Inject</key>
<string>No</string>
</dict>
<key>FakeID</key>
<dict>
<key>ATI</key>
<string>0x0</string>
<key>IMEI</key>
<string>0x0</string>
<key>IntelGFX</key>
<string>0x0</string>
<key>LAN</key>
<string>0x0</string>
<key>NVidia</key>
<string>0x0</string>
<key>SATA</key>
<string>0x0</string>
<key>WIFI</key>
<string>0x0</string>
<key>XHCI</key>
<string>0x0</string>
</dict>
<key>USB</key>
<dict>
<key>AddClockID</key>
<true/>
<key>FixOwnership</key>
<true/>
<key>Inject</key>
<true/>
</dict>
</dict>
<key>DisableDrivers</key>
<array>
<string>Nothing</string>
</array>
<key>GUI</key>
<dict>
<key>Hide</key>
<array>
<string>Windows</string>
<string>BOOTX64.EFI</string>
</array>
<key>Language</key>
<string>en:0</string>
<key>Mouse</key>
<dict>
<key>Enabled</key>
<true/>
<key>Mirror</key>
<false/>
<key>Speed</key>
<integer>8</integer>
</dict>
<key>Scan</key>
<dict>
<key>Entries</key>
<true/>
<key>Legacy</key>
<true/>
<key>Tool</key>
<true/>
</dict>
<key>Theme</key>
<string>metal</string>
</dict>
<key>Graphics</key>
<dict>
<key>Inject</key>
<dict>
<key>ATI</key>
<true/>
<key>Intel</key>
<true/>
<key>NVidia</key>
<false/>
</dict>
</dict>
<key>KernelAndKextPatches</key>
<dict>
<key>AppleRTC</key>
<true/>
<key>AsusAICPUPM</key>
<true/>
<key>KextsToPatch</key>
<array>
<dict>
<key>Comment</key>
<string>External icons patch</string>
<key>Find</key>
<data>
RXh0ZXJuYWw=
</data>
<key>Name</key>
<string>AppleAHCIPort</string>
<key>Replace</key>
<data>
SW50ZXJuYWw=
</data>
</dict>
</array>
</dict>
<key>SMBIOS</key>
<dict>
<key>Trust</key>
<true/>
</dict>
<key>SystemParameters</key>
<dict>
<key>InjectKexts</key>
<string>Detect</string>
<key>InjectSystemID</key>
<false/>
</dict>
</dict>
</plist>

Clover thinks you're running an iMac 12,2 because that's what's written in your config.plist in the SMBIOS section. You can also add a memory sub-section to the SMBIOS information where you can populate the make/speed/serial# of each of your memory sticks. I'm not sure why the config.plist you've copied/pasted hasn't got the SMBIOS section expanded but you might want to look at it using a plist editor if you're not already doing so.

zookini13 said:

Clover thinks you're running an iMac 12,2 because that's what's written in your config.plist in the SMBIOS section. You can also add a memory sub-section to the SMBIOS information where you can populate the make/speed/serial# of each of your memory sticks. I'm not sure why the config.plist you've copied/pasted hasn't got the SMBIOS section expanded but you might want to look at it using a plist editor if you're not already doing so.

Click to expand...

That didn't do anything either... I have tried all that. I want clover to recognize it as 12.2 and not 13.2 because my overclock does not function with that smbios. It seems whatever I do with the config.plist clover like ignores it or something. I put another config.plist to my current frustrations. Thanks for replying

Sorry about that, read it the wrong way round. Either way it doesn't seem like Clover is picking up your config.plist as it doesn't contain any boot arguments such as kext-dev-mode=1 which I believe is currently required to load fakesmc. What kind of Clover install did you use and where is your config.plist located?

zookini13 said:

Sorry about that, read it the wrong way round. Either way it doesn't seem like Clover is picking up your config.plist as it doesn't contain any boot arguments such as kext-dev-mode=1 which I believe is currently required to load fakesmc. What kind of Clover install did you use and where is your config.plist located?

Click to expand...

I am using EFI partition fat32. I will try the Kext-dev-mode=1 and see if that makes a difference. I should have fully read the clover wiki before jumping into clover but it seems kinda vague. I guess its just a learning curve from Chimera. Should I try re-formatting my EFI drive don't install and try UEFI?

My guess would be that the config.plist you're working on is either in the wrong location or another one is being used that's located elsewhere as suggested by the fact that your changes to it don't seem to make a difference and it's missing a critical boot argument. What I use to test changes with is a GUID-partitioned USB stick onto which I install Clover (UEFI install) in the ESP/EFI along with FakeSMC, any required EFI drivers, SSDT/DSDT files and a fairly minimal config.plist. That way I can point my PC's BIOS to boot the installation of Clover on the USB stick and experiment with the config.plist or other kexts/drivers while keeping everything on the actual boot drive fairly untouched. Assuming you can still currently boot into OSX then I'd recommend maybe trying something like that so you don't risk messing up a working installation.

zookini13 said:

My guess would be that the config.plist you're working on is either in the wrong location or another one is being used that's located elsewhere as suggested by the fact that your changes to it don't seem to make a difference and it's missing a critical boot argument. What I use to test changes with is a GUID-partitioned USB stick onto which I install Clover (UEFI install) in the ESP/EFI along with FakeSMC, any required EFI drivers, SSDT/DSDT files and a fairly minimal config.plist. That way I can point my PC's BIOS to boot the installation of Clover on the USB stick and experiment with the config.plist or other kexts/drivers while keeping everything on the actual boot drive fairly untouched. Assuming you can still currently boot into OSX then I'd recommend maybe trying something like that so you don't risk messing up a working installation.

Click to expand...

That is a great method and didn't think about that. Ill download the basic Config tony has on his guide and do it step by step of my
USB stick so I can Diagnose what is changing. Thanks for the advice. I guess you never know unless you ask. Damn why didn't I think of that! and again thank you. Ill let you know how it goes.

I dedicated a whole drive to test with clover so i'm not worried I might mess something up. I have a clean install on another HD. I did your method and it worked. I think what I said was correct it is not using the config at all when booting. I am going to do a fresh install and add my already working config into my efi partition. I could be because I am partitioning the hard drive in half and I don't have it Partitioned correctly. Since I can get it working Ill put it on a single one. Thanks for your help!!! I do have one question to make sure I am doing it correctly what do I have to enable in the config to use my SSDT and DSDT files. I know where to put them but don't know what to enable in clover to use them?

Good to hear it's progressing well. For DSDT/SSDT I believe that all you need is the following although I'm still not entirely certain about the SSDT part of it: