Contribute
Register

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

Status
Not open for further replies.
Maybe a stupid question: How can I rename the SL05 to GFX0? I am not having an Asus Prime (its an Asus Strix) and I don't get it. Can anyone explain to me the steps necessary to do it?
 
Maybe a stupid question: How can I rename the SL05 to GFX0? I am not having an Asus Prime (its an Asus Strix) and I don't get it. Can anyone explain to me the steps necessary to do it?

See post #4806 for one option..

For second options see SSDT-X299-Nvidia.aml.

Code:
    Scope (_SB.PC02.BR2A)
    {
        Scope (SL05)
        {
            Name (_STA, Zero)  // _STA: Status
        }

        Scope (PEGP)
        {
            Name (_STA, Zero)  // _STA: Status
        }

        Device (GFX0)
        {
            Name (_ADR, Zero)  // _ADR: Address

And especially read the guide..
 
@ kgp: In case someone may have overlooked it: an updated Unibeast v. 9.0 for Mojave has been released, but (as of Oct. 10) not yet an updated Multibeast version for Mojave.
https://www.tonymacx86.com/resources/categories/tonymacx86-downloads.3/
Has there perhaps been plans for incorporating better X299 support within those two tonymacx86.com softwares (Multibeast & Unibeast)?
 
@ kgp: In case someone may have overlooked it: an updated Unibeast v. 9.0 for Mojave has been released, but (as of Oct. 10) not yet an updated Multibeast version for Mojave.
https://www.tonymacx86.com/resources/categories/tonymacx86-downloads.3/
Has there perhaps been plans for incorporating better X299 support within those two tonymacx86.com softwares (Multibeast & Unibeast)?

Not that I would know. There are Multibeast & Unibeast threads and there are my X299 threads. All threads are under separate permanent development so far and also take respectively separate credits.
 
Last edited:
First of all, thanks for the awesome guide.

Now I've Mojave up un runnig for about 48 hours of computig flawlessy.

I've just a question regarding the speedstep. I configured all like reported in the guide, with manual vcore voltage (in my case, 1.120 for 4,5 Ghz all-core).
With these setting in windows, the frequency in idle goes down, while the voltage remais fixed.
In MacOS, VID sensor reportes a fixed voltage of 0,99 Volt (slightly lower under load), which I suppose is incorrect. Checking kgp screenshot, there are similar values so I suppose an incorrect reading of a fixed voltage similar to the one reported in windows.
If I use voltage offset with negative offset in bios, in windows it's all ok (frequency and voltage go down in idle), while MacOS can't boot. So I suppose there are different voltage applied from winndows to MacOS.

How is your experience about that?

Best Regards.
 
First of all, thanks for the awesome guide.

Now I've Mojave up un runnig for about 48 hours of computig flawlessy.

I've just a question regarding the speedstep. I configured all like reported in the guide, with manual vcore voltage (in my case, 1.120 for 4,5 Ghz all-core).
With these setting in windows, the frequency in idle goes down, while the voltage remais fixed.
In MacOS, VID sensor reportes a fixed voltage of 0,99 Volt (slightly lower under load), which I suppose is incorrect. Checking kgp screenshot, there are similar values so I suppose an incorrect reading of a fixed voltage similar to the one reported in windows.
If I use voltage offset with negative offset in bios, in windows it's all ok (frequency and voltage go down in idle), while MacOS can't boot. So I suppose there are different voltage applied from winndows to MacOS.

How is your experience about that?

Best Regards.

Honestly, I now leave CPU Core Voltage simply on "Auto", "enable" CPU SVID Support and introduce AVX and AVX-512 offsets of "2" and "3", respectively.

Else with ASUS Multicore Enhancement on "Auto" and CPU Core Ratio on "SyncAllCores" my i9-7980XE works flawless @4.7GHz.

However, please keep mind and don't forget about my extended and sophisticated custom water blocking, which is absolutely mandatory for such BIOS configuration!

BIOS settings are the same for macOS and Windows, as required, common and recommended for dual boot systems.

Cheers,

KGP
 
First of all thanks a lot for the Guide, it's perfect!

But I have a few minor issues, which is driving me crazy (my monitor is LG 38WK95C and Vega with last bios):
1) HDMI: when the display goes into stand-by, to be able to reactivate, from the black screen, i have to choose HDMI2 and then return to HDM1 (HDMI Compatibility mode is grey in the monitor settings)
2) DP: using the DisplayPort of the GC-Titan Ridge, the BIOS works, the Clover and the verbose Mac boot works, but black screen at login (DisplayPort 1.2 enabled in the monitor settings)
3) Sleep: if i try to send the computer to sleep, it goes off and a second later it turns on again

Thanks for your time
MM
 

Attachments

  • EFI.zip
    35.8 MB · Views: 204
First of all thanks a lot for the Guide, it's perfect!

But I have a few minor issues, which is driving me crazy (my monitor is LG 38WK95C and Vega with last bios):
1) HDMI: when the display goes into stand-by, to be able to reactivate, from the black screen, i have to choose HDMI2 and then return to HDM1 (HDMI Compatibility mode is grey in the monitor settings)
2) DP: using the DisplayPort of the GC-Titan Ridge, the BIOS works, the Clover and the verbose Mac boot works, but black screen at login (DisplayPort 1.2 enabled in the monitor settings)
3) Sleep: if i try to send the computer to sleep, it goes off and a second later it turns on again

Thanks for your time
MM

1.) Install Whatevergreen.kext and Lili.kext
2.) Choose proper Display frequency under Display settings. Optional: Install SwitchResX
3.) Only adopt and include aml files required for your system. Verify under section "PCI" of Apple's system report and by means of IOREG that all PCI devices are implemented as expected.
 
1.) Install Whatevergreen.kext and Lili.kext
2.) Choose proper Display frequency under Display settings. Optional: Install SwitchResX
3.) Only adopt and include aml files required for your system. Verify under section "PCI" of Apple's system report and by means of IOREG that all PCI devices are implemented as expected.

1) Latest release causes more problems, the above does not resolve the problem
2) If I understood well, I tried to reduce the resolution to 3200x1333 instead of 3840x1600 but the problem remains
3) Our systems differ only in the CPU, I am using all your aml from GitHub, except the Thunderbolt I use just one for the Titan (EFI Folder included in the previous msg)

Thanks
Screenshot 2018-10-12 at 14.05.08.png
 

Attachments

  • Screenshot 2018-10-12 at 14.05.08.png
    Screenshot 2018-10-12 at 14.05.08.png
    309.2 KB · Views: 130
Status
Not open for further replies.
Back
Top