no good. can't even get bluetooth to turn on. it worked fine under big sur. once upgraded to monterey i lost it.
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 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
No wonder, we all know this and that is why it has been already mentioned in the documentation. If you do not want to read docs or release notes I cannot help.
Got a bit daring on a machine and now it is stuck. Any help would be appreciated.
Late 2013 15 MBP. 0.4.2 going from 11.6.4 to 12.2.1. Installed with SMBIOS spoof level minimum and showpicker set to off. Seems stuck at Apple. Keyboard lights up so it does get someplace in the boot process. Tried to restart and start in safe by holding option then ctrl on OCLP and enter. Same.
Thoughts?
Late 2013 15 MBP. 0.4.2 going from 11.6.4 to 12.2.1. Installed with SMBIOS spoof level minimum and showpicker set to off. Seems stuck at Apple. Keyboard lights up so it does get someplace in the boot process. Tried to restart and start in safe by holding option then ctrl on OCLP and enter. Same.
Thoughts?
Last edited:
try holding command-option-P and R and see if that works. and if you can get into your desktop I would enable show boot picker
Thank You! I just sorted it. Not sure why it didn‘t go into Safe Mode the first time, since bc it is an 11,3 I need to do the graphics fix, but it did the second. Just sorting some inconsistencies with the login background and wallpaper but looks like it worked. Thank You for replying. Your help on here is always appreciated even when I am not the one needing the help!
The docs Ausdauersportler mentioned do cover this issue, as do searches within this forum thread.
However, to summarise: you must have upgraded your wifi/bt internal card for Big Sur use (I presume). That mPCIe adapter board is fed by the USB + and - data signals from the original mobo BT connector. As that connector was only USB 1.1, that USB support was dropped by Apple in Monterey. To now get your card and internal adapter to work, you have to solder a long USB 2 cable - with standard 4 pin plug (NB. the 5v and Gnd pins don't get connected) onto the 2 data pads or holes on the adapter board. Route this new extension cable and plug out the back of the MP5,1 (best to feed the cable through any small round air hole first before doing the soldering!). Then plug a basic USB 2.0 hub into any free (orig) USB port, and the BT extension cable/plug into the hub. Your BT should now work (and with os10.12 and higher too).
If you have a USB 3 PCIe card installed, that may provide a USB 2 'hub' out of one of its back ports, without needing a further physical USB 2 hub as well (my MP5,1 USB 3.1 PCIe card works like this). Some USB 2 and 3 PCIe cards also have an internal header connector which can provide the necessary + and - data feeds (you'll probably still need to solder in a longer cable to get from the lower left side of the mobo to the top right side, but a header saves having to route the cable through the back metal bulkhead to get to an external hub).
I have an issue with Migration Assistant. My setup is a Mac Mini 2009 2.26GHz, 8GM RAM. The sole OS on this is Monterey 12.2.1 via OCLP (v0.42 default settings for Mac Mini 3,1). I initially wanted to resize an existing installation of the same but couldn't get this to work so I backed up what I had and wiped the disk. Installed Monterey and want to use MA to restore my apps and settings.
What happens is on starting up, MA asks for my password and then says it is logging out. It does things in the background and then the background wallpaper changes to default Monterey. The next thing is that the desktop flips as it does when you change user and I get a screen showing two logins - one for the default user and another called Setup User with a tick by it. If I log back in as myself the MA dialog box is there but the process is stalled. If I Ctrl+Cmd+Opt+Del+Ret to get a login box for Setup User, it does the same. I cannot progress with MA whatever I do. Is MA borked? I've reinstalled Monterey twice now and it still does the same.
What happens is on starting up, MA asks for my password and then says it is logging out. It does things in the background and then the background wallpaper changes to default Monterey. The next thing is that the desktop flips as it does when you change user and I get a screen showing two logins - one for the default user and another called Setup User with a tick by it. If I log back in as myself the MA dialog box is there but the process is stalled. If I Ctrl+Cmd+Opt+Del+Ret to get a login box for Setup User, it does the same. I cannot progress with MA whatever I do. Is MA borked? I've reinstalled Monterey twice now and it still does the same.
Only way MA works is using it at first startup after a clean installation.
Thanks to everyone involved in this project. My MBA 2010 with 12.2.1 and oclp 0.4.3 is running fine.
Only graphics anomaly is notifications which displays a weird unsightly blur. Any ideas?
Only graphics anomaly is notifications which displays a weird unsightly blur. Any ideas?
Just installed 12.3 beta, only major issue is trackpad. It's not working at all. Anyone on facing similar issue on MacBook 5,1 or other devices? Do we have any patch or something for it?
What happens when Bluetooth is turned on? 🤷♂️
I tried that actually and what happened is that after completion, I booted up to a login which after putting my password in just gave me a perpetual swirling circle and would not load the desktop.
There's a beta blur setting in OCLP. It's supposed to help with artefacts with unsupported graphics. Maybe turning it off may help.
Oh, sorry. I see. Odd, never hapenned to me. Maybe because I used the first version of Montery, and then upgraded once the MA was completed?
Then it shows 'searching for trackpad...' something. Probably it's because of beta release, what you think? Should I try 12.2?
I can't seem to get Mavericks to install on my Mac Pro 3,1 (with OCLP 0.4.2).
The installer starts just fine, and gets to the point where (I'm assuming) it's time to actually register the temporary copies of the install files from the external drive to the disk.
The installer then proceeds to crash. Nothing is registered as being on the target drive, and no logs are written to that disk (I'm unable to boot from the installed-to drive). The OCLP logs don't appear to show anything wrong.
Any ideas?
The installer starts just fine, and gets to the point where (I'm assuming) it's time to actually register the temporary copies of the install files from the external drive to the disk.
The installer then proceeds to crash. Nothing is registered as being on the target drive, and no logs are written to that disk (I'm unable to boot from the installed-to drive). The OCLP logs don't appear to show anything wrong.
Any ideas?
I don't think Opencore Patcher supports Mavericks install. Correct me if I'm wrong.
If that's the case, then how'd you initially manage to get
It seems to patch the install without error, and their guide specifically says it's compatible- it's worth noting that trying to install Big Sur fails in the same way at the same point in the install.
I'm more than willing to try something else if it's going to work; it just needs to not destroy my ability to boot the Catalina install it currently possesses.
Last edited:
For lower numbered OS's, add '-no_compat_check' [w/o quotes] to the boot-args (config.plist's NVRAM/Add/<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key> section). I can boot into 10.6, 10.9, 10.12 with this.
Oh, I think I misspoke; I'm trying to install Monterey, not Mavericks.
On that note, however, is there a best place to start looking as far as tweaking OpenCore goes? I'm curious as to how the system actually works/is configured, and suspect that might help in the future as well.
On that note, however, is there a best place to start looking as far as tweaking OpenCore goes? I'm curious as to how the system actually works/is configured, and suspect that might help in the future as well.
Last edited:
Right - now that we're back to Monterey and not Mavericks! - I recently experienced a similar endless reboot cycle and non-expansion of the installer files. The only way I progressed was to change the spoofing to iMacPro1,1 (changing the various MacPro7,1 name and BoardID instances in the config.plist to the iMacPro1,1 ones). After this, the full installer properly formatted the target partition and successfully installed (after numerous auto-boots) to the User creation screens and desktop. You can change the spoofing back to 7,1 after this.
Yeah. That is sort of what I initially did and I suspected that the 12.2.1 installer is a bit buggy, so I remade the installer downloading 12.2, which is what I used for my first successful install. Finally got it to work. Had the MA complete over Firewire rather than USB and still got the swirling circle. Left it for twenty-thirty minutes and finally got a desktop. It's not as if I had a tremendous amount of stuff to drag over (about 13GB) so why it took so long before bringing up the desktop is a mystery. It took two goes before the post install patch would work though. Looked at the version and it was 12.2.1. Dunno. OCLP must have had an off day.
Noticed one more thing. On my other Mac Mini (2012) also running Monterey, attaching a FW device causes the system to lock up and requiring a hard reset. Booting up with the FW device already attached is the only way to get it to behave. This doesn't happen on the 2009 Mac Mini although that needs a lot more help to run Monterey and you would think would be less stable.
I am THRILLED for you.
FireWire boot support relies on Catalina/Mojave extensions injected by OpenCore. While I can use them now to boot from directly connected disks I have also experienced a crashing system if I try to use target disk mode over FireWire, the disk slave just started does nothing, the disk master expected to show the FW connected drives just crashes.
Edit: On direkt reboot of the master the mount works!
Happend to iMac11,3 and iMac12,2 - no time to sort this out..
Last edited: