Contribute
Register

[GUIDE] Full Power Management w/ Dual/Single Broadwell-EP/Haswell-EP CPUs on 10.12.

Joined
Oct 31, 2013
Messages
21
Motherboard
Supermicro X10-DAi
CPU
1x Intel Xeon E5 2643 v4 3.4 GHz
Graphics
XFX Radeon RX 480 8 GB
Mac
MacBook Air, MacBook Pro, Mac mini, Mac Pro
@metacollin, It's ~2 years later but your guide here let me upgrade a non-working Sierra install to a working High Sierra. X10DAi with TB add-in card (UAD Apollo works great when TB is set to Legacy in BIOS), 64 GB 2400 MHz DDR4 RAM. Only 32 GB utilized from using a single 2643 v4 CPU. RX 480 in slot 1. Thanks again. :)
 
Joined
Jul 23, 2011
Messages
55
Motherboard
Supermicro X11DAi-N
CPU
2x Platinum 8260M
Graphics
Radeon VII
Mac
Mac Pro
Classic Mac
Classic, Power Mac, PowerBook, Quadra, SE
Mobile Phone
iOS
@metacollin, quick question: Did you disable the automatic HFS+ to APFS conversion, or are you running APFS? Or did you upgrade from Sierra to High Sierra and not get the mandatory conversion to APFS? I know APFS is nice but risky for Hackintoshes. Thanks!
Sorry for taking so long to reply. I'm crazy busy these days.

Honestly, I uh didn't even know about the HFS+ to APFS without asking policy of the 10.13 installer, and didn't even notice/realize that anything had changed for a embarrassingly long time afterwards. If I had the option, I would have probably opted out, but I also don't care enough to actually go through the trouble of formatting my drive and reinstalling to get back to HFS+.

It also helps that my boot drive is an SSD, which theoretically APFS will someday be the best choice for. But, from a compatibility standpoint, let's just say that it doesn't matter at all. I used my desktop for months without even realizing the boot volume was APFS and not HFS+. I honestly don't think there is anything risky, it's just a file system. The disk is still a GPT disk, your bios can still see it, your bootloader (clover) can find the correct boot partitions and it all just seems to work. I would argue that all the reasons to use or not use APFS are completely 'real mac vs hackintosh' agnostic.

Actually, that's not quite true. If you need to manually fix something in the actual root partition, and you are dual-booting windows, then your options for working with APFS volumes are pretty limited and will require buying some software most likely. This will certainly change over time, but 3rd party support for APFS is limited right now.

That said, you should not be doing anything to your actual APFS partition anyway, as anything you might need to do you can do on the EFI (clover) partition, which remains good ol' FAT32.



I have the same motherboard and processes everything work fine on 10.13.4 but I am trying to make the sleep functionality work probably.

Any suggestions?

I assume when you try to sleep, your machine immediately wakes up? This is the same USB sleep problem seen in less exotic hardware, rehabman has some great tutorials on fixing this.

There is one caveat though, which is you will lose any ability to wake the computer via USB. So no key presses or mouse movements will wake your computer up. You pretty much have to press the power button to wake the computer back up.

I spent a very long time trying to find a solution to this, as this is kind of inconvenient and for me, the entire point of sleep is that one can easily wake the computer out of it simply by attempting to use the keyboard or mouse.

I ultimately traced the issue back to Apple's USB driver kext itself, and the fact that it was interfacing with a slightly different intel chip set, and when the system was put to sleep, the kext was actually disconnecting the virtual hubs of the USB controllers completely, so it was as if one had just unplugged everything from all the USB ports. The specific USB kext was, sadly, one of the parts of Darwin that Apple hadn't really open sourced at all, so the source code was unavailable.

Long story short, Apple's USB driver kext mismanages certain chipset's USB controllers in regards to sleep, so we can work around this using rehabman's DSDT/SSDT USB sleep fix, but there is really nothing to be done (except maybe a binary patch but I was never able to find exactly the bit of code responsible in Hopper) if you want sleep AND usb wake-ability. C'est la vie.
 
