Contribute
Register

OS X 10.11 El Capitan setup guide for ASUS Rampage V Extreme x99 Haswell-E

Joined
Aug 30, 2010
Messages
123
Motherboard
ASUS Rampage V Extreme
CPU
i7 5930k
Graphics
GTX 970
Mac
Mac Pro
Mobile Phone
iOS
Intro

This is a guide on how to set up Mac OS X 10.11 El Capitan on an x99 motherboard, more precisely for the ASUS Rampage V Extreme in ten steps. Owners of any other brand of x99 chipset may follow this as well accordingly to their own motherboard’s structure. I will try to be as brief as possible except for the DSDT part and apology for my bad English (not my native language).

It is normal to face a lot of hassles to make all peripherals and features of El Capitan to work with the x99 chipset. While Apple itself is not yet officially supporting x99, x79 remain the most stable platform as of this writing. It took (me) more than four months of work to figure out the proper methods and fixes. I will proceed with the Clover boot-loader method.

UEFI BIOS settings
Enter into BIOS and load default values. Go to advanced configuration, set the USB EHCI Handoff to Enable.
If you are doing a new setup disable Bluetooth, Wi-Fi for the time being and save changes and restart.

Very important to keep in mind is that at this step of the process, in no way should any overclocking features such as X.M.P or in any other form it might be turned ON.

Prerequisites

I will not go into details on how to create a bootable OS X USB installer. There are already plenty of guides available here at tonymacx86 itself. However, I can briefly suggest to use UniBeast to create your bootable OS X installer as it will also install Clover as boot-loader and avoid the hassle of relocating the folders manually.

It might be useful to have a look at this guide; http://www.insanelymac.com/forum/to...stallation-guide-with-full-speedstep-working/ user Stinga11 has done a great job there! You can follow the latter's way to install OS X but don’t go beyond Step 4 or alternatively, follow my method described below to install OS X.

Before initializing OS X setup we need to edit the config.plist located in the setup drive. Download the latest Clover Configurator app from this link: http://mackie100projects.altervista.org/download/. Open the downloaded app and mount the USB drive’s EFI partition. Open the config.plist and in SMBIOS section use/change the model to MacPro 6,1.

SMBIOS is becoming more and more an integral part of OS X features. No one will ever want to mess up things with negotiations profiles with Apple servers. I highly recommend to follow this outstanding guide by moderator “jaymonkey”; How to Fix iMessage to have a solid foundation and a valid/working iMessage which relies on a valid SMBIOS.

Go to RtVariables and insert 0x28 value in BooterConfig and 0x3 (0x67 as from 10.11.3) value in CsrActiveConfig to disable System Integrity Protection. Depending on which model of processor is being used, set FakeCPUID accordingly. For example; a Core i7 5930k best FakeCPUID would be 0x0306E4 as it is the best one representing the CPU’s model. For other CPU models try a bit of research on the above mentioned link. Moreover, note that some FakeCPUID such as 0x306A0 requires KernelPM enabled.

Users of Rampage V Extreme can directly use the config.plist provided in the attachment below and replace the one in the OS X USB installer’s EFI partition. Keep in mind that you still have to generate your own SMBIOS serial number as mentioned above.

The system is now ready to proceed with OS X setup.

In the Clover boot menu, for unsupported nVIDIA GTX models like the GTX 970 or any Maxwell generation’s GPU, use boot argument “nv-disable=1” and enable DSDT mask “Fake LPC”.

Step 1: Boot-loader and NVRAM.
Credits: slim.jim and jaymonkey

After OS X has been successfully installed, open this link https://sourceforge.net/projects/cloverefiboot/ and download the latest Clover boot-loader following the method provided in the screenshot below.

Note that RC scripts is mandatory for NVRam to work.

Clover 1.jpg
Clover 2.jpg



Step 2: Fundamental Kexts.
Credits: RehabMan, Stinga11 and AndrewKern

After the Clover set up has completed, open this link: https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads to download RehabMan’s latest Fake SMC and this link: https://bitbucket.org/RehabMan/os-x-intel-network/downloads to download RehabMan’s latest IntelMausi network kext. Copy the “Release” versions of the downloaded kexts and paste them in the hard drive’s EFI/Clover/kexts/10.11/

Download the "NullCPUPowerManagement.kext from this link: http://www.tonymacx86.com/resources/nullcpupowermanagement.268/
and place it in EFI/Clover/kexts/10.11/

Download the "Kext" attachment. Search and open the info.plist of the VoodooTSCSync.kext and edit the IOCPUNumber from “1” to “11” and save changes. The result should look like this:

<key>IOPropertyMatch</key>
<dict>
<key>IOCPUNumber</key>
<integer>11</integer>
</dict>

Place the kext in /EFI/Clover/kexts/10.11/

Note: The number “11” is the result of the number of CPU cores multiplied by 2 and minus one. So, for an 8 Core processor it would have been: 8x2=16, 16-1=15.

Install any OS X “system update” that is available (which is 10.11.3 as of this writing) and restart computer still with “nv_disable=1” argument for unsupported nVIDIA GPUS’.

Step 3: Create SSDT and DSDT
Credits: Piker-Alpha, Stinga11, RehabMan and AndrewKern

Intro

Using the famous Piker-Alpha’s (formerly RevoGirl’s) tool to generate DSDT and SSDTs’ is the best method so far. Depending on which type of boot configuration is being used in Clover’s DSDT section, SSDT parameters prior to the booting of OS X and arguments used to generate the script will impact in the outcome of the generated DSDT and SSDTs’.

The Ethical method

The ethical way wants that no DSDT mask is being used prior to the generating of the DSDT. The same goes for the SSDTs’, at least for the CPU Frequencies and Power Management, by disabling “Generate PSates” and “Generate CStates” in Clover’s SSDT parameters (not to be confused with “Enable” C states, e.g: Enable C2, Enable C4 and Enable C6 which should always be kept enabled). Piker Alpha’s tool will in anyway generate both SSDTs’.

Clover is able to generate its own untouched DSDT and SSDTs’ by pressing “F4” key at boot menu before booting in OS X. Clover will dump all the data tables in /EFI/Clover/ACPI/Origin/

Note: There won’t be any kind notification or confirmation appearing on the screen when this is done.

The Custom method

However, according to my findings, Rampage V Extreme carries one exception: “Fake LPC”. Fake LPC must always be kept enabled before booting in OS X. The “why?” is because without “Fake LPC” mask enabled, when generating the DSDT, it will contain an error preventing the user to compile the DSDT back as detailed with the “add DTGP” mask referred in Step 9. (Note that this error will only occur when using ACPI 4.0 compliant).

Furthermore, again according to my findings and adversely to the ethical method, letting Clover generating the C and P States have contributed to a better output of data tables. The benefits are shown when the system is booting with overclocked configurations or X.M.P enabled.

Process

For a better overview, it might be useful to have a look at this link http://www.insanelymac.com/forum/to...stallation-guide-with-full-speedstep-working/. You may as well follow the step 7, 9, 10. Nonetheless, I don’t guarantee the reliability of the output.

Otherwise, my method goes as follows:
Open this link https://github.com/Piker-Alpha/ssdtPRGen.sh (outstanding job by Piker-Alpha) and download the ZIP file. Open Terminal and drag the ssdtPRGen.sh over it and add these arguments: -x 1 –w 3 –b Mac-DB15BD556843C820 –turbo 6300 and press Enter.

Note: –b Mac-DB15BD556843C820 is to tell the script to use iMac 17,1 board-id to enable the CPU’s C2 and C7.

The script will download some files, generate the resulting DSDT and SSDTs’ and when something similar to this appears: “Do you want to copy /Users/hansherchenroder/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? “ press “N” and same of the second message.

