Contribute
Register

iMac Pro X299 - Live the Future now with macOS 10.14 Mojave [Successful Build/Extended Guide]

Status
Not open for further replies.
Hi KGP,
thank you for your assessment. I think too that there is the need of a few microcode/ME-Updates from the board manufacturers. The X299 Taichi XE UEFI for example is from late 2018, the one from the Prime X299-A is from 02/2019 anyhow. But confusingly enough W10 is booting, so there is obviously a HS/Mojave kernel problem with 9820X and newer 9900X (maybe not newer but specific revision).

Not necessarily, as any BIOS firmware is optimised for Windows at first place. If you look at the recent post #2,716 of @mcitiy, his i9-9900X is properly working with the ASROCK X299 TAICHI XE under HS, thus I would exclude any HS/Mojave kernel problem and I also doubt that there are actually different versions of the i9-9900X distributed by Intel.

Anyway, I guess one should really address such issues directly to the manufacturers, whereas any respective discussion here might not really help in this case.
 
Attached the System SSDT configuration for your X299-WU8 and current PCIe slot population you should build on.

I guess that any bug fixing, if necessary at all, and likely missing cosmetic corrections/adaptations can be done by yourself.

I would appreciate, if this time we could avoid any excess of subsequent posts like last time. ;)

Good luck,

KGP
I test your SSDTs .EGP7
Please look IOREG.
Thank you.
 

Attachments

  • Screen Shot 2019-04-15 at 11.11.39 AM.png
    Screen Shot 2019-04-15 at 11.11.39 AM.png
    230.8 KB · Views: 70
  • navaratnam’s iMac Pro (2).ioreg
    8.6 MB · Views: 75
This is a long shot but curious if anyone has tried the Rampage VI Extreme Omega and tried shorting pin 3 and 5 of the Titan ridge tb3 header cable to make thunderbolt work? Apparently shorting the pins forces the Titan ridge to stay active from cold boot on systems without a tb3 header.

With this it might be possible to move the Titan ridge card from slot 2 to another slot on the WS Sage boards.

Might have some experimenting to do :lol:
 
  • Like
Reactions: kgp
I test your SSDTs .EGP7
Please look IOREG.
Thank you.

There are no TB signatures in your current ACPI Table and EGP7.UPSB is unpopulated. Please check APR hardware/BIOS implementation. There might be also no TB implementation without any SSDT in your EFI-Folder at present.

Unplug/replug APR and THB_C to make APR again work on your system. If necessary, initialise APR under Windows at first place and ensure that it is working as expected. Everything else seems now properly implemented anyway.

399826
 
Last edited:
There are no TB signatures in your current ACPI Table. Please check APR hardware/BIOS implementation. There might be also no TB implementation without any SSDT in your EFI-Folder at present.

Unplug/replug APR and THB_C to make APR again work on your system. If necessary, initialise APR under Windows at first place.
Yes
I know If I add hot plug Detail in SSDT not work Alpine Ridge.
I thing All X299 System same like my System..
In windows 10 pro UEFI If I connect Thunderbolt devices show in Device manager.
 
Yes
I know If I add hot plug Detail in SSDT not work Alpine Ridge.
I thing All X299 System same like my System..
In windows 10 pro UEFI If I connect Thunderbolt devices show in Device manager.

@nmano,

please connect a TB device and USB-C device at boot to see if EGP7.UPSB becomes properly populated.

By this we can see at first place if the new common SSDT for all devices under PC01.BR1A.SL01 is now correctly defined!

Step by step and don't mix up things again. HP under macOS with the APR is a different story, we can discuss later and not now.

For now I am not interested if HP works on your system. For now I am interested if TB properly works with the current SSDT configuration.
 
Last edited:
@nmano,

please connect a TB device and USB-C device at boot to see if EGP7.UPSB becomes properly populated.

By this we can see at first place if the new common SSDT for all devices under PC01.BR1A.SL01 is now correctly defined!

Step by step and don't mix up things again. HP under macOS with the APR is a different story, we can discuss later and not now.

For now I am not interested if HP works on your system. For now I am interested if TB properly works with the current SSDT configuration.
I connect USB-C device and thunderbolt Adapter with SSDT not work.
If I remove thunderbolt SSDT It's worked.
 
I connect USB-C device and thunderbolt Adapter with SSDT not work.
If I remove thunderbolt SSDT It's worked.

What do you mean by "If I remove TB SSDT"? There is no specific TB SSDT anymore. Everything is implemented within SSDT-X299-SL01-FRWR-XHC2-TB3HP-SAT2.aml now.
 
What do you mean by "If I remove TB SSDT"? There is no specific TB SSDT anymore. Everything is implemented within SSDT-X299-SL01-FRWR-XHC2-TB3HP-SAT2.aml now.
If I remove SSDT-X299-SL01-FRWR-XHC2-TB3HP-SAT2.aml THB implemented.

This snap from windows
 

Attachments

  • Capture with THB.PNG
    Capture with THB.PNG
    1.1 MB · Views: 70
If I remove SSDT-X299-SL01-FRWR-XHC2-TB3HP-SAT2.aml THB implemented.

This snap from windows

We have to find the bug why it is not working. Please try SSDT-X299-SL01-FRWR-XHC2-TB3HP-SAT2-test.aml.zip attached below for testing proposes. It implements for now your own just basic TB device definition.

There are no respective ACPI replacements left in your config.plist that could mess up the entire EGP7@9 TB implementation, correct?
 

Attachments

  • SSDT-X299-SL01-FRWR-XHC2-TB3HP-SAT2-test.aml.zip
    1.6 KB · Views: 79
Last edited:
Status
Not open for further replies.
Back
Top