nⓩxtMac Pro - i9-9900k - Gigabyte Aorus z390 Pro - macOS Mojave - Sapphire Vega 64 Reference

[ModMike]

I replaced all files and did a reboot. Fans and pumps are back but I also get a strange text right before the Clover Bootmenu (see attached pic).

Install VirtualSMC-64 and make sure that you don't have SMCHelper-64 installed. Don't rely on Clover Configurator, mount your EFI partition and make sure it's not there.

 

[ModMike]

Install VirtualSMC-64 and make sure that you don't have SMCHelper-64 installed. Don't rely on Clover Configurator, mount your EFI partition and make sure it's not there.

If you still get the same warning, update VirtualSMC itself. Please do one at a time so I know where the issue is.

 

[zoomlenz]

I installed the version of VirtualSMC that was in your archive. Wouldn't there by a conflict with installing the release version since it has the SMC kexts as Plugins within its bundle?

 

[ModMike]

I don't think so, because I only added to the kexts. I did try it and it worked for me although I didn't get that error. Then again I don't have those sensors which is why I am relying on you guys to test

I am following up with the SMC guys to resolve.

 

[ModMike]

I replaced all files and did a reboot. Fans and pumps are back but I also get a strange text right before the Clover Bootmenu (see attached pic).

Figured it out, I posted the debug version. I will post the proper version when I rescue my machine from a nightmare BIOS upgrade.

 

[kolutsham]

Figured it out, I posted the debug version. I will post the proper version when I rescue my machine from a nightmare BIOS upgrade.

Ok, good luck with that BIOS!

 

[ModMike]

So angry at ASUS right now. I have the motherboard out just to disconnect the CMOS battery. Boots beautifully in Windows but can’t get it to boot in OSX.

What worries me is that, on behalf of Intel, they downloaded uCode to the processor. I’m starting to wonder if that affects how OSX reacts to it.

It’s far fetched but I have no other theories. Wish me luck!

 

[kolutsham]

I don't think that it has anything to do with new CPU microcode, as I did an UEFI update for my Gigabyte board with the latest UEFI (with microcode update etc.) about 2 weeks ago and had no problems at all. But I remember that I've read (at a German hackintosh board) about similar problems about UEFI updates with Mojave 10.14.3 which seem to be gone with 10.14.4 - unfortunately, I can't find that thread anymore. It could also be a bug with the UEFI as someone mentioned in that thread, that he was in contact with ASUS support, and it was something with XMP memory settings (voltage)... Maybe you could try disable XMP.

 

[ModMike]

I don't think that it has anything to do with new CPU microcode, as I did an UEFI update for my Gigabyte board with the latest UEFI (with microcode update etc.) about 2 weeks ago and had no problems at all. But I remember that I've read (at a German hackintosh board) about similar problems about UEFI updates with Mojave 10.14.3 which seem to be gone with 10.14.4 - unfortunately, I can't find that thread anymore. It could also be a bug with the UEFI as someone mentioned in that thread, that he was in contact with ASUS support, and it was something with XMP memory settings (voltage)... Maybe you could try disable XMP.

That makes a lot of sense, it wouldn’t even post with optimized settings.

 

[ModMike]

Sure, would be happy to try it out. Do I need the efi or just the kext files?

Everything updated and officially merged to VirtualSMC GitHub. Not an official release yet but you can get the drivers in this thread. Let me know how it works out.