On Finder/desktop, click on Go> Go to folder and paste this: ~/library/ssdtPRGen and press Enter. It will open the folder containing the generated SSDT and DSDT. Open the “ACPI” folder and make a copy of all SSDTs’ and DSDT only and paste them in a new folder on your desktop. Rename the SSDTs’ to one digit above. For example: SSDT, SSDT-1 and SSDT-2 would change to SSDT-1, SSDT-2 and SSDT-3 and so on so as there is no file named “SSDT.aml” present in the folder. Now there is place in the folder to accommodate for the real “ssdt.aml” which can be copied from this directory: ~/library/ssdtPRGen

Note: This “ssdt.aml” should always be the first SSDT, thus simply named as “ssdt.aml”. It should never be named as SSDT-1 or SSDT-2 etc…as it contains Power Management and frequencies configurations for the processor.

Download and install the latest MaciASL app from this link: https://sourceforge.net/projects/maciasl/
Open the new folder created on desktop and open the DSDT. Click on compile, the compiler should not return any error at this stage. If the compiler is retuning errors, then, you must have made a mistake or done something wrong up to this stage. In the good scenario, go to “Save as” and save a “Disassembled ASL File” copy in the same directory. We will now work and edit changes with the disassembled version of the DSDT as recommended by RehabMan.

Step 4: Enable Graphics Hardware Acceleration for unsupported nVIDIA GPU.
Credits: RampageDev and PikerAlpha

There are two methods of proceeding to enable unsupported Maxwell architecture nVIDIA GPU. The first one is by editing the AppleGraphicsDevicePolicy.kext (not the ethical way) and the second one is by inserting the device in the DSDT which I highly recommend as it avoids messing around with the original kext. Furthermore, it also instantly enable audio via HDMI and should be persistent even after OS X updates and fills PCI devices section in the system profiler.

First Method: Editing AppleGraphicsDevicePolicy.kext

Open this link; http://www.tonymacx86.com/graphics/161256-solving-nvidia-driver-install-loading-problems.html scroll to “Problem 4” and follow “Method 2” instructions. Download the latest nVIDIA web drivers for OS X which link should be provided on the aforementioned link. You should now be able to boot without “nv_disable=1” flag and instead use “nvda_drv=1” as boot argument to enable accelerated graphics.

Second Method: DSDT injection method

Open the IORegistryExplorer app provided in the attachment or use any other similar app of your choice. Go to the search box and type keywords like “.Display_boot” or “NVDA” and the app should list the device path as referred in the example below.

7ADB0DA9-B5B6-4949-98F0-A4B9A9158DED.png


You will notice, highlighted in red, the device path is PCI0@0>BR3A@3>H000@0. Note that this is according to my motherboard’s structure and your device path might be different. For e.g: PCI0@0>PEGP@0>H000@0.
Open the DSDT.dsl and expand “_SB” which normally should be around the fourth one in the list or expand them until you find “PCI0” then head to BR3A>H000. The device section should look like this:

Screen Shot 2016-05-15 at 6.07.26 PM.png


change the code to this:

Code:
Device (_SB.PCI0.BR3A.GFX1)
                {
                    Name (_ADR, Zero)
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x0C)
                        {
                            "AAPL,slot-name",
                            Buffer (0x07)
                            {
                                "Slot-1"
                            },

                            "@0,connector-type",
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            },

                            "@1,connector-type",
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            },

                            "@2,connector-type",
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            },

                            "@3,connector-type",
                            Buffer (0x04)
                            {
                                0x00, 0x08, 0x00, 0x00
                            },

                            "hda-gfx",
                            Buffer (0x0A)
                            {
                                "onboard-1"
                            }
                        })
                    }
                }
the new device code now should look like this:

Screen Shot 2016-05-15 at 6.08.24 PM.png


Enabling HDMI audio.

To Enable HDMI audio, edit the “Device (H001)” and change the code to this:

Code:
Device (_SB.PCI0.BR3A.HDAU)
                {
                    Name (_ADR, One)
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x02)
                        {
                            "hda-gfx",
                            Buffer (0x0A)
                            {
                                "onboard-1"
                            }
                        })
                    }
                }
