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.
Support for Nvidia maxwell cards (such as the gtx 960 & 980 models) stopped with High Sierra, when NVIDIA stopped producing/releasing its web drivers. Whoever wanted to upgrade to mojave and higher, in mapros that is, had to buy AMDs Polaris and Vega cards. Did you actually mean a gtx 780? To echo Ausdauersportler there hasn't been a gtx980m for apple's laptops or iMacs.

I cannot answer with regard to your specific startup problem. I use Catalina and Big Sur in a 5,1 Mac Pro via open core.
If you check his (@OKonnel) signature you can see he owns an iMac14,2 with an 780M. I knew it was a typo from the beginning and I was not starting a tour de horizon about ancient NVIDIA graphics cards.

There exists in fact a GTX 980M (MXM) card which runs fine in these iMacs using an MXM slot, unfortunately - as we both know - only with non macOS system offering driver support. Apple laptops had ?never? used MXM cards?
 
Last edited:
  • Love
Reactions: OKonnel
Try just this other modified version, that should work with your particular multiple APFS macOS.
it already worked

it would be formicable if you can put the steps to do in order to change these steps to be able to use on other machines

because I was testing on another one and Github's works and this one doesn't

so i suppose if you have more than one system installed there is something to change and that would be of great importance to me and the community to be able to use

this tool is more than great and has a lot of interest even for the Hackintosh community

I have several hackintosh with a lot of different hardware and I can test it for you with the graphics patches on the ATI 5730 if you need to.

I just have the language barrier that I have to use google translate !
 

Attachments

  • 0.png
    0.png
    697.9 KB · Views: 449
If you check his (@OKonnel) signature you can see he owns an iMac14,2 with an 780M. I knew it was a typo from the beginning and I was not starting a tour de horizon about ancient NVIDIA graphics cards.

There exists in fact an GTX 980M (MXM) card which runs fine in these iMacs using an MXM slot, unfortunately - as we both know - only with non macOS system offering driver support. Apple laptops had ?never? used MXM cards?
Actually I did not check the signature and for Apple's laptops I just know they never had a 980 in them; to be honest I never really followed apple's laptop business.
 
Support for Nvidia maxwell cards (such as the gtx 960 & 980 models) stopped with High Sierra, when NVIDIA stopped producing/releasing its web drivers. Whoever wanted to upgrade to mojave and higher, in mapros that is, had to buy AMDs Polaris and Vega cards. Did you actually mean a gtx 780? To echo Ausdauersportler there hasn't been a gtx980m for apple's laptops or iMacs. I cannot answer with regard to your specific startup problem. I use Catalina and Big Sur in a 5,1 Mac Pro via open core.
Mistake...;) My iMac with invidia GTX 780M 4GB, in fact, is well supported perfectly, by default, up to macOS Catalina :)
The nVidia GTX 780M graphics card is original and I chosed in the purchase OTA directly from the Apple Store site. It represents the best of graphic cards for iMac 27'' (Late 2013) equipped with i7 CPU with maximum clock.
However the speech also applies to the others iMac14,2 equipped with other less performing nVidia; they are all supported up to Catalina.

The beauty (or the ugly if we think at one schedulated obsolescence by Apple...) is that my iMac has never gone so well, how it goes now with Monterey! I just tried a very heavy 2K video, downloaded from YouTube and runs in QuickTime without latch, even if I move the window quickly!!!...

We think of all those who, like me, were thinking about buying a new iMac after seeing that with Big Sur their Macs had problems. On Internet I found that even some Macs supported by Big Sur had unresolved issues with Photo Booth, as I had with my IMAC not supported! And instead everything works with Monterey now!... I am convinced that even the Preview defects with the .HEIC files depend on a poor Apple programming and not from my hardware ..
 
Last edited:
Up and running on my 2015 MacBook Pro 15. Fans ran constantly during installation but they're quiet while it is running and downloading email, notes and other stuff. I've played around with it and I'm going to use it as my daily driver. So far, it's good enough for me to upgrade to from Mojave on this system. If it continues to be good, then I will update my 2014 as well. My test for this thread will be to just hook the disk to my 2014 and see if it boots.
 
  • Like
