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.
  • Like
Reactions: Vvglyy Wzxit
Hi guys, I'm stuck with installing Monterey on an iMac8,1. I managed to get it running up until the configuration screen after install where you set all the basic settings and the user account. So I'm really close to success, but right at this stage the USB patches including keyboard and bluetooth access seem to be broken.
During the installation, the paired Bluetooth Mouse and the USB keyboard worked well, but now at the first boot of the installed system I have no possibility to continue the setup of the machine.
I looked in the documentation, but found no workarounds for this case. Any ideas on how to fix this?
 
You want to use wired keyboard and mouse initially.

Present the most basic hardware config while getting it patched.
Great, thanks! Weirdly enough, after trying to boot for a few times more, it suddenly worked with both the USB keyboard and the bluetooth mouse.

Now I applied the post-install patches (option #3 in the menu) in order to have audio and wifi on the iMac 8,1 - but after applying them in the OCLP 0.3.3 TUI, I only can boot to a black screen now.
I patched the boot volume before with the GUI 0.3.3, this worked well except for audio and wifi. Then I applied the post-install patches in the TUI and can't boot into the system anymore.
The same problem happens on Big Sur after the post-install patches: The apple logo + progress bar disappear during boot, only a black screen with no mouse pointer whatsoever remains, but the HDD keeps working noticeably for a while and then: complete silence with a black screen.

Is there anything I can do to get it back running? Thanks for any suggestions!

BTW, I'm so grateful for this project and this community - Thank you so much for this amazing effort to keep those great machines running, even up to 14 years later!
 
Hi guys,

2011 iMac 27" with OCLP 0.3.3 and non-metal patch (Monterey 12.1). Extremely long boot time - Apple logo and progress bar take approx. 3 min 40 s to finally enter the login screen. This is caused by OCLP? Or is the any other culprit? I did a clean install of macOS Monterey 12.1, I have Fusion drive (240 GB SSD + 1 TB HDD) - I installed the OCPL build to SSD when asked. Also I added 4 GB (2x 2 GB) of additional memory recently - now I have 8 + 8 + 2 + 2 (20 GB in all 4 slots). Is there anything I could try to speed up the boot little bit? Thanks.
 
This is an ongoing issue with Lilu:

FYI there is a Lilu fix that was just released today for OCLP
not sure if it fixes your exact issue but worth looking into and trying out
 
FYI there is a Lilu fix that was just released today for OCLP
not sure if it fixes your exact issue but worth looking into and trying out
I can see still same version 0.3.3, shold I just re-download this version and try to create and install new build on the internal Fusion drive?
 
Personally I'd wait for the next public macOS release and oclp 034. No hurry. I have learned when to quit banging my head against a brick wall. Sometimes you need to have a stable reference point from which to report progress otherwise it's kind of a moving target. Work is going on in the background I imagine. But anyway I wish you luck.
 
  • Like
Reactions: jirin
FYI there is a Lilu fix that was just released today for OCLP
not sure if it fixes your exact issue but worth looking into and trying out
Yes, this fix will work. In fact, we discussed it here two days ago:

 
  • Like
Reactions: K two and hvds
This happens to me with monotonous regularity when installing OTA to an external SSD with 512 GB. I have noted that the current 12.1 is a release candidate, not the final production version. I've decided to wait until the production version is released, maybe next week. Will try OTA first, if that fails will do a clean install.
Did you get it updated? still having the same issues...
 
  • Like
Reactions: rehkram and K two
I can see still same version 0.3.3, shold I just re-download this version and try to create and install new build on the internal Fusion drive?
I personally download OCLP using git and then when updates come I do a git pull and use the CLI version of OCLP
hope this helps
 
The proposed fix is in the most current _034 NIGHTLY. :rolleyes:
Great. Please, whats the steps if I am currently on 0.3.3? Just download and run the app (0.3.4) from internal HDD, create new build and install it on internal HDD?
 
  • Like
Reactions: K two
I’ve update my late 2013 iMac on 12.1 from 12.0.1 with oclp 0.3.1
Everything runs fine except one thing. My iMac wakes from time to time alone from sleep and the display turn on.
I take a look in the terminal to find what the reason is and the are two things listened:
- RTC (Alarm)
- XHC1

I think this have something to do with the update because I don’t had this problems before but I don’t know what to do.
Thanks for help
 
It should be automatic.
https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30715101
How is the external SSD connected? The screen should go black - just wait a few minutes and it should continue.
Maybe change the background color to something special - not white or black or gray - so you know when OpenCore has started.

For example, without OpenCore, I use the following command to set the background color to a light orange color (see it in the Apple Startup Manager by holding the option key):
Code:
source "/Volumes/Work/Programming/ThunderboltProjects/Other/OSXOLVED/gfxutil.sh"
setnvramhex 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:DefaultBackgroundColor 7f7fff80

And in the OpenCore config.plist, I use a light blue color:
Code:
                <key>DefaultBackgroundColor</key>
                <data>/39/AA==</data>
Which was converted from hex like this:
xxd -p -r <<< ff7f7f00 | base64
And converted to hex like this:
base64 -d <<< /39/AA== | xxd -p

The four bytes are the blue, green, red components (the last byte is unused I think).

So whenever I reboot, I know when OpenCore is booting.


It will say "Macintosh HD" for the update from 12.0.1 to 12.1 but during the installation of 12.0.1, there will be a "macOS Installer" item. Anyway, it should be automatically selected and booted by OCLP.
Just an update regarding installation to an external SSD. So on my Imac 13,1, it isn't automatic, meaning if I don't manually select the correct boot picker during installation reboots, the process will just error out/hang on a black screen. I've spotted a few Youtube comments stating the same issue. Here is the workaround in case it helps anyone else:

• Make sure you you have verbose mode as well as boot picker menu set to true in OCLP settings
• During each reboot, you need to select macOS installer during the first 2 reboots and thereafter the SSD that you're installing to. If you choose to hold down alt/option during these reboots, you'll first need to select and enter the USB EFI boot picker, and then select and enter macOS installer/SSD.
• If you encounter a looping error stating "failed to obtain model information". Shut down with the power button and restart. When the boot picker menu shows up, select SSD (as stated above) and the installation process will continue

Thanks to everyone involved with OCLP.
 
  • Like
Reactions: K two and hvds
Hi guys,

2011 iMac 27" with OCLP 0.3.3 and non-metal patch (Monterey 12.1). Extremely long boot time - Apple logo and progress bar take approx. 3 min 40 s to finally enter the login screen. This is caused by OCLP? Or is the any other culprit? I did a clean install of macOS Monterey 12.1, I have Fusion drive (240 GB SSD + 1 TB HDD) - I installed the OCPL build to SSD when asked. Also I added 4 GB (2x 2 GB) of additional memory recently - now I have 8 + 8 + 2 + 2 (20 GB in all 4 slots). Is there anything I could try to speed up the boot little bit? Thanks.
I noticed the same thing when booting to an external SSD. It takes almost 4 minutes compared to 1 with Big Sur. There are some users stating boot times of 30+ minutes, so I guess it could be worse. It looks like a Monterey bug
 
  • Like
Reactions: K two
Did you get it updated? still having the same issues...

Here's the TL;DR summary - Yes, 12.1 public release installed fine on the internal drive over the top. I used gibMacOS to download the installer, ignoring the OTA offer.

More details: I only install betas on the external SSD and, currently, only do clean installs of them. Installing OTT (over the top) / OTA has seldom worked for my external USB SSD drive and so I've come to regard it as a waste of time even attempting. That way I avoid the frustration of it spending hours installing only for it to end up booting the older version, cue "slide trombone 'epic fail' sound effects"...

I don't run betas on the internal drive, which I reserve for the current public release. Public releases install OTA / OTT smoothly on the internal. It's just the external drive betas that won't install without erasing the disk and re-migrating. No big deal to clean install.

Also, I decided at some point to always use gibMacOS to get the installers (ignoring the OTA offering of same) as it always seems to work. I don't really trust the OTA thing on my unsupported rMBP, having wasted a lot of time with failed updates. Curiously, OTA does work flawlessly on my supported Mac mini though.
 
Last edited:
  • Like
Reactions: hvds and K two
I just tried installing 12.1 on my 2012 Mac Mini using OCP and it worked! It worked the first time! No random crashes or failed installs! I couldn't be happier.

I think the answer to this question is yes, but I'll ask it anyway. When a new update comes out, can I install it using the software updater or do I need to wait until it's been vetted and repackaged for OCP somehow?

Also, it might be my imagination but I swear that Monterey seems snappier than Catalina did. The only thing I'm disappointed about is that there's no cool dynamic photo wallpaper this time, just some abstract colors or weird cartoony pictures. Oh well... :)

