Jump to content

[Success] El Capitan on ASUS X99/A i7 5820k Radeon r9 270x M.2


macandrea
 Share

30 posts in this topic

Recommended Posts

Hi, 

Here is my experience with this setup:

 

- ASUS X99/A USB3.1 Mainboard

- i7 5820k processor

- Radeon R9 270x

- SAMSUNG M.2 MZHPV256 storage

- ASUS PB287Q 4k display (Display Port connector)

 

Since I had to go through a lot of different resources to have it working properly, I wanted to share all the info in a single place.

 

Following the guide from http://www.rampagedev.com, and with the help from Slice, Mieze and Vlada from http://www.insanelymac.com/forum/topic/308025-no-graphics-usb-audio-after-wake/, the  info from Stinga from http://www.insanelymac.com/forum/topic/309717-haswell-e-5820k-5930k-installation-guide-with-full-speedstep-working/, El Capitan USB threads from Rehabman and constant updates from Pike's blog https://pikeralpha.wordpress.com we can get a really stable build based on X99 chipset with the following features:

 

- Speedstep working

- Audio through DP

- All USB2/3 ports working (USB3.1 ports disabled in BIOS)

 

You can find a screenshot attached

 

post-238487-0-09856300-1452296293_thumb.png

 

List of steps to be performed:

  • Disable Serial Port in BIOS (I cannot boot the system with Serial Port enabled), disable ASMEDIA USB 3.1 controller
  • Strictly Follow the installation guide in Rampagedev.com
  • Follow the X99 guide from Ramapgedev (except for config.plist) for 10.10 using the following files:

config.plist probably has redundant info, but basically provides the following features:

  • Rename EHC1, EHC2, XHCI in order to have USB fully working
  • use xcpm for power management
  • Patches AppleUSBXHCIPCI to remove usb port limit
  • Forces a fake processor ID to enable xcpm and speedstep

There is NO need for a specific processor P-states SSDT, but if you want to get no errors on boot you can create one following the details in the threads above. That's it. Attached mine, in case you want to use my configurations (47x max multiplier, 100Mhz BCLK)

 

BIOS configuration (for my setup):

  • Speedstep enabled
  • Turbo states enabled
  • Max CPU multiplier 47x as you can see from the xcpm info - I would suggest to start with "AUTO" for all CPU-related settings
  • BCLK 100 Mhz
  • Memory set to 2133 Mhz - If I increase memory speed to the upper 2k range or set the BCLK to higher freq. the system is very unstable and reboots without notice (this happens in El Capitan only, Yosemite works perfectly!)

Other:

  • M.2 disk does not require ANY specific action on BIOS or OSX
  • USB does not require any specific kext apart from the config.plist patches
  • OSX Sleep/Wake is NOT working properly - Radeon times out

In order to use Display Port I had to modify Rampagedev SSDT GFX0 section from:

                "@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
                }, 

to:

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

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

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

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

In order to fake MacPro6,1 AMD FirePro300 Video card you can add the following item in clover Info.plist under the KextsToPatch section:

 

post-238487-0-55581200-1453581443_thumb.png

 

 

Hope this helps!!

 

Andrea

 

 

X99_Injector.kext.zip

config.plist.zip

SSDT-1.aml.zip

  • Like 1
Link to comment
Share on other sites

I've seen a lot of post of X99 users claiming proper Speedstep and Turbo working, yet I've yet to see a screen shot of MSRDumper or AppleIntelInfo

verifying it. Can you give us a pic?  Thanks-

 

Also, looking at your config.plist boot args: <string>-v -xcpm npci=0x2000 kext-dev-mode=1 -f</string>

 

kext-dev-mode=1 is not used in ElCap and I don't think -f is a valid Clover flag...

Link to comment
Share on other sites

I've seen a lot of post of X99 users claiming proper Speedstep and Turbo working, yet I've yet to see a screen shot of MSRDumper or AppleIntelInfo

verifying it. Can you give us a pic?  Thanks-

 

Also, looking at your config.plist boot args: <string>-v -xcpm npci=0x2000 kext-dev-mode=1 -f</string>

 

kext-dev-mode=1 is not used in ElCap and I don't think -f is a valid Clover flag...

 

Is Intel Power Gadget not a good enough measure? Several people in Stinga's thread with screenshots of speedstep/turbo.

 

Plus, considering Cinebench scores increase by 15% after doing this, clearly turbo is working.

Link to comment
Share on other sites

