Mac Pro 5,1 2010 (with updated BT/Wifi)
After updating OC to 0.6.4 I lost Recovery Partition in the bootpicker, how to get it back?
After applying the Security Update (OS build now reads 19H114) in VMM mode, I now lost audio and wifi. Any ideas?
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
Mac Pro 5,1 2010 (with updated BT/Wifi)
After updating OC to 0.6.4 I lost Recovery Partition in the bootpicker, how to get it back?
After applying the Security Update (OS build now reads 19H114) in VMM mode, I now lost audio and wifi. Any ideas?
Both hardware issues have been solved by entering recovery with
Code:
sudo nvram "recovery-boot-mode=unused"
sudo rebootAnd disabling SIP with
Code:
csrutil disableFinally, I installed "legacy audio patch" and "legacy wifi patch" from @dosdude1 Catalina patcher.
Recovery Partition still not visible in OC boot picker, though.
Hello,
okay so I ran into a new problem. I tried to install macOS Big Sur 11.1 with a USB installer on a separate HDD. It did not worked for me, my cMP booted into the installation process just fine. However, the installation status bar did not appear ... after a short time the mouse cursor popped up on the screen for several seconds and then my cMP went off and everything started all over again.
I have waited an hour.
After that I also tried to install macOS Big Sur on a 60GB SSD, this did not work either. Same problem.
I did this with OpenCore 0.6.4 and the config from post 1 with the firmware features of the iMac Pro.
I also did this with the sample macOS Big Sur config from post #1,314 this also did not worked for me.
Does anyone know maybe what this is due to and maybe someone can try this as well?
Thanks in advance!
okay so I ran into a new problem. I tried to install macOS Big Sur 11.1 with a USB installer on a separate HDD. It did not worked for me, my cMP booted into the installation process just fine. However, the installation status bar did not appear ... after a short time the mouse cursor popped up on the screen for several seconds and then my cMP went off and everything started all over again.
I have waited an hour.
After that I also tried to install macOS Big Sur on a 60GB SSD, this did not work either. Same problem.
I did this with OpenCore 0.6.4 and the config from post 1 with the firmware features of the iMac Pro.
I also did this with the sample macOS Big Sur config from post #1,314 this also did not worked for me.
Does anyone know maybe what this is due to and maybe someone can try this as well?
Thanks in advance!
Last edited:
This will happen if the destination drive is formatted MacOS Extended rather than APFS.
Let me explain again. My Catalina was installed with OC, not using the Dosdude Catalina Patcher. The Recovery Partition was always available in the bootpicker. It vanished after updating OC to 0.6.4.
The patched kexts I've mentioned are a different thing - they were the only thing to allow my audio and wifi to work, despite using OC. Vanilla Catalina kexts are patched using a separate app called "Patch Updater" I extracted from Dosdude Catalina Patcher. They do not interfere with the system installation per se.
Hullo Dayo; So I've now had time to sit and get this sorted.
The RefindPlus/Opencore chainload combo is far and away the easiest and most reliable BootLoader I've had the pleasure of using.
So where as previously I could get;
Mac to Boot 10.13.6 with AMD.
Mac to Boot 10.13.6 with Nvidia.
Mac to Boot Win10 with AMD.
Could not get;
Mac to Boot Win10 with ANvidia.
This morning I uninstalled the whole bootoader shebang, (Opencore and RefindPlus). It couldn't complete for some reason so I took my dedicated Bootloader drive and used Win10 in parallels to format it as MBR.
I then did the NVRAM reset thing and put the AMD back in, (the 1070 wouldn't boot to recover either).
Next step, disable SIP.
Boot back into the Mac OS with the 1070 installed and choose the Nvidia webdriver.
Reboot and make sure all is good.
Format the BootLoader drive as normal to give my back my EFI partition.
Downloaded MyBootMgr 0.64a and went from there.
On first reboot on completion everything showed as good. Ran the Mac OS to check anyway.
Shutdown and rebooted and this time chose Windows. It loaded beautifully. As soon as I was in the PC recognised the 1070 and asked if I wanted to update the driver, which is what I'm doing now.
Just wanted to say a sincere thanks for all your work.
Just download the full installer and reinstall it over the existing installation with the VMM flag. That is what I normally do when I have issues.
Open your config and search for that string:
Code:
<key>HideAuxiliary</key>Hide Recovery with<true> show all with <false>
If they hide press space bar to show.
Just a thought...
Thank you for your reply!
Doesn't the installer actually format the destination drives itself to the appropriate format?
Anyways... I pre - formatted my destination drive (in this case the 60GB SSD) to APFS before I tried to install macOS Big Sur again but the problem occurs still.
Could you or someone else try it yourself to be 100% sure? Maybe it's a new problem in macOS Big Sur version 11.1 that needs to be fixed.
Should I maybe try to perform a full spoofing for the installation?
Thank you again in advance!
Cheers!
Attachments
Last edited:
I have the latest Big Sur installed. I use nvram variable for the firmware features and the mask. The regular MacPro5;1 features plus bit 29.
Perfect. Spot on solution that wouldn't happen no matter how many times I reinstalled Catalina. I must have omitted this setting when manually upgrading my 0.6.1 config.plist to 0.6.4. Thank you.
That, as well as reinstalling Catalina, is not the solution to what I wanted to achieve. The "press space to unveil all drives", I read it here first. It is not (as well as the setting) mentioned in #1 post (which is becoming an increasing mess, BTW).
So you performed a clean install?
Could you please share your config with me?
You're welcome
Different ppl have different conditions...
I prefer not to see the boot picker. But if I want them to see I press and hold ESC after boot chime and then I want to see all I maybe need...
OpenCore on the Mac Pro
My OpenCore 0.63 is working nicely now on my cMP 5,1. But one puzzling thing is that in the Boot Menu I see an extra bootable drive with a name that I had used for one of the bootable partitions some weeks ago. I have had several NVAM resets since then, not sure what that is from. Selecting it...
forums.macrumors.com
BTW first post is an abridged version and is not a substitution for the requirement to read the manual (also stated in the first post)
So if I understand you correctly, I no longer need the firmware features in the SMBIOS and VMM either, since everything is then in NVRAM Variable, right?OpenCore on the Mac Pro
My OpenCore 0.63 is working nicely now on my cMP 5,1. But one puzzling thing is that in the Boot Menu I see an extra bootable drive with a name that I had used for one of the bootable partitions some weeks ago. I have had several NVAM resets since then, not sure what that is from. Selecting it...
So if I understand you correctly, I no longer need the firmware features in the SMBIOS Variable and VMM in the Cpuid1Mask Variable either, since everything is then in NVRAM Variable, right?OpenCore on the Mac Pro
My OpenCore 0.63 is working nicely now on my cMP 5,1. But one puzzling thing is that in the Boot Menu I see an extra bootable drive with a name that I had used for one of the bootable partitions some weeks ago. I have had several NVAM resets since then, not sure what that is from. Selecting it...
So if I understand you correctly, I no longer need the firmware features in the SMBIOS Variable and VMM in the Cpuid1Mask Variable either, since everything is then in NVRAM Variable, right?OpenCore on the Mac Pro
My OpenCore 0.63 is working nicely now on my cMP 5,1. But one puzzling thing is that in the Boot Menu I see an extra bootable drive with a name that I had used for one of the bootable partitions some weeks ago. I have had several NVAM resets since then, not sure what that is from. Selecting it...