This part in Dortania concerns me:
Looks like the MP3,1 won't be able to have OC enable built-in audio without some other means.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Looks like the MP3,1 won't be able to have OC enable built-in audio without some other means.
Sound is broken even with OCLP using the VoodooHDA.kext on most legacy machines. The latest update of AppleALC.kext (which got legacy Apple support) does not work either. You can check out both and add them to your OC config. But only one at a time
So from my little iMac world I can confirm that sound is currently broken on more than one of legacy Apple systems with an OC only approach. I use an BT connected Anker cube with mic and speaker and will wait until the Empire strikes back with AppleALC.kext updates. The problem is well known to the OCLP developers and my hope is it will work soon.
BTW:
I got OC working with Mojave and Catalina on an iMac12,2, too. But sound is broken there, too. One could now reinstall AppleHDA back with @dosdude1 or @Barry K. Nathan micropatcher (Big Sur), but this will break delta OTA upgrades. When using the @jackluke type of spoofing one gets OTA upgrades with Mojave and Catalina. But this is a different story.
Last edited:
They are (for the most part). Look for the WikiPost History button at the bottom of the post.
That's right, because those values are now automatically set.
Thank you for this. It confirms to me that I wasn't going BSC. I kept thinking something must be amiss with my configuration and spent the last two days pouring over the config files as well as installing/re-installing different operating systems on my MP3,1.Sound is broken even with OCLP using the VoodooHDA.kext on most legacy machines. The latest update of AppleALC.kext (which got legacy Apple support) does not work either. You can check out both and add them to your OC config. But only one at a time
So from my little iMac world I can confirm that sound is currently broken on more than one of legacy Apple systems with an OC only approach. I use an BT connected Anker cube with mic and speaker and will wait until the Empire strikes back with AppleALC.kext updates. The problem is well known to the OCLP developers and my hope is it will work soon.
BTW:
I got OC working with Mojave and Catalina on an iMac12,2, too. But sound is broken there, too. One could now reinstall AppleHDA back with @dosdude1 or @Barry K. Nathan micropatcher (Big Sur), but this will break delta OTA upgrades. When using the @jackluke type of spoofing one gets OTA upgrades with Mojave and Catalina. But this is a different story.
I can confirm that USB audio devices function once plugged in. It's only built-in Apple hardware that relies on AppleHDA.kext which fails without some sort of external patching.
Last edited:
I'm helping some people behind the scenes and I've noticed that they are moving in parallel with your exact same goal of having a fully working MP3,1 with Big Sur/OC (please note that I'm not suggesting in any way that you stop to post here), but could you please open a new thread to make easier to track the MP3,1 problems with Big Sur/OC and converge efforts?
Hi Alexandre. I don't mind opening a new, separate thread if it will help (especially with Big Sur on an MP3,1 as that is my eventual goal). However, the issues I described earlier revolve around my experiences trying to get Mojave audio to work under OC. Despite my best efforts, nothing worked. The general response to that has been to use a patched version of the OS - which is what I'm trying to avoid by using OC in the first place.
That said, my Big Sur experiences with OC v0.6.7 and the MP3,1 haven't been pretty. First stage of installation from an already installed OS with VMM active is usually fine. Second stage installation (after the first reboot) generally ends the moment it starts with a KP and a hard reset. VMM on or off doesn't make a difference. I haven't taken the time to archive the OC logs from those attempts because I was focused on something else entirely, but can do so again if needed.
So I dropped the PCIe card + SSD into another Windows machine and deleted all partitions/cleared the drive. When I put it back in my Mac Pro, Big Sur booted. I flashed the BootROM back to normal using Mojave. So now I will rebuild and reinstall OC. Any reason not to install Windows via Boot Camp on the recently cleared drive?
Hi all,
I just updated update my old OC 0.5.6 to the latest 0.6.7 Martin Lo config, and all is running ok. Enjoying the new boot picker and OS loading screen!
My current goal is to test Big Sur on a spare SSD before updating my main system drive, to test the Big Sur compatibility for my PCIe audio card, and I just have a few questions:
1) Can I install a OC and Big Sur on an SSD connected via USB3 or does it need to be internal? I'm intending on doing a clean install of Big Sur via a USB stick drive.
2) Is installing a fresh copy of Big Sur on a drive as simple as mounting the EFI, copying the files across, then booting from my 'Install macOS Big Sur' USB thumb drive, and selecting my test SSD, install and voila?
3) Big Sur updates - can I do them without issue, or is it best to exercise caution and check back here each time there's an update?
Thanks again!
I just updated update my old OC 0.5.6 to the latest 0.6.7 Martin Lo config, and all is running ok. Enjoying the new boot picker and OS loading screen!
My current goal is to test Big Sur on a spare SSD before updating my main system drive, to test the Big Sur compatibility for my PCIe audio card, and I just have a few questions:
1) Can I install a OC and Big Sur on an SSD connected via USB3 or does it need to be internal? I'm intending on doing a clean install of Big Sur via a USB stick drive.
2) Is installing a fresh copy of Big Sur on a drive as simple as mounting the EFI, copying the files across, then booting from my 'Install macOS Big Sur' USB thumb drive, and selecting my test SSD, install and voila?
3) Big Sur updates - can I do them without issue, or is it best to exercise caution and check back here each time there's an update?
Thanks again!
Hi, I was wanting to try and get some help. I have OC 0.6.7 and the new config.plist. Following the guide I have cpuid1data set to ON and cpuid1mask set to ON. I have enabled hardware acceleration and hybridization with the kext and using iMacPro. I checked my config.plist with terminal and it says OK.
Im trying to do a clean install of macOS Catalina(not using dosdude1 patcher) and I get
"An error occurred while verifying firmware. Quit the installer to restart your computer and try again."
I use the same open core to boot High Sierra and it boots and works great. So I don't think I messed something up on it. Maybe I'm just missing something?
Any help is appreciated!!
Im trying to do a clean install of macOS Catalina(not using dosdude1 patcher) and I get
"An error occurred while verifying firmware. Quit the installer to restart your computer and try again."
I use the same open core to boot High Sierra and it boots and works great. So I don't think I messed something up on it. Maybe I'm just missing something?
Any help is appreciated!!
Try the basic config without the hybridization. The iMac Pro spoofing is causing the firmware warning. Set it back to spoofing after you're done installing Catalina.
I should still have the cpuid1data and cpuid1mask turned on when I make a new config. Right? And try with just that changed and nothing else?
I read it´s only for Big Sur. It´s Catalina than I want to install. Thanks.Try this:
GitHub - dortania/OpenCore-Legacy-Patcher: Experience macOS just like before
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.github.com
There will be currently no support for Mojave and Catalina from the developer side, but honestly I use it for weeks now to create Catalina and Mojave installations, too!
You will likely have to add extensions to be injected (take a look at the patches @dosdude1 applies to your system to get an idea) and add devices in the DeviceProperty section and you need some experience with OC to do so.
Right now I got (after days of playing around and with help) iMac11,x and iMac12,x configs fully working with Mojave and Catalina (except sound is still broken) including OTA, WiFi, sleep and so on.
If we get sound working with AppleALC I would happily and loudly announce the end patching...
Thnx! I´m almost there witn my macbook pro 17" 2011. Just the display it´s not recognized. I´ll try with this tool.
What's that abbreviation "OCLP" I see popping up everywhere?
OC = OpenCore
RFP/OC = RefindPlus / OpenCore
OCLP = ? ? ? ?
OC = OpenCore
RFP/OC = RefindPlus / OpenCore
OCLP = ? ? ? ?
I carefully followed the guide to upgrade to OC 0.6.7 as described below:
in the EFI volume I overwritten only the OC and BOOT folder (the Windows folder remained) and on the OC Drivers folder I copied the ExFatDxeLegacy.efi file. I then made the modification of the config.plist file by adding the XML string as indicated in the guide.
Unfortunately, when I reboot I don't see the Windows volume anymore!
I then uninstalled OC, removed the Windows disk, and reinstalled OC 0.6.6 (backup).
I reinserted the Windows disk, but I still can't see the Windows volume icon at startup!
I am asking for help on how to restore OC and Windows!
Thanks in advance!
OpenCore can’t see a legacy (Boot Camp) version of Windows. It will only see a UEFI version of Windows. See post #1.
RefindPlus is simply "RP". "RFP" is an aberration from some incorrigible fellows who also tend to use all sorts of weird unsanctioned capitalisations such as "reFindPlus" or "rEFIndPlus" or anything inbetween.
OCLP is for the "OpenCore Legacy Patcher":
GitHub - dortania/OpenCore-Legacy-Patcher: Experience macOS just like before
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
github.com
Yes, you can by creating an fstab file in /etc. Follow these instructions for more information:
Prevent a volume from mounting at startup - Apple Community
discussions.apple.com
I've used the above to prevent my Mojave volumes from automatically mounting in Big Sur. I've also done the same in Mojave to stop BS volumes from mounting.
That's awesome.
I hesitated to open
Code:
sudo vifsI am very glad I can reuse my fstab file Templates were I included a Tutorial on how to set it up.
WARNING:
before going to edit that fstab file be sure to at least understand or know the basic commands of the vim editor.
Google for "vim Tutorial"
Anyone else had a problem with Windows 10 crashing while trying to boot into the newly installed Windows for the first time? Iv tried 5 different times now same result.
VMM flag is off.
Once Windows crashes it usually causes macOS to crash as well. I have to remove the drive with OC on it and let the Mac boot into HS by itself to fix it.
just a pain in the ass to get Windows installed
VMM flag is off.
Once Windows crashes it usually causes macOS to crash as well. I have to remove the drive with OC on it and let the Mac boot into HS by itself to fix it.
just a pain in the ass to get Windows installed
WORD!
Always keep in mind: "the Past knows nothing about the Future!" ... and especially about the different flavours of APFS.
having multiple Mac OS X versions on the same disk separated with Partitions was never a problem with HFS+
- until Apple introduced APFS and then did change it on every macOS.
In my extended testDrive sessions on formating HFS+ and APFS Container Volumes, I found severe formating limitations in Apple's DiskUtility.
In retrospect you will understand this:
my advise based upon my own reSEARCH on APFS:
1) NEVER edit an APFS Container with an older macOS Version than it was created. (exactly as [mention]Ausdauersportler [/mention]told you).
2) KEEP macOS Big Sur (11.x) and macOS Catalina (10.15) physically SEPERATE (or better, avoid Catalina) from any OS.
3) macOS Mojave (10.14) and macOS High Sierra (10.13) on same Disk is OK (if you do not want to buy yet another Disk).
I didn't know about fstab when I was setting things up to handle disks that are not usually needed and haven't tested with BS (which I don't use) but I think my less sophisticated method might work well with it.
I have a bash script with lines of
diskutil unmount "/Volumes/Volume Name" saved in a folder where I keep misc scripts. I then have a Launch Daemon that triggers this when I boot. A Launch Daemon, as different to a Launch Agent, runs before user log in.
I am fairly confident you wouldn't get the notice with this since the BS disk would have been unmounted before logging in.