pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[pastrychef]

The good news is that I am up and running again. I suppose that the update download may have been corrupted?

I don't think the update can cause all of that. I think something else was wrong with the hardware.

 

[elfcake]

I don't think the update can cause all of that. I think something else was wrong with the hardware.

I have the hardware tester now. Tomorrow I will spend some time testing.

 

[A4t0n10]

Yes, if you are going to use my EFI folder, remove all hackintosh kexts from /Library/Extensions/ and /System/Library/Extensions.

Please see post #4598.

I managed to solve by eliminating the Kext duplicates. Thanks for your help.

But now I have another problem, with your EFI folder the hardware acceleration is not activated (I used MacX Video converter) and in System Report there is only the GTX 1080 and not the iGPU. Using my EFI folder instead the iGPU is present and the hardware acceleration is active.

In my confing.plist is set by default "inject intel" in your config.plist no. If I try to set inject intel in your config.plist the iGPU is present in system reports but does not recognize any Kext in the Metal section.

 

[pastrychef]

I managed to solve by eliminating the Kext duplicates. Thanks for your help.

But now I have another problem, with your EFI folder the hardware acceleration is not activated (I used MacX Video converter) and in System Report there is only the GTX 1080 and not the iGPU. Using my EFI folder instead the iGPU is present and the hardware acceleration is active.

In my confing.plist is set by default "inject intel" in your config.plist no. If I try to set inject intel in your config.plist the iGPU is present in system reports but does not recognize any Kext in the Metal section.

Not possible. If you have IGPU enabled, it will be used by macOS.

The IGPU is not supposed to appear in System Information because it's configured to be headless/connector-less. Just because it doesn't appear in System Information does not mean it's not in use. Even on real iMacs, the IGPU does not appear in System Information. Use IORegistryExplorer to look for the IGPU.

Using config.plist > Graphics > Inject Intel is an older method that has been superseded. If you are on Mojave, you should not need any injections macOS should detect your IGPU. Make sure you have your BIOS set up correctly.

 

[dclive]

10.14.2 updated without issue.

 

[Juhne]

Just replace my Z370 Prime with a Strix Z390e (I'm that close to replace it to an Aorus Master but yeah the BIOS you know. My window to exchange it close January 31, so I will see). No problems since 2 weeks. All is working 100% as before (Just ofc need to use the emu kext for restart/sleep/shutdown). Updated to 10.14.2 without issue

 

[corint1]

I still think that z390 has nvram native ... I used uefitools and to my surprise I found in bios from 390 nvram the same as bios 370 ... even bigger ... I have no knowledge to interpret this information, but I do not think they have given up their native nvram ... maybe they just changed their shape or their memory address and fakesmc can not interpret it ... I do not know, but at first sight seems to have nvram ...maybe someone with more advanced knowledge will "dig" in this sense...

 

[pastrychef]

I still think that z390 has nvram native ... I used uefitools and to my surprise I found in bios from 390 nvram the same as bios 370 ... even bigger ... I have no knowledge to interpret this information, but I do not think they have given up their native nvram ... maybe they just changed their shape or their memory address and fakesmc can not interpret it ... I do not know, but at first sight seems to have nvram ...maybe someone with more advanced knowledge will "dig" in this sense...

Yes, Z390 has NVRAM. But AptioMemoryFix and OsxAptioFixDrv are not writing/reading to and from it correctly.

 

[corint1]

Yes, Z390 has NVRAM. But AptioMemoryFix and OsxAptioFixDrv are not writing/reading to and from it correctly.

thank you for confirmation...I suspected it was something unclean in the middle ... did you hear somewhere in the forum that it would work in the sense that the 390 nvram becomes readable?

 

[pastrychef]

thank you for confirmation...I suspected it was something unclean in the middle ... did you hear somewhere in the forum that it would work in the sense that the 390 nvram becomes readable?

I don't know. Hopefully, AptioMemoryFix or OsxAptioFixDrv will be updated with support for Z390 NVRAM. The same thing happened about 2 years ago and native NVRAM was broken for many motherboards. It took about a year before vit9696 fixed it with AptioMemoryFix.