Hi, thanks for info. I will try to do it your way one more time. I will do it from scratch, mean I will install OCLP again completely.
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
There is a workaround for this. Install Intel Power Gadget and reboot, what this installation does is rebuild the Preboot volume and OpenCore gets the new name after that.
I would recommend and external enclosure and boot with NMVe, I use one on my 2011 27" and 2013 21.5" and its fantastic even on TB1.
Is there any chance that the “airplay receiver” issue that affects iMac 14.x and maybe others will be fixed?
I also saw a post that said there was a missing Core Graphics driver issue with Photoshop. I experienced this myself, but it now seems to have disappeared. Has anyone else noticed this?
I also saw a post that said there was a missing Core Graphics driver issue with Photoshop. I experienced this myself, but it now seems to have disappeared. Has anyone else noticed this?
I know, I should've tagged with <sarcasm>
That's the point. As a large number of users backup to Time Machine on NASes (or servers like myself) the statement "Monterey requires APFS for Time Machine" is actually false which is what I wanted to point out. For directly attached backups (or iSCSI as you correctly noted, which technically is a disk directly attached from OS point of view) - it's a recommended filesystem yet not a strict requirement. Apple actually points it out in the help article linked above:
Apple said:
Yep. I still use HFS+ when using HDDsI know, I should've tagged with <sarcasm>
That's the point. As a large number of users backup to Time Machine on NASes (or servers like myself) the statement "Monterey requires APFS for Time Machine" is actually false which is what I wanted to point out. For directly attached backups (or iSCSI as you correctly noted, which technically is a disk directly attached from OS point of view) - it's a recommended filesystem yet not a strict requirement. Apple actually points it out in the help article linked above:
Hello
i have a late 2013 MacBook Pro retina.
1. did a clean install
2. got the voiceover black screen with Apple logo at end of it.
3. To resolve as others pointed out I booted into Safe mode (hold shift) at boot
4. Setup Monterey and logged into macOS in safe mode
5. When trying to install opencore patcher to SSD internal drive EFI I get the following error:
“execution error volume on disk0s1 failed to mount…“ (see attachment)
is it because I’m trying to install in safe mode? If I don’t boot into safe mode I can’t even get into Monterey.
thnks For your help
nick
i have a late 2013 MacBook Pro retina.
1. did a clean install
2. got the voiceover black screen with Apple logo at end of it.
3. To resolve as others pointed out I booted into Safe mode (hold shift) at boot
4. Setup Monterey and logged into macOS in safe mode
5. When trying to install opencore patcher to SSD internal drive EFI I get the following error:
“execution error volume on disk0s1 failed to mount…“ (see attachment)
is it because I’m trying to install in safe mode? If I don’t boot into safe mode I can’t even get into Monterey.
thnks For your help
nick
Attachments
You can run OCLP to install the post install patches needed by your system in safe mode, this should allow to reboot into the normal mode. I bet it is somewhere mentioned in the docs...
Mounting the EFI in safe mode is blocked by Apple for security reason...
Install patches. Then reboot, no safe mode, and install OpenCore.
Uppps, i arrived seconds later. @Ausdauersportler answered while I was writing.
Thanks, but I would prefer run SSD as internal drive.
I tried to install Monterey on SSD only, boot time was 1:30 (acceptable). Rebooted several time after clean install, always 1:30. I created Fusion drive once again (240 GB SSD + 1 TB HDD), clean install again, boot time 1:36. Second boot about the same. I installed few apps, setup iCloud etc. - after that, boot time 6 minutes. I get back home now, tried it again and its 4:30. I dont understand how the times can be so different, but probably will go with single 1 TB SSD.
Guys, can I use SATA 3 drive in my iMac 2011? Is Samsung 870 EVO good enough?
You can pick any SATA III drive and you can also try cheaper solutions. The Samsung drives are known for a long life (high TBW) and are more expensive.
I got only one drive into the read only mode after a few years using it for hosting virtual machines. The 2011 has a two SATA III ports for disks and a single SATA II port used with the DVD.
I got only one drive into the read only mode after a few years using it for hosting virtual machines. The 2011 has a two SATA III ports for disks and a single SATA II port used with the DVD.
I switched stock RAM (2x 2 GB) in my 2011 iMac 27inch to 2x 8 GB (using slots 1 and 2). If I add old 2x 2GB to slots 3 and 4, will it work fine? Isn't it counter-productive (could possible slow down the computer), meaning does is matter how RAM are combined? All four modules are 1333 MHz of course.
Hi Team,
After preparing a USB drive with Monterey and configuring its EFI partition for a 2011 macmini5,3, I used bootpicker to choose the EFI volume, and then chose Install Monterey to continue installing macOS on a macmini5,3's internal drive. From the macmini5,3, the Monterey installer seems to boot most of the way and then reaches a flashing screen (1:30 into this video):
Verbose logging shows no significant errors. Has anyone encountered this and found a way to get past it? The project team has an issue report on this.
After preparing a USB drive with Monterey and configuring its EFI partition for a 2011 macmini5,3, I used bootpicker to choose the EFI volume, and then chose Install Monterey to continue installing macOS on a macmini5,3's internal drive. From the macmini5,3, the Monterey installer seems to boot most of the way and then reaches a flashing screen (1:30 into this video):
Verbose logging shows no significant errors. Has anyone encountered this and found a way to get past it? The project team has an issue report on this.
Wth? How about connecting a mouse and keyboard?
Looks like it is looking for mouse and keyboard.
Plug in a wired keyboard and mouse to your mini.
Haha, you can't see it in the video, but a keyboard is definitely plugged in to the mini.
An Apple USB keyboard is plugged in to the mini, it's just not shown in the video. If you look at the video at 1:30 in, it seems to be indicating something should be turned on but sliding a green switch, but I can't make out whatever Apple is referring to. And it's a macmini5,3, so there are no external switches other than the power switch.
A keyboard is not enough. As the colleagues above pointed out, MacOS will always prompt you for both a mouse and keyboard.
The Mini is asking for a BT mouse and a BT trackpad which have been previouly connected. ?