AptioMemoryFix and ApfsDriverLoader-64.efi

[spackley]

Hi all,
I've read that current thinking is to replace OsxAptioFix2Drv-64.efi and EmuVariableUefi-64.efi in /drivers64UEFI with AptioMemoryFix and ApfsDriverLoader-64.efi in Multibeast but am wondering if that will kill iMessage in Mojave. Took me a while to get iMessage working with my H170m DS3H mobo as it needs the Emulated NVRAM and scripts. Am not sure if I should go the new route and risk breaking it or stick with the old method. Anyone know if iMessage will it still work with the new method?

 

[spackley]

Anyone... anyone... Bueller... Bueller...

 

[P1LGRIM]

Your choice - Both methods work fine.
Very easy to test and equally easy to revert.

 

[spackley]

Your choice - Both methods work fine.
Very easy to test and equally easy to revert.

I guessed both methods worked, it was the effect on iMessage that I just wondered if anyone else had any experience of. Thanks for the reply P1lgr1m.

 

[jaymonkey]

Hi all,
I've read that current thinking is to replace OsxAptioFix2Drv-64.efi and EmuVariableUefi-64.efi in /drivers64UEFI with AptioMemoryFix and ApfsDriverLoader-64.efi in Multibeast but am wondering if that will kill iMessage in Mojave. Took me a while to get iMessage working with my H170m DS3H mobo as it needs the Emulated NVRAM and scripts. Am not sure if I should go the new route and risk breaking it or stick with the old method. Anyone know if iMessage will it still work with the new method?

@spackley,

No problem with iMessage when using AptioMemoryFix and ApfsDriverLoader-64 (you should also use AppleImageLoader-64 when using ApfsDriverLoader-64), I updated all my systems months ago to these efi drivers and iMessage works fine on all of them.

Cheers
Jay

 

[spackley]

@spackley,

No problem with iMessage when using AptioMemoryFix and ApfsDriverLoader-64 (you should also use AppleImageLoader-64 when using ApfsDriverLoader-64), I updated all my systems months ago to these efi drivers and iMessage works fine on all of them.

Cheers
Jay

Thank you @jaymonkey

 

[Blerticus]

Should "EmuVariableUefi-64.efi" be removed if "AptioMemoryFix-64.efi" is being used?

My (very non-scientific/subjective) experiments show that the following setup results in a stuttery/high-cpu experience

Activity Monitor shows kerneltask, sysmond, and WindowServer all running at the 80-110+% usage; and it looks like only one processor is being used, based on Activity Monitor's "CPU Usage" window.

/Volumes/EFI_M2/EFI/CLOVER/drivers64UEFI $ ls -la​

-rwxrwxrwx 1 mdj staff 12128 Oct 10 13:27 ApfsDriverLoader-64.efi​

-rwxrwxrwx 1 mdj staff 17280 Oct 10 13:27 AppleImageCodec-64.efi​

-rwxrwxrwx 1 mdj staff 1732 Oct 10 13:27 AppleImageLoader-64.efi​

-rwxrwxrwx 1 mdj staff 5376 Oct 10 13:27 AppleKeyAggregator-64.efi​

-rwxrwxrwx 1 mdj staff 2400 Oct 10 13:27 AppleUITheme-64.efi​

-rwxrwxrwx 1 mdj staff 25440 Oct 10 13:27 AptioMemoryFix-64.efi​

-rwxrwxrwx 1 mdj staff 5696 Oct 10 13:27 DataHubDxe-64.efi​

-rwxrwxrwx 1 mdj staff 21824 Oct 10 13:27 EmuVariableUefi-64.efi​

-rwxrwxrwx 1 mdj staff 21952 Oct 10 13:27 FSInject-64.efi​

-rwxrwxrwx 1 mdj staff 7232 Oct 10 13:27 FirmwareVolume-64.efi​

-rwxrwxrwx 1 mdj staff 24900 Jun 5 2018 HFSPlus.efi​

-rwxrwxrwx 1 mdj staff 4672 Mar 3 2017 OsxFatBinaryDrv-64.efi​

-rwxrwxrwx 1 mdj staff 4480 Oct 10 13:27 SMCHelper-64.efi​

​

Whereas, the following does not exhibit the high-cpu usage:

/Volumes/EFI_M2/EFI/CLOVER/drivers64UEFI $ ls -la​

-rwxrwxrwx 1 mdj staff 12128 Oct 10 13:27 ApfsDriverLoader-64.efi​

-rwxrwxrwx 1 mdj staff 17280 Oct 10 13:27 AppleImageCodec-64.efi​

-rwxrwxrwx 1 mdj staff 1732 Oct 10 13:27 AppleImageLoader-64.efi​

-rwxrwxrwx 1 mdj staff 5376 Oct 10 13:27 AppleKeyAggregator-64.efi​

-rwxrwxrwx 1 mdj staff 2400 Oct 10 13:27 AppleUITheme-64.efi​

-rwxrwxrwx 1 mdj staff 5696 Oct 10 13:27 DataHubDxe-64.efi​

-rwxrwxrwx 1 mdj staff 21824 Oct 10 13:27 EmuVariableUefi-64.efi​