The result should look like this:

Screen Shot 2016-05-15 at 6.08.51 PM.png


then click on compile. As the object have been assigned with new names, the compiler should return 2 errors like this:

62F5B3DE-5EC4-4EA2-BBB7-1F249895F83C.png


To fix this, “H000” needs to be changed to “GFX1” and “H001” to “HDAU”.

DF83695D-4DFC-4FBD-A599-13CFA43E8764.png


Now, these two external declarations needs to be added in the DSDT in order for the compiler to compile them. Scroll to the top of the DSDT and add these two lines as referred below, highlighted in red.

0A9F60FD-098C-4E59-A7F6-40CF2CA9AAA6.png


You should now be able to compile the DSDT.dsl without errors. Save an .aml copy of it as well and place the DSDT.aml in EFI>Clover>ACPI>Patched. Edit Clover’s config.plist to remove “nv_disable=1” and use “nvda_drv=1” flag. Download and install the matching nVIDIA web drivers for OS X and reboot the computer. Hardware Graphics acceleration should be enabled.

Step 5: Enable USB 2.0/3.0 and Sleep/Wake.
Credits: RehabMan

Within the edited DSDT.dsl find and replace EHC1>EH01 (there should be 3), EHC2>EH02 (there should be 3) and XHCI>XHC (there should be 11). Search for “XWAK” and make it do nothing.

Example;

Original:

Method (XWAK, ...)
{
... original code ...
}

To:

Method (XWAK, ...)
{
Return(0)
... original code ...
}

Compile the DSDT.dsl and save and replace both .dsl and .aml versions. Replace all the resulting DSDT and SSDTs’ (.aml versions only) in EFI>Clover>ACPI>Patched

Follow these steps chronologically;
Open this link https://github.com/RehabMan/OS-X-USB-Inject-All and download the provided ZIP file. Open the downloaded folder and locate “XHCI-x99-injector.kext”. Initially this kext prevent Sleep and will need to be edited to enable sleep.

Right click on the file and click “Show Package Contents” open Contents> Info.plist and add these lines;

<key>IOPCIPauseCompatible</key>
<true/>

Save changes and copy the kext to EFI>Clover>kexts>10.11>
Add the patches provided below respectively in your config.plist.

<key>ACPI</key>
<dict>
<key>DSDT</key>
<dict>
<key>Patches</key>
<array>
<dict>
<key>Comment</key>
<string>change EHC1 to EH01</string>
<key>Find</key>
<data>RUhDMQ==</data>
<key>Replace</key>
<data>RUgwMQ==</data>
</dict>
<dict>
<key>Comment</key>
<string>change EHC2 to EH02</string>
<key>Find</key>
<data>RUhDMg==</data>
<key>Replace</key>
<data>RUgwMg==</data>
</dict>
</array>
</dict>
</dict>

<key>KernelAndKextPatches</key>
<dict>
<key>KextsToPatch</key>
<array>
<dict>
<key>Comment</key>
<string>change 15 port limit to 30 in XHCI kext (9-series)</string>
<key>Find</key>
<data>g72M/v//EA==</data>
<key>Name</key>
<string>AppleUSBXHCIPCI</string>
<key>Replace</key>
<data>g72M/v//FQ==</data>
</dict>
<dict>
<key>Comment</key>
<string>change 15 port limit to 30 in XHCI kext (100-series)</string>
<key>Find</key>
<data>g72M/v//EA==</data>
<key>Name</key>
<string>AppleUSBXHCIPCI</string>
<key>Replace</key>
<data>g72M/v//Gw==</data>
</dict>
</array>
</dict>

Restart the computer and check if all the USB 3.0 ports are working and if sleep/wake is working and stable.
Only after confirming the above, open the downloaded “Kexts” folder and copy the GenericUSBXHCI.kext to EFI>Clover>kexts>10.11> and restart computer.

ASUS USB 3.1 add-in card

To enable the provided ASUS USB 3.1 add-in card (note you will still be limited to the USB 3.0 speed though as OS X is not yet supporting USB 3.1 protocol) open this link: https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads and download the latest USBInjectAll.kext and copy the “release” version to EFI>Clover>kexts>10.11>
Open Clover configurator app, mount EFI partition and open your config.plist. Go to “Boot” section and enable -gux_defer_usb2 and -gux_nosleep.
Restart the computer and check if all the USB 3.0 ports are working and if sleep/wake is working and stable.

Now, I have heard that there might be some devices plugged in the USB header that might prevent sleep such as: Corsair Link devices. A possible way to fix this might be to open the IORegistry app and locate the device’s path. Then open the DSDT.dsl, locate the device and delete the whole section and recompile the DSDT and replace the .dsl and .aml versions. This should make the system to ignore this device.

Step 6: NVMe with sleep fix.
Download the MacVidCards's NVMeGeneric.kext from this link: http://www.macvidcards.com/nvme-driver1.html and place the kext in EFI>Clover>kexts>10.11> and reboot your computer. Open the IORegistryExplorer app provided in the attachment and in search use keywords like “MinnowStor” or according to your NVMe drive model, for example “Samsung 950 Pro” and you should get the device path like in the example below.

657D220D-5444-41F1-B959-3603156D2A32.png


As illustrated above, my NVMe device path is PCI0>BR1B>H000. Keep in mind that your device path might be different. Open the edited DSDT.dsl, search for the corresponding device:

Screen Shot 2016-05-15 at 7.00.59 PM.png


and replace the code with this one:

Code:
Device (_SB.PCI0.BR1B.H000)
                {
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x02)
                        {
                            "AAPL,slot-name",
                            Buffer (0x07)
                            {
                                "Slot-6"
                            }
                        })
                    }
                }
Scroll to the beginning of the DSDT and add this external declaration: External (\_SB_.PCI0.BR1B.H000). Compile the DSDT.dsl and save and replace the .aml version as well. Replace the DSDT.aml in the EFI partition and restart, you should be able to achieve sleep.

For other motherboards’ model:

Note that “slot-6” is according to my configuration. However, if the NVMe port is not an integrated within the motherboard and is being used via a PCI-E add-in card, you should edit the “Slot-6” according to which PCI-E slot is it being used in.


Step 7: Enabling audio: Realtek ALC 1150.
Credits: Stinga11

Open this link: http://www.insanelymac.com/forum/to...stallation-guide-with-full-speedstep-working/ and follow Step 11.

Step 8: Enabling Bluetooth, AirDrop and Handoff.
Credits: RehabMan
Open this link https://bitbucket.org/RehabMan/os-x-brcmpatchram/downloads and download the latest BrcmPatchRAM. Open the “Release” folder and copy BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext to Clover>kexts>10.11>
Add the patch provided below into your config.plist under “KextsToPatch” section to enable Bluetooth, AirDrop and Handoff.

<dict>
<key>Comment</key>
<string>10.11.dp1+ BT4LE-Handoff-Hotspot, credit RehabMan based on Dokterdok original</string>
<key>Find</key>
<data>SIX/dEdIiwc=</data>
<key>Name</key>
<string>IOBluetoothFamily</string>
<key>Replace</key>
<data>Qb4PAAAA60Q=</data>
</dict>

Step 9: Energy Saver features.
After everything has been fixed and no DSDT edits will be required, you can now open the config.plist in Clover and enable “Add DTGP” and save changes. This will enable all (or mostly all) Energy Saver features like on a real Mac, for e.g. Power Nap.

Note: Every time you need to do whatever edit in the DSDT you will have to disable DTGP as it will create a byte error in a bit field at line 21727.

Alternatively, to avoid this hassle, you can change the “byte” word to “bit”. Therefore, the line shall change from:

