macOS 12 Monterey on Unsupported Macs Thread

[XLN82]

Firmware updated successfully.
View attachment 2009318

how did you do? is it doing automatically?

 

[Ausdauersportler]

Not sure if this is the right place, but as my issue started with upgrading to monterey...

I have an imac mid 2011 with a WX7100 MXM card running Monterey 12.3 and OCLP/OC0.8.1.

Before I was using a Sonnet Solo10G PCIe Card flawlessly in a TB1 enclosure (Atto Thunderlink).

After upgrading to Monterey, the card is no longer recognized as an ethernet card upon start and after poering off and on again either it is detected but does not receive an IP or the system freezes.

Neither manual Aquantia patches nor the new OC Kernel Quirk changes something.
IORegistryExplorer does not list AppleVTD. As I don't have a hackintosh, I cant't activate VT-d in Bios either...

Ideas anyone?

Is it due to Thunderbolt? Internal Aquantia cards seem to work in MP with OC?

Best regards,

r.

EDIT: Upgrade to OCLP 0.4.5 and Monterey 12.4 went flawlessly, but Aquantia ethernet still "broken"...

Another hunch:
You should go back to the lastet working macOS and check out which extension has been used to drive the 10G card. Possibly one can identify it and patch it and inject it back as khronokernel did for the 5701BCMEthernet and IntelL210Ethernet (fixed a freeze with the Elgato TB dock Ethernet ports)?

 

[laertemeira]

Read through the last two or three pages.

Edit: It would be really helpful if you add a signature with your Mac system and exact hardware description.

Perfect. I will adjust soon. Thank you!

 

[Tockman]

how did you do? is it doing automatically?

No, manually, installing latest updates on Catalina.

 

[makra]

No, manually, installing latest updates on Catalina.

And because of your posts I know, that it works fine just to add a Catalina volume on the system disk - as long as a PRAM/NVRAM reset is being done. Update to 429.... worked flawlessly on MBP 9,1 10,2 and iMac 13,1.

 

[techguy82]

Hi everyone. I still can’t copy files via the finder to my iPhone in the files section. I can copy files from the phone to my Mac but not to the phone. Can anyone help me please with some ideas what I can try out? My workaround is to copy files from my Mac to my iPhone via SMB but strangely I can’t delete those files from my l ok phone. The trash can icon is missing.

 

[laertemeira]

Hi everyone!

I was reading the crash report... I'm wondering if the "cpu 2" mentioned in report has some link with AppleMCEReporter kext used in OCLP... despite it doesn't be necessary anymore...

Question: mixed memories or a Nehalem processor can be the cause for this instability? Upgrading with a x5690 can solve the problem? Or using all same model/specs ECC memory modules? With Catalina the machine ran perfectly without any crash. Only workaround was disabling machine sleep - if I remember correctly.

Thanks for any insight!

 

[techguy82]

I have noticed another problem. I had it several times that when I closed the lid and when I later opened it again, the MacBook wasn't locked. Same problem noticed without closing the lid when the display goes to standby. I sometimes can reactivate the MacBook without typing the password. This is a huge security issue.

 

[hwojtek]

I was reading the crash report... I'm wondering if the "cpu 2" mentioned in report has some link with AppleMCEReporter kext used in OCLP... despite it doesn't be necessary anymore...

Please double-check the instructions. Expand "Complete your setup" section and keep scrolling until you find AppleMCEReporterDisabler.kext, which I believe is still mandatory in a dual-CPU Mac Pro.

If you don't use it, enabling this will help. If you use it and it loads properly, I'd first look into the mismatched RAM and only if matched RAM fails go for the CPU swap.

 

[roysterdoyster]

I have noticed another problem. I had it several times that when I closed the lid and when I later opened it again, the MacBook wasn't locked. Same problem noticed without closing the lid when the display goes to standby. I sometimes can reactivate the MacBook without typing the password. This is a huge security issue.

