Jump to content

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


KGP-iMacPro
 Share

iMacPro Build/Guide Feedback   

26 members have voted

  1. 1. Does this guide help you in your endeavour?

    • yes
      21
    • no
      5

This poll is closed to new votes


656 posts in this topic

Recommended Posts

Hi @interferenc nice to see you in insanelymac (many of us don not use other forum for various reasons)

 

If you have some time could you explain your TSC patches and if you know why with uefipatch they can't be used with asrrock or gigabyte bios?

 

I have found a way to patch them in two steps but I am not very sure if their use could be useful or not ;)

Thank you

 

Okay so let's continue the discussion here.

 

@kgp

 

Yes, clover can put the plugin type into the first cpu with that option you selected in clover configurator.

 

Personally I prefer to edit my own SSDTs, but it should have the same effect.

Link to comment
Share on other sites

If you have some time could you explain your TSC patches and if you know why with uefipatch they can't be used with asrrock or gigabyte bios?

 

Sadly I am not familiar with all the different container types these bios capsule files use. UEFIPatch should be able to patch anything sooner or later, for example they added ffsv3 support when it was needed.

 

If you have problems patching some of the GUIDs then file an issue at github and I think they will sort it out.

 

I also have problems patching the same GUID more then one in the same run, that does not work, but patching in two rounds do work.

 

So, thats all I know about UEFIPatch, sorry.

 

As a last resort, you can patch manually be extracting the body, editing with a hex editor, and then replacing the body.

Link to comment
Share on other sites

You miss in my messages last two lines

