That's expected with non-metal graphics card in your iMac12,1. Use Google Maps with a web browser instead.
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.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
Anyone else have issue's with the latest OCLP when applying post patches with the latest nightly builds.
MacBookPro 8,1
MacBookPro 8,1
Code:
- Merging AppleGVA Hardware Accel patches for non-Metal
rsync: link_stat "/private/var/folders/rp/_9_drfdx5wv_f00hp1w3jf4c0000gn/T/_MEIwdvdSQ/payloads/Apple/PrivateFrameworks/Legacy-GVA/." failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at /System/Volumes/Data/SWE/macOS/BuildRoots/38cf1d983f/Library/Caches/com.apple.xbs/Sources/rsync/rsync-55/rsync/main.c(996) [sender=2.6.9]
With the release of OCLP the update to 11.6 on a cMP5,1 was mostly flawless in my case. The download via software update was about 5.7GB and took a little over 3 hours just to download. However, there seems to be an issue with the keyboard I have plugged into my monitor that goes through a KVM switch between a gaming PC and the cMP. The keyboard worked fine with 11.2.3 and OCLP 0.2.5. I don't think the issue is with OCLP since the keyboard works in the boot picker screen. After the system boots to desktop the only way to get the keyboard to work is to plug it into the USB 3.1 card in the back. No other ports seem to be working although the ports themselves show up in the USB section of system report. The Bluetooth module seems to be the only USB device to work other than the card.
How the KVM is setup: the keyboard connected to the monitor goes to the PC via USB C when Display Port is the input. When HDMI 1 is the input the keyboard goes to the cMP via USB A to the USB 3.1 card.
As a way of troubleshooting I connected an old PowerMac G4 via DVI to HDMI adapter (with the same USB 3.1 A cord to transfer the keyboard) and the keyboard worked fine switching between the PC and G4.
After 1 of the many restarts there was 1 time the keyboard worked long enough for me to login but wasn't detected once I got to the desktop (via port on front of cMP). The keyboard always works for the boot picker screen no matter what port it's plugged into.
Its all a bit weird.
There is 1 thing I changed when I upgraded to OCLP 0.3... I noticed secure boot model was listed as false so I enabled it. It sounded like something that should be enabled. Is this disabled by default for a reason? The cause of my USB issues? Always used default values previously. As far as I know the cMP5,1 doesn't need root volume patching. Checked the patcher TUI settings and it wants it disabled again.
How the KVM is setup: the keyboard connected to the monitor goes to the PC via USB C when Display Port is the input. When HDMI 1 is the input the keyboard goes to the cMP via USB A to the USB 3.1 card.
As a way of troubleshooting I connected an old PowerMac G4 via DVI to HDMI adapter (with the same USB 3.1 A cord to transfer the keyboard) and the keyboard worked fine switching between the PC and G4.
After 1 of the many restarts there was 1 time the keyboard worked long enough for me to login but wasn't detected once I got to the desktop (via port on front of cMP). The keyboard always works for the boot picker screen no matter what port it's plugged into.
Its all a bit weird.
There is 1 thing I changed when I upgraded to OCLP 0.3... I noticed secure boot model was listed as false so I enabled it. It sounded like something that should be enabled. Is this disabled by default for a reason? The cause of my USB issues? Always used default values previously. As far as I know the cMP5,1 doesn't need root volume patching. Checked the patcher TUI settings and it wants it disabled again.
I don't know how or why but I plugged in just the cable used to charge my mouse into the USB card and everything works? Everything seems to be fine even after 5 additional restarts. The USB 2.1 hub connected to the USB 3.1 bus is the KVM switch connected to the card in the cMP. Just wasted hours fiddling with things just to have a cable with nothing attached to it fix the problem.
Attachments
I'm currently on Big Sur 11.6 with a Mac Mini 2012 using latest OCLP 0.3.0.
When Monterey drops, do I just do an in place upgrade using Monterey dmg? Or do I need to create USB and upgrade from USB on boot? Sorry if I missed this.
When Monterey drops, do I just do an in place upgrade using Monterey dmg? Or do I need to create USB and upgrade from USB on boot? Sorry if I missed this.
You will see it as an available update in System Preferences > Software Update. So you will be able to just download & install Monterey "OTA" (over the air)
I am also on 2012 mini, using OCLP 0.2.5 now.
The big change in Monterey(relevant to 2012 mini) is the drop of support for graphics HD 4000. That means you need to run post-install patch for it, to restore HD 4000 support. Which also means disabling SIP.
So, if you use OCLP 0.3.0 default settings, SIP is disabled already.
You can in-place OTA to monterey and then run OCLP for the post install patch of HD 4000. That should be it.
Installed Big Sur 11.6 using OCLP 0.3.0, default settings. Everything seems to be running fine (Late 2013 iMac 14,2 27") According to Silent Knight, SSV is disabled. Is this normal, should I be concerned?🪓AHOY! OCLP_030 has been released.: https://github.com/dortania/OpenCore-Legacy-Patcher/releases
I'm on a 2012 Mini. Sounds like you have dual boot experience (Big Sur/Monterey)? What's the easiest way to do that?
The way it's set in OCLP default, see #5 then #2. All good.
Big Sur 11.6.1 (20G221) is available as an InstallAssistant.pkg (12.44GB download):
http://swcdn.apple.com/content/down...gm89ydg0leugbdepfudnvse0/InstallAssistant.pkg
Release info:
1. macOS Big Sur 11.6.1 (20G221) - 002-21096 - Added 2021-10-18 18:02:48
**this is not beta**
Note: I don't see the 11.6.1 OTA update yet; also no 11.6.1 at Apple Store yet.
http://swcdn.apple.com/content/down...gm89ydg0leugbdepfudnvse0/InstallAssistant.pkg
Release info:
1. macOS Big Sur 11.6.1 (20G221) - 002-21096 - Added 2021-10-18 18:02:48
**this is not beta**
Note: I don't see the 11.6.1 OTA update yet; also no 11.6.1 at Apple Store yet.
Last edited:
Hi! Having some issues installing in my 2009 MacBookPro 5,3.
I am able to use OCLP (0.3.0 and 0.3.1) to install Big Sur (11.6) on my system. Of course it is almost unusable because of the GPU. I am able to install OCLP on internal memory and it reboots normally. On the other hand when I apply the beta patches the system goes to a blank screen midway during the apple logo system loading.
NVRAM reset has no effect on this behavior.
Any hints?
I am able to use OCLP (0.3.0 and 0.3.1) to install Big Sur (11.6) on my system. Of course it is almost unusable because of the GPU. I am able to install OCLP on internal memory and it reboots normally. On the other hand when I apply the beta patches the system goes to a blank screen midway during the apple logo system loading.
NVRAM reset has no effect on this behavior.
Any hints?
Try OCLP 0.2.5 instead, I had trouble yesterday with a mbp5,4 and 0.2.5 fixed it immediately
This is the same as someone experienced for Monterey beta 10. Why not try the latest OCLP 0.3.1N TUI? You may get lucky. Otherwise, report back to @khronokernel by raising a new issue to OCLP in GitHub.
Almost everything works nicely on 11.6 on my MacbookPro10,2 - there's just one tiny thing. The HDMI output is supposed to be able to output 192kHz audio, but for some reason it's limited to 96kHz. This problem also existed on 11.4; I'm using Patched Sur to perform the installation but no kexts are required. I know the HDMI device supports 192kHz as the option for 192kHz audio shows up correctly in Audio MIDI Setup when connecting to other Macs, including a 2010-or-so Macbook Air. I checked the EDID of the device and it's correctly reporting 192kHz, and running an Ubuntu live USB showed that the HD4000 graphics support 192kHz, so there's something odd going on.
Has anyone else seen this, or better yet, fixed it?
Has anyone else seen this, or better yet, fixed it?
Just reporting that I have successfully installed Big Sir using 0.3.0 of OCLP onto a USB SSD by upgrading a clone of my Fusion drive on an iMac 2013 27”. I used the GUI version.
Last edited:
For my non-metal iMac running Big Sur or Monterey, I really need to have the Messages app working. Giving the fact the Messages app in Catalina works correctly on the same iMac, I am wondering if it is possible to run this old version of Messages app in Big Sur or Monterey.
Based on this premise, I copied the Messages app from Catalina to Big Sur / Monterey and got a crash report saying the IMCore is missing in /System/Library/PrivateFrameworks/IMCore.framework/Versions/A/ folder. I then tried to copy this IMCore from Catalina but could not paste to this folder, assuming it's related to the permission. Adding permission was denied and set SIP to disable in recovery mode did not help neither (OCLP recovery mode). I then booted to Monterey and tried to add this IMCore to Big Sur's PrivateFrameworks (both macOS are in the same external SSD) and also failed the paste. It may also be related to APFS snapshots, but it's really beyond my current comprehension about macOS.
I realise I may have multiple issues here and would like to know if it is even possible to run Catalina Messages app in Big Sur / Monterey?
Based on this premise, I copied the Messages app from Catalina to Big Sur / Monterey and got a crash report saying the IMCore is missing in /System/Library/PrivateFrameworks/IMCore.framework/Versions/A/ folder. I then tried to copy this IMCore from Catalina but could not paste to this folder, assuming it's related to the permission. Adding permission was denied and set SIP to disable in recovery mode did not help neither (OCLP recovery mode). I then booted to Monterey and tried to add this IMCore to Big Sur's PrivateFrameworks (both macOS are in the same external SSD) and also failed the paste. It may also be related to APFS snapshots, but it's really beyond my current comprehension about macOS.
I realise I may have multiple issues here and would like to know if it is even possible to run Catalina Messages app in Big Sur / Monterey?
what on messages doesn't work?
mine works on a MacBook Pro 8,1...
I do sometimes have issues and have to delete chat.db* and resyn, it has happened to me about 6 times in the last few months. A little annoying but not bad, it mostly happens with images received via messenger
It's very slow when scrolling, and uses almost 100% energy. The issue is identified here called "Catalyst Apps Scrolling Slow" by @ASentientBot. I am still waiting for his fix 😇
Another observation is that the default Messages app worked well (scrolling) before the OCLP Post-Install Volume Patch was applied. But the PIVP is required for other apps like safari. So it has become a "catch 22" issue. I am also wondering if it is possible to selectively not apply the PIVP to resolve this Messages app scrolling issue.
Last edited: