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.

Trinfa

macrumors newbie
Jun 8, 2021
3
1
I have the same problem, MBP10,2 refusing to run in retina 2x mode, so yes, all text is tiny.

Also, I'm running a basic 'no kexts' OC (I previously updated my Wi-Fi card to a supported one), just spoofing SMBIOS BoardProduct, and Monterey installed fine (no boot loops).

I did get the thing where the whole screen went black with just a cursor and a (tiny!) white spinning wait icon at one point (after successfully installing), but I think other machines are getting that too?
I had exactly the same result on mac mini 2012
 

Stratus Fear

macrumors 6502a
Jan 21, 2008
696
433
Atlanta, GA
Yep. I would imagine they will remove the drivers from final release as it would be pointless to include them. As you suspect though, we should easily be able to inject the drivers down the line if required.

The last time I recall Apple included “unneeded” code in a developer beta, it was the 32-bit kernel in Mountain Lion DP1 that disappeared on the very next beta release. So it doesn’t bode well for us, I suppose. Unless Apple intentionally included the drivers, but by all appearances there is no reason that they needed to. If it was a mistake on their part, and they “fix” it later, it certainly is fortunate for us since we now have drivers that were built on the Monterey code base that we can likely reuse.
 

David dongfox

macrumors member
Jul 26, 2020
75
59
I have the same problem, MBP10,2 refusing to run in retina 2x mode, so yes, all text is tiny.

Also, I'm running a basic 'no kexts' OC (I previously updated my Wi-Fi card to a supported one), just spoofing SMBIOS BoardProduct, and Monterey installed fine (no boot loops).

I did get the thing where the whole screen went black with just a cursor and a (tiny!) white spinning wait icon at one point (after successfully installing), but I think other machines are getting that too?
you said (after successfully installing) you mean you installed that OS ?
 

lesliewong

macrumors newbie
Jul 1, 2020
24
31
United States
On my MBP 10,1 with BCM94360CSAX Airport, I booted using OpenCore-Legacy-Patcher-monterey-support and Software Update had the macOS 12.0 Developer Beta 1 (21A5248p).

Installation was successful with no problems yet.

Thanks @khronokernel, @K two
 
  • Like
Reactions: K two

nandor690

macrumors 6502
Jun 25, 2011
374
221
For anybody wondering: At this time, I am planning on creating a brand new patcher for Monterey. I plan on using a fully native approach (IE not using OpenCore), and supporting only Metal-comptible systems (2012 and later, plus older systems with upgraded video cards). If this ends up being a huge pain I may reconsider, but as of now I will start working on a patcher within the next few weeks.
He’s back!!
 

Bmju

macrumors 6502a
Dec 16, 2013
702
768
you said (after successfully installing) you mean you installed that OS ?

I do. Monterey installed with no apparent problems (except tiny text, i.e. not in 2x retina mode) on my MBP10,2, using very minimal board-id spoofing only via OC (not using OCLP, no Lilu, no WhateverGreen, no kexts, no patches!).

It was only after a first 'normal' reboot (i.e. after fully installing, going through OS setup, etc.) that it went to the black screen with a cursor and wait icon.

That was this morning, and I had to get off to work ;) - I haven't tried again since - so don't yet know whether it can actually reboot okay sometimes (though I was assuming so...) - will report back.
 
  • Like
Reactions: David dongfox

DmitryZ

macrumors newbie
Jun 30, 2019
21
6
Ukraine
Hi everybody.
I have macBook 11.2 (Pro 15 mid 2014) + ”Matt Card” with patch the Boot ROM/system firmware with a NVMe driver from 2015 MacBook.
Officially Apple doesn't provide macOS Monterey for this laptop. Who can provide/help with information about patch Boot Rom on Matt Card for usage NVMe + macOS Monterey on this macBook 11.2 (Pro 15 mid 2014)?

p.s. Forwarded from thread "Upgrading 2013/2014 Macbook Pro SSD to M.2 NVMe"
 
  • Like
Reactions: macpro_mid2014

thatguywill

macrumors regular
Jun 7, 2021
165
287
used bigsur micropatcher and create install media method, works fine on MBP 11,3 Late 2013.
Nice, same laptop, i tried and was met with this when selecting the bootable USB...
 

Attachments

  • Unknown.png
    Unknown.png
    1.4 KB · Views: 123

pshufd

macrumors G4
Oct 24, 2013
10,155
14,579
New Hampshire
A new approach this morning. Install Ubuntu, Create macOS Big Sur KVM, upgrade to Monterey Beta 1. I'm away during the day so will do most of this tonight.
 

steverae

macrumors member
Mar 10, 2009
89
65
UK
Hi Guys

Has no one mentioned the iMac 13,2...? the original late 2012 skinny model - Ive got Monterey running on this using the Big Sur Micropatcher and installing from a USB drive without issue. This was previously running Big Sur 11.4 via the patcher app.

The only issue I have is the kexts won't patch for the WIFI etc. I've modified the patch-kext.sh file to allow attempt to fool it into working with Build 21 instead of 20 but this fails....


Everything else seems to work fine, bluetooth (keyboard and mouse) USB can see the USB drive still - just the WIFI.

Any help from you extremely clever people would be awesome and please add iMac 13,2 to the list of supported platforms once we get this WIFI issue working :D
 

andrey_russian

macrumors newbie
Jul 4, 2018
23
18
I have The 2007 iMac 7,1 with the CPU is upgraded to a Penryn-based Core 2 Duo, such as a T9300.
I will wait for a solution for my iMac.
 

webg3

macrumors 6502a
Jul 19, 2018
507
774
As I mentioned earlier, I managed to install macOS Monterey on my MacBook Air 2012 11" 4GB RAM Intel HD Graphics 4000, thanks to OpenCore 0.7.0 (I didn't use OpenCore Legacy Patcher)

But I'm without graphics acceleration.

When trying to fix, black screen and mouse pointer on the welcome screen.

Without acceleration, it is unfeasible, but it is already a big step to have it working.
 

mansley12

macrumors newbie
Oct 10, 2019
27
5
See the hardwares of my cMP I posted, that make the difference.
Hi,

Can you elaborate a bit more? Your hardware specs do not seem out of the ordinary when compared to admins/users testing in the mac pro group referenced. The bar to which all users have set is approximately 20 boot cycles, assuming there were no installation hangs already on 12, which would reveal disk corruption.

Can you provide insight into the following:

1. Which hardware you think sets the difference to previous testers for 5,1 in regard to to 11.3+ who observed disk corruption.
2. What tests you have done to confirm successful installation and usability.
3. Results after 20 boot cycles.

Many thanks to any additional information you can provide.

Mark
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.