Is Intel Power Gadget not a good enough measure? Several people in Stinga's thread with screenshots of speedstep/turbo.

 

Plus, considering Cinebench scores increase by 15% after doing this, clearly turbo is working.

Certainly not. Look at the attached screenshots in that thread, do you see many post that show in IPG a flat line at CPU max? No you don't. The point is that it's easy to get a few p-states, but who cares if you can't max the cpu. Also a 15% increase in Cinebench, Geekbench, or any tool is useless without knowing the starting point and again, being able to max the cpu... Might as well built a 4790 box.  Example:

 

post-922667-0-14989900-1452326579_thumb.png  post-922667-0-01380100-1452326610_thumb.png

 

The difference in the these 2 sreenies could easily equate to 3000 to 5000 points in Geekbench. I have yet to see in any post, anywhere, someone being able to max their X99 cpu in El Cap regardless of any FakeCPUID, without running NullCPUPowerManagement...

 

EDIT: If anyone can show otherwise I'd love to see it... :)

 

EDIT 2: For those that believe you can't get speed stepping while running null... (Playing movie in VLC)

https://dl.dropboxusercontent.com/u/34708684/IPG.m4v

Link to comment
Share on other sites

Hi snatch,

here is the screenshot, you are right the CPU is not maxed properly under a high load. I will make some other experiments, but it is clear to me this is a workaround, waiting for proper CPU support from Apple (if ever).

The main difference for me for using the fake processor ID is that I get some intermediate PStates I was not getting earlier.

 

Here the screenshots with the extreme scenarios:

 

First screenshot: fake CPUID and 47x overclock. Probably the worst profile (keeps moving among 33,40,47 where 40 and 47 are turbo states)

 

post-238487-0-70419800-1452338048_thumb.png

 

Second screenshot: no CUPID and no overclock. Probably the best profile (always 33, 34, 36), so lower temps, lower wattage, CPU is somehow maxed due to the few available states (34 and 36 are turbo states)

 

post-238487-0-91591800-1452338040_thumb.png

 

on a side note, here is the output for sysctl madcap.xcpm showing xcmp is enabled - if I understood Pike posts on xcmp correctly there is no need for AICPUPM or NullCPU to be loaded (in my situation those are not loaded an system is not complaining at all)

machdep.xcpm.mode: 1
machdep.xcpm.hard_plimit_max_100mhz_ratio: 47
machdep.xcpm.hard_plimit_min_100mhz_ratio: 8
machdep.xcpm.soft_plimit_max_100mhz_ratio: 47
machdep.xcpm.soft_plimit_min_100mhz_ratio: 8
machdep.xcpm.tuib_plimit_max_100mhz_ratio: 47
machdep.xcpm.tuib_plimit_min_100mhz_ratio: 8
machdep.xcpm.tuib_enabled: 0
machdep.xcpm.power_source: 0
machdep.xcpm.bootplim: 0
machdep.xcpm.bootpst: 47
machdep.xcpm.tuib_ns: 0
machdep.xcpm.ratio_changes_total: 199562
machdep.xcpm.maxbusdelay: 4294967295
machdep.xcpm.maxintdelay: 0
machdep.xcpm.mbd_mode: 1
machdep.xcpm.mbd_applications: 3
machdep.xcpm.mbd_relaxations: 3
machdep.xcpm.forced_idle_ratio: 100
machdep.xcpm.forced_idle_period: 30000000
machdep.xcpm.deep_idle_log: 0
machdep.xcpm.qos_txfr: 1
machdep.xcpm.deep_idle_count: 0
machdep.xcpm.deep_idle_last_stats: n/a
machdep.xcpm.deep_idle_total_stats: n/a
machdep.xcpm.cpu_thermal_level: 0
machdep.xcpm.gpu_thermal_level: 0
machdep.xcpm.io_thermal_level: 0
machdep.xcpm.io_control_engages: 0
machdep.xcpm.io_control_disengages: 1
machdep.xcpm.io_filtered_reads: 0

Andrea

Link to comment
Share on other sites

Hi snatch,

here is the screenshot, you are right the CPU is not maxed properly under a high load. I will make some other experiments, but it is clear to me this is a workaround, waiting for proper CPU support from Apple (if ever).

The main difference for me for using the fake processor ID is that I get some intermediate PStates I was not getting earlier.

 

Here the screenshots with the extreme scenarios:

 

First screenshot: fake CPUID and 47x overclock. Probably the worst profile (keeps moving among 33,40,47 where 40 and 47 are turbo states)

 

