Haswell-E mach_kernel patch (5960X, 5830K and 5820K) 10.10 - 10.10.1 Yosemite

[Edkroket]

Props Guys! Works great!

 

One question anyone using VMware Fusion or Parallels?  Both products on my gigabyte X99 OS X 10.10 run VM's really slow!  Cant even install windows.  I am assuming it is due to the kernel patch. Also assuming there won't be a fix till Apple Native CPU support. Looking for ideas or suggestions.

Have you ever found a fix for this? I'm using VMWare Fusion 7 as well for some windows purposes.

I need it badly. If somebody knows?

 

It has nothing to do with settings in the virtual machine or what so ever. I know because I have run these machines on many different systems and they all run fine there. Only not here on my X99-UD4 with 5930K

[jamiethemorris]

Have you ever found a fix for this? I'm using VMWare Fusion 7 as well for some windows purposes.

I need it badly. If somebody knows?

 

It has nothing to do with settings in the virtual machine or what so ever. I know because I have run these machines on many different systems and they all run fine there. Only not here on my X99-UD4 with 5930K

I was proposing more of a workaround rather than saying the vm's settings are wrong. I think because of the patched kernel it may be detecting something incorrectly and that's why it's running slow. My guess is that it's detecting the clock speed wrong.

[drewintheav]

Update: Latest Clover now works on the Asus x99 Deluxe. Off to test more boards. 

 

Has there been any progress with the Clover bootloader and the "Asus X99-E WS" mainboard? Is it working yet?

[Edkroket]

I was proposing more of a workaround rather than saying the vm's settings are wrong. I think because of the patched kernel it may be detecting something incorrectly and that's why it's running slow. My guess is that it's detecting the clock speed wrong.

I've tried  many different work arrounds but nothing seems to help any.

When running VM I can see vmware-vmx running at 100% and it looks like it's using only one of the cores.

Here is my configfile:

.encoding = "UTF-8"

config.version = "8"

virtualHW.version = "11"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsisas1068"

memsize = "1024"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Windows 7 clean.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

ethernet0.present = "TRUE"

ethernet0.connectionType = "nat"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.addressType = "generated"

ethernet0.linkStatePropagation.enable = "TRUE"

usb.present = "TRUE"

ehci.present = "TRUE"

sound.present = "TRUE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

mks.enable3d = "TRUE"

serial0.present = "TRUE"

serial0.fileType = "thinprint"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

roamingVM.exitBehavior = "go"

tools.syncTime = "FALSE"

displayName = "Windows 7 clean"

guestOS = "windows7"

nvram = "Windows 7 clean.nvram"

virtualHW.productCompatibility = "hosted"

printers.enabled = "TRUE"

proxyApps.publishToGuest = "FALSE"

tools.upgrade.policy = "upgradeAtPowerCycle"

powerType.powerOff = "soft"

powerType.powerOn = "soft"

powerType.suspend = "soft"

powerType.reset = "soft"

extendedConfigFile = "Windows 7 clean.vmxf"

numvcpus = "1"

cpuid.coresPerSocket = "1"

checkpoint.vmState = ""

ethernet0.generatedAddress = "00:0c:29:a1:ab:30"

uuid.location = "56 4d 19 bb 7a db 02 8c-71 5a a5 38 ac a1 ab 30"

uuid.bios = "56 4d 19 bb 7a db 02 8c-71 5a a5 38 ac a1 ab 30"

cleanShutdown = "FALSE"

replay.supported = "FALSE"

replay.filename = ""

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "160"

usb.pciSlotNumber = "32"

ethernet0.pciSlotNumber = "33"

sound.pciSlotNumber = "34"

ehci.pciSlotNumber = "35"

vmci0.pciSlotNumber = "36"

scsi0.sasWWID = "50 05 05 6b 7a db 02 80"

vmotion.checkpointFBSize = "67108864"

usb:1.present = "TRUE"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "1146273376"

usb:1.deviceType = "hub"

ide1:0.startConnected = "FALSE"

unity.wasCapable = "FALSE"

hpet0.present = "TRUE"