“CreateByteField (CRS3, \_SB.PCI0.LPC0.SIO1._Y0D._HE, IRQS)”

To:

“CreateBitField (CRS3, \_SB.PCI0.LPC0.SIO1._Y0D._HE, IRQS)”.

Step X: Enjoy!

Credits to: tonymacx86.com, insanelymac.com, RehabMan, Piker-Alpha, Stinga11, slim.jim and AndrewKern

Special Notes
ROG OC Panel and Sleep conflict.

Having the ROG OC Panel plugged in the motherboard will cause instant wake from sleep. To fix this open the ROG’s module lid and turn “slow mode” switch OFF. Unplug the SATA power cable as well and sleep should work.
Thanks to user “Chino” who provided this solution at the ROG community https://rog.asus.com/forum/showthread.php?82012-OC-Panel-stops-quot-wake-up-from-Sleep-quot

Voltage Stability.

Users of Haswell-E architecture make sure that in BIOS under the “External DIGI+ Power Control” section the option for “CPU Spread Spectrum” is set to “disabled”. In fact it will not help for stability anyway as the Haswell-E chip has got it’s own FIVR (Fully Integrated Voltage Regulator) and by enabling the “CPU Spread Spectrum” it causes conflicts, thus, resulting in random resets. Thanks to user “Luke77” who has provided helped and crosschecked this.
 

Attachments

Last edited:
Joined
May 24, 2014
Messages
91
Motherboard
Asus X99-E WS
CPU
Intel 5820K
Graphics
Gigabyte GTX 980 G1 Gaming
Mac
MacBook Pro
Mobile Phone
iOS
This is a guide on how to set up Mac OS X 10.11 El Capitan of an x99 motherboard, more precisely for the ASUS Rampage V Extreme. Users of any other brand of x99 chipset may follow this as well. I will try to be as brief as possible and apologies for my bad English (not my native language).
...
Credits to: tonymacx86.com, insanelymac.com, RehabMan, Piker-Alpha, Stinga11, slim.jim and AndrewKern
Thanks a lot for your guide Hans. I am trying to get my Asus X99-E WS to work with a 5820K. I have been trying to use Clover but I read in another post of yours that you recommend UniBeast instead for the Clover installer. I will try that soon, but I was wondering why you recommend UniBeast over the Clover installer. What are the differences between both?
 
Last edited:
Joined
Aug 30, 2010
Messages
123
Motherboard
ASUS Rampage V Extreme
CPU
i7 5930k
Graphics
GTX 970
Mac
Mac Pro
Mobile Phone
iOS
Thanks a lot for your guide Hans. I am trying to get my Asus X99-E WS to work with a 5820K. I have been trying to use Clover but I read in another post of yours that you recommend UniBeast instead for the Clover installer. I will try that soon, but I was wondering why you recommend UniBeast over the Clover installer. What are the differences between both?
Hi Mulder, you're welcomed! :thumbup: In fact, I meant to use UniBeast in order to create the bootable USB disk drive installer which is a more convenient way to create the USB drive to avoid the hassle of going to redirect the folders manually etc... But you shouldn't be bothered about it because the latest UniBeast uses Clover as bootloader anyway. So, while it will create the OS X installer drive, it will install Clover along. Adversely, the previous versions of UniBeast might use Chimera or Chameleon so make sure to use the latest one. The difference is that Clover is light years more advanced than the legacy one's like Chameleon and also very handy for UEFI boot and fixes a lot of things rather than going to manually fix them in the DSDT (though the ethical way stills remains editing the DSDT manually) and also kext patching will be very useful...and there's so much more.

I hope I was able to clarify this for you. I will be adding some edits in my guide during the beginning of the coming week, for ex: fixes for NVME drive etc..

Stay tuned!:headbang:
 
