Recent content by Qres

  1. Qres

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

    @jonisign, great! With the trick, do you still have OC and WEG ?
  2. Qres

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

    @jonisign I have the same issue and under testing of RTCMemoryFixup.kext. The reference comes from this thread.
  3. Qres

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

    @candurin I'm using OC 0.59, and I noticed the OC CleanNvram function can alter the boot priority without getting into BIOS setting page. It seems that 4.4c stores some parameters in the NVRAM. Could that be the main different between Clover and OC ?
  4. Qres

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

    Clover or OC and which version No. ?
  5. Qres

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

    I have the same issue, even after I disable the SSDT. Maybe it's related to BIOS 4.4c.
  6. Qres

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

    @candurin you're using Clover ?
  7. Qres

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

    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.
  8. Qres

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

    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...
  9. Qres

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

    Thanks! @mango1122 . The KP keeps happening esp. after a long sleep. The error message is fixed. panic(cpu 4 caller 0xffffff8000e91b2c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x2cedd...
  10. Qres

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

    Thanks @mango1122 , in terms of a random DROM, I decided to put the original UID in though that's not following the CaseySJ's TB rule. No more error found. But the link speed changed. And the Domain UUID still changing every reboot. Is that normal ?
  11. Qres

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

    Sorry to confuse you @sffjawsh , my graphic card is RX460. Follow the CaseySJ's method, I build my own DROM into the SSDT. The system showed "Failed CRC8 Verification", while the UID in the TB page remain the same. I wonder if the SSDT DROM works only after we flashing the patched ROM.
  12. Qres

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

    The same as @fangf2018 , I use SSDT method. Don't know the relationship of enabling TB and the KP. But the error code can be traced to this article but I can not duplicate the process as the article mentioned.
  13. Qres

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

    Congratulate ! And great to know that our UID are different. UUID dominio changes every reboot while UID remain the same. It's better to mask UID. You still stay in the stock 14? Is the type-c working normally?
  14. Qres

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

    Maybe disable TB Boot Support.
  15. Qres

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

    @mango1122 Every reboot, the Domain UUID changes while UUID remain the same. Which means we do not have a fixed DROM and the system creates one by itself . Am I right ?
Top