usb.vbluetooth.startConnected = "TRUE"

sound.virtualDev = "hdaudio"

mem.hotadd = "TRUE"

usb:1.speed = "2"

tools.remindInstall = "FALSE"

monitor.phys_bits_used = "42"

softPowerOff = "FALSE"

keyboardAndMouseProfile = "5268a43d-aee9-6deb-1f51-f1748ee3"

ide1:0.autodetect = "TRUE"

migrate.hostlog = "/Volumes/Backup 3tb/Windows 7 clean.vmwarevm/./Windows 7 clean-0d1f7c24.hlog"

gui.fitGuestUsingNativeDisplayResolution = "FALSE"

vmotion.checkpointSVGAPrimarySize = "67108864"

sound.startConnected = "TRUE"

serial0.startConnected = "FALSE"

vpmc.enable = "FALSE"

svga.graphicsMemoryKB = "1048576"

isolation.tools.dnd.disable = "TRUE"

isolation.tools.copy.disable = "TRUE"

isolation.tools.paste.disable = "TRUE"

bios.forceSetupOnce = "FALSE"

vhv.enable = "TRUE"

proxyApps.publishToHost = "FALSE"

chipset.useAcpiBattery = "FALSE"

chipset.useApmBattery = "FALSE"

floppy0.present = "FALSE"

MemTrimRate = "0"

sched.mem.pshare.enable = "FALSE"

prefvmx.useRecommendedLockedMemSize = "TRUE"

host.TSC.noForceSync = "TRUE"

host.useFastclock = "TRUE"

host.TSC.forcedDelta = "TRUE"

host.TSC.maxDelta = "TRUE"

host.cpukHz = "36"

host.noTSC = "TRUE"

ptsc.noTSC = "TRUE"

usb:0.present = "TRUE"

usb:0.deviceType = "hid"

usb:0.port = "0"

usb:0.parent = "-1"

 

Any thing else?

 

 

Problem solved! Seemed that I had to install Generic USB3 kext.!

It's running like it should!

Edited December 3, 2014 by Edkroket

[jamiethemorris]

I've tried many different work arrounds but nothing seems to help any.

When running VM I can see vmware-vmx running at 100% and it looks like it's using only one of the cores.

Here is my configfile:

.encoding = "UTF-8"

config.version = "8"

virtualHW.version = "11"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsisas1068"

memsize = "1024"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Windows 7 clean.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

ethernet0.present = "TRUE"

ethernet0.connectionType = "nat"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.addressType = "generated"

ethernet0.linkStatePropagation.enable = "TRUE"

usb.present = "TRUE"

ehci.present = "TRUE"

sound.present = "TRUE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

mks.enable3d = "TRUE"

serial0.present = "TRUE"

serial0.fileType = "thinprint"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

roamingVM.exitBehavior = "go"

tools.syncTime = "FALSE"

displayName = "Windows 7 clean"

guestOS = "windows7"

nvram = "Windows 7 clean.nvram"

virtualHW.productCompatibility = "hosted"

printers.enabled = "TRUE"

proxyApps.publishToGuest = "FALSE"

tools.upgrade.policy = "upgradeAtPowerCycle"

powerType.powerOff = "soft"

powerType.powerOn = "soft"

powerType.suspend = "soft"

powerType.reset = "soft"

extendedConfigFile = "Windows 7 clean.vmxf"

numvcpus = "1"

cpuid.coresPerSocket = "1"

checkpoint.vmState = ""

ethernet0.generatedAddress = "00:0c:29:a1:ab:30"

uuid.location = "56 4d 19 bb 7a db 02 8c-71 5a a5 38 ac a1 ab 30"

uuid.bios = "56 4d 19 bb 7a db 02 8c-71 5a a5 38 ac a1 ab 30"

cleanShutdown = "FALSE"

replay.supported = "FALSE"

replay.filename = ""

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "160"

usb.pciSlotNumber = "32"

ethernet0.pciSlotNumber = "33"

sound.pciSlotNumber = "34"

ehci.pciSlotNumber = "35"

vmci0.pciSlotNumber = "36"

