Contribute
Register

ASUS prime Z370-A Big Sur 11.2 sleep problem

I remember reading somewhere about the cable/reconnect thing. There was solution/hack which somehow simulates a dis-/reconnect (force a port rescan) in order to prevent having to mess with the cables. Not ideal, but maybe the only way, idk.

I'm very interested in that. Please link to the post if you can find it again. Thanks!
 
The quick fix for this distortion is toggling the power button on the monitor(s) - a more elegant hot plugging.

I tried a variation on that yesterday by leaving the power off of one monitor during boot. I was able to avoid the need for hot plugging if I left the DP monitor off while booting from the DVI monitor. After MacOS completed its boot, turning on the DP monitor caused MacOS to recognize it without screen corruption. However, it didn't work in reverse as the iGPU recognized that a DVI monitor was plugged in regardless of power state. It was already very late in the evening so I didn't try the same experiment with the HDMI monitor.

Any thoughts on running the iGPU in a headless mode as an "assist" to the dGPU?

If I'm not mistaken, that would be achieved by changing the AAPL,ig-platform-id entry from 07009B3E (3 display connectors) to 0300913E (0 display connectors). From the WhateverGreen FAQ.IntelHD for Coffee Lake and Comet Lake systems:

Recommended framebuffers:
  • Desktop:
    • 0x3EA50000 (default)
    • 0x3E9B0007 (recommended)
  • Laptop:
    • 0x3EA50009 (default)
  • Empty framebuffer (CFL):
    • 0x3E910003 (default)
  • Empty framebuffer (CML):
    • 0x9BC80003 (default)

However, this is not something that I can test since I don't have a discrete GPU.
 
@Scimitar
Maybe have a look here:

Translated to english



Original link

 
Last edited:
I've just created a thread about mds_stores running after every startup. May have a look at it.


Who deleted my thread about mds_stores? And why? I'm still bothered by that issue.
 
Who deleted my thread about mds_stores? And why? I'm still bothered by that issue.

You'll need to ask the moderator for the forum you posted that thread in.
 
For my latest quarterly maintenance update, I've updated my EFI folder to OpenCore 0.8.8 using OCAT. Everything seems to be working fine so I'm posting it for anyone interested in updating. I didn't mess with the new .contentVisibility option to suppress EFI volumes from showing up in the boot picker since I'm controlling that via ScanPolicy. However, I may play around with that at some point in the future. In the meantime, anyone having trouble seeing the MacOS installation volume can set ScanPolicy to 0 under Misc -> Security to restore default functionality.

Please note that 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.
 

Attachments

  • EFI.zip
    11 MB · Views: 67
Back
Top