Following up with my own experience: I enabled the VMM flag, rebooted, installed the update from Software Update uneventfully... disabled the VMM flag once the 12.1 RC was up and running, and everything seems just as happy as it was under the 12.1 beta I was running previously.
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
The official documentation is now attached to each release, I would refer to it from now on.
I never enable the VMM flag to upgrade, in fact, with the latest configuration, there is no need for VMM flag to be defined at all, use the failsafe values for Cpuid1Data and Cpuid1Mask:
OC 0.7.5 upgrade (#117) · axivo/opencore@213d05b
* Set LauncherOption to full * Added Monterey settings * Updated description * Switched back to NightShiftEnabler * Added MonteRand patches * Removed MonteRand patches * Updated S...
github.com
Last edited:
I recently upgraded from Catalina to Monterey on my Mac Pro 5,1:
My graphics card is a GT 710 1 GB (I know, I know). It worked fine in Catalina, but in Monterey the graphical lag is basically unusable. Are there any settings I can tweak to make this better? I noticed the amount of VRAM is showing up as 22 MB, which doesn't seem right.
If Monterey just won't work, should I go back to Catalina? Or might I have better luck with Big Sur?
I'm running the latest version of OpenCore. I would be happy to provide my config file, but it's grayed out when I try to attach it. Might be because I'm a new user?
My graphics card is a GT 710 1 GB (I know, I know). It worked fine in Catalina, but in Monterey the graphical lag is basically unusable. Are there any settings I can tweak to make this better? I noticed the amount of VRAM is showing up as 22 MB, which doesn't seem right.
If Monterey just won't work, should I go back to Catalina? Or might I have better luck with Big Sur?
I'm running the latest version of OpenCore. I would be happy to provide my config file, but it's grayed out when I try to attach it. Might be because I'm a new user?
Monterey dropped support for NVIDIA Kepler GPUs.
I have not tried it but others have reported that OCLP has a post install utility that can reapply the drivers for NVIDIA Kepler GPUs. It would have to be reapplied after every OTA update.
Note that this concerns MonteRand, not SurPlus. MonteRand was only needed for an early beta of 12.1, so you can safely remove it if you've updated beyond that or are not doing the betas. SurPlus, on the other hand, remains necessary.
Has anyone got this message "The package “%@” is missing or invalid." while updating to Monterey? Almost 90%..
Thanks
Thanks
edit: when updating 0.7.5 > 0.7.6, I stupidly replaced both BOOT and OC from the 0.7.6 file into my EFI volume, and now I can only get OC to work if I only have my mac ssd connected, and all of my other drives disconnected.
If I connect all of my drives, no bootpicker shows, and my cMP automatically boots into Windows 11. I know this is a result of replacing BOOT, but I need to fix this to get it back to how it was before .
If I connect all of my drives, no bootpicker shows, and my cMP automatically boots into Windows 11. I know this is a result of replacing BOOT, but I need to fix this to get it back to how it was before .
Last edited:
Hi prefuse,
If you installed OC as explained in this thread , Windows is installed in UEFI mode.
This means that Windows will write Certificates to the BootROM of the MP and (if repeated) will corrupt or even brick it.
OpenCore prevents this, but (ofcourse) only when it's working as it should.
Make sure you got OC running before you reinstall the Windows drive.
Short: reinstall OC without the Windows drive installed and when 100% confirmed it works , you can insert the Windows drive again.
Last edited:
Anyone else having issues installing Linux with OC 0.7.6 & OpenLinuxBoot?
I was very happy when i read that OC now supports Linux w/o GRUB but i can'T seem to get it to work for me.
I have included the OpenLinuxBoot.efi as well as the ext4_x64.efi in my config and droped the files in the drivers folder of my OC EFI partition. I have also enabled LauncherOption as well as RequestBootVarRouting as stated in the OC Cofig Guide.
The problem is the guide just says install Linux as normal but whatever i do my installer will just freezy at the GRUB installation usually at the "GRUB-install dummy" part. I have disabled SIP and everything but it just wont properly install Linux.
When i force reboot i can already see the Debian Partition and i can even boot it but it won't accept any of the passwords i have set during install.
When i choose advanced install and dont install GRUB at all it will finish the install as normal but no Linux Partition will show up in the OC bootmenu.
Anyone got it succesfully working yet? I can't seem to figure it out....
I was very happy when i read that OC now supports Linux w/o GRUB but i can'T seem to get it to work for me.
I have included the OpenLinuxBoot.efi as well as the ext4_x64.efi in my config and droped the files in the drivers folder of my OC EFI partition. I have also enabled LauncherOption as well as RequestBootVarRouting as stated in the OC Cofig Guide.
The problem is the guide just says install Linux as normal but whatever i do my installer will just freezy at the GRUB installation usually at the "GRUB-install dummy" part. I have disabled SIP and everything but it just wont properly install Linux.
When i force reboot i can already see the Debian Partition and i can even boot it but it won't accept any of the passwords i have set during install.
When i choose advanced install and dont install GRUB at all it will finish the install as normal but no Linux Partition will show up in the OC bootmenu.
Anyone got it succesfully working yet? I can't seem to figure it out....
Yes. I've installed Ubuntu using the new OpenLinuxBoot approach, and while I haven't documented the process, I can confirm that it works as expected without any special steps.
The reason is that OpenLinuxBoot uses the GRUB configuration files for booting. (Note that these files are not the GRUB files on the EFI partition. Those files can actually be deleted.)
Look for a comfortable seat.
Much better install windows in legacy mode, so you have all the drivers. Keys for sound and brightness included. And boot from Windows pressing Alt.
Last edited:
UEFI mode does not preclude any of that.
Ok in the Guide it says something about
I'm trying to get a dabian bullseye distro to run. As i mentioned i can not complete the install with GRUb since it will just get stuck at the "grub-dummy install" step.
Is there a way to get those GRUB configuration files manually? The OC config guide mentions that the correct boot options must be manually specified, but without any futher explanation.
Can you explain to me what i need to do?
I would recommend testing a Ubuntu installation, which is known to work with OpenLinuxBoot. If the installation still fails, then you know something is wrong with your setup. If the installation works, then you can submit a request to get OpenLinxuBoot to better support your distro.
? I'm not having any issues running Monterey via OC 0.7.6 and SurPlus. Why should I wait for a Monterey patcher? Wait to achieve what?
I tried it with the lates Ubuntu LTS 20.04. It works almost identicall to my Debian distro:
Installer boots fine i can setup everything but when it comes to installing GRUB it will freeze. The installer displays "GRUB-install /dev/sdb" and just doesn't move past this point.
i guess its my setup but where do i even begin to look for errors?
Maybe the installer is having trouble with the EFI partition. Use Disk Utility in macOS to reformat the disk. Use View > Show All Devices to reveal the disk itself. Select the disk and erase it, reformatting it with the GUID scheme to recreate the EFI partition.
I´m of the same opinion. Mac Pro 5,1 Monterey works perfect in OC.