scsi0.sasWWID = "50 05 05 6b 7a db 02 80"

vmotion.checkpointFBSize = "67108864"

usb:1.present = "TRUE"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "1146273376"

usb:1.deviceType = "hub"

ide1:0.startConnected = "FALSE"

unity.wasCapable = "FALSE"

hpet0.present = "TRUE"

usb.vbluetooth.startConnected = "TRUE"

sound.virtualDev = "hdaudio"

mem.hotadd = "TRUE"

usb:1.speed = "2"

tools.remindInstall = "FALSE"

monitor.phys_bits_used = "42"

softPowerOff = "FALSE"

keyboardAndMouseProfile = "5268a43d-aee9-6deb-1f51-f1748ee3"

ide1:0.autodetect = "TRUE"

migrate.hostlog = "/Volumes/Backup 3tb/Windows 7 clean.vmwarevm/./Windows 7 clean-0d1f7c24.hlog"

gui.fitGuestUsingNativeDisplayResolution = "FALSE"

vmotion.checkpointSVGAPrimarySize = "67108864"

sound.startConnected = "TRUE"

serial0.startConnected = "FALSE"

vpmc.enable = "FALSE"

svga.graphicsMemoryKB = "1048576"

isolation.tools.dnd.disable = "TRUE"

isolation.tools.copy.disable = "TRUE"

isolation.tools.paste.disable = "TRUE"

bios.forceSetupOnce = "FALSE"

vhv.enable = "TRUE"

proxyApps.publishToHost = "FALSE"

chipset.useAcpiBattery = "FALSE"

chipset.useApmBattery = "FALSE"

floppy0.present = "FALSE"

MemTrimRate = "0"

sched.mem.pshare.enable = "FALSE"

prefvmx.useRecommendedLockedMemSize = "TRUE"

host.TSC.noForceSync = "TRUE"

host.useFastclock = "TRUE"

host.TSC.forcedDelta = "TRUE"

host.TSC.maxDelta = "TRUE"

host.cpukHz = "36"

host.noTSC = "TRUE"

ptsc.noTSC = "TRUE"

usb:0.present = "TRUE"

usb:0.deviceType = "hid"

usb:0.port = "0"

usb:0.parent = "-1"

 

Any thing else?

 

 

Problem solved! Seemed that I had to install Generic USB3 kext.!

It's running like it should!

no way. Glad you got that fixed.

[rkelleyrtp1]

Greetings,

 

I have been watching this thread for a while hoping to get my new Gigabyte GA-X99-UD4 working (BIOS F9, Intel 5960X CPU, 32GB RAM, older ATI 3650 PCIe video card, 256G SSD).  I have followed the instructions in this thread as closely as possible but still end up with the "PCI configuration begin" and "Waiting on boot-uuid-media" messages.  Here is what I have done thus far:

 

* Create clean boot USB using "U" and "M" tools from another site

* Made the kernel modification per the OP on page 1

* Added the Voodoo kext to /Extras/Extensions and changed the IOCPUNumber value to 15

* Booted from USB drive (npci=0x2000 kext-dev-mode=1) and got completely thru the Yosemite installer - yes; the installer made it 100% complete

* Booted again from USB drive and copied the modified kernel to /S/L/Kernels (after making a backup of the original kernel)

* Booted again from USB drive pointing to new Yosemite drive and get "Waiting on .... boot-uuid-media"

 

I have read this thread over and over - trying all the ideas from other members.  However, my system still gets stuck.  I have been at this for >3 days and have made little progress.  I find it very strange the installer works but the runtime system does not.

 

Can anyone else with the UD4 motherboard and the 5960x CPU please let me know how they able to get their system working?  Did you have to do any BIOS magic?  What specifically did you have to add to the /Extras/Extensions or /S/L/E directories?

 

...I am stumped...

 

Thanks in advance for any help!

[jamiethemorris]

Greetings,

 