Joined
May 24, 2014
Messages
91
Motherboard
Asus X99-E WS
CPU
Intel 5820K
Graphics
Gigabyte GTX 980 G1 Gaming
Mac
MacBook Pro
Mobile Phone
iOS
Hi Mulder, you're welcomed! :thumbup: In fact, I meant to use UniBeast in order to create the bootable USB disk drive installer which is a more convenient way to create the USB drive to avoid the hassle of going to redirect the folders manually etc... But you shouldn't be bothered about it because the latest UniBeast uses Clover as bootloader anyway. So, while it will create the OS X installer drive, it will install Clover along. Adversely, the previous versions of UniBeast might use Chimera or Chameleon so make sure to use the latest one. The difference is that Clover is light years more advanced than the legacy one's like Chameleon and also very handy for UEFI boot and fixes a lot of things rather than going to manually fix them in the DSDT (though the ethical way stills remains editing the DSDT manually) and also kext patching will be very useful...and there's so much more.

I hope I was able to clarify this for you. I will be adding some edits in my guide during the beginning of the coming week, for ex: fixes for NVME drive etc..

Stay tuned!:headbang:
Thanks for your reply Hans! So basically there is no difference between using UniBeast or Clover? I have been using Clover for quite some time now on my Z97 platform, but getting X99 to work is quite challenging. Hopefully I can work on it later today and let you know where I get stuck. Since I read you spend several months getting the Rampage to work, you probably have encountered quite some problems along the way. I will let you know how it goes and I am looking forward to your NVME update :)
 
Joined
May 24, 2014
Messages
91
Motherboard
Asus X99-E WS
CPU
Intel 5820K
Graphics
Gigabyte GTX 980 G1 Gaming
Mac
MacBook Pro
Mobile Phone
iOS
Thanks for your reply Hans! So basically there is no difference between using UniBeast or Clover? I have been using Clover for quite some time now on my Z97 platform, but getting X99 to work is quite challenging. Hopefully I can work on it later today and let you know where I get stuck. Since I read you spend several months getting the Rampage to work, you probably have encountered quite some problems along the way. I will let you know how it goes and I am looking forward to your NVME update :)
At the moment I am stuck at the infamous: Missing Bluetooth Controller Transport error. After a while, the prohibited sign comes up. Any suggestions how to fix this? I have already put my USB installer in a USB 2 port and disabled all USB 3 ports.
 
Joined
Aug 30, 2010
Messages
123
Motherboard
ASUS Rampage V Extreme
CPU
i7 5930k
Graphics
GTX 970
Mac
Mac Pro
Mobile Phone
iOS
At the moment I am stuck at the infamous: Missing Bluetooth Controller Transport error. After a while, the prohibited sign comes up. Any suggestions how to fix this? I have already put my USB installer in a USB 2 port and disabled all USB 3 ports.
Right now I don't have a precise indicator of what is causing this. I would suggest if you could reset your BIOS to default value and leave all USBs' enabled (even USB 3), enable USB EHCI handoff if it's present and disable any Wifi and Bluetooth as mentioned in my guide. If it doesn't fix it, post your config.plist I would like to have a look at it.
 
Joined
May 24, 2014
Messages
91
Motherboard
Asus X99-E WS
CPU
Intel 5820K
Graphics
Gigabyte GTX 980 G1 Gaming
Mac
MacBook Pro
Mobile Phone
iOS
Right now I don't have a precise indicator of what is causing this. I would suggest if you could reset your BIOS to default value and leave all USBs' enabled (even USB 3), enable USB EHCI handoff if it's present and disable any Wifi and Bluetooth as mentioned in my guide. If it doesn't fix it, post your config.plist I would like to have a look at it.
At the moment I have disabled all my USB 3.0 ports, but use a USB 3.0 stick in a USB 2.0 port. I also set the bios according to the following guide for my motherboard: http://www.tonymacx86.com/threads/5...x99-e-ws-clover-efi-sm951.168396/#post1069374
When trying to run the installer, I get the following outputs with the attached config file.

Verbose_1.jpg
Verbose_2.jpg
Verbose_3.jpg

I hope you can help me.
 

Attachments