Reactions: OKonnel
Up and running on my 2015 MacBook Pro 15. Fans ran constantly during installation but they're quiet while it is running and downloading email, notes and other stuff. I've played around with it and I'm going to use it as my daily driver. So far, it's good enough for me to upgrade to from Mojave on this system. If it continues to be good, then I will update my 2014 as well. My test for this thread will be to just hook the disk to my 2014 and see if it boots.
But 2013-14 MBP use older Intel graphics support for which is dropped.
 
But 2013-14 MBP use older Intel graphics support for which is dropped.

The 2015 MacBook Pro 15 models use the same CPUs as the 2014 MacBook Pro 15 models. The 2014 models had optional nVidia GPUs and the 2015 models had the optional AMD GPUs. The 2014 MacBook Pro 15 models have the exact same Intel graphics as the 2015 MacBook Pro 15 models so the 2014 models should be fine. My 2015 has the optional AMD graphics while the 2014 only has Intel integrated. I'm going to shut down the 2015, remove the external SSD, and see if I can boot it from the 2014.
 
It didn't work. It looks like I'll have to use one of the hacks posted here on the 2014. I need to rearrange my desk setup to bring the 2015 MacBook Pro onto it.
 
Monterey on MBP mid 2012.(external HDD)Lack of GPU acceleration is evident. (Disabling animations helped.) Installation with modified Micropatcher went fine.
Trying to install HD 4000 kext, will report.

EDIT: system stuck on login after reboot as others reported.
F0D82C43-9926-46A3-B8A5-B81CC388E938.jpeg
 
Last edited:
I am jus
The 2015 MacBook Pro 15 models use the same CPUs as the 2014 MacBook Pro 15 models. The 2014 models had optional nVidia GPUs and the 2015 models had the optional AMD GPUs. The 2014 MacBook Pro 15 models have the exact same Intel graphics as the 2015 MacBook Pro 15 models so the 2014 models should be fine. My 2015 has the optional AMD graphics while the 2014 only has Intel integrated. I'm going to shut down the 2015, remove the external SSD, and see if I can boot it from the 2014.
I am just curious how 2015 MBP are supported and 2014 (11,3) not? The only difference is the Apple SSD (which can be converted to NVMe) and the Nvidia (still with drivers in Monterey) versus AMD?
 
So -no_compat_check does not work?
Possibly? I do not own such a device, was just searching trough the complete list and compiling the results. All normal models 2014/2015 had the Intel Iris Graphics, the 2014 top models the Nvidia GT750, the 2015 top models the AMD R9 M370X. All other specs are the same.

May be we will see the Nvidia code for another year? The HD4000 has be deprecated last year and stripped this year. Okay, this is glass ball watching.
 
  • Like
Reactions: iMac-iPad
I am jus

I am just curious how 2015 MBP are supported and 2014 (11,3) not? The only difference is the Apple SSD (which can be converted to NVMe) and the Nvidia (still with drivers in Monterey) versus AMD?

I have the feeling that it's the potential presence of the nVidia GPU; either that or it's just arbitrary. I will get it to run on the 2014 to see how it feels but my guess is that it feels just like the 2015.
 
I have the feeling that it's the potential presence of the nVidia GPU; either that or it's just arbitrary. I will get it to run on the 2014 to see how it feels but my guess is that it feels just like the 2015.

How is then 11,5 supported model? Apple says early 2015 models are supported.
Most likely the NVIDIA GPU in the 11,3. No officially supported machine has NVIDIA graphics, and the inclusion of the kexts in the initial beta was probably either a mistake or it just hasn't been pulled yet, much like the 32-bit kernel support in the initial Mountain Lion beta years ago. I sort of expect this to be "rectified" in a later beta, and definitely before GM.

If I had to guess, Apple doesn't want to keep supporting new iterations of Metal on an 8-9 year old graphics architecture from a vendor that they haven't had a relationship with in years. That would explain most of the cutoff decisions.
 