I have been watching this thread for a while hoping to get my new Gigabyte GA-X99-UD4 working (BIOS F9, Intel 5960X CPU, 32GB RAM, older ATI 3650 PCIe video card, 256G SSD). I have followed the instructions in this thread as closely as possible but still end up with the "PCI configuration begin" and "Waiting on boot-uuid-media" messages. Here is what I have done thus far:

 

* Create clean boot USB using "U" and "M" tools from another site

* Made the kernel modification per the OP on page 1

* Added the Voodoo kext to /Extras/Extensions and changed the IOCPUNumber value to 15

* Booted from USB drive (npci=0x2000 kext-dev-mode=1) and got completely thru the Yosemite installer - yes; the installer made it 100% complete

* Booted again from USB drive and copied the modified kernel to /S/L/Kernels (after making a backup of the original kernel)

* Booted again from USB drive pointing to new Yosemite drive and get "Waiting on .... boot-uuid-media"

 

I have read this thread over and over - trying all the ideas from other members. However, my system still gets stuck. I have been at this for >3 days and have made little progress. I find it very strange the installer works but the runtime system does not.

 

Can anyone else with the UD4 motherboard and the 5960x CPU please let me know how they able to get their system working? Did you have to do any BIOS magic? What specifically did you have to add to the /Extras/Extensions or /S/L/E directories?

 

...I am stumped...

 

Thanks in advance for any help!

you didn't mention using the appleacpiplaform and iopcifamily kexts from mavericks. If you're using the 5960x this is currently the only way to get past PCI configuration begin on Yosemite.

 

If you're getting stuck on waiting for boot-uid media, that sounds like a kernel problem. Try just putting the kernel at the root of the drive and renaming it to mach_kernel. I remember this being a problem with Chameleon when the first Yosemite DPs came out. AFAIK it's not any more, but it should definitely be able to see it at the root of the drive if it's name correctly.

[rkelleyrtp1]

you didn't mention using the appleacpiplaform and iopcifamily kexts from mavericks. If you're using the 5960x this is currently the only way to get past PCI configuration begin on Yosemite.

 

If you're getting stuck on waiting for boot-uid media, that sounds like a kernel problem. Try just putting the kernel at the root of the drive and renaming it to mach_kernel. I remember this being a problem with Chameleon when the first Yosemite DPs came out. AFAIK it's not any more, but it should definitely be able to see it at the root of the drive if it's name correctly.

Thanks for the quick reply!  I just pulled both of those kext files from a working Mavericks installation and put them in the /Extra/Extensions *and* S/L/E folder (just to be safe).  

 

As for putting the kernel at the root of the drive, do I still need to call it "mach_kernel" since this is Yosemite?

[jamiethemorris]

Thanks for the quick reply! I just pulled both of those kext files from a working Mavericks installation and put them in the /Extra/Extensions *and* S/L/E folder (just to be safe).

 

As for putting the kernel at the root of the drive, do I still need to call it "mach_kernel" since this is Yosemite?

the bootloader looks for mach_kernel at the root of the drive automatically since that's the name and location of it on older versions. You can name it whatever you want though as long as you type the name at the boot menu. If you want to leave it named kernel, then just type that at the boot menu. If you want too use a kernel somewhere else besides the root of the drive, just type out the full path of the kernel. Of course you can also put this in the kernel flags section of your org.chameleon.boot.plist.

[rkelleyrtp1]

Thanks again for the help.  Unfortunately, adding those kext to the system did not work.  

 

However, I have found something odd related to the GA-X99-UD4 BIOS (currently running F10).  I decided to start from scratch and get the base system installed so I can isolate the source of the boot-uuid-media problem.   I reset the BIOS to Optimized Defaults and plugged in my trusty boot installer.  However, resetting the BIOS has resulted in the USB installer getting stuck on PCI Configuration Begin.  This particular USB installer worked flawlessly before but now fails to boot past the PCI Configuration output message.  So, it appears there is something going on with the BIOS that is causing some of the problems.

 

I was hoping someone who has a Yosemite system running with the GA-X99-UD4 board could share their BIOS options so I can compare with mine.  Maybe this is purely a BIOS issue and not a Yosemite issue.

[jamiethemorris]