attachicon.gifScreen Shot 2016-01-09 at 11.42.51.png

 

Second screenshot: no CUPID and no overclock. Probably the best profile (always 33, 34, 36), so lower temps, lower wattage, CPU is somehow maxed due to the few available states (34 and 36 are turbo states)

 

attachicon.gifScreen Shot 2016-01-09 at 11.54.50.png

 

on a side note, here is the output for sysctl madcap.xcpm showing xcmp is enabled - if I understood Pike posts on xcmp correctly there is no need for AICPUPM or NullCPU to be loaded (in my situation those are not loaded an system is not complaining at all)

machdep.xcpm.mode: 1
machdep.xcpm.hard_plimit_max_100mhz_ratio: 47
machdep.xcpm.hard_plimit_min_100mhz_ratio: 8
machdep.xcpm.soft_plimit_max_100mhz_ratio: 47
machdep.xcpm.soft_plimit_min_100mhz_ratio: 8
machdep.xcpm.tuib_plimit_max_100mhz_ratio: 47
machdep.xcpm.tuib_plimit_min_100mhz_ratio: 8
machdep.xcpm.tuib_enabled: 0
machdep.xcpm.power_source: 0
machdep.xcpm.bootplim: 0
machdep.xcpm.bootpst: 47
machdep.xcpm.tuib_ns: 0
machdep.xcpm.ratio_changes_total: 199562
machdep.xcpm.maxbusdelay: 4294967295
machdep.xcpm.maxintdelay: 0
machdep.xcpm.mbd_mode: 1
machdep.xcpm.mbd_applications: 3
machdep.xcpm.mbd_relaxations: 3
machdep.xcpm.forced_idle_ratio: 100
machdep.xcpm.forced_idle_period: 30000000
machdep.xcpm.deep_idle_log: 0
machdep.xcpm.qos_txfr: 1
machdep.xcpm.deep_idle_count: 0
machdep.xcpm.deep_idle_last_stats: n/a
machdep.xcpm.deep_idle_total_stats: n/a
machdep.xcpm.cpu_thermal_level: 0
machdep.xcpm.gpu_thermal_level: 0
machdep.xcpm.io_thermal_level: 0
machdep.xcpm.io_control_engages: 0
machdep.xcpm.io_control_disengages: 1
machdep.xcpm.io_filtered_reads: 0

Andrea

Pikes post were long before the was a X99 platform. For giggles test 0x0306E0, add null and see what happens to your scores. Then you can decide between theory and results.

I think your post above was @ 4.70 clock, here's a 4.20:

 

post-922667-0-10951300-1452340061_thumb.png

Link to comment
Share on other sites

Thank you! I managed to get a flat line at CPU max without xcmp, but this is the behaviour I experienced:

 

- CPUs only reach 2 Pstates: min and max (from MSRDump)

- Intel monitor shows the average of the 6 cores, so under load I get a flat line because all processors are at max speed, but all the other peaks in the graph are just average values calculated on the 6 cores when <6 cores are at minimum speed (i.e. not actual PStates reached)

 

So:

- using xcmp with the fake 0x0306a0 processor I get 6 P-states (including turbo states), and rarely a flat line because it never happens that all cores are at max turbo speed at the same time

- using NULLCPU I get two P-states only, so a flat line is displayed under high load, and using Intel monitor I get the impression I am reaching other speeds - but that is just an average value

 

of course using NULLCPU I get a much higher Geekbench score, but on longer tasks (I work with audio) the temperatures rise fast - this is not a feasible solution for me.

 

Am I missing something or are you experiencing more PState values with MSRDump?

Link to comment
Share on other sites

MSRDump is not a good idea for your Hardware.

 

You can use Intel Power Gadget, or AppleIntelInfo  ;) 

 

Hi Ailan

My system when load AppleIntelInfo.kext quit system  shutdown.

x99gamingG1 with 5820K

Any fixes?

Thank you.

Link to comment
Share on other sites

More than likely bios settings...

 

attachicon.gifconfig.plist.zip

 

What BIOS settings then?

 

As for the 15% I mentioned earlier, Cinebench with Null and IPG shows a flat line at my max non-turbo multiplier with a score of ~1430-1440.

 

After -xcpm, fakecpuid, SSDT-1, that turns into 1650 average and up to 1710. Definitely NOT a flat line, but those gains are significant and real-world. 

 

I will gladly give your method a try and see if I get more stable Pstates, but clearly this is all a placeholder until the MacPro7,1 comes out. Yes, turbo is not "working" in the absolute sense, but it is much improved for my build and I'll take it!

 