The 2015 MacBook Pro 15 models use the same CPUs as the 2014 MacBook Pro 15 models. The 2014 models had optional nVidia GPUs and the 2015 models had the optional AMD GPUs. The 2014 MacBook Pro 15 models have the exact same Intel graphics as the 2015 MacBook Pro 15 models so the 2014 models should be fine. My 2015 has the optional AMD graphics while the 2014 only has Intel integrated. I'm going to shut down the 2015, remove the external SSD, and see if I can boot it from the 2014.
You only need a basic OpenCore, changing the 2014 model to 2015 and the board ID for the system to think it's using a 2015. These are two lines that need to be changed in a config.plist OpenCore 0.7.0
 
You only need a basic OpenCore, changing the 2014 model to 2015 and the board ID for the system to think it's using a 2015. These are two lines that need to be changed in a config.plist OpenCore 0.7.0

I've never gotten OC to work. I've done TonyMacx86 hacks, KVMs, VirtualBox and VMWare but not OC.

Hopefully there are some really easy directions in this thread on how to do this.
 
so i suppose if you have more than one system installed there is something to change and that would be of great importance to me and the community to be able to use

I made that app to provide an easier way to replace system files directly from BigSur (or Monterey) Finder, so I considered installations made on their own APFS container where System is on diskXs5 by default apple scheme.

Anyway the modification to target a different diskXsY is really simple, just check here:

https://github.com/jacklukem/BigSur...3be0/Contents/Resources/Scripts/main.scpt#L20

just change only the number "5" with the matching number of your Big Sur (or Monterey) System.

Big Sur and Monterey installation on their own APFS container use the Volume number "5", multiple APFS macOS on the same APFS container is unusual (also apple on some document doesn't advise it).
 
  • Like
  • Love
Reactions: olad, webg3 and PG7
just change only the number "5" with the matching number of your Big Sur (or Monterey) System.

Big Sur and Monterey installation on their own APFS container use the Volume number "5", multiple APFS macOS on the same APFS container is unusual (also apple on some document doesn't advise it).
thank you so much

it was really that part that I was missing!
 
Hello, thought I'd shed a bit of light regarding the Bluetooth situation on macOS Monterey and older Macs. For many machines running BRCM2046 and BRCM2070 bluetooth modules you'll likely have noticed that once booted into Monterey, there is no Bluetooth support. This is due to Apple dropping the firmwares used on these modules.

Can we add them back? Not so easily unfortunately. Monterey moved a ton of the Bluetooth stack from kernelspace to userspace including firmware loading. Specifically now a new binary called BlueTool will load firmwares from usr/share/firmware. Additionally, the device IDs are hard coded into BlueTool so manually adding the binaries will not help.

For the time being, I highly encourage users with upgradable Bluetooth modules to search for cards that use the BRCM20702 and BRCM20703 chipset. We will be investigating further regarding re-adding support

Additionally we are still researching support for legacy Wireless cards such as the BCM94322, BCM94328 and Atheros series. BCM943224, BCM94331, BCM94360 and BCM943602 still work great with our current patch set in OpenCore Legacy patcher so recommend users upgrade to these wireless cards for best support .


Edit: Information updated from this finding


Models that use the BRCM2046:
  • iMac12,x and older
  • Macmini4,1 and older
  • MacBook7,x and older
  • MacBookAir4,1 and older
  • MacBookPro8,x and older
  • MacPro5,1 and older
 
Last edited:
Sorry I found the oblivion after uploading

To resolve your issue:
Edit "patch-kexts.sh" in "Payload" folder of your patched USB installer an replace "20" by "21" at this ligne (385)

Code:
if echo $SVPL_BUILD | grep -q '^20'

Or download the "patch-kexts.sh" file here and replace it in the "Payload" folder of your patched USB stick.

And retry to patch the Wifi kext
Now i’ve got this:
 

Attachments

  • AC20A587-07D7-43E1-A009-5310E097FABB.jpeg
    AC20A587-07D7-43E1-A009-5310E097FABB.jpeg
    599.7 KB · Views: 184
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.