Thanks again for the help.  Unfortunately, adding those kext to the system did not work.  

 

However, I have found something odd related to the GA-X99-UD4 BIOS (currently running F10).  I decided to start from scratch and get the base system installed so I can isolate the source of the boot-uuid-media problem.   I reset the BIOS to Optimized Defaults and plugged in my trusty boot installer.  However, resetting the BIOS has resulted in the USB installer getting stuck on PCI Configuration Begin.  This particular USB installer worked flawlessly before but now fails to boot past the PCI Configuration output message.  So, it appears there is something going on with the BIOS that is causing some of the problems.

 

I was hoping someone who has a Yosemite system running with the GA-X99-UD4 board could share their BIOS options so I can compare with mine.  Maybe this is purely a BIOS issue and not a Yosemite issue.

Check this link. These are the ones that the 5960x users are using with success.: http://www.insanelymac.com/forum/topic/301585-haswell-e-mach-kernel-patch-5960x-5830k-and-5820k-yosemite/?p=2077062 It is a problem specific to Yosemite on the 5960x, it does not happen with the 6-core CPUs and it does not happen in Mavericks.

 

I guess they were 10.9.4 and not 10.9.5. I don't know if it matters. Make sure you boot without the kernel cache by using UseKernelCache=No in your boot.plist otherwise it will still use the cached Yosemite kexts. 

 

