Here's to hoping this saves someone else 27(!) reboots into the Catalina installer followed by black screens after verbose boot completes.
As the title says, this was done on an ASUS Prime H310M-A.
GPU connector patch settings: Obviously, you need to have WhateverGreen available, have a Pci(0x2) section in your config and set ig-platform-id to its correct value, which is likely to be 07009B3E in its raw form, as well as setting framebuffer-patch-enable. In this section, create the following properties (the type, as always, is Data):
| Name | Value |
|---|---|
| framebuffer-con0-busid | 02000000 |
| framebuffer-con0-enable | 01000000 |
| framebuffer-con0-index | 02000000 |
| framebuffer-con0-pipe | 12000000 |
| framebuffer-con0-type | 00080000 |
| framebuffer-con2-busid | 01000000 |
| framebuffer-con2-enable | 01000000 |
| framebuffer-con2-index | 01000000 |
| framebuffer-con2-pipe | 12000000 |
| framebuffer-con2-type | 00080000 |
| framebuffer-con1-enable | 01000000 |
| framebuffer-con1-index | 03000000 |
| framebuffer-con1-pipe | 12000000 |
Safe Mode POST fix: If, after rebooting cleanly or otherwise, you get an error about the firmware starting in safe mode, macOS has corrupted part of your firmware configuration while trying to keep time. Besides being an inconvenience on every reboot (especially if you have a firmware password protecting the setup screen...), consistent repeated corruption during the course of normal operation doesn't sound like something very comforting.
Thankfully the OpenCore developers have acknowledged this and there is indeed a fix you can apply to your config.plist after making sure you have the latest OpenCore release:
- Quirks -> DisableRtcChecksum should be set to true/yes.
- NVRAM -> Add -> 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 -> rtc-blacklist should be a Data type value set to
5859.
With all this done, I have a working Catalina installation via OpenCore with no verbose boot, FileVault 2, and a USBMap SSDT (corpnewt's script worked just fine here) properly handling all the devices hanging off my machine with the port limit patch disabled.
Additionally: If you have a USB headset that started making "whooshing" sounds or the like when you move around post Catalina installation, and this headset has a mic, with the mic potentially retracted/upright, and especially if you have long hair, you very likely don't have a USB problem.
You instead have an issue with microphone "monitor mode" (where you hear what you speak faintly) and the audio input volume being automatically set to max. Turning it down from system preferences is the fix.
Rebooting during FileVault's initial encryption process works just fine, macOS picks up where it left off with no issues and you still end up with a fully encrypted disk. The password screen works perfectly, thanks OpenCore developers!
[link] [comments]
Post a Comment