Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I have noticed that since I replaced my old monitor with a 4K, which I am using in HiDPI mode at 3008x1692, some operations have become particularly slow. For example, displaying photos with the space bar was immediate before and now need several seconds after pressing the bar. But redrawing in ArchiCAD is also very slow. I know that using HiDPI mode, the GPU has to process quadruple pixels, but I thought it was no problem for my Radeon RX580 with 8GB of vram. At the native resolution (3840x2160) things are better, but it's all too small to work with. Is there any setting in OpenCore that could affect GPU performance? Is there anyone who has had similar experiences? Is there any thread regarding this issue?
 
Thanks again, sorry for all the questions just making sure I don’t cause a problem. So after installing Big Sur you don’t need to worry about the VMM flag then
That is correct. I am currently on 11.6 and when I installed, I did not need the VMM flag.

Has anyone had any noticeable problems using the Big Sur 11.6 version so far?
I have had zero issues with running Big Sur 11.6 and SurPlus. Everything works for me as intended. I use @h9826790 package and it's fantastic.
 
Many thanks HuRR for your reply and time.
I’ve went ahead and installed Big Sur on its own partition and it installed perfectly fine. Just restoring from a time machine backup which is going to take a while
 
  • Like
Reactions: HuRR
I've been searching all the MacPro OpenCore threads but coming up confused on the issue of a proper modern WIFI/Bluetooth card for my 2010 12core 5,1. I'd like to replace the WIFI and Bluetooth with something that is natively supported in Big Sur and beyond. I have no PCI slots available (it's a music production computer fully loaded an NVME drive with HDX and UAD processing cards).

Can someone link to a replacement WIFI/Bluetooth card that doesn't use up a PCI slot but rather replaces the stock unit? thx.
 
I've been searching all the MacPro OpenCore threads but coming up confused on the issue of a proper modern WIFI/Bluetooth card for my 2010 12core 5,1. I'd like to replace the WIFI and Bluetooth with something that is natively supported in Big Sur and beyond. I have no PCI slots available (it's a music production computer fully loaded an NVME drive with HDX and UAD processing cards).

Can someone link to a replacement WIFI/Bluetooth card that doesn't use up a PCI slot but rather replaces the stock unit? thx.
There's a fair bit of information flying around about this. There's a separate thread on MacRumors here that this belongs in and there are guides on the web, for example this one. I did it a while ago and while fiddly, it wasn't difficult. I bought a card from eBay.
 
  • Like
Reactions: offdwall and TECK
Has anyone seen the "Device Support Update" in software update?

I am on 11.6 with OpenCore. I use Hybridization to see Software Updates and moved from 11.5.2 to 11.6 recently. However I am not seeing the "Device Support Update" that was released yesterday so curious if others are seeing it and it something is going on with my system.

Regards
 
Has anyone seen the "Device Support Update" in software update?
I got a notification the other day and installed it, update did not asked for reboot.

1633104705500.png
 
Last edited:
I have never been able to update any Catalina/Big Sur installation via OpenCore directly from Software Update. My setup is a multi-OSX affair on various disks and volumes. Big Sur occupies its the whole of a PCI nVME drive. All my other instances are on SATA drives. I prefer to set the default drive to a non-Open Core installation of Mojave and to hold the option key at the boot chime and select EFI whenever I want to boot into Big Sur.

In Big Sur, SysPref does find the latest update and downloads and processes it as expected. However, when it comes to rebooting to apply it, it doesn't follow through. I can either hold the option key and select the Update volume (how it appears in the default boot picker) but that just conks out and does nothing. Otherwise I can select EFI in which case the Open Core bootpicker just shows the same list of drives as normal but the update process is not kicked off.

Do I need to do anything, even change my config temporarily, to get Software Update to work as it should?

Currently, I am just using the latest Martin's Package with zero edits on my side.
 
I have never been able to update any Catalina/Big Sur installation via OpenCore directly from Software Update. My setup is a multi-OSX affair on various disks and volumes. Big Sur occupies its the whole of a PCI nVME drive. All my other instances are on SATA drives. I prefer to set the default drive to a non-Open Core installation of Mojave and to hold the option key at the boot chime and select EFI whenever I want to boot into Big Sur.

In Big Sur, SysPref does find the latest update and downloads and processes it as expected. However, when it comes to rebooting to apply it, it doesn't follow through. I can either hold the option key and select the Update volume (how it appears in the default boot picker) but that just conks out and does nothing. Otherwise I can select EFI in which case the Open Core bootpicker just shows the same list of drives as normal but the update process is not kicked off.

Do I need to do anything, even change my config temporarily, to get Software Update to work as it should?

Currently, I am just using the latest Martin's Package with zero edits on my side.
What happens for me (I use OpenCore on an external USB drive) is that I boot into Big Sur or Catalina with the appropriate config.plist to see updates - start the update process.

Upon reboot I select the EFI partition and then from the OC boot menu I select the update partition. The update will then process.

I have to also catch subsequent reboots and follow the same process until I can boot into Big Sur/Catalina to verify all is done properly.
 
  • Like
Reactions: weckart
What happens for me (I use OpenCore on an external USB drive) is that I boot into Big Sur or Catalina with the appropriate config.plist to see updates - start the update process.

Upon reboot I select the EFI partition and then from the OC boot menu I select the update partition. The update will then process.

I have to also catch subsequent reboots and follow the same process until I can boot into Big Sur/Catalina to verify all is done properly.
When you say you select the update partition, do you mean the volume you want to update or the temporary volume created by Software Update containing the update files? The latter is not visible in the OpenCore boot picker screen.
 
^It is, at least if it’s rightly configured. It is for me. It has the same name as the target disk, and it’s preselected by default.
 
When you say you select the update partition, do you mean the volume you want to update or the temporary volume created by Software Update containing the update files? The latter is not visible in the OpenCore boot picker screen.
The temporary volume created by the installer. Doing it this way boots the installer via OpenCore to complete the install.
 
  • Like
Reactions: weckart
I got a notification the other day and installed it, update did not asked for reboot.

View attachment 1854011
Thanks for the reply (everyone). Something must be up with my OpenCore settings as I got the update in Catalina but not Big Sur. Can someone take a look at my config.plist and see if you notice anything I might have messed up.

I create the config.plist "by hand" using the directions in the first post. It is pretty minimal with only OpenCanopy and now SurPlus enabled as well as hybridization to enable updates. I use a separate config.plist for Catalina with the VMM flag set for updates. Otherwise in Catalina I usually boot without OpenCore.

To get around unsupported hardware I edit the PlatformSupport.plist on the preboot and recovery partitions so i don't need to use the -no_compat_check bootarg for both Catalina and Big Sur.

Appreciate any help.

RESOLVED - Well after a lot of trial and error including signing in and out of iCloud on my MP5,1 this morning (for about the umpteenth time since I started having issues) all my devices asked me to resign into iCloud. After completing all of that my Apple watch unlock is working again.

I am not sure what or why it all "synced". Generally when I have had issues in the past a simple sign out and back in to iCloud on my MP5,1 is enough to fix it.
 

Attachments

  • config.plist.zip
    3.7 KB · Views: 63
Last edited:
Appologises if this question has been asked before:
How do you change the name of the disks(Volumes) when in the Boot Picker, OpenCore?
I've renamed them in 'Disk Utility' to they remain the same on the Boot Picker?
 
Appologises if this question has been asked before:
How do you change the name of the disks(Volumes) when in the Boot Picker, OpenCore?
I've renamed them in 'Disk Utility' to they remain the same on the Boot Picker?
my guess would be to reset the NVRAM
And or re-build OC
 
Appologises if this question has been asked before:
How do you change the name of the disks(Volumes) when in the Boot Picker, OpenCore?
I've renamed them in 'Disk Utility' to they remain the same on the Boot Picker?
Do a search for disk_label in this thread.
 
Also, in the Boot picker for every drive shown it shows it’s relevant EFI volume also?
Is there a way to stop the EFI s from showing in the Boot picker
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.