I have patched it using your patches.txt (I don't know if it is useful or not also for those boards)

Thank you for your answer

 

Sadly I am not familiar with all the different container types these bios capsule files use. UEFIPatch should be able to patch anything sooner or later, for example they added ffsv3 support when it was needed.

 

If you have problems patching some of the GUIDs then file an issue at github and I think they will sort it out.

 

I also have problems patching the same GUID more then one in the same run, that does not work, but patching in two rounds do work.

 

So, thats all I know about UEFIPatch, sorry.

 

As a last resort, you can patch manually be extracting the body, editing with a hex editor, and then replacing the body.

Edited by Guest
Link to comment
Share on other sites

You miss in my messages last two lines

I have patched it using your patches.txt (I don't know if it is useful or not also for those boards)

Thank you for your answer

 

Oh yes I missed that.

 

About the usefulness:

 

If you have MSR 0xE2 locked, you need these three patches an Asus boards:

https://gist.github.com/interferenc/713e48b40735b2dbc15977bec4013d24

 

If you have Unsynced TSCs, you need a fix of some kind. We resorted to VoodooTSCSync, but I tried to sync the TSCs on boot and wake by using the location of the MSR 0xE2 locking asm code, nopping it out and then inserting a simple wrmsr(IA32_TSC_ADJUST, 0) instruction. This also needs to happen at two places, one for boot (pmpInitialize) and on wake (CpuInitPei). The third patch is just an occurence of the bios writing to the tsc (CpuMpDxe), and as that is something that we do not want in any case, I disabled it in any case.

https://gist.github.com/interferenc/d82357a13751bc24dcc5942f6af2374b

 

So thats it. If you have an unlocked board, the patches do not apply. If you have a different board with a bios that locks the registers in a different way/place, the patches do not apply. For those boards, alternative patches should be made.

  • Like 1
Link to comment
Share on other sites

Thank you for extended clarification you did here

I can't confirm this your quoted last part because some patterns you have in patches txt can be found and patched in different ways also in "unlocked board as Gigabyte or some ASrock)

So I am asking to understand well

now I will try to verify Asus X299 WS sage because if I will do a changement this one will be my motherboard

 

----

 

So thats it. If you have an unlocked board, the patches do not apply. If you have a different board with a bios that locks the registers in a different way/place, the patches do not apply. For those boards, alternative patches should be made.

Link to comment
Share on other sites

Now I understeand why normal people stoped to visit/use other forum (we know all which one)

 

How someone have to be an idiot to block the BEST, revolutionary thread on their forum, after few weirds comments, which were few days ago, everybody forgot and try to do something more for better support/ test etc... and some idiot came and block our thread - people are cool, but theirs admins are total idiot, it's increddible how someone can be sooo stupid.

 

I needed few moths to understeand people here and some reasons to stay only here...

now it's clear as sun... or something like that.. :)

 

I think I will change my principal place now and I hope some other great people will do the same...

 

If you're going to stay here it might be a good idea to lose the judgements and personal attacks.

That blocked thread was pretty well the only angry thread in all of the hackintosh community and we all know why. So please let this one keep away from that kind of emotion and let's stick to helping each other here ok :)

  • Like 2
Link to comment
Share on other sites

If you're going to stay here it might be a good idea to lose the judgements and personal attacks.

That blocked thread was pretty well the only angry thread in all of the hackintosh community and we all know why. So please let this one keep away from that kind of emotion and let's stick to helping each other here ok :)

I'm Sorry, I don't understeand "lose  the jugements and personal attacks".  - and I'm not sure but I think I don't know more details.

 

Angry thread? It was't angy thread, it was perfect thread,

...

 

Have a good night.

Link to comment
Share on other sites

I would also like to advice in a very quite and friendly mode to moderate some tones also here

Two or three harsh answer used against some very and old skilled user talking here are not good at all for a good way to interact with people and to do of this guide a really ‘flawless’ one

So I hope language barrier do not contribute also here to have some weird and unrespectfull behavior

Best regards to all

Link to comment
Share on other sites

I'll be getting that board too, so I guess will be two of us again :)

 

Thank you for extended clarification you did here

I can't confirm this your quoted last part because some patterns you have in patches txt can be found and patched in different ways also in "unlocked board as Gigabyte or some ASrock)

So I am asking to understand well

now I will try to verify Asus X299 WS sage because if I will do a changement this one will be my motherboard

 

Link to comment
Share on other sites

I need some help with my graphics settings :

 

When I had installed High Sierra with the guide I applied the following graphics seettings for my RX 580 :

 

 1/ RadeonDelnit in config.plist and watevergreen and lilu kexts in EFI/Clover/Kexts/Other and CPU ssdt.aml in ACPI/Patched

So my benchmark wasn't good about 55 fps

My system was stable sleep and wake with one clic on mouse.

 

2/ I did some research to improve that :

I set one change  enable-baffin-CUs.sh ellsmere 36

But another time my benchmark wasn't good about 55 fps

 

3/ I tried another way :

I removed only  watevergreen and lilu kexts :

I can boot my GPU was recognize as R9 XXX

but this time bingo the benchmark was quite good about 108 fps

 

But another problem this time I had sleep issue my build was randomly rebooting to wake.

 

Witch way to have graphics and sleep /wake  good ? 

Link to comment
Share on other sites

I need some help with my graphics settings :

 

When I had installed High Sierra with the guide I applied the following graphics seettings for my RX 580 :

 

 1/ RadeonDelnit in config.plist and watevergreen and lilu kexts in EFI/Clover/Kexts/Other and CPU ssdt.aml in ACPI/Patched

So my benchmark wasn't good about 55 fps

My system was stable sleep and wake with one clic on mouse.

 

2/ I did some research to improve that :

I set one change  enable-baffin-CUs.sh ellsmere 36

But another time my benchmark wasn't good about 55 fps

 

3/ I tried another way :

I removed only  watevergreen and lilu kexts :

I can boot my GPU was recognize as R9 XXX

but this time bingo the benchmark was quite good about 108 fps

 

But another problem this time I had sleep issue my build was randomly rebooting to wake.

 

Witch way to have graphics and sleep /wake  good ? 

As you figured it out already you should not use Whatevergreen and RadeonDeInit together use only one of them or if you have a custom SSDT or just patched the DSDT only use that.

What I mean is:

1. Just Lilu and WhateverGreeen

or

2. Only RadeonDeInit

or

3. SSDT for GPU

or

4. DSDT patch from Mieze

 

WhateverGreen can solve the sleep/wake issue but as far as I know there were some issues regarding macOS High Sierra (I didn't follow WhateverGreen's evolution for a while I guess if you can compile the latest version it might solve the sleep issue).

 

You can also use a SSDT for your GPU which essentially does exactly what the RadeonDeInit does but it's more specific to your GPU and it can also solve the R9 XXX issue as well (Which is cosmetic and has no effect on the performance)

 

To solve the R9 XXX you can either use the SSDT I mentioned or you can use Clover's on the fly patch

 

Look at http://www.insanelymac.com/forum/topic/328549-tracing-back-the-amd-gpu-wakeup-issue-to-its-origin/and you can fine all about the SSDT or DSDT patching to avoid the black screen on AMD GPUs.

 

Pavo also has a repo for customs SSDTs for AMD GPUs if you can find it it would help you a lot. It was posted in the topic I just gave the link.

  • Like 3
Link to comment
Share on other sites

As you figured it out already you should not use Whatevergreen and RadeonDeInit together use only one of them or if you have a custom SSDT or just patched the DSDT only use that.

What I mean is:

1. Just Lilu and WhateverGreeen

or

2. Only RadeonDeInit

or

3. SSDT for GPU

or

4. DSDT patch from Mieze

 

WhateverGreen can solve the sleep/wake issue but as far as I know there were some issues regarding macOS High Sierra (I didn't follow WhateverGreen's evolution for a while I guess if you can compile the latest version it might solve the sleep issue).

 

You can also use a SSDT for your GPU which essentially does exactly what the RadeonDeInit does but it's more specific to your GPU and it can also solve the R9 XXX issue as well (Which is cosmetic and has no effect on the performance)

 

To solve the R9 XXX you can either use the SSDT I mentioned or you can use Clover's on the fly patch

 

Look at http://www.insanelymac.com/forum/topic/328549-tracing-back-the-amd-gpu-wakeup-issue-to-its-origin/and you can fine all about the SSDT or DSDT patching to avoid the black screen on AMD GPUs.

 

Pavo also has a repo for customs SSDTs for AMD GPUs if you can find it it would help you a lot. It was posted in the topic I just gave the link.

  Thank's cyberdevs for your reply !

 

You're right i can't have "mixed seettings" :

 

Well :

- i have compiled my SSDT-RX 580.aml

- i have my ssdt.aml for my CPU

 

So i will to try to  boot without RadeonDeInit, watevergreen and lilu and see.

 

I readed the tread about the DSDT patch from Mieze but don't understand well to apply it.

Link to comment
Share on other sites

  Thank's cyberdevs for your reply !

 

You're right i can't have "mixed seettings" :

 

Well :

- i have compiled my SSDT-RX 580.aml

- i have my ssdt.aml for my CPU

 

So i will to try to  boot without RadeonDeInit, watevergreen and lilu and see.

 

I readed the tread about the DSDT patch from Mieze but don't understand well to apply it.

If you already have the SSDT it will do the exact same thing as the DSDT patch but in form of the SSDT and since you already compiled it, you don't need to worry about the DSDT stuff ;)

  • Like 2
Link to comment
Share on other sites

How do I check if my x299 asrock taichi is unlocked?

 

 

"X299 Systems with unlocked mainboard BIOS MSR 0xE2 BIOS register"

 

I have successfully installed my first mackintosh using your EFI and guide.  Now I'm going back just learning all of the things that kinda went over my head.  

 

Thank you for your guide :)

 

Link to comment
Share on other sites

How do I check if my x299 asrock taichi is unlocked?

 

 

"X299 Systems with unlocked mainboard BIOS MSR 0xE2 BIOS register"

 

I have successfully installed my first mackintosh using your EFI and guide.  Now I'm going back just learning all of the things that kinda went over my head.  

 

Thank you for your guide :)

 

 

 