EDIT: found a cool user made photo to fill the void. https://www.macrumors.com/2021/11/02/missing-macos-monterey-wallpaper-created/
 
Last edited:
  • Like
Reactions: rehkram and Tockman
or do I need to wait until it's been vetted and repackaged for OCP somehow?
When a new macOS update comes out, do you mean a beta or a public release? The reason I ask is that public macOS releases are, by definition, waaay more reliable than macOS betas. Lately the public macOS releases are generally followed by a new OCLP release to go with it.

In other words, which do you want to install, what's your tolerance for risk, and do you have the backups in place so you can recover if it goes south?

Wallpaper concerns are irrelevant when you get to this point so forget the visuals. You just need to keep on truckin' on with the new software, visuals can be fixed manually by you anytime you have a free moment to get creative. :)

Anyway, good luck!
 
Last edited:
Bootable volume renaming issue
I apologise if this has been addressed before, but I've been unable to locate the specific instruction to rename an EFI volume. I initially installed Big Sur on a volume called "macOS Big Sur". Subsequently I upgraded to Monterey and changed the Volume from "macOS Big Sur" to "macOS Monterey" in a hope to change the icon name in OCLP picker screen. However, it still shows "macOS Big Sur" even though the icon has changed to Monterey. I've read somewhere mentioning a program called disklabel in here. But I don't see this program in my OCLP EFI (v0.3.3) and also not sure what to do with it anyway.
Your help will be greatly appreciated. Better still, to add this feature in the future OCLP release.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.