Thanks for posting!

Link to comment
Share on other sites

Set logMSRs and logIGPU to false in the Info.plist file within the kext

Can you attach your AppleIntelInfo.kext, I can't get it to compile properly...

What BIOS settings then?

 

As for the 15% I mentioned earlier, Cinebench with Null and IPG shows a flat line at my max non-turbo multiplier with a score of ~1430-1440.

 

After -xcpm, fakecpuid, SSDT-1, that turns into 1650 average and up to 1710. Definitely NOT a flat line, but those gains are significant and real-world. 

 

I will gladly give your method a try and see if I get more stable Pstates, but clearly this is all a placeholder until the MacPro7,1 comes out. Yes, turbo is not "working" in the absolute sense, but it is much improved for my build and I'll take it!

 

Thanks for posting!

My bios won't settings won't help you as I'm not using your board. In your bios you might try leaving Turbo Settings to default and change the base clock to 42, 43 ,44, or whatever you're trying to reach. I think "MovieMaker" is using the same board as you, maybe shoot him a PM...

Link to comment
Share on other sites

Can you attach your AppleIntelInfo.kext, I can't get it to compile properly...

My bios won't settings won't help you as I'm not using your board. In your bios you might try leaving Turbo Settings to default and change the base clock to 42, 43 ,44, or whatever you're trying to reach. I think "MovieMaker" is using the same board as you, maybe shoot him a PM...

 

Out of curiosity, what did you do for your board? I am quite familiar with the Gigabyte BIOS as well.

Link to comment
Share on other sites

@snatch: attached you can find the compiled kext, and this is the output after a few minutes:

CPU Ratio Info:
------------------------------------
CPU Low Frequency Mode.............: 1200 MHz
CPU Maximum non-Turbo Frequency....: 3300 MHz
CPU Maximum Turbo Frequency........: 4700 MHz
CPU P-States [ (12) 28 33 ]
CPU C6-Cores [ 0 2 4 6 8 10 ]
CPU P-States [ (12) 19 28 33 ]
CPU C6-Cores [ 0 2 4 6 8 10 11 ]
CPU P-States [ (12) 19 28 29 33 ]
CPU C6-Cores [ 0 2 4 5 6 8 10 11 ]
CPU P-States [ (12) 17 19 28 29 33 ]
CPU C6-Cores [ 0 2 4 5 6 7 8 9 10 11 ]
CPU P-States [ (12) 14 17 19 28 29 33 ]
CPU P-States [ (12) 14 16 17 19 28 29 33 ]
CPU P-States [ (12) 14 16 17 18 19 28 29 33 ]
CPU P-States [ (12) 13 14 16 17 18 19 28 29 33 ]
CPU C6-Cores [ 0 2 3 4 5 6 7 8 9 10 11 ]
CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]
CPU P-States [ (12) 13 14 16 17 18 19 21 28 29 33 ]
CPU P-States [ (12) 13 14 15 16 17 18 19 21 28 29 33 ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 (22) 28 29 33 ]
CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 28 29 30 33 ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 28 29 30 32 33 (40) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 (27) 28 29 30 32 33 39 40 ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 27 28 29 30 32 33 39 40 41 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 27 28 29 30 32 33 35 39 40 41 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 27 28 29 30 32 33 35 39 40 41 42 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 27 28 29 30 32 33 35 39 40 41 42 46 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 24 27 28 29 30 32 33 35 39 40 41 42 46 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 24 27 28 29 30 32 33 34 35 39 40 41 42 46 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 24 27 28 29 30 32 (33) 34 35 39 40 41 42 44 46 47 ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 24 (27) 28 29 30 32 33 34 35 36 39 40 41 42 44 46 47 ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 24 27 28 29 30 31 32 33 34 35 36 39 40 41 42 44 46 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 24 27 28 29 30 31 32 33 34 35 36 37 39 40 41 42 44 46 (47) ]
CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 24 25 27 28 29 30 31 32 33 34 35 36 37 39 40 41 42 44 46 47 ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 24 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 44 46 (47) ]
CPU P-States [ 12 13 14 15 16 17 18 19 20 21 (22) 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 44 46 47 ]
 

AppleIntelInfo.kext.zip

Link to comment
Share on other sites

Set logMSRs and logIGPU to false in the Info.plist file within the kext

Thank you.

I just test without overclock

 

 

Last login: Tue Jan 12 11:14:39 on console

manoranjans-Mac-Pro-2:~ manoranjan$ sudo -s