Nice to see another Hackintosh Happy user :)

 

so to check if your MB is unlocked, I thking the easiest way:

 

mv ~/Downloads/voltageshift ~/Desktop/  (if you have downloaded voltageshift in downloads folder, you will copy that folder to desktop)

 

so then

 

cd ~/Desktop/voltageshift/

sudo chmod -R 755 VoltageShift.kext

sudo chown -R root:wheel ~/Desktop/voltageshift/VoltageShift.kext

./voltageshift read 0xe2

 

and the result should be something like

RDMSR e2 returns value 0x7e000003

 

voila :P

If someone have some other idea, I'm sure they will share .. :)

 

Have a nice day! :)

Link to comment
Share on other sites

yep

if you want another confirm

copy kext attached in your desktop 

then open a terminal window

 

cd desktop

 

sudo chown -R root:wheel AppleIntelInfo.kext

sudo chmod -R 755 AppleIntelInfo.kext

sudo kextload AppleIntelInfo.kext

 

sudo cat /tmp/AppleIntelInfo.dat

 

and search for MSR 0xE2

AppleIntelInfo.kext.zip

Link to comment
Share on other sites

yep

if you want another confirm

copy kext attached in your desktop 

then open a terminal window

 

cd desktop

 

sudo chown -R root:wheel AppleIntelInfo.kext

sudo chmod -R 755 AppleIntelInfo.kext

sudo kextload AppleIntelInfo.kext

 

sudo cat /tmp/AppleIntelInfo.dat

 

and search for MSR 0xE2

 

Please, just note once more that AppleIntelInfo.kext is incompatible with the i9-7980XE.. your system will immedeately reboot on kextload. 

Link to comment
Share on other sites

Please..just note his signature ;)

 

Please, just note once more that AppleIntelInfo.kext is incompatible with the i9-7980XE.. your system will immedeately reboot on kextload. 

post-468967-0-52075600-1518546011_thumb.jpg

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...