ASUS prime Z370-A

zap737 said:

I have tried that as well. I was using 3200 x 1800 as my desktop resolution (as the UI is too small @ 4k) so I put 3200 x 1800 in my config and it made no difference,

Click to expand...

Bummer. Since the iGPU doesn't have this issue, I thought perhaps forcing the resolution in config.plist would solve the problem. Sorry I can't be of more help.

zap737 said:

I'm a compulsive BIOS updater.

Click to expand...

How do you recommend applying a ME update that ASUS sometimes posts along with a BIOS update? For example would you boot the machine into Windows on an external drive or is there a better way to do this?

I am looking into this for the profile rig (Z690P ...) where the ME update is strongly recommended by ASUS.

TIA

Just a heads up for those updating to macOS Sonoma 14.4 with a Fenvi wireless card. See this post if you have no wireless after running the OCLP root patches with OCLP 1.4.1. You need to update the IOSkywalkFamily.kext in your EFI/kexts folder.

zap737 said:

Just a heads up for those updating to macOS Sonoma 14.4 with a Fenvi wireless card. See this post if you have no wireless after running the OCLP root patches with OCLP 1.4.1. You need to update the IOSkywalkFamily.kext in your EFI/kexts folder.

Click to expand...

Thanks for the heads up @zap737! It's been a busy few months so I haven't had a chance to update OpenCore for a while now but your post motivated me to finally bring everything up to date with OC 0.9.9. I also took the opportunity to make some additional adjustments as well:

1. Enabled Wake-on-LAN functionality in IntelMausi.kext via a new Device Property entry.
2. Updated IOSkywalkFamily.kext to 1.1.0 and AMFIPass to 1.4.0 for Fenvi T919 support. Also removed the -amfipassbeta boot flag.
3. Removed the stolenmem parameter from the framebuffer patches (I recall that this was reportedly causing issues with UHD630 iGPU 4K monitor support).

Here are the two EFI folders, one unpatched and the other patched for Fenvi T919 WiFi support. As before, you'll need to input your own PlatformInfo values for ROM (onboard ethernet MAC address), MLB, SystemSerialNumber, and SystemUUID to ensure that the various iServices work properly.