Joined
Aug 30, 2010
Messages
123
Motherboard
ASUS Rampage V Extreme
CPU
i7 5930k
Graphics
GTX 970
Mac
Mac Pro
Mobile Phone
iOS
lol...I still don't get it why this obsession of turning that USB 3.0 OFF. You can leave it ON, in fact that's what I would suggest but of course you should install OS X via a USB 2.0 port. Only Bluetooth and WiFi are required to be OFF for the moment.

Secondly, I don't know the purpose of using MacPro 3,1 or MacPro 5,1 SMBIOS, this is completely absurd. You should use a MacPro 6,1 SMBIOS for x99 architecture. Delete any provided DSDT and SSDT also make sure that you have your BIOS at default setting, that is; no overcloking in any kind it might be and no X.M.P turned ON. Give that version of FakeSMC a try https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/RehabMan-FakeSMC-2015-1230.zip and replace it with the one present in your EFI partition. Make sure that NullCPUPowerManagement.kext and VoodooTSCSync.kext are present in the aforesaid folder as well.

Attached is a modified config.plist, give it a try and let me know. If it doesn't work, try disabling all the DSDT fix on Clover boot menu and try again. Afterwards, you will have to use a new serial number reflecting those expected from a MacPro 6,1.
 

Attachments

Joined
May 24, 2014
Messages
91
Motherboard
Asus X99-E WS
CPU
Intel 5820K
Graphics
Gigabyte GTX 980 G1 Gaming
Mac
MacBook Pro
Mobile Phone
iOS
lol...I still don't get it why this obsession of turning that USB 3.0 OFF. You can leave it ON, in fact that's what I would suggest but of course you should install OS X via a USB 2.0 port. Only Bluetooth and WiFi are required to be OFF for the moment.

...

Attached is a modified config.plist, give it a try and let me know. If it doesn't work, try disabling all the DSDT fix on Clover boot menu and try again. Afterwards, you will have to use a new serial number reflecting those expected from a MacPro 6,1.
Thanks for your reply. I also asked this question on another thread and there kduvernay replied with an EFI folder which booted my system into the installer. It can be found here:
http://www.tonymacx86.com/threads/good-news-for-x99-10-11-haswell-e-el-capitan.178425/page-34#post-1250887
When I have installed OSX, I think I can start following your guide on how to get USB and power management and such working. Thanks again :)
 
Joined
May 29, 2016
Messages
26
Motherboard
Asus Rampage V Extreeme
CPU
Intel Core i7 5930k Haswell-E @4.4 Ghz
Graphics
Gigabyte GTX 980 G1 Gaming
Mac
Mac Pro
Mobile Phone
Android, iOS
Hello. I try to modify DSDT.aml, but i just can't work with ssdtPRGen.sh to get DSDT file.

1) I get error when try to process command "Open Terminal and drag the ssdtPRGen.sh over it and add these arguments: -x 1 –w 3 –b Mac-DB15BD556843C820 –turbo 6300 and press Enter."" :

Code:
System information: Mac OS X 10.11.5 (15F34)
Brandstring: "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"

Override value: (-x) XCPM mode, now set to: 1!

Error: Invalid argument detected: –w (check ssdtPRGen.sh -h)
Aborting ...
Done.
Why it do not recognize -w ?

2) I try to get sleeping mode. But computer wakes up automatically after 2 seconds. (Video works fine, but audio is not playback sounds (audio devices display correct... Sometimes PS/2 keyboard is not working after wake up. And also i use xmp profile and overclock processor on 42*100 , when i just start hackintosh my processor works only 3500 mghz - speedstep works fine. But after instant wake up processor work up to 4160 mghz speedstep works fine, but with wrong voltages. What's wrong in my config, can you tell?) Hope thast is gone, when i get DSDT file with ssdtPRGen.sh and edit it.

3) Should i delete nullcpupowermanagment.kext for speedstep working (now it works fine)?
This is my kexts:

Thank you!
 
Last edited by a moderator:
Top