Search results

Painless install. This version corrected a login screen weirdness introduced in 11.2, namely the login accounts being offset to the left as seen below: Things are now back to normal. I'm using a Sapphire Pulse RX580 8GB card.

Update worked fine using System Preferences > Software Update. I did not detect an installation volume during boot up; no boot intervention was required. I updated from macOS 11.1 to 11.2. All my kexts were up to date (see pic), and I'm on OpenCore 0.6.5. There was a lengthy delay from the...

It's really hard to say. A mistake that I've made in the past is not selecting the proper boot disk in the BIOS. That is, selecting the boot disk that actually contains your changes. The only other thing I could recommend is re-doing the entire procedure, step by step. Make certain that your...

Update from 11.0.1 to 11.1 went fine. I encountered two reboots, and a very long "black screen" after the Apple logo/timed progress bar, where there was extensive disk activity. Total time was about 45 minutes. Note that upon each reboot, the typical "Install" volume never appeared. Instead...

Well, I figured it out. It's a two-step process. 1) Go here for the procedure on creating custom files called .disk_label and .disk_label_2x which both live in each disk's EFI/BOOT folder, using a utility called disklabel which is included as part of the OpenCore distribution. In using the...

I am running Big Sur 11.0.1 using OpenCore 0.6.3. Using Carbon Copy Cloner, I back up my macOS boot disk (named Macintosh SSD) to three separate disks, which are all APFS formatted, bootable and named: Daily M2 macOS Backup (internal M2) Daily Backup (internal SSD) Weekly Backup (external USB)...

In the Dortania guide, there's a "Sanity Checker" for your OC config.plist that is pretty cool. You can run your own file through the checker to see if you're missing anything obvious. See: here.

Yes they are. I have 15 ports working, including USB 3.0 and 2.0, internal and external.

Certainly. I've also attached my modified SSDT-UIAC-ALL.dsl with comments so you can modify it if necessary to reflect the USB ports you're using, and recompile it for your own SSDT-UIAC.aml. I've also attached a couple PDF's with USB port numbers indicated. Of course, you'll need to change...

It's the ASUS ROG STRIX Z370-H.

That is one very sweet guide @Feartech. I only wish I had found yours when I did this for Clover. The author of the one I used (who shall remain nameless), had an aversion to writing actual sentences.

After going through the mostly EXCELLENT "Dortania's OpenCore Installation Guide" the thorny subject of USB mapping reared its head. Initially, I was under the assumption that all the work I did creating a custom SSDT in Clover was for naught, and I'd again face this tedium. With that in mind...

I predict that Apple will offer Mac Pro users a generous trade-in value to purchase new ARM-based hardware.

I see that the latest version of MultiBeast discontinues IntelMausiEthernet.kext, and instead offers IntelMausi.kext. Why? Should I replace IntelMausiEthernet.kext with IntelMausi.kext?

Ultimately, I resolved this issue be abandoning the Clover Emulated NVRAM option, and instead went with a new SSDT fix. Even through this fix is for "300 Series" motherboards, I used in on my Asus PRIME Z270-A, and it appears to work fine. Ultimately, the old NVRAM function test, i.e.: sudo...

Update: I implemented your suggestions (added the SSDT-PMC.aml, switched from current Aptio fix to OcQuirks+FwRuntimeServices, etc), rebooted, and now iMessage is working! The NVRAM test: sudo nvram TestVar=HelloWorld reboot sudo nvram -p | grep 'TestVar' still doesn't work, but I've read...

Here's what I get: LocationServicesEnabled %01 fmm-computer-name Studio Hackintosh bluetoothActiveControllerInfo %8d%82%ac%05%00%00%00%00%b3%14x1%c1%e8%88 SystemAudioVolumeDB %f0 bluetoothInternalControllerInfo %8d%82%ac%05%00%00%b3%14x1%c1%e8%88 SystemAudioVolume A

Well, the operative word is "should." Unfortunately mine doesn't work. To confirm, I ran the "Clover Emulated NVRAM Uninstaller" app, verified that the NVRAM emulator components were gone, and then rebooted. Then I tested NVRAM with the following: sudo nvram TestVar=HelloWorld reboot...

Excellent - I'll definitely give this a shot. Question: I'm using an Asus Prime Z270-A, so is this "300 series" fix applicable?

I will definitely give that a try. Will I need to remove the NVRAM RC scripts and files that were previously installed? Thanks!