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.
Just have put ASB's latest binaries for SkyLight, CoreDisplay, QuartzCore into my 12.3b4 installation, using Bigsurmountsrw - file save and upload work! Writing from this system. I guess will soon be part of OCLP 0.4.3.
Waiting until this quick fix shows up in the Nightly root patch. Following this on Discord and GITHUB is helpful. ;)
 
I went to try the fix for the card reader in the latest OCLP nightly but it won't build for me, anyone else have the same issue or could try.

thanks

Code:
Building Configuration on model: MacBookPro8,1
Created build folder

- Adding OpenCore v0.7.8 RELEASE
- Adding config.plist for OpenCore
- Adding Lilu.kext 1.6.0
- Adding AppleALC.kext 1.6.3
- Enabling VMM exemption patch
- Enabling HW_BID reroute
- Adding FeatureUnlock.kext 1.0.7
- Adding additional FeatureUnlock args:  -disable_sidecar_mac
- Fixing ACPI SMC Power Management support
- Adding ASPP-Override.kext 1.0.0
- Adding CatalinaBCM5701Ethernet.kext 1.0.2
- Adding SurPlus Patch for Race Condition
- No 3rd Party NVMe drives found
- Found Wireless Device 14E4:4331
- Adding AirportBrcmFixup.kext 2.1.3
- Found ARPT device at PciRoot(0x0)/Pci(0x1c,0x1)/Pci(0x0,0x0)
- Applying fake ID for WiFi, setting Country Code: US
- Enabling Windows 10 UEFI Audio support
Traceback (most recent call last):
  File "OpenCore-Patcher.command", line 6, in <module>
  File "main.py", line 23, in init
  File "main.py", line 98, in main_menu
  File "utilities.py", line 542, in start
  File "build.py", line 1230, in build_opencore
  File "build.py", line 415, in build_efi
AttributeError: 'list' object has no attribute 'vendor_id'
[42092] Failed to execute script 'OpenCore-Patcher' due to unhandled exception!

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Seems this was a bug in build.py which is solved in the latest OCLP nightly version (33min ago, "Resolve crash on Vendor detection")
 
I went to try the fix for the card reader in the latest OCLP nightly but it won't build for me, anyone else have the same issue or could try.

thanks

Code:
Building Configuration on model: MacBookPro8,1
Created build folder

- Adding OpenCore v0.7.8 RELEASE
- Adding config.plist for OpenCore
- Adding Lilu.kext 1.6.0
- Adding AppleALC.kext 1.6.3
- Enabling VMM exemption patch
- Enabling HW_BID reroute
- Adding FeatureUnlock.kext 1.0.7
- Adding additional FeatureUnlock args:  -disable_sidecar_mac
- Fixing ACPI SMC Power Management support
- Adding ASPP-Override.kext 1.0.0
- Adding CatalinaBCM5701Ethernet.kext 1.0.2
- Adding SurPlus Patch for Race Condition
- No 3rd Party NVMe drives found
- Found Wireless Device 14E4:4331
- Adding AirportBrcmFixup.kext 2.1.3
- Found ARPT device at PciRoot(0x0)/Pci(0x1c,0x1)/Pci(0x0,0x0)
- Applying fake ID for WiFi, setting Country Code: US
- Enabling Windows 10 UEFI Audio support
Traceback (most recent call last):
  File "OpenCore-Patcher.command", line 6, in <module>
  File "main.py", line 23, in init
  File "main.py", line 98, in main_menu
  File "utilities.py", line 542, in start
  File "build.py", line 1230, in build_opencore
  File "build.py", line 415, in build_efi
AttributeError: 'list' object has no attribute 'vendor_id'
[42092] Failed to execute script 'OpenCore-Patcher' due to unhandled exception!

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
The just-now Nightly may have fixed this? 🧐
 
Hi Folks
this is my first post on here so be gentle
I have a 2009 mac4,1 flashed to 5,1 with 64gb ram, 2x 3.46 xeon processors and radeon rx580 8gb gpu
I have it currently running mojave but am trying to get it to run monterey, as I need to be able to use the latest version on lightroom
I have used the opencore 4.0 gui and run through and created an install disk on a USB drive, everything went smoothly until I tried holding down option to get to the boot screen, it will either just start up normally or will just hang on a black screen, what am i missing??
Many thanks
 
Stuck on Discord Captcha, while trying to sign up for the OpenCpre Patcher Paradise.
Does anyone know, how to fix this?
 
Hi Folks
this is my first post on here so be gentle
I have a 2009 mac4,1 flashed to 5,1 with 64gb ram, 2x 3.46 xeon processors and radeon rx580 8gb gpu
I have it currently running mojave but am trying to get it to run monterey, as I need to be able to use the latest version on lightroom
I have used the opencore 4.0 gui and run through and created an install disk on a USB drive, everything went smoothly until I tried holding down option to get to the boot screen, it will either just start up normally or will just hang on a black screen, what am i missing??
Many thanks
Do you have an EFI flashed RX580?
Do you have a boot screen with Mojave? If not flash your RX580 with a GOP vBIOS (read OpenCore docs how to do this).

If you have no EFI flashed GPU you can press alt/option on boot all day and night long, there is simply no such functionality to offer an EFI boot screen available.

Read the OCLP online docs!

- format the Monterey disk using APFS/GUID
- switch the Mac off
- pull all other disks except the Monterey and the Monterey USB and restart
- on boot select the installer and install Monterey, possibly reformat the APFS disk
- after finishing the installation and setup download OCLP again and run and install it your your internal SSD EFI Partition, pull the USB and reboot
 
Last edited:
Thanks to all the kind people who make this possible.
Fixing sleep would be nice.
Screenshot 2022-02-25 at 3.26.06 PM.png
 
Do you try to connect from an unknown computer or iphone?
If yes, you must first valid your connection from your email address OCPP.
Thanks for the tip, Jean_JD. I tried to register from scratch with a valid email, still can n o t get past the Captcha screen, which brings one Captcha after the other. The problem may lie with the Captcha service, not with discord. So, is there a way to circumvent this?
 
  • Like
Reactions: TimothyR734
Still waiting for the OCLP nightly fix for the graphics problem under 12.3b4 on non-metal macs, as per @hvds solution a few posts earlier here.

Q: Since 12.3b3, when I close the lid overnight on my MBP4,1, there is a kernel panic. Does anyone know of a solution?
 
  • Like
Reactions: TimothyR734
Just have put ASB's latest binaries for SkyLight, CoreDisplay, QuartzCore into my 12.3b4 installation, using Bigsurmountsrw - file save and upload work! Writing from this system. I guess will soon be part of OCLP 0.4.3.
Thanks for this tip hvds, I did follow your recipe (replacing SkyLight, SkyLightOld.dylib (?), CoreDisplay and QuartzCore Frameworks) on my MacBookPro4,1 with latest OCLP 0.4.3n and it works as well, what I recognized is that the combination of menu bar transparency and menu items shadows has a bit of a different look to it – not quite as nice as before. Maybe that can be fixed before integration of the patched versions into the coming OCLP?

Top image part is from 12.3Beta3, bottom one is 12.3Beta4 after replacing the Frameworks:

monte12.3Beta3vsBeta4-fixed-Frameworks.png
 
Thanks for this tip hvds, I did follow your recipe (replacing SkyLight, SkyLightOld.dylib (?), CoreDisplay and QuartzCore Frameworks) on my MacBookPro4,1 with latest OCLP 0.4.3n and it works as well, what I recognized is that the combination of menu bar transparency and menu items shadows has a bit of a different look to it – not quite as nice as before. Maybe that can be fixed before integration of the patched versions into the coming OCLP?

Top image part is from 12.3Beta3, bottom one is 12.3Beta4 after replacing the Frameworks:

View attachment 1964934
any chance you could go into more detail on how to apply this fix.
I saw it on discord a couple nights ago but not sure how to apply it.
I have not used Bigsurmountsrw before

thanks,
 
I also did use Bigsurmountsrw for the first time to do this. It is needed to temporarily work around the SSV (Sealed System Volume) protection. It does mount your System Volume as read/writable, so you can edit, move or replace files. When done with all changes, you switch back to the still running Bigsurmountsrw app, which then allows to finish the process by updating kernel caches and writing a new APFS snapshot in one go.

(This may not be a technically fully exact description, but for the most part that should be how it works)

The files to be replaced are located in:

/System/Library/Frameworks /System/LIbrary/PrivateFrameworks
 
Last edited:
I also did use Bigsurmountsrw for the first time to do this. It is needed to temporarily work around the SSV (Sealed System Volume) protection. It does mount your System Volume as read/writable, so you can edit, move or replace files. When done with all changes, you switch back to the still running Bigsurmountsrw app, which then allows to finish the process by updating kernel caches and writing a new APFS snapshot in one go.

(This may not be a technically fully exact description, but for the most part that should be how it works)

The files to be replaced are located in:

/System/Library/Frameworks /System/LIbrary/PrivateFrameworks
do you have to boot using a different install or can you patch it from within.
I tried within and it didn't find the OS
 
  • Like
Reactions: TimothyR734
I had a problem like yours with two of my family's five MacBook Pro 7,1 (mid 2010) when installing Catalina with the Dosdude1 patch. Based on this, I assumed that the problem was in hardware.
In fact, an MBP had faulty RAM and I only discovered it ONLY thanks to a free Utility that can be started from scratch, using a USB Key and which carries out a very thorough test.
It may be useful to know that the Timing of the new RAM (original Crucial) gives me 2-2-2-2 in System Information.
Since the RAM of the other identical MBP was instead good, I replaced the SSD disk (I had mount a Samsung) and after mounting an SSD Crucial the problem no longer arose.
So! Regarding the Memory Test utility, here I don't have the link and the instructions to create the USB Key; but if I find them in my work’s iMac I will send them to you. I think it create a (Linux?) Boot to start Macs without Operating System and in this way to be able to check all memory cells.
Important: if I had not installed Catalina with the Dosdude1 patch I would not have noticed either the faulty RAM of a Mac or the unsuitable SSD, in the other Mac... With the original Operating System (High Sierra), in fact, the two Macs they seemed to work fine. It could also happen in your case that Monterey fails, while Big Sur seems to be working well.
Thanks for your input. If this was the issue wouldn't I also have it when running Big Sur (last OS my Mac is entitled to)? I only have the full system crashes with OCLP and Monterray beta.
I'm still back on Big Sur at the mo and it runs perfectly.
 
  • Like
Reactions: TimothyR734
Thanks for this tip hvds, I did follow your recipe (replacing SkyLight, SkyLightOld.dylib (?), CoreDisplay and QuartzCore Frameworks) on my MacBookPro4,1 with latest OCLP 0.4.3n and it works as well, what I recognized is that the combination of menu bar transparency and menu items shadows has a bit of a different look to it – not quite as nice as before. Maybe that can be fixed before integration of the patched versions into the coming OCLP?

Top image part is from 12.3Beta3, bottom one is 12.3Beta4 after replacing the Frameworks:

View attachment 1964934
Thanks for you help, figured it out.
let the testing fun begin. Looks like I can save and upload again :)
 
I’ve restored SkyLightOld.dylib to the one from before the Frameworks replacement, now the menu bars transparency and shadows are back to normal (looking better). Image saving as JPEG, PNG, etc. from e. g. Preview app are still working.

1645883790876.png
 
Last edited:
I’ve restored SkyLightOld.dylib to the one from before the Frameworks replacement, now the menu bars transparency and shadows are back to normal (looking better). Image saving as JPEG, PNG, etc. from e. g. Preview app are still working.

View attachment 1965239
ASB🟢 as of Fri. nite did not know when and if these fixes will get into OCLP. fwiw
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.