Contribute
Register

How to build your own iMac Pro [Successful Build/Extended Guide]

Status
Not open for further replies.
Since the update, I cannot boot with both of my monitors plugged in. I can boot with 1 monitor, then I can plug in the second, but both plugged in at boot = black screen. Any thoughts? Any other Maxwell owners that can vouch for dual monitor on 10.13.4?

GFX: Titan X (Maxwell)

Thanks!

nVidiaGraphicFixup.kext is installed, correct? Make sure you have the latest.
 
For those of you with sleep / wake issues, do you have a AIO connected to usb?

I built a hackintosh for a friend, and had the H100i that the system would wake after sleeping for 2 seconds.

The fix was to remove the USB port it was plugged in using the allusb.kext route.

It is connected yes. However the issue isn't about waking up the machine, it's to put it to sleep.
I had sleep/resume working on the Designare with the H115i plugged in, but only when nothing was connected to the thunderbolt ports.

Talking about H115i, there's now experimental support working in OSX. You can set the different profiles or read the fans speed.
 
My guess is that it doesn't work because of the thunderbolt devices I'm using (apple TB display), Promise Pegasus R4 and lacie TB ssd.

I have working Thunderbolt hotswap using Promise Pegasus R4 (TB1), Lacie 2big (TB3) and Drobo 5D (TB2). Using all devices in chain in this order - Lacie -> TB3 to TB2 adapter -> Drobo -> Pegasus. Before I got Lacie it was hotswaping fine using it like this - TB3 to TB2 adapter -> Drobo -> Pegasus.
Only thing I noticed is that for example if I plug Drobo into TB3 to TB2 adapter and then plug adapter into TB3 card, my Drobo wont show up, but if I plug it in diferent order - adapter into TB3 card first, then connect Drobo to adapter, it shows up fine.
 
I have working Thunderbolt hotswap using Promise Pegasus R4 (TB1), Lacie 2big (TB3) and Drobo 5D (TB2). Using all devices in chain in this order - Lacie -> TB3 to TB2 adapter -> Drobo -> Pegasus. Before I got Lacie it was hotswaping fine using it like this - TB3 to TB2 adapter -> Drobo -> Pegasus.
Only thing I noticed is that for example if I plug Drobo into TB3 to TB2 adapter and then plug adapter into TB3 card, my Drobo wont show up, but if I plug it in diferent order - adapter into TB3 card first, then connect Drobo to adapter, it shows up fine.

I have them connected like this:
TB3 -> TB3/TB2 adapter -> Pegasus 2 R4 -> Apple TB display -> Lacie

I tried just the Pegasus \, just the Apple display, or just the Lacie... Behaviour is always the same. All those devices are TB1 except the Pegasus (TB2)
I have a Samsung S8 connected to the second TB3 port via a 2m TB3 thunderbolt cable (that's just for charging). If I plug the S8 while the mac is running, it will cause the OS to hang.
the registry explorer shows that PCIHotplugCapable is properly set on the PC01->BR1A->UPSB->DSB0 device
and PCI-Thunderbolt is also set on PC01->BR1A->UPSB

I've had the same behaviour with the Asus ThunderboltEX (either in port 4 or port 7), the built-in TB3 ports on the designare, or with the ASRock TB3 card with either the Asus Prime Deluxe or the ASRock Professional Gaming EX...

Also, with the Asus ThunderboltEX card, I can't boot the machine if the Apple TB display is connected ; I get an error message about too great USB power draw and then it shuts down. This doesn't occur with the ASRock TB3 card (which uses exactly the same TB3 chipset has the real iMac Pro)
 
I have no doubt an SSDT can help, but I'm yet to read anyone actually pinpointing which change was absolutely necessary or which change caused sleep/wake to suddenly work.
So I'm very curious about that.

People have reported sleep/wake to work for them, even without SSDT changes. Or people using the SSDTfor the asus with a different motherboard, even though nine of the ACPI paths matched.

DSM2 had sleep/wake working with nothing.
Me even though I have the exact same board as you and configuration, and use an identical EFI folder, I never managed to get sleep to work properly. I've tried with 4 different motherboards. Never worked.
So my guess is the sleep/wake works depending on what you actually connect.
I have a device in my system that prevents sleep. I can't figure out which one though.
I'm certain it has nothing to do with the SSDT
Hi, since 10.13.4 update my 2nd monitor do not work anymore.... do you have both monitors working?
Some suggestions? Did you changed anything in your efi?
 
So I found it was the OS X WiFi card implementation doing me in. I removed that code and disabled the acpi dsdt patch for SLOC -> ARPT and almost everything is perfect.

The one thing that still isn’t working is HDMI audio. I did activate the kexts to patch from FredWst but still no audio. HDEF thru the Realtek audio works fine though. Will try DP audio later. Anyone else have this issue?

Awesome! I'm going to try this out, I couldn't even get the HDEF to populate in the PCI section, and was wondering if I needed to delete entries from the SSDT that have not been adjusted and implemented yet. I've got all the correct device id entries and ACPI patches in.. hoping for the best. :p

YES! all implemented and working! I managed to delete the entries from the SSDT that were not applicable to my motherboard and everything fell strait into place. The only thing that has changed is that when my system goes to sleep and come out of it the screen resolution is so small and just in the centre of the screen.. ill have to figure out what is going on there.
 
Last edited:
Just FYI, there is a very recent update to NvidiaGraphicsFixup that contains a workaround for the lag some have been experiencing with since .106 release of Nvidia web drivers.

I'm happy to report that with the 1.2.5 version of NvidiaGraphicsFixup kext and the latest Nvidia web driver the lag is gone!
 
Status
Not open for further replies.
Back
Top