Indeed, this is hugely problematic.
Same problem on my MBP4,1.

Anyone know how to solve this?

 

[iMac-Oldschool]

iMac 13,1 late 2012, updated to 12.5 Beta 1.
OTA update failed twice during the download. Downloaded Install_macOS_12.5-21G5027d.dmg and created a bootable USB installer. Booted from the USB stick and everything ran smoothly.
No progress with SideCar. Only works over USB, not WiFi.
Firmware is now 429.0.0.0.0 following the guidance given in posts #6279, #6282 and #6283.

 

[webg3]

It was a pain in the ass to get Windows finally working on my Macbook Pro 11,1 (late 2013)

As recommended I created a separate partition for OCLP and removed

/System

and

/EFI/OC

from the Original EFI-Partition. However when booting, both partitions now look like OCLP (one of them is Bootcamp of course and boots directly into Windows 10). For the other one, the actual OCLP, I activated Boot Picker mode. But no matter how often I try to set Macintosh HD as default, I still picks Windows first. And everytime I boot into macOS Monterey it displays an error message that the system "has restarted after a problem".

I already tried switching partitions and both system were still bootable from OCLP, but the error message in macOS persisted. Any suggestions how I could fix that? My partition table looks like that:

 #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         919.8 GB   disk0s2
   3:       Microsoft Basic Data ⁨OC⁩                      199.2 MB   disk0s3
   4:       Microsoft Basic Data ⁨Bootcamp⁩                80.0 GB    disk0s4

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +919.8 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD⁩            15.2 GB    disk1s1
   2:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.2 GB    disk1s1s1
   3:                APFS Volume ⁨Preboot⁩                 298.7 MB   disk1s2
   4:                APFS Volume ⁨Recovery⁩                1.1 GB     disk1s3
   5:                APFS Volume ⁨VM⁩                      3.2 GB     disk1s4
   6:                APFS Volume ⁨Macintosh HD - Daten⁩    181.9 GB   disk1s5

look at my partition scheme:


#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI ⁨. EFI⁩ 209.7 MB disk0s1
2: Apple_APFS ⁨. Container disk1⁩ 748.0 GB disk0s2
3: Microsoft Basic Data ⁨. BOOTCAMP⁩ 252.0 GB disk0s3

/dev/disk1 (synthesized):


#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +748.0 GB disk1
Physical Store disk0s2
1: APFS Volume ⁨Preboot⁩ 299.0 MB disk1s2
2: APFS Volume ⁨Recovery⁩ 1.1 GB disk1s3
3: APFS Volume ⁨VM⁩ 3.2 GB disk1s4
4: APFS Volume ⁨SSD - Dados⁩ 301.4 GB disk1s7
5: APFS Volume ⁨SSD⁩ 16.5 GB disk1s8


6: APFS Snapshot ⁨com.apple.bless.338F...⁩ 16.5 GB disk1s8s1


I was on macOS Catalina and I used Bootcamp Assistant to install Windows 11, so it doesn't depend on OpenCore, it has a separate partition, I hold the option key and select it even before the bootloader OpenCore Legacy Patcher

In case I don't hold the option key, it boots directly into OpenCore (EFI) of macOS Monterey, Bootcamp partition doesn't even appear in Opencore;

works perfectly like this

 

[Aston441]

look at my partition scheme:


#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI ⁨. EFI⁩ 209.7 MB disk0s1
2: Apple_APFS ⁨. Container disk1⁩ 748.0 GB disk0s2
3: Microsoft Basic Data ⁨. BOOTCAMP⁩ 252.0 GB disk0s3

/dev/disk1 (synthesized):


#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +748.0 GB disk1
Physical Store disk0s2
1: APFS Volume ⁨Preboot⁩ 299.0 MB disk1s2
2: APFS Volume ⁨Recovery⁩ 1.1 GB disk1s3
3: APFS Volume ⁨VM⁩ 3.2 GB disk1s4
4: APFS Volume ⁨SSD - Dados⁩ 301.4 GB disk1s7
5: APFS Volume ⁨SSD⁩ 16.5 GB disk1s8