-rwxrwxrwx 1 mdj staff 21952 Oct 10 13:27 FSInject-64.efi​

-rwxrwxrwx 1 mdj staff 7232 Oct 10 13:27 FirmwareVolume-64.efi​

-rwxrwxrwx 1 mdj staff 24900 Jun 5 2018 HFSPlus.efi​

-rwxrwxrwx 1 mdj staff 21984 Dec 8 12:10 OsxAptioFix2Drv-64.efi​

-rwxrwxrwx 1 mdj staff 4672 Mar 3 2017 OsxFatBinaryDrv-64.efi​

-rwxrwxrwx 1 mdj staff 4480 Oct 10 13:27 SMCHelper-64.efi​

​

Does this make sense? Or are these observations merely coincidental?

Thanks,

-- Mark

 

[Blerticus]

Should "EmuVariableUefi-64.efi" be removed if "AptioMemoryFix-64.efi" is being used?

My (very non-scientific/subjective) experiments show that the following setup results in a stuttery/high-cpu experience

Activity Monitor shows kerneltask, sysmond, and WindowServer all running at the 80-110+% usage; and it looks like only one processor is being used, based on Activity Monitor's "CPU Usage" window.

/Volumes/EFI_M2/EFI/CLOVER/drivers64UEFI $ ls -la​

-rwxrwxrwx 1 mdj staff 12128 Oct 10 13:27 ApfsDriverLoader-64.efi​

-rwxrwxrwx 1 mdj staff 17280 Oct 10 13:27 AppleImageCodec-64.efi​

-rwxrwxrwx 1 mdj staff 1732 Oct 10 13:27 AppleImageLoader-64.efi​

-rwxrwxrwx 1 mdj staff 5376 Oct 10 13:27 AppleKeyAggregator-64.efi​

-rwxrwxrwx 1 mdj staff 2400 Oct 10 13:27 AppleUITheme-64.efi​

-rwxrwxrwx 1 mdj staff 25440 Oct 10 13:27 AptioMemoryFix-64.efi​

-rwxrwxrwx 1 mdj staff 5696 Oct 10 13:27 DataHubDxe-64.efi​

-rwxrwxrwx 1 mdj staff 21824 Oct 10 13:27 EmuVariableUefi-64.efi​

-rwxrwxrwx 1 mdj staff 21952 Oct 10 13:27 FSInject-64.efi​

-rwxrwxrwx 1 mdj staff 7232 Oct 10 13:27 FirmwareVolume-64.efi​

-rwxrwxrwx 1 mdj staff 24900 Jun 5 2018 HFSPlus.efi​

-rwxrwxrwx 1 mdj staff 4672 Mar 3 2017 OsxFatBinaryDrv-64.efi​

-rwxrwxrwx 1 mdj staff 4480 Oct 10 13:27 SMCHelper-64.efi​

​

Whereas, the following does not exhibit the high-cpu usage:

/Volumes/EFI_M2/EFI/CLOVER/drivers64UEFI $ ls -la​

-rwxrwxrwx 1 mdj staff 12128 Oct 10 13:27 ApfsDriverLoader-64.efi​

-rwxrwxrwx 1 mdj staff 17280 Oct 10 13:27 AppleImageCodec-64.efi​

-rwxrwxrwx 1 mdj staff 1732 Oct 10 13:27 AppleImageLoader-64.efi​

-rwxrwxrwx 1 mdj staff 5376 Oct 10 13:27 AppleKeyAggregator-64.efi​

-rwxrwxrwx 1 mdj staff 2400 Oct 10 13:27 AppleUITheme-64.efi​

-rwxrwxrwx 1 mdj staff 5696 Oct 10 13:27 DataHubDxe-64.efi​

-rwxrwxrwx 1 mdj staff 21824 Oct 10 13:27 EmuVariableUefi-64.efi​

-rwxrwxrwx 1 mdj staff 21952 Oct 10 13:27 FSInject-64.efi​

-rwxrwxrwx 1 mdj staff 7232 Oct 10 13:27 FirmwareVolume-64.efi​

-rwxrwxrwx 1 mdj staff 24900 Jun 5 2018 HFSPlus.efi​

-rwxrwxrwx 1 mdj staff 21984 Dec 8 12:10 OsxAptioFix2Drv-64.efi​

-rwxrwxrwx 1 mdj staff 4672 Mar 3 2017 OsxFatBinaryDrv-64.efi​

-rwxrwxrwx 1 mdj staff 4480 Oct 10 13:27 SMCHelper-64.efi​

​

Does this make sense? Or are these observations merely coincidental?

Thanks,

-- Mark

Well. The problem recurred after running over 6 hours.

I've attached my EFI and IOReg files.

Thanks, in advance, for any comments/suggestions,

-- Mark

 

[donw35]

these are the only drivers I have in drviers64UEFI

ApfsDriverLoader-64.efi
AptioMemoryFix-64.efi

 

[Blerticus]

these are the only drivers I have in drviers64UEFI

ApfsDriverLoader-64.efi
AptioMemoryFix-64.efi

Yeah, I have several drives I boot from, with different OSes. Don't want to break that!

Thanks,

-- Mark