Joined
Nov 5, 2016
Messages
14
Motherboard
MSI X99A SLI PLUS
CPU
Intel i7-6800K 3.6Ghz
Graphics
MSI GeForce GTX 1060 Armor OC 6GB GDDR5
@metacollin, I have a working hack with High Sierra. I have a Broadwell-E processor, but I'm forced to use FakeCpuId as if it were a Haswell. Is it still possible to get power management working?
 
Joined
Jul 22, 2011
Messages
41
Motherboard
Supermicro X10DAI
CPU
Dual 14 core Xeon E5-2690v4 CPUs
Graphics
Radeon Vega Frontier Edition
Mobile Phone
Android
Sorry for taking so long to reply. I'm crazy busy these days.

Honestly, I uh didn't even know about the HFS+ to APFS without asking policy of the 10.13 installer, and didn't even notice/realize that anything had changed for a embarrassingly long time afterwards. If I had the option, I would have probably opted out, but I also don't care enough to actually go through the trouble of formatting my drive and reinstalling to get back to HFS+.

It also helps that my boot drive is an SSD, which theoretically APFS will someday be the best choice for. But, from a compatibility standpoint, let's just say that it doesn't matter at all. I used my desktop for months without even realizing the boot volume was APFS and not HFS+. I honestly don't think there is anything risky, it's just a file system. The disk is still a GPT disk, your bios can still see it, your bootloader (clover) can find the correct boot partitions and it all just seems to work. I would argue that all the reasons to use or not use APFS are completely 'real mac vs hackintosh' agnostic.

Actually, that's not quite true. If you need to manually fix something in the actual root partition, and you are dual-booting windows, then your options for working with APFS volumes are pretty limited and will require buying some software most likely. This will certainly change over time, but 3rd party support for APFS is limited right now.

That said, you should not be doing anything to your actual APFS partition anyway, as anything you might need to do you can do on the EFI (clover) partition, which remains good ol' FAT32.






I assume when you try to sleep, your machine immediately wakes up? This is the same USB sleep problem seen in less exotic hardware, rehabman has some great tutorials on fixing this.

There is one caveat though, which is you will lose any ability to wake the computer via USB. So no key presses or mouse movements will wake your computer up. You pretty much have to press the power button to wake the computer back up.

I spent a very long time trying to find a solution to this, as this is kind of inconvenient and for me, the entire point of sleep is that one can easily wake the computer out of it simply by attempting to use the keyboard or mouse.

I ultimately traced the issue back to Apple's USB driver kext itself, and the fact that it was interfacing with a slightly different intel chip set, and when the system was put to sleep, the kext was actually disconnecting the virtual hubs of the USB controllers completely, so it was as if one had just unplugged everything from all the USB ports. The specific USB kext was, sadly, one of the parts of Darwin that Apple hadn't really open sourced at all, so the source code was unavailable.

Long story short, Apple's USB driver kext mismanages certain chipset's USB controllers in regards to sleep, so we can work around this using rehabman's DSDT/SSDT USB sleep fix, but there is really nothing to be done (except maybe a binary patch but I was never able to find exactly the bit of code responsible in Hopper) if you want sleep AND usb wake-ability. C'est la vie.

I did as you suggested I disabled the usb controller entirely by patching my DSDT with the help of Rehabman, so it goes to sleep normally but when I wake the system up by pressing the power button the system restart instead of waking it self. I tried a lot of solutions but I couldn’t find what makes the system panic.

I hope if you don’t mind to share with me your patched bios rom and your clover folder l want to trace your files and compare them with mine. To see if I am missing something.
 
Joined
May 28, 2018
Messages
34
Motherboard
MSI X99A-RAIDER
CPU
Intel 6800k
Graphics
ZOTAC GeForce GTX 1060-6GD5 X-Gaming OC
Sorry for taking so long to reply. I'm crazy busy these days.

Honestly, I uh didn't even know about the HFS+ to APFS without asking policy of the 10.13 installer, and didn't even notice/realize that anything had changed for a embarrassingly long time afterwards. If I had the option, I would have probably opted out, but I also don't care enough to actually go through the trouble of formatting my drive and reinstalling to get back to HFS+.