6: APFS Snapshot ⁨com.apple.bless.338F...⁩ 16.5 GB disk1s8s1


I was on macOS Catalina and I used Bootcamp Assistant to install Windows 11, so it doesn't depend on OpenCore, it has a separate partition, I hold the option key and select it even before the bootloader OpenCore Legacy Patcher

In case I don't hold the option key, it boots directly into OpenCore (EFI) of macOS Monterey, Bootcamp partition doesn't even appear in Opencore;

works perfectly like this

I don't know for certain, but I have the impression that Monterey's version of Bootcamp Assistant is significantly more buggy than what shipped with Catalina.

 

[Bmju]

It was a pain in the ass to get Windows finally working on my Macbook Pro 11,1 (late 2013)

As recommended I created a separate partition for OCLP and removed

/System

and

/EFI/OC

from the Original EFI-Partition. However when booting, both partitions now look like OCLP (one of them is Bootcamp of course and boots directly into Windows 10). For the other one, the actual OCLP, I activated Boot Picker mode. But no matter how often I try to set Macintosh HD as default, I still picks Windows first. And everytime I boot into macOS Monterey it displays an error message that the system "has restarted after a problem".

You have to be aware that the file /EFI/BOOT/BOOTx64.efi (upper/lower case may vary) changes depending on what was most recently installed (Windows, OpenCore, Linux). It is not needed once the new s/ware has booted once (and saved an NVRAM boot entry to its actual startup file). But it is needed for the firmware to detect and (offer to) boot something newly installed.

Once you're aware of that, then while it is less secure (because on an easily accessible volume), it is much easier to manage, if you copy that file and the /BOOT/Microsoft files to a very small (say 50MB) FAT partition to launch Windows. (Similar to what you already tried, to move OCLP; and the same issue about BOOTx64.efi applies to that )

The other single biggest issue with dual-booting Bootcamp Windows is that the hybrid MBR setting keeps getting lost if you make any other disk manipulations at all. The symptom is that the Windows install seems to be just lost, it won't start at all, and it seems you have to redo it all over again. But in fact all you have to do is follow the gdisk instructions (and only those) e.g. from here, to bring it back.

 

[KevinClark]

I have reinstalled from full 12.4 with usb bootable key and OCLP 045 on my Mac Pro 2010 12 cores RX580 Smashed Mac 8 go and NVME works good no restart

 

[0134168]

I don't know for certain, but I have the impression that Monterey's version of Bootcamp Assistant is significantly more buggy than what shipped with Catalina.

Not on supported macs. Works like a champ.

 

[laertemeira]

Please double-check the instructions. Expand "Complete your setup" section and keep scrolling until you find AppleMCEReporterDisabler.kext, which I believe is still mandatory in a dual-CPU Mac Pro.

If you don't use it, enabling this will help. If you use it and it loads properly, I'd first look into the mismatched RAM and only if matched RAM fails go for the CPU swap.

Hi friends! Hope you all are having a good day!

Looking in the NVRAM section of OpenCore on the Mac Pro thread I'm not sure if I may delete these lines, as the instructions. Below, a print of my config.plist (created by the OCLP 0.4.6n today.

As the thread tells, I need some keys here only if I need boot Mojave or if I need SurPlus.

Below, the thread print.

Thank you!

 

[hwojtek]

Looking in the NVRAM section of OpenCore on the Mac Pro thread I'm not sure if I may delete these lines, as the instructions. Below, a print of my config.plist (created by the OCLP 0.4.6n today.
As the thread tells, I need some keys here only if I need boot Mojave or if I need SurPlus.

You may keep it. Will do no harm, you can always remove them later. It would help, BTW, if you included your hardware/software, it would not make us have to search for your kernel data to find you run Mavericks 12.3 (update it to 12.4).
What is important, is your AppleMCEReporterDisabler.kext. If you used OCLP, it's there, so after what you did today, does your system still panic?

 

[laertemeira]

You may keep it. Will do no harm, you can always remove them later. It would help, BTW, if you included your hardware/software, it would not make us have to search for your kernel data to find you run Mavericks 12.3 (update it to 12.4).
What is important, is your AppleMCEReporterDisabler.kext. If you used OCLP, it's there, so after what you did today, does your system still panic?

Thank you @hwojtek. I forgot to tell that I'm running Monterey 12.3.1. My Mac is almost original, except for the GPU and SATA SSD.

MacPro4,1->5,1 Early 2009/Nehalem 2.66GHz QuadCore Intel Xeon - 16GB mixed ECC and Non ECC RAM - ASUS STRIX R9 380 2GB - Kingston SA400 240GB SSD (boot)- Seagate Barracuda 1TB - Western Digital Caviar Green 1TB (TimeMachine).

I installed the last nightly build OCLP (0.4.6n) and did the edition on the config.plist recommended. Almost no differences between the file generated by OCLP and the template in the OpenCore Mac Pro thread. After that I used Parallels Desktop for 90 minutes without crashes. And them machine freezes 2 times, without leaving any entry in Console.

I removed AppleMCEReporterDisabler kext section cuz my Mac has only one CPU.

In a week I will update RAM and processor...

 

[Aston441]

Not on supported macs. Works likea champ.

Not my supported 2015 iMac 😂

ETA: I think "supported" is a lousy description. We should start calling them what they really are. Not sure what the term should be. Something that means "Machines not yet prematurely and maliciously abandoned by Apple because they're trying to force us to give them more money and for no other reason, and they're getting away with it because of the horrible inefficient and uncompetitive Monopoly/Oligopoly situation that now exists, and that was described hundreds of years ago by early economists, and that Congress is shirking their duty to break them up, but they've been neglecting this duty since the late 1800s Trust Busting era."

 

[XLN82]

Hi everyone, is there a way to install opencore patcher from Terminal in recovery mode?

 

[0134168]

Not my supported 2015 iMac 😂

ETA: I think "supported" is a lousy description. We should start calling them what they really are. Not sure what the term should be. Something that means "Machines not yet prematurely and maliciously abandoned by Apple because they're trying to force us to give them more money and for no other reason, and they're getting away with it because of the horrible inefficient and uncompetitive Monopoly/Oligopoly situation that now exists, and that was described hundreds of years ago by early economists, and that Congress is shirking their duty to break them up, but they've been neglecting this duty since the late 1800s Trust Busting era."

Maybe a bit long?

 

[mwidjaya]

Not on supported macs. Works like a champ.

Bootcamp works in a narrow corridor as Apple sees it.

For eg, I did some absurd experimentation to finally run unsupported Bootcamp version to run unsupported Win11 on a partition on 2010 MacBook Pro running supported High Sierra.

All working well now, so it stays like that, not fiddling with it some more, lol.

 

[0134168]

Bootcamp works in a narrow corridor as Apple sees it.

For eg, I did some absurd experimentation to finally run unsupported Bootcamp version to run unsupported Win11 on a partition on 2010 MacBook Pro running supported High Sierra.

All working well now, so it stays like that, not fiddling with it some more, lol.

Well, in fact, any Intel Mac can run Windows. Bootcamp just suply drivers. But I like to have the same controls for Audio and Bright in Windows. I could install Windows 10 in my Mac pro 5,1 with native key controls.

 

[hwojtek]

I removed AppleMCEReporterDisabler kext section cuz my Mac has only one CPU.
In a week I will update RAM and processor...

OK, that's cool, you don't need this kext.
Start with the RAM, please. The probability of RAM failing is somewhat higher than CPU and the replacement procedure is way simpler. Upgrade the RAM, don't forget to cmd+alt+p+r for a couple of times after you're done, let the computer run for a while.