Ok, but as a data point, here's my iMac info with Monterey Beta 3 running :13,2, to be precise
Ok, but as a data point, here's my iMac info with Monterey Beta 3 running :13,2, to be precise
Thanks for the screenshot, I have made a note to allocate 50 GB. Is your Monterey Install on your internal Aura Pro Drive, I assume when you know there is a firmware update you boot into the ExtSSD External Drive?The bare bones Catalina install volume I created on external SSD for getting firmware updates currently occupies 34 GB, with 7.2 GB allocated for unmounted 'other volumes'. So you'd better make it bigger, maybe 50 GB. I did a clean install and just created an admin login. Did not migrate any data or apps other than installing SilentKnight.
View attachment 2019819
SilentKnight is your friend - not just because of the notification about firmware updates. It updates MRT- and XProtect-files, which is done automatically in the background on supported Macs.Thanks for the screenshot, I have made a note to allocate 50 GB. Is your Monterey Install on your internal Aura Pro Drive, I assume when you know there is a firmware update you boot into the ExtSSD External Drive?
As stated above, silent knight is your friend, but it also doesn’t hurt to just update your Catalina when security updates are released. The security updates for each OS are usually all released on the same day. So if there’s an update for Monterey, there’s probably an update for Catalina too until the end of this year, or until Ventura is publically released. Sometimes there will be a firmware update Bundled with the security update, sometimes there won’t be. But, Catalina will only be updated for another 6 months maximum. So, it will probably only be about 3 or 4 more times that you’ll need to do Catalina security updates.Thanks for the screenshot, I have made a note to allocate 50 GB. Is your Monterey Install on your internal Aura Pro Drive, I assume when you know there is a firmware update you boot into the ExtSSD External Drive?
Smart money is on ALWAYS having the last fully supported macOS by Apple (in @DragenFi's case, this will be Catalina) on a separate partition or volume or external drive when venturing into the land of unsupported macOS. It gives one a fall-back OS that is completely stable in the event that something with one's unsupported OS goes sideways.about firmware update, no need to have original Apple SSD or another SSD.
I just add a Container and install macOS Catalina, after the firmware update I remove that Container.
Since Windows times opportunity of double boot is must-have.Smart money is on having the last fully supported macOS by Apple on a separate partition or volume ALWAYS when venturing into the land of unsupported macOS. It gives one a fall-back OS that is completely stable in the event that something with one's unsupported OS goes sideways.
Smart money is on ALWAYS having the last fully supported macOS by Apple (in @DragenFi's case, this will be Catalina) on a separate partition or volume or external drive when venturing into the land of unsupported macOS. It gives one a fall-back OS that is completely stable in the event that something with one's unsupported OS goes sideways.
I loved the TUI. I have read that you can compile it by yourself, but no idea how to do it.With the move to the GUI app for ease of use will the option to change the CPU name be added? It currently only exists in the TUI version (AFAIK). My machine currently identifies as a PowerPC G6 and shows up in various crash reports sent to Apple. Quite comical.
This is true but we can easily get used to the GUII loved the TUI. I have read that you can compile it by yourself, but no idea how to do it.
"Developers can still compile TUIs from source,…!
How do I go back to 12.5 Beta 2? I log in and it goes back to a login all over n over again. Hmmm... Any ideas? iMac 13.2I have an issue after running the patch on 12.5 beta 3:
I'm using a 5,1 and after patching, I log in and it goes back to a login all over n over again. Hmmm... Any ideas?
I'm using OCLP -0.4.7n
Note: This issue is happening on 2 of my 5,1 machines
Thanks!
UPDATE:
I went back to 12.5 Beta 2
Simply install beta 2 right over the top of beta 3 using a USB beta 2 installer.How do I go back to 12.5 Beta 2? I log in and it goes back to a login all over n over again. Hmmm... Any ideas? iMac 13.2
Or log in to Safe Mode, download Beta 2 installer through OCLP and start it.How do I go back to 12.5 Beta 2? I log in and it goes back to a login all over n over again. Hmmm... Any ideas? iMac 13.2
i am having issues with monterey patcher on my macbook pro 2012 where whenever i use twiiter on safri it crashes and it gives me something like this. Does anybody have a soltion for this View attachment 2021050View attachment 2021051
I have this exact same problem occasionally on Safari on my 2012 MacBook Pro using CATALINA, which is still a fully supported OS. So I don’t think this is an opencore problem.
When I encounter this, I just restart, and the problem is gone. If it reoccurs later on, just restart again.
I’m not sure of the details, but I think that it has something to do with Safari on our particular hardware. Unfortunately, Apple doesn’t care because to them, it’s a vintage / obsolete device, that just barely made the cut for Catalina, so it still has just a little bit of official support.
I also have a macbook 2010 13 inch mid and twitter work on safri interms of having no crashes. Even when i restart the computer i am still having the same crashes issue when twitter loads a videoI have this exact same problem occasionally on Safari on my 2012 MacBook Pro using CATALINA, which is still a fully supported OS. So I don’t think this is an opencore problem.
When I encounter this, I just restart, and the problem is gone. If it reoccurs later on, just restart again.
I’m not sure of the details, but I think that it has something to do with Safari on our particular hardware. Unfortunately, Apple doesn’t care because to them, it’s a vintage / obsolete device, that just barely made the cut for Catalina, so it still has just a little bit of official support.
You have to have a way to build a EFI. You could use a different computer, but OCLP should be run from the computer you want to install to so it knows what hardware it's dealing with. Actually, there's a setting to tell OCLP what Mac you want to build OpenCore for so it shouldn't matter what Mac you build it from.Just so I'm clear, there's no way to use/install OCLP + Monterey from a "completely erased" SSD right? You always have to have a base OS loaded so you can build a patched EFI root volume with OCLP?