Password:

bash-3.2# chown -R 0:0 ~/Desktop/AppleIntelInfo.kext

bash-3.2# chmod -R 755 ~/Desktop/AppleIntelInfo.kext

bash-3.2# kextload ~/Desktop/AppleIntelInfo.kext

bash-3.2# cat /tmp/AppleIntelInfo.dat

 

AppleIntelInfo.kext v1.2 Copyright © 2012-2015 Pike R. Alpha. All rights reserved

 

Settings:

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

logMSRs............................: 0

logIGPU............................: 0

logIntelRegs.......................: 1

logCStates.........................: 1

logIPGStyle........................: 1

InitialTSC.........................: 0xc84fd84522

MWAIT C-States.....................: 8480

PCH device.................: 0x8D478086

 

CPU Ratio Info:

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

CPU Low Frequency Mode.............: 1200 MHz

CPU Maximum non-Turbo Frequency....: 3300 MHz

CPU Maximum Turbo Frequency........: 3600 MHz

CPU P-States [ (12) 27 33 ]

CPU C6-Cores [ 0 2 4 6 8 11 ]

CPU C6-Cores [ 0 1 2 4 6 8 10 11 ]

CPU P-States [ (12) 18 27 33 ]

CPU C6-Cores [ 0 1 2 3 4 6 8 10 11 ]

CPU P-States [ 12 18 26 27 (33) ]

CPU C6-Cores [ 0 1 2 3 4 5 6 8 10 11 ]

CPU P-States [ 12 16 18 26 27 (33) ]

CPU C6-Cores [ 0 1 2 3 4 5 6 8 9 10 11 ]

CPU P-States [ (12) 16 18 20 26 27 33 ]

CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]

CPU P-States [ (12) 16 18 20 22 26 27 33 ]

CPU P-States [ 12 16 18 20 22 25 26 27 (33) ]

CPU P-States [ (12) 16 18 20 22 24 25 26 27 33 ]

CPU P-States [ (12) 16 18 20 22 24 25 26 27 28 33 ]

CPU P-States [ (12) 16 18 19 20 22 24 25 26 27 28 33 ]

CPU P-States [ (12) 16 18 19 20 22 24 25 26 27 28 29 33 ]

CPU P-States [ 12 16 18 19 20 21 22 24 25 26 27 28 29 (33) ]

bash-3.2#

 

 

Edited by Allan
Spoiler tag added
Link to comment
Share on other sites

Hi,

Radeon R9 270x is natively supported since Yosemite. The only problem is that sleep/wake will not work (see links in my first post).

 

In order to configure the card You have two options:

- use generic Radeon framebuffer - basically doing no configurations at all

- use futomaki framebuffer (I.e. Injecting Ati in clover and setting Futomaki as frame buffer), it might require FB connectors patching.

 

No performance differences on my side, the second option shows the correct card name in System Information.

 

You can then Modify dsdt or ssdt to have hdmi/dp audio enabled (see rampagedev ssdt) and rename the device to GFX0 (not strictly necessary to have video working)

 

There is a great post from Vlada specific for this card but I cannot find it right now.

 

Andrea

Link to comment
Share on other sites

  • 4 months later...

Hi macandrea. Is your build running smoothly? Are you experiencing any unexpected reboots? How is you USB-ports working? Still good?

The reason I'm wondering is I have a Gigabyte X99-UD4 board and also an Asus X99-A (non USB 3.1 version). I had the UD4 running for a year, super smooth also under El Capitan, but I was about to RMA the card because it wouldn't let me overclock. I then ordered the X99-A, but had all kinds of USB problems with it. Then reinstalled the UD4 and right about that time Gigabyte released a BIOS update fixing the overclock issue. But now I have USB and reboot issues with the UD4 card. Can't get my setup back to the state it was in. Have been struggling with this for two weeks now. Maybe it was the new BIOS version screwing up my USB ports, because I can't get it to work. I'm now wondering weather to go with the UD4 or the X99-A since I have them both. It seems that the USB issue is something I will really have to work hard to eliminate on both cards, and I therefore wonder if I just should switch to the X99-A board and try working out the USB issues there.

 

Any thoughts or hints? I have tried following your guide in this post, as well as stinga's in his speedstep post, but can't get USBs to work. Have also tried the plain old setup just following rampagedev's guide and nothing else (this was whats worked for me for a year), but the USB issues are the same.

 

Thanks

Link to comment
Share on other sites

 Share

×
×
  • Create New...