It IS possible you have another problem as well, however what I can tell you is that you will definitely not be able to get past PCI configuration begin without those kexts with a 5960x on Yosemite. I think this is still the problem though. Try those kexts in the link (I don't know if you need the FakeSMC he posted or not, but you might as well use that too).

 

Let me know how it goes.

[rkelleyrtp1]

Making progress.  After adding those extensions to the S/L/E folder, my X99-UD4 system booted to the login screen 

 

However, I don't have any USB connectivity (keyboard, mouse).  I think I saw another thread about this issue.  Time for some more investigation.

 

Many thanks for helping me get this far!

[jamiethemorris]

Making progress.  After adding those extensions to the S/L/E folder, my X99-UD4 system booted to the login screen 

 

However, I don't have any USB connectivity (keyboard, mouse).  I think I saw another thread about this issue.  Time for some more investigation.

 

Many thanks for helping me get this far!

That sounds it might be a BIOS thing. Are they plugged in to USB2 or USB3 ports? If you're plugged into USB3 you may need to install GenericUSBXHCI.

[rkelleyrtp1]

Well, better news.   It appears I can boot successfully (mouse, keyboard working) using Chimera (via the "M" tool).  Ethernet and sound are not working, but that should be a relatively easy fix compared to what I have been through so far.

 

However, Clover is definitely not working for me.  And, since I am going to run a pair of 290x cards, I need Clover to work due to the boot BIOS problem.  By chance, do you have a working config.plist you can share?

 

Thanks again for the tremendous help!

[jamiethemorris]

Well, better news. It appears I can boot successfully (mouse, keyboard working) using Chimera (via the "M" tool). Ethernet and sound are not working, but that should be a relatively easy fix compared to what I have been through so far.

 

However, Clover is definitely not working for me. And, since I am going to run a pair of 290x cards, I need Clover to work due to the boot BIOS problem. By chance, do you have a working config.plist you can share?

 

Thanks again for the tremendous help!

I don't have an x99 so I don't have anything useful to give you, but what isn't working about clover? Can you get to the clover boot menu?

 

Edit: oops, I misunderstood. You mean that the keyboard and mouse doesn't work with clover. Post your config here and I'll take a look at it. First thing I would try is turn USB inject off if it's on.

[rkelleyrtp1]

Yeah, when I boot via Clover, the system stops at the "PCI Configuration Begins" message.  I get no keyboard/mouse activity, and ultimately I get the Ghostbusters sign (inaccessible drive).  However, if I boot the exact same system using Chimera/"M", I am able to boot all the way.  

 

I am trying to attach my config.plist, but it says "You aren't permitted to upload this kind of file".  Not sure how I can upload it here.

 

[jamiethemorris]

Yeah, when I boot via Clover, the system stops at the "PCI Configuration Begins" message. I get no keyboard/mouse activity, and ultimately I get the Ghostbusters sign (inaccessible drive). However, if I boot the exact same system using Chimera/"M", I am able to boot all the way.

 

I am trying to attach my config.plist, but it says "You aren't permitted to upload this kind of file". Not sure how I can upload it here.

compress the config.plist first and it will let you upload it. Also upload your org.chameleon.boot.plist.

[rkelleyrtp1]

Here it is.  This was taken directly from RampageDev's "X99" package. 

Oops - one more time...

Here is what my org.chameleon.boot.plist file looks like

<?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>Boot Banner</key>
        <string>No</string>
        <key>EthernetBuiltIn</key>
        <string>No</string>
        <key>GraphicsEnabler</key>
        <string>No</string>
        <key>IGPEnabler</key>
        <string>No</string>
        <key>Instant Menu</key>
        <string>Yes</string>
        <key>Kernel Flags</key>
        <string>npci=0x2000 kext-dev-mode=1</string>
        <key>Legacy Logo</key>
        <string>Yes</string>
        <key>UseKernelCache</key>
        <string>Yes</string>
</dict>
</plist>

config.plist.zip

[Rampage Dev]

To start if you install using chameleon and then install clover the system basicly will never run right. Needs to be installed using clover to advoid these issues.

 

It's not a alacart where you can select what ever you want.

[rkelleyrtp1]

Perhaps I am misunderstanding your statement, but I read it this way:  "If I build a system using the "U" and "M" tools and boot via Chameleon, I must rebuild the system in order to use Clover.  Otherwise, my system will never work properly if I go from Chameleon to Clover".  Please clarify if I misunderstand.

 

At the end of the day, I need my X99-UD4 system with a 5960X CPU to boot using Clover because I have dual 290X cards (and Chameleon has the video card BIOS boot issues with 290x cards).  The problem thus far is I can get my system running using Chameleon and an older ATI card but can't get it booted at all using the latest 3050 Clover package (with old card or new card).

 

Do we have a 100% foolproof method of getting the 5960X systems running with Yosemite and Clover (complete with necessary kexts, the config.plist, and any .aml files)?  If so, please point me in the right direction.  Otherwise, I am willing to test/tackle such a project;  I just need some assistance getting the right files in the right place.

 

Thanks!

[jamiethemorris]

Just looked at your config.plist, You need to have a proper SMBios. In your config you only had the product name so I generated the reset for you. The easiest way to do this is with Clover Configurator. I would recommend that app any time you need to edit the config.plist. I also disabled USB injection as that has caused issues with keyboard and mouse for me, and disabled fix ownership because it serves no purpose on UEFI. Oh, and I gave you a few useful kext patches. Hopefully this helps.

configrkeylleyrtp1.zip

[rkelleyrtp1]

Just looked at your config.plist, You need to have a proper SMBios. In your config you only had the product name so I generated the reset for you. The easiest way to do this is with Clover Configurator. I would recommend that app any time you need to edit the config.plist. I also disabled USB injection as that has caused issues with keyboard and mouse for me, and disabled fix ownership because it serves no purpose on UEFI. Oh, and I gave you a few useful kext patches. Hopefully this helps.

Thanks a ton!  I will try this out as soon as I get home and let you know what I find.

 

Appreciate all the help!  Once I get a foolproof way of getting Clover working with the 5960x, I will put together a good write-up and post it here.

[Rampage Dev]

Perhaps I am misunderstanding your statement, but I read it this way:  "If I build a system using the "U" and "M" tools and boot via Chameleon, I must rebuild the system in order to use Clover.  Otherwise, my system will never work properly if I go from Chameleon to Clover".  Please clarify if I misunderstand.

 

At the end of the day, I need my X99-UD4 system with a 5960X CPU to boot using Clover because I have dual 290X cards (and Chameleon has the video card BIOS boot issues with 290x cards).  The problem thus far is I can get my system running using Chameleon and an older ATI card but can't get it booted at all using the latest 3050 Clover package (with old card or new card).

 

Do we have a 100% foolproof method of getting the 5960X systems running with Yosemite and Clover (complete with necessary kexts, the config.plist, and any .aml files)?  If so, please point me in the right direction.  Otherwise, I am willing to test/tackle such a project;  I just need some assistance getting the right files in the right place.

 

Thanks!

 

Simplest method for people who are new to using a modded kernel is to install to the drive using a real mac or working hack without a modded kernel. Change the kernel post install. Then boot to the system with clover on the Hack. 

 

Tested about 10 x99 boards so far with many different methods of installation. Installation guide if slim due to only wanted people who have a great understanding of how Mac OS X works to test thus getting useful feedback that can be applied to improving the over all performance. I did the same thing with x79 and after a few month we got the issues addressed and built up from there. 

Just looked at your config.plist, You need to have a proper SMBios. In your config you only had the product name so I generated the reset for you. The easiest way to do this is with Clover Configurator. I would recommend that app any time you need to edit the config.plist. I also disabled USB injection as that has caused issues with keyboard and mouse for me, and disabled fix ownership because it serves no purpose on UEFI. Oh, and I gave you a few useful kext patches. Hopefully this helps.

 

You do know that all of the kext patching you did does nothing right? It actually breaks things. Please be mindful of these things. Stop enabling features that breaks peoples installs. We do not patch the DSDT but use SSDT injection. Now the SSDT will not load or cause the system to panic. 

[rkelleyrtp1]

Success!!!       Many thanks for the great information, jamiethemorris!

 

I finally have my GA-X99-UD4 system with the Intel 5960x CPU and 32G RAM system working in Clover.  It took a while to get it all sorted out, but the system is running via Clover v3050 (typing on said system as I write this reply).  I had to make the following changes to get it all working:

 

X99-UD4 (F10) BIOS Settings

---------------

  --> Reset X99-UD4 BIOS (ver F10) to Factory Default - Optimized Settings

 

  --> Enabled 4.3GHz CPU overclock

 

  --> Enabled Extreme Memory Setting (XMS) Profile 1 (default profile)

 

  --> Plugged in SSD to onboard SATA port 0

 

 

Software Settings

--------------------------------------------

  --> Using another Mac, I mounted my SSD (both the EFI and HFS+ partitions)

 

  --> Installed your config.plist file in the EFI/CLOVER directory

 

  --> Cleaned out (erased) ALL kexts files from EFI/CLOVER/kext directories

 

  --> Added the following kext files to the EFI/CLOVER/kext/10.10 folder:

      ==> AppleACPIPlatform.kext (from stinga11's "5960x_test_number_one.zip" file)

      ==> IOPCIFamily.kext (from stinga11's "5960x_test_number_one.zip" file)

      ==> VoodooTSCSync.kext with the 8-core config

 

  --> Removed all sdt.aml and ssdt.aml files in the EFI/CLOVER/ACPI/patched directory

 

  --> Removed the AppleACPIPlatform.kext kernel extension from /System/Library/Extensions directory

 

  --> Removed the IOPCIFamily.kext kernel extension from /System/Library/Extensions directory

 

  --> Removed any non-standard kernel extensions (Voodoo, any "MBeast" files, etc) from /System/Library/Extensions directory

 

  --> Ran the "Kext Wizard" tool to repair permissions and rebuild cache on the SSD

 

  --> Unmounted the SSD from working system and plugged into the X99-UD4 system

 

  --> Booted the X99 system and was greeted with the CLOVER boot loader.

 

  --> Selected my SSD and within 10secs I was greeted by the 2560x1600 login screen! (yah! my 290x card works!)

---------------------------------------------

 

That is all.  I did not add any other kernel extensions to either the CLOVER or /S/L/E directories.  As it stands, my onboard audio and ethernet card devices don't work (I had a spare ethernet PCI card lying around to get 'net access).    I still need to work on that.

 

Even though my system is running 4.3GHz OC'd, OSX only recognizes a 3GHz CPU and 2166MHz DDR3 (probably a tweak somewhere).  A quick run of GeekBench 3 gives me a single core score of 3207 and a Multi-Core Score of 27199.  I was expecting something like 4300 and 34,400 (or close to that).

 

 

Many thanks for your help and patience as I went through this process.  I hope my shortened guide above can help someone else!

[jamiethemorris]

 

Success!!!       Many thanks for the great information, jamiethemorris!

 

I finally have my GA-X99-UD4 system with the Intel 5960x CPU and 32G RAM system working in Clover.  It took a while to get it all sorted out, but the system is running via Clover v3050 (typing on said system as I write this reply).  I had to make the following changes to get it all working:

 

X99-UD4 (F10) BIOS Settings

---------------

  --> Reset X99-UD4 BIOS (ver F10) to Factory Default - Optimized Settings

 

  --> Enabled 4.3GHz CPU overclock

 

  --> Enabled Extreme Memory Setting (XMS) Profile 1 (default profile)

 

  --> Plugged in SSD to onboard SATA port 0

 

 

Software Settings

--------------------------------------------

  --> Using another Mac, I mounted my SSD (both the EFI and HFS+ partitions)

 

  --> Installed your config.plist file in the EFI/CLOVER directory

 

  --> Cleaned out (erased) ALL kexts files from EFI/CLOVER/kext directories

 

  --> Added the following kext files to the EFI/CLOVER/kext/10.10 folder:

      ==> AppleACPIPlatform.kext (from stinga11's "5960x_test_number_one.zip" file)

      ==> IOPCIFamily.kext (from stinga11's "5960x_test_number_one.zip" file)

      ==> VoodooTSCSync.kext with the 8-core config

 

  --> Removed all sdt.aml and ssdt.aml files in the EFI/CLOVER/ACPI/patched directory

 

  --> Removed the AppleACPIPlatform.kext kernel extension from /System/Library/Extensions directory

 

  --> Removed the IOPCIFamily.kext kernel extension from /System/Library/Extensions directory

 

  --> Removed any non-standard kernel extensions (Voodoo, any "MBeast" files, etc) from /System/Library/Extensions directory

 

  --> Ran the "Kext Wizard" tool to repair permissions and rebuild cache on the SSD

 

  --> Unmounted the SSD from working system and plugged into the X99-UD4 system

 

  --> Booted the X99 system and was greeted with the CLOVER boot loader.

 

  --> Selected my SSD and within 10secs I was greeted by the 2560x1600 login screen! (yah! my 290x card works!)

---------------------------------------------

 

That is all.  I did not add any other kernel extensions to either the CLOVER or /S/L/E directories.  As it stands, my onboard audio and ethernet card devices don't work (I had a spare ethernet PCI card lying around to get 'net access).    I still need to work on that.

 

Even though my system is running 4.3GHz OC'd, OSX only recognizes a 3GHz CPU and 2166MHz DDR3 (probably a tweak somewhere).  A quick run of GeekBench 3 gives me a single core score of 3207 and a Multi-Core Score of 27199.  I was expecting something like 4300 and 34,400 (or close to that).

 

 

Many thanks for your help and patience as I went through this process.  I hope my shortened guide above can help someone else!

 

Try installing NullCPUPowerManagement, people have reported that helps performance. I think that should let it go up to 4.3 ghz. Try turning XMP detection on in Clover configurator. If you used the automatic overclock option in the bios, then XMP is probably enabled so your FSB is actually at 125 mhz instead of the standard 100 mhz, OS X may not recognize this. Without elaborating too much, one solution would be to just take a look at the voltages everything is using as well as the memory timings, disable XMP, and then set the frequencies and voltages manually with XMP off. Then if you wish you can set the RAM frequency you want and set the timings to what you recorded. Another solution would be to add this in the BusSpeedKHz entry in Clover: 125000 which hopefully should tell clover the correct frequency. You could also try another SMBios like MacPro3,1 or even MacPro6,1. Again you can generate that easily with Clover Configurator.

 

EDIT: Actually, before you do anything, humor me and try this SSDT. Created with ssdtprgen. I set the frequency to 4300 and the blck to 125.

SSDT.aml.zip