Recent content by antiserum420

IMO It's still better to create your own SSDT-UIAC because you are not dependent on the port limit patch. The port limit patch can break in future updates.

Okee thx, I will keep OsxAptioFix3Drv. Next step is to switch to OpenCore :)

I Removed the remaining Clover RC-scripts along with EmuVariableUefi.efi. Then I copied SSDT-PMC.aml to Clover patched dir. I tested NVRAM with a test variable and I can confirm it works. Thank you very much for this input. I have one question left regarding to this. I use OsxAptioFix3Drv.efi...

How did you manage to get native NVRAM to work? I have Asus ROG STRIX Z390-I board and as far as I know only emulated NVRAM works with this board. p.s I created a SSDT with this guide -> https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/

They are close, see -> https://www.tonymacx86.com/threads/the-everything-works-asus-z390-i-gaming-i7-8700k-sapphire-rx580-pulse-build.272572/page-300#post-2068228

I installed HWMonitorSMC2 2.6.0 found in here -> https://github.com/CloverHackyColor/HWMonitorSMC2/releases. It now shows my mainboard with sensor readings in combination with VirtualSMC, except my ambient temps. Does somebody know how I can fix this? I'm currently trying to fix it myself but if...

#update Today I successfully upgraded from MacOS Mojave 10.14.6 to MacOS Catalina 10.15.2. The only problem I had was Bluetooth not working correctly. I am using Dell DW1560 card which needs BrcmPatchRAM driver for Bluetooth to work. I did some investigation on this matter and found out that...

Unfortunately not yet. I am tempted to write an extension for VirtualSMC myself to support motherboard temperature and voltages.

I have 16 GB memory (2 x 8GB) and therefore can't reproduce your issue. 16GbB total memory does not have the issue you are describing. Maybe others in this thread could help you.

I use latest BIOS (Version 2417), and the latest Intel ME (Version 12.0.39.1431_S) without issues. Which EFI do you use? You also need to boot with -v (verbose) to see the boot log to have a better understanding what's going on.

Have you had the same behaviour using DGPU-EFI from the guide?

You have a DGPU build as your signature indicates. You probably have enabled intel IGPU without correct headless platform ID. If you disable intel IGPU in bios it probably works, but I recommend you keep it enabled and configure your IGPU in headless mode as is explained in this guide for Quick...

Try to disable onboard WiFi and Bluetooth in BIOS. I had similar issue when reaching the installer. After installation, enable them.

Try install BrcmPatchRAM2.kext, BrcmFirmwareData.kext and AirportBrcmFixup.kext in EFI/CLOVER/kexts/other. Open config.plist and under boot section add brcmfx-country=#a under Boot Arguments. Also be sure bluetooth onboard device is enabled in bios.

Increasing VRAM to 2048MB on systems that are connected to a single 1080P display or when using a Headless PlatformID will have no beneficial effect. So property: Key = framebuffer-patch-enable | Value = 01000000 | Type = Data is not needed when using IGPU in headless mode.