[SUCCESS] ASUS Z270 ROG Maximus IX Hero - i7-7700K - 32GB RAM - Intel HD 630

[luckyal]

Hey @JCMunsonII - could I ask you to try and enable VT-d and remove dart=0 in Clover to see if you get the same effect? I wonder if my Hero 9 is defective.

 

[pastrychef]

Gotta say I'm a bit surprised you have so many inside the CLOVER/kexts/other. I have long followed your advice to keep as much as possible in the /L/E. As a result I have been getting away with only FakeSMC.kext in the Clover folder. Granted, you do state:

Please note that /EFI/CLOVER/kexts/Other/ is NOT the recommended location for kexts. However, I have been doing it this way for quite a while now and have not had any problems doing so. If you want to do it the proper way, you can move all these kexts to /Library/Extensions/. Remember to rebuild kext cache if you do this. I also recommend that you install LiluFriend if you do this.

Curious as to why the change.

I've been keeping all my kexts in /EFI/CLOVER/kexts/Other/ for a long time. Zero problems.

In my opinion, it seems vit9696 (developer of Lilu, WhateverGreen, and AppleALC) originally intended his kexts to be in /EFI/CLOVER/kexts/Other/. Evidence:

Source: https://github.com/acidanthera/Lilu/releases


Also, Lilu and its extensions need to load early. This happens when they are in /EFI/CLOVER/kexts/Other/. When placed in /Library/Extensions, there's no guarantee that they will load early, this necessitates the use of LiluFriend. This, again, implies that Lilu and its extensions were meant be in /EFI/CLOVER/kexts/Other.

Source: https://github.com/PMheart/LiluFriend


Other than that, I have FakeSMC, IntelMausiEthernet, and USBInjectAll. These are considered "essential" to booting. (Try using a macOS USB installer and/or Recovery partition without these.)

Having these kexts in /EFI/CLOVER/kexts/Other/ allows me to boot and use (1) unmodified macOS USB installers and (2) unmodified hard drives/SSDs pulled from real Macs. It also means that when done doing whatever I need to do to those drives, they can be put back in the real Macs without any hackintosh files ever needing to be installed.

Lastly, I am able to boot macOS with SIP enabled on my hack without issues.

I don't want to start a debate on the topic. People far smarter and knowledgable than myself recommend using /Library/Extensions/. Personally, I use /EFI/CLOVER/kexts/Other/ without issues. It's up to you to decide how you want to configure your system.

 

[luckyal]

I've been keeping all my kexts in /EFI/CLOVER/kexts/Other/ for a long time. Zero problems.

In my opinion, it seems vit9696 (developer of Lilu, WhateverGreen, and AppleALC) originally intended his kexts to be in /EFI/CLOVER/kexts/Other/. Evidence:
View attachment 384274
Source: https://github.com/acidanthera/Lilu/releases


Also, Lilu and its extensions need to load early. This happens when they are in /EFI/CLOVER/kexts/Other/. When placed in /Library/Extensions, there's no guarantee that they will load early, this necessitates the use of LiluFriend. This, again, implies that Lilu and its extensions were meant be in /EFI/CLOVER/kexts/Other.
View attachment 384275
Source: https://github.com/PMheart/LiluFriend


Other than that, I have FakeSMC, IntelMausiEthernet, and USBInjectAll. These are considered "essential" to booting. (Try using a macOS USB installer and/or Recovery partition without these.)

Having these kexts in /EFI/CLOVER/kexts/Other/ allows me to boot and use (1) unmodified macOS USB installers and (2) unmodified hard drives/SSDs pulled from real Macs. It also means that when done doing whatever I need to do to those drives, they can be put back in the real Macs without any hackintosh files ever needing to be installed.

Lastly, I am able to boot macOS with SIP enabled on my hack without issues.

I don't want to start a debate on the topic. People far smarter and knowledgable than myself recommend using /Library/Extensions/. Personally, I use /EFI/CLOVER/kexts/Other/ without issues. It's up to you to decide how you want to configure your system.

Fair enough. It's great to have competing perspectives so that one can decide for themselves.

 

[luckyal]

I got my USB back, but even though I have an SSDT for the usb per Rehabman's guide, I have to Inject USB and FixOwnership. Does that seem strange?

 

[JCMunsonII]

Between 4/4 and 4/5/2019 I have been wrestling with the 10.14.4 update.

As usual, it comes down to kexts. Thanks to @pastrychef 's assistance, I ended up needing to remove all the sensor kexts as well as XHCI-200-series-injector.kext. This left IntelMausiEthernet.kext, Lilu.kext, WhateverGreen.kext, AppleALC.kext, FakeSMC.kext, and Vega_tab64.kext. I also disabled my onboard iGPU, and will be re-enabling it shortly to see if I can get back to my desktop. That will be done after Time Machine gets its current backup completed.

And then it will be on to cloning the system, and creating a proper install key! All time consuming of course, but needing to be done.

 

[manHands]

Between 4/4 and 4/5/2019 I have been wrestling with the 10.14.4 update.

As usual, it comes down to kexts. Thanks to @pastrychef 's assistance, I ended up needing to remove all the sensor kexts as well as XHCI-200-series-injector.kext. This left IntelMausiEthernet.kext, Lilu.kext, WhateverGreen.kext, AppleALC.kext, FakeSMC.kext, and Vega_tab64.kext. I also disabled my onboard iGPU, and will be re-enabling it shortly to see if I can get back to my desktop. That will be done after Time Machine gets its current backup completed.

And then it will be on to cloning the system, and creating a proper install key! All time consuming of course, but needing to be done.

Are you using WhateverGreen 1.2.8? It fixes KPs with KabyLake and 10.4.4...

Added KBL graphics kernel panic workaround on 10.14.4+

 

[JCMunsonII]

@manHands , do you have a build of that kext? Current release is v1.2.7.

At this point having the iGPU enabled KPs the system no matter the various graphics settings in BIOS.

 

[manHands]

@manHands , do you have a build of that kext? Current release is v1.2.7.

At this point having the iGPU enabled KPs the system no matter the various graphics settings in BIOS.

Here you go...

 

[JCMunsonII]

That fixed it! Thanks!

I also now have hardware acceleration, which I hadn't had up until this point. It may, or may not, be due to that version of the kext, or perhaps the lack of the sensor/XHCI kexts. I'm not up for strictly finding out though...

 

[manHands]

That fixed it! Thanks!

I also now have hardware acceleration, which I hadn't had up until this point. It may, or may not, be due to that version of the kext, or perhaps the lack of the sensor/XHCI kexts. I'm not up for strictly finding out though...

Good to hear! It was definitely the kext for me. I use CCC, and went through 3 or 4 installs that would hang at a black screen after the 2nd restart until I found another thread discussing this exact thing and replaced WG with the 1.2.8 version. After that, the install went smooth.