It also helps that my boot drive is an SSD, which theoretically APFS will someday be the best choice for. But, from a compatibility standpoint, let's just say that it doesn't matter at all. I used my desktop for months without even realizing the boot volume was APFS and not HFS+. I honestly don't think there is anything risky, it's just a file system. The disk is still a GPT disk, your bios can still see it, your bootloader (clover) can find the correct boot partitions and it all just seems to work. I would argue that all the reasons to use or not use APFS are completely 'real mac vs hackintosh' agnostic.

Actually, that's not quite true. If you need to manually fix something in the actual root partition, and you are dual-booting windows, then your options for working with APFS volumes are pretty limited and will require buying some software most likely. This will certainly change over time, but 3rd party support for APFS is limited right now.

That said, you should not be doing anything to your actual APFS partition anyway, as anything you might need to do you can do on the EFI (clover) partition, which remains good ol' FAT32.






I assume when you try to sleep, your machine immediately wakes up? This is the same USB sleep problem seen in less exotic hardware, rehabman has some great tutorials on fixing this.

There is one caveat though, which is you will lose any ability to wake the computer via USB. So no key presses or mouse movements will wake your computer up. You pretty much have to press the power button to wake the computer back up.

I spent a very long time trying to find a solution to this, as this is kind of inconvenient and for me, the entire point of sleep is that one can easily wake the computer out of it simply by attempting to use the keyboard or mouse.

I ultimately traced the issue back to Apple's USB driver kext itself, and the fact that it was interfacing with a slightly different intel chip set, and when the system was put to sleep, the kext was actually disconnecting the virtual hubs of the USB controllers completely, so it was as if one had just unplugged everything from all the USB ports. The specific USB kext was, sadly, one of the parts of Darwin that Apple hadn't really open sourced at all, so the source code was unavailable.

Long story short, Apple's USB driver kext mismanages certain chipset's USB controllers in regards to sleep, so we can work around this using rehabman's DSDT/SSDT USB sleep fix, but there is really nothing to be done (except maybe a binary patch but I was never able to find exactly the bit of code responsible in Hopper) if you want sleep AND usb wake-ability. C'est la vie.
I have the same sleep black issus,Can you help me?
 
Joined
Dec 16, 2015
Messages
2
Motherboard
Supermicro X10DAL-i
CPU
Dual Xeon E5-2623v3
Graphics
AMD FirePro W9000
Mac
MacBook Pro
Mobile Phone
iOS
Just followed this for the second time for High Sierra, and almost everything is smooth and flawless -- the one exception being audio, which is mysteriously refusing to work with the usual set-it-and-forget it Lilu+AppleALC latest releases from GitHub. The first time I tried this and definitely had audio working was back on 10.13.5; might something have changed in 10.13.6?
 
Joined
Jul 2, 2017
Messages
44
Motherboard
MSI X99A Godlike Gaming
CPU
i7-6850K
Graphics
Vega 64
Mac
MacBook Pro
Mobile Phone
iOS
thank you @metacollin, great job!
now my rig is on 10.13.6, iMAC PRO SMBIOS + Broadwell E fakecpuid + native XCPM and OC.

where did you find this patch?

C1E30848 63D389D0 48C1EA20 B9990100 000F3048 FF05C99E 6B004883 C4085B5D C3662E0F 1F840000 000000
to
BB00FF00 004863D3 89D048C1 EA20B999 0100000F 3048FF05 C99E6B00 4883C408 5B5DC390 90909090 909090

:thumbup: :wave:
 
Joined
Aug 18, 2014
Messages
61
Motherboard
Asus X99 PRO USB 3.1
CPU
i7 6800K
Graphics
M6000
Mac
Mac Pro
Hello @metacollin! I need some help or advice. I'm working with Asus X99 PRO USB 3.1 and i7 6800K. Everything works fine but the GPU. It's a PNY Nvidia Quadro M6000. The performance is extremely poor and it crash with some apps like Final Cut X. It is enabled by Nvidia Webdrivers. I tried two other cards and found no issues (GTX 1050 and Rx 580).
Any ideas?
Thanks!
 
Top