Contribute
Register

[Success] ASRock Z390 Phantom Gaming-ITX + TB3 + iGPU + Mojave + SFF Build

I'm very glad to hear you.
I want to using iGPU.
Clover version is 4972. and I didn't update clover from post#1

Could you share your EFI files?
Hi. Here's my EFI, which I have changed the serial numbers/motherboard serials also and checked the coverage. They are new so you should be good-to-go.
This EFI should have Native NVRAM from SSDT-PMC.aml.
This EFI (mine) does not have any configuration regarding any NVMe storage devices/controller as you have in your orginal EFI post. That is, I have not included the "Sandisk Mass Storage Controller - NVMe PCIe" WD Black defination which you had in your orginal config.
Try this. :)

And BTW, this EFI contains Clover much newer. Can't remember actually, but it's like v511x.
 

Attachments

  • EFI.zip
    17.5 MB · Views: 98
Don't know if it's related to TB SSDT ? But it happened many times after TB SSDT was set. Could this be a conflict between WEG and TB SSDT ?

panic(cpu 0 caller 0xffffff7f86a858b6): "virtual bool AMD9500Controller::detectPowerDown(): GPU is not found. PCI config access fails!!!
"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/GPUDriversAMD/GPUDriversAMD-3.8.24/Common/IONDRV/ATI/IOFramebuffer/ATIFramebuffer/Abstraction/Sources/ATIController.cpp:3125
Backtrace (CPU 0), Frame : Return Address
0xffffff83bad4b350 : 0xffffff80053215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff83bad4b3a0 : 0xffffff800545a3c5 mach_kernel : _kdp_i386_trap + 0x155
0xffffff83bad4b3e0 : 0xffffff800544bf7e mach_kernel : _kernel_trap + 0x4ee
0xffffff83bad4b430 : 0xffffff80052c7a40 mach_kernel : _return_from_trap + 0xe0
0xffffff83bad4b450 : 0xffffff8005320c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff83bad4b550 : 0xffffff8005321087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff83bad4b5a0 : 0xffffff8005ac2c7c mach_kernel : _panic + 0x54
0xffffff83bad4b610 : 0xffffff7f86a858b6 com.apple.kext.AMDSupport : __ZN13ATIController10doGPUPanicEPKcz + 0x106
0xffffff83bad4b890 : 0xffffff7f86cdaa1c com.apple.kext.AMD9500Controller : __ZN17AMD9500Controller15detectPowerDownEv + 0xcc
0xffffff83bad4b8d0 : 0xffffff7f88d2e694 com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer6doWakeEv + 0xd4
0xffffff83bad4b9e0 : 0xffffff7f88d2f268 com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer6doDozeEv + 0x38
0xffffff83bad4ba10 : 0xffffff7f88d2e59e com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer19setSystemPowerStateEj + 0x7e
0xffffff83bad4ba40 : 0xffffff7f88d2e1dd com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer15doSetPowerStateEj + 0x8d
0xffffff83bad4ba70 : 0xffffff7f88d266b6 com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer12setAttributeEjm + 0x5e6
0xffffff83bad4bbf0 : 0xffffff7f88d276dc com.apple.kext.AMDFramebuffer : __ZN14AMDFramebuffer12setAttributeEjm + 0x160c
0xffffff83bad4bd70 : 0xffffff7f8671dfaa com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer14checkPowerWorkEj + 0x280
0xffffff83bad4be10 : 0xffffff7f8671dd08 com.apple.iokit.IOGraphicsFamily : __ZN14IOFBController14checkPowerWorkEj + 0x9a
0xffffff83bad4be40 : 0xffffff7f86724aeb com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer10systemWorkEP8OSObjectP22IOInterruptEventSourcei + 0x123
0xffffff83bad4bee0 : 0xffffff8005a2eb6d mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x17d
0xffffff83bad4bf30 : 0xffffff8005a2d43e mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffff83bad4bf70 : 0xffffff8005a2ca36 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffff83bad4bfa0 : 0xffffff80052c713e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f86713000->0xffffff7f86763fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f85d31000
com.apple.kext.AMDSupport(3.0.8)[6F5D9E4A-5DC8-3A3F-86E3-CF1AA832867F]@0xffffff7f86a81000->0xffffff7f86c86fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f8646f000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f85d31000
dependency: com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f86713000
dependency: com.apple.AppleGraphicsDeviceControl(5.1.16)[56FDE242-D4A6-3E8F-A81C-CE9BA61E3828]@0xffffff7f86a4a000
com.apple.kext.AMD9500Controller(3.0.8)[B5D08BE6-8777-38D1-8258-2C4A5DAE4C46]@0xffffff7f86ca6000->0xffffff7f86da1fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f8646f000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f85d31000
dependency: com.apple.kext.AMDSupport(3.0.8)[6F5D9E4A-5DC8-3A3F-86E3-CF1AA832867F]@0xffffff7f86a81000
dependency: com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f86713000
dependency: com.apple.AppleGraphicsDeviceControl(5.1.16)[56FDE242-D4A6-3E8F-A81C-CE9BA61E3828]@0xffffff7f86a4a000
com.apple.kext.AMDFramebuffer(3.0.8)[6E140F21-6547-3913-9A7F-C7FA19E607C1]@0xffffff7f88d1c000->0xffffff7f88d58fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[9D1FF279-C4A2-3344-902F-E0B22B508689]@0xffffff7f8646f000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4]@0xffffff7f85d31000
dependency: com.apple.kext.AMDSupport(3.0.8)[6F5D9E4A-5DC8-3A3F-86E3-CF1AA832867F]@0xffffff7f86a81000
dependency: com.apple.iokit.IOGraphicsFamily(575.1)[D47CA481-C5E5-3F03-9B04-6634DF5F3121]@0xffffff7f86713000

BSD process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 alcid=1 shikigva=80 igfxfw=2

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
 
Hello @rj510
I also want minimalistic setup without dGPU based on ASRock Z390 Phantom Gaming-ITX
I need hackintosh for work. My main requirements = 3 monitors 2560x1080 75Hz.

Is it possible to connect all 3 monitors at the same time? Maybe you try it.
1st - via HDMI, 2nd - via Display port, 3rd - via Thunderbolt 3 with Thunderbolt 3 to Dual DisplayPort Adapter

I see that such configuration is possible in theory, according to Intel website docs
1590247823874.png


What is your recommendation?
Or it's easier to take simpler motherboard, but with dGPU?

Thank you in advance.
 
@Qres, I've also noticed some GPU related kernel panics after adding these TB SSDTs, particuarly upon wake from sleep. Crashes don't always occur.

Another thing I've noticed is that with these TB SSDTs I'm getting an ACPI error (and panic) upon booting into Windows with OpenCore 0.5.8. No error when booting Windows using the Windows boot loader. Has anyone else noticed this?
 
@Qres, I've also noticed some GPU related kernel panics after adding these TB SSDTs, particuarly upon wake from sleep. Crashes don't always occur.

Another thing I've noticed is that with these TB SSDTs I'm getting an ACPI error (and panic) upon booting into Windows with OpenCore 0.5.8. No error when booting Windows using the Windows boot loader. Has anyone else noticed this?
According to the blog of @fangf2018 these SSDT’s cause BSOD when booting into Windows from OC. You can use rEFInd if you don’t want to change the boot options thru BIOS.
 
WEG is WhateverGreen
Thanks @sffjawsh .
Cause I’m not quit sure the exact function of WEG.
In my opinion, if it’s mimicking an EGPU, maybe the cause would be the system failed to catch the graphic card that supposed to be connected to TB but actually not.
 
Thanks @sffjawsh .
Cause I’m not quit sure the exact function of WEG.
In my opinion, if it’s mimicking an EGPU, maybe the cause would be the system failed to catch the graphic card that supposed to be connected to TB but actually not.
Its easy to disable WEG. Pass boot argument -wegoff to test. Look through GitHub for more details on what WEG does.
 
@mango1122, do you have any issues with crashes related to AMD GPUs with these TB3 SSDTs? Mine are sporadic. Some times there is no problem with wake from sleep, other times there are problems. Also seeing some variability with the attached TB device connecting properly after sleep-wake.

Have you had better success with the modified firmware?
 
Back
Top