Contribute
Register

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

Status
Not open for further replies.
I already told you that your current SSDT adaptation is totally wrong. Even if you ask a second time, the answer will still be that your actual SSDT implementation is totally wrong. Yet you have GFX0 and HDAU only implemented thanks to WEG.kext and not thanks to your SSDT implementation! Don't you see that the entire ACPI path in front of GFX0 is not like currently implemented in your SSDT implementation, and that due to your erroneous ACPI path definition within your SSDT, GFX0 is even implemented twice, once by your SSDT and and a second time by the WEG.kext? Don't you see that your current IROEG result after using your SSDT makes no sense at all?

Carefully study this small guideline which anyway provides all information you need to know. I guess I wrote this sentence already several dozens of times along my threads.. ;)

Else, following your IOREG.save above, one would intuitively expect the following necessary SSDT adaptation:

Code:
Scope: PC02.BR2A
Scope: nulling SL05
Scope:  PEGP (implementing existing PEGP device after nulling SL05)
Device: EGPA (implementing new EGPA device substituting "PCI bridge")
            Name (_ADR, 0x00100000)  // _ADR: Address
Device: EGPB (implementing new EGPB device substituting "PCI bridge")
            Name (_ADR, 0x00080000)  // _ADR: Address
Device: GFX0 (implementing new GFX0 device substituting "display")
            Name (_ADR, Zero)  // _ADR: Address


This should be really sufficient information to get your things properly done by yourself.

Good luck, my friend!

KGP

Holy this Holy that!!!

I've learned something!
Now you can say you helped me KGP! Well..you can say it anyway.

Is what's in the screenshot to be considered progress?
I bet it is some progress...but why EGPA? and not KAKA or PELE or WHAT...?
:D:D:D

Dankyou Dankyou so much!
 

Attachments

  • Schermata 2019-02-28 alle 21.32.52.png
    Schermata 2019-02-28 alle 21.32.52.png
    104 KB · Views: 202
  • Schermata 2019-02-28 alle 21.37.22.png
    Schermata 2019-02-28 alle 21.37.22.png
    115.7 KB · Views: 192
  • Like
Reactions: kgp
@merong
put CSM enabled in your Bios
It worked for me in dual screen with DVI and HDMI.
 
Holy this Holy that!!!

I've learned something!
Now you can say you helped me KGP! Well..you can say it anyway.

Is what's in the screenshot to be considered progress?
I bet it is some progress...but why EGPA? and not KAKA or PELE or WHAT...?
:D:D:D

Dankyou Dankyou so much!

You can also use KAKA or PELE or WHAT if not already in use. ;)
 
You can also use KAKA or PELE or WHAT if not already in use. ;)

Thank you so much...I really learned to think a bit more those PCI paths.
Namaste..:thumbup:
 
  • Like
Reactions: kgp
Thank you so much...I really learned to think a bit more those PCI paths.
Namaste..:thumbup:

Good.. now you might be also able to help others here and take some workload.. ;)
 
Thank you so much...I really learned to think a bit more those PCI paths.
Namaste..:thumbup:

Yep the X299 sage boards are a bit more difficult to adapt the ssdts due to it having more pci bridges. It makes a lot more sense once you get it :lol:
 
hi there, please do update your info so we can see your correct CPU model.

You seem to be using nvidia graphics, which is from where the KP is coming from -CUDA and such- your .plist has no NvidiaWeb checked in System Parameters, which in your case, should be.

You have unnecessary kext in your EFI folder, and two different instances of a "SMC" pluging, which can cause conflict, use the set provided in guide and remove all instances of FakeSMC and lugins, plus VirtualSMC and its plugins.

You should also remove instances of SSDT-RX in your ACPI patched section and unnecessary SSDT in your EFI folder. Check clover version, and verify your CPU has 12 core as set on your TSCAdjustReset.kext .plist

report with changes


Finally got around to making these amends and now my system hangs on DSMOS.

I've double checked and I have a FakeSMC in my ktexts and I added that NvidiaWeb checkbox in System Parameters.

Any ideas?

Thanks
 
Finally got around to making these amends and now my system hangs on DSMOS.

I've double checked and I have a FakeSMC in my ktexts and I added that NvidiaWeb checkbox in System Parameters.

Any ideas?

Thanks
Boot with -v, keepsyms=1, debug=0x100 and upload pictures

Upload your current EFI folder to see what have you changed.
 
Status
Not open for further replies.
Back
Top