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

[manHands]

Let me know if anything looks out of place (btw, i noticed that most people don't have Audio inject=1 and a bunch of USB settings at the top like I do).

Is JPEG preview still not working? If so, your DVMT pre-alloc looks high. Set it back to the default of 64M, and see if that fixes it.

Injecting audio this way is one method. The other is described in that guide I reference earlier using Properties and the correct layout-id. Either way works with proper DSDT patches and AppleALC.kext. Also note that layout-id 1 is no longer valid in Mojave. I personally use layout-id 2 for this board. I also don't inject USB. This section of config.plist looks like this for me...

    <key>Devices</key>
    <dict>
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
            <dict>
                <key>layout-id</key>
                <data>
                AgAAAA==
                </data>
            </dict>
        </dict>
        <key>USB</key>
        <dict>
            <key>Inject</key>
            <false/>
        </dict>
    </dict>

In the end, just make sure you're only following one method.

 

[luckyal]

Is JPEG preview still not working? If so, your DVMT pre-alloc looks high. Set it back to the default of 64M, and see if that fixes it.

Injecting audio this way is one method. The other is described in that guide I reference earlier using Properties and the correct layout-id. Either way works with proper DSDT patches and AppleALC.kext. Also note that layout-id 1 is no longer valid in Mojave. I personally use layout-id 2 for this board. I also don't inject USB. This section of config.plist looks like this for me...

    <key>Devices</key>
    <dict>
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
            <dict>
                <key>layout-id</key>
                <data>
                AgAAAA==
                </data>
            </dict>
        </dict>
        <key>USB</key>
        <dict>
            <key>Inject</key>
            <false/>
        </dict>
    </dict>

In the end, just make sure you're only following one method.

SOLVED! I got rid of the entry in Clover Configurator and there is no longer an issue with JPEG and Preview. So thank you to both you and @pastrychef

As for Audio, I have been working for weeks to get my Thunderbolt Audio interface working to no avail. I have disabled all on board audio in BIOS but now wonder if my audio driver for the VRS8 is somehow conflicting with this setting. Would it hurt if I got rid of it altogether?

 

[luckyal]

Injecting audio this way is one method. The other is described in that guide I reference earlier using Properties and the correct layout-id. Either way works with proper DSDT patches and AppleALC.kext. Also note that layout-id 1 is no longer valid in Mojave. I personally use layout-id 2 for this board. I also don't inject USB. This section of config.plist looks like this for me...

I'm a bit confused. Are you talking about Audio the whole time here? If so, are you saying that I need to re-add Device properties within Clover Config once again? I just removed what I had earlier and my JPEG preview came back. Can you elaborate?

And is any form of Audio Injection required? I've been trying to get an Audio Interface to work without any success, so anything related to Audio I'm becoming suspicious of.

 

[manHands]

Are you talking about Audio the whole time here?

Yes, you asked about this setting in your config. I am talking about on-board audio however. I have no advice on a separate audio interface. Sorry.

 

[luckyal]

Yes, you asked about this setting in your config. I am talking about on-board audio however. I have no advice on a separate audio interface. Sorry.

Right, so the code you include in your post, specifically addresses Audio then, right? I ask because it looks a lot like code you shared a few posts earlier in reference to headless config.

 

[manHands]

Right, so the code you include in your post, specifically addresses Audio then, right? I ask because it looks a lot like code you shared a few posts earlier in reference to headless config.

Sorry, don't mean to confuse you. The code I posted before is specific to onboard audio for your MB, and getting it to work via Lilu, AppleALC, and your config.plist. This is all outlined in An iDiot's Guide To Lilu and its Plug-ins and the section on AppleALC on how to obtain this code via Hackintool using Method-2 (Device Properties).

However, since it sounds like you're not using onboard audio, none of this may be of any benefit for you.

 

[pastrychef]

I will try now. For now this is what I have as far as BIOS settings go and Clover Settings. Let me know if anything looks out of place (btw, i noticed that most people don't have Audio inject=1 and a bunch of USB settings at the top like I do).

You don't really need to enter anything in config.plist > Devices > Properties. macOS will detect your IGPU and dGPU properly.

You can enable virtualization.

 

[JCMunsonII]

If you are using an APFSDriverLoader, you do not strictly need apfs.efi - the driver loader will fetch the appropriate version for you. You should be able to safely remove it.

Ignore this post - I hadn't seen the slew of conversation prior to posting it...

 

[luckyal]

If it's not one thing, it's another. I got past the black screen and machine was stable, so I thought I'd implement an SSDT for USB port limit. Spent a solid 3 days reading and re-reading @RehabMan post, got USB working without issues. Went back into BIOS to enable Intel Virtualization and noticed that ALL of my BIOS settings are set to default. Hmm...I had never reset them, or hit clear CMOS button while testing my USB ports (don't even try ). Anyway, I decided to go through and set all my settings to what they were one by one. I discovered that I'm getting the same error as I attached to this post. Funny thing is I implemented all of the suggestions made by @pastrychef and @manHands . If I disable Thunderbolt, boots no problem. But obviously there's no way I'm going to do that because I need to get Thunderbolt going. The card is in great working condition and my UAD Apollo Twin MKII is recognized in Windows 10 and previously in macOS. So I'm sitting here scratching my head....again.

Most posts like the one here by @P1LGRIM talk about ensuring that all the usual drivers are loaded in the drivers64UEFI. One that caught my attention is AptioMemoryFix.efi which is what I have in the folder now. Should it be AptioMemoryFix-64.efi instead?

This one here by @BreBo says that I need to make changes to my config.plist by ensuring that CsrActiveConfig is set to 0x67 not 0x03.

@CaseySJ on the other hand was able to solve similar issue by "by using OsxAptioFix2Drv-free2000.efi in combination with slide=0. All other memory fix drivers are ineffective" as he describes in his build. I am accounting for the fact that his system is different than mine but also a fairly recent build.

Any thoughts?

 

[CaseySJ]

@CaseySJ on the other hand was able to solve similar issue by "by using OsxAptioFix2Drv-free2000.efi in combination with slide=0. All other memory fix drivers are ineffective" as he describes in his build. I am accounting for the fact that his system is different than mine but also a fairly recent build.

Any thoughts?

There are at least 3 methods for resolving Couldn't Allocate Runtime Area on boot. These methods may or may not work for your motherboard, but are worth attempting:

1. Shutdown system and unplug power cable for 10 seconds. This has the effect of clearing certain CMOS parameters and is easiest of the 3 methods.
2. If method 1 does not work, the next in order of inconvenience is replacing AptioMemoryFix with OsxAptioFix2Drv-free2000 as you pointed out. This should be attempted with and without slide=0. Removing AptioMemoryFix may also impact access to NVRAM, but don't worry about that yet. You can always install EmuVariableUefi64 in combination with "Install RC scripts on Target Volume" if you encounter problems with shutdown and reboot.
3. If method 2 also fails with and without slide=0, then re-flash the BIOS and configure BIOS parameters again.