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.
Hello all. I have a Mac 5,1 with 64 GB RAM, a Radeon 7950 , and two 27" LED Cinema displays. I have the two monitors attached to th 7950 by the mini-DP ports. My problem is I can only get one monitor working. Is there a tweek, a ,kext, or somehting I missed? Everything else is working fine.

One note, I didn't use OpenCore when I setup my Big Sur. I used one of he other patchers. Unfortunately I don;t remember which one. Would this possibly help?
I have the same Mac as you have, with the 7950 and two Cinema LED displays. So far, I’ve only installed Big Sur with OCLP on my Macbook Pro from 2012. I’ve been planning to install BS on my 5,1 si your post is of interest for me.

Does anyone else have trouble driving two monitors?

Willem
 
I have the same Mac as you have, with the 7950 and two Cinema LED displays. So far, I’ve only installed Big Sur with OCLP on my Macbook Pro from 2012. I’ve been planning to install BS on my 5,1 si your post is of interest for me.

Does anyone else have trouble driving two monitors?

Willem
I'm running Big Sur 11.2.3 on a Mac Pro 5,1 with an Nvidia GTX 680 and 2 DELL S2817Q Displays running at 3840x2160with no problem. I've been thinking of throwing my HD7970 in it just for grins. I'll report back if I do.
 
I have the same Mac as you have, with the 7950 and two Cinema LED displays. So far, I’ve only installed Big Sur with OCLP on my Macbook Pro from 2012. I’ve been planning to install BS on my 5,1 si your post is of interest for me.

Does anyone else have trouble driving two monitors?

Willem
#7,829
 
  • Like
Reactions: whgmkeller
I now installed Big Sur on my unsupported 2012 Air through OCLP which is working perfectly. As I understood, updates to future Big Sur versions through System Preferences should also work. Thanks for your efforts to make this work!
But just in case I want to go back to officially supported Catalina, can I just format the whole internal SSD and install Catalina or do I have to do stuff regarding EFI etc.?
 
Maybe I made a discovery.
Premise: does Photo Boot work in your Big Sur 11.2.3 with Opencore or Micropatcher?... I just found out that Photo Booth is not working properly in my << Late 2013 iMac i7 27 inch CPU and NVIDIA GeForce GTX 780M 4GB VRAM >>. (Note: my Big Sur installation, with Opencore Legacy Patcher is from scratch and not over Catalina or an old System).

My sudden doubt is that iMac 14,2 to 15,1 spoofing is not enough to activate all the original Big Sur features, contrary to what has been stated so far (!!!!). Maybe there are problems with Quartz and therefore it would be necessary to also patch the graphics of the iMac late 2013, inserting a special Kext or other?...

I explain the problem in detail and how I provisionally solved it, hoping to help @khronokernel and @Ausdauersportler solve it in an intelligent mode than me. Perhaps, behind the exclusion of late 2013 iMacs from official Big Sur support, there could also be an incompatibility of the graphics cards and not just the Fusion Drive (???).

ISSUE DESCRIPTION
1) Launch Photo Booth
2) The FaceTime HD camera (built-in) LED turns on, but the Photo Booth window appears black.
3) Taking a photo or starting a video, their creation works fine and the related preview icons appear, but the image of the HD FaceTime Camera (integrated) still does not appear on the screen.
4) ATTENTION, now! By clicking on "Effects" there are two effects that are active (I can see the previews with my image framed by the HD FaceTime Camera (integrated) and the two suggested effects.
5) So! If I select one of these effects now, my image taken by the HD FaceTime Camera (integrated) appears regularly in the video window of Photo Booth, obviously with the effect superimposed on me (birds or hearts surrounding my head).

HYPOTHESIS
All other Photo Booth's Quartz filters contained in /System/Library/Compositions/ are not accepted by Big Sur which perhaps sees a conflict with an officially unsupported graphics card.

FOLLOWS A MY PROVISIONAL SOLUTION which works in my case.
1) I make a copy of "Dizzy.qtz" effect contained in /System/Library/Compositions/ as it is one of only two working effects.
2) I have modified this effect, being in XML, using "Quartz Composer" (of Xcode Tools 11.4) and I experimented (casually) with cuts to the part concerning the birds that revolve around the head. I've been lucky!!!
3) So! I renamed "Dizzy.qtz" to "Normal.qtz"
4) I made a copy of Photo Booth which I called "Photo Booth my" and replaced the "Normal.qtz" file contained in Photo Boot me.app/Contents/Resources/Normal.qtz with the "Normal.qtz" file created by me.
5) Now my "Photo Booth my" opens showing normally my image taken normally and without overlay effects. Enjoy!

For those who want, I am attaching my "Normal.qtz" file. and if you don't want to create a copy of Photo Booth and use the file as explained above, put the file in the You_Home/Library/Compositions/ folder or in Macintosh HD/Library/Compositions/ (for all Mac users) and logout and log-in or restart your Mac.
In this case, starting the official Photo Booth app the black window will continue to appear; however, by clicking on Effects and scrolling through the pages, you will see the Normal filter with the image taken by the Facetime HD Camera (internal) without any effect on you. You can then select this normal effect and use it until a better solution than mine is found.

I hope there may be a more effective and radical solution that ALLOWS Photo Booth and therefore Big Sur to activate ALL other Quartz effects, as if it were an original iMac supported by Big Sur.

Khronokernel, Ausdauersportler and other talented friends, please help us, kindly :)
 

Attachments

  • Normal.qtz.zip
    2 KB · Views: 97
Last edited:
  • Like
Reactions: Ausdauersportler
I too have this, mainly in Safari but also with a few images in Photos.

I have patched Big Surbut the problem is quite recent.
 
Perhaps this world is the best of the worlds 👍OpenCore Legacy Patcher👏
AppleALC is excellent, sounds amazing in quality🔉
MacPro3,1 and MacBook7,1 downloaded InstallAssistant for macOS 11.3 20E5229a Beta 7 created a USB flash drive and installed it on top.
Thank you dosdude1, khronokernel, Ausdauersportler and authors developers, I only admire you🙌😊
Our favorite hobby gets even more interesting✨
 

Attachments

  • Screenshot 2021-04-12 at 20.24.34.png
    Screenshot 2021-04-12 at 20.24.34.png
    319.4 KB · Views: 114
  • Screenshot 2021-04-12 at 20.34.54.png
    Screenshot 2021-04-12 at 20.34.54.png
    217.3 KB · Views: 116
  • Снимок экрана 2021-04-12 в 23.09.30.png
    Снимок экрана 2021-04-12 в 23.09.30.png
    723.3 KB · Views: 118
I too have this, mainly in Safari but also with a few images in Photos.

I have patched Big Surbut the problem is quite recent.
Please add a signature to your account settings with your hardware and software. Since most installations of Big Sur were patched so far I do not get which patching tool you used before.

And the reference of your „I too have this....“ is not existing.
 
Maybe I made a discovery.
Premise: does Photo Boot work in your Big Sur 11.2.3 with Opencore or Micropatcher?... I just found out that Photo Booth is not working properly in my << Late 2013 iMac i7 27 inch CPU and NVIDIA GeForce GTX 780M 4GB VRAM >>. (Note: my Big Sur installation, with Opencore Legacy Patcher is from scratch and not over Catalina or an old System).

My sudden doubt is that iMac 14,2 to 15,1 spoofing is not enough to activate all the original Big Sur features, contrary to what has been stated so far (!!!!). Maybe there are problems with Quartz and therefore it would be necessary to also patch the graphics of the iMac late 2013, inserting a special Kext or other?...

I explain the problem in detail and how I provisionally solved it, hoping to help @Kronokornel and @Ausdauersportler solve it in an intelligent mode than me. Perhaps, behind the exclusion of late 2013 iMacs from official Big Sur support, there could also be an incompatibility of the graphics cards and not just the Fusion Drive (???).

ISSUE DESCRIPTION
1) Launch Photo Booth
2) The FaceTime HD camera (built-in) LED turns on, but the Photo Booth window appears black.
3) Taking a photo or starting a video, their creation works fine and the related preview icons appear, but the image of the HD FaceTime Camera (integrated) still does not appear on the screen.
4) ATTENTION, now! By clicking on "Effects" there are two effects that are active (I can see the previews with my image framed by the HD FaceTime Camera (integrated) and the two suggested effects.
5) So! If I select one of these effects now, my image taken by the HD FaceTime Camera (integrated) appears regularly in the video window of Photo Booth, obviously with the effect superimposed on me (birds or hearts surrounding my head).

HYPOTHESIS
All other Photo Booth's Quartz filters contained in /System/Library/Compositions/ are not accepted by Big Sur which perhaps sees a conflict with an officially unsupported graphics card.

FOLLOWS A MY PROVISIONAL SOLUTION which works in my case.
1) I make a copy of "Dizzy.qtz" effect contained in /System/Library/Compositions/ as it is one of only two working effects.
2) I have modified this effect, being in XML, using BBEdit and I experimented (casually) with cuts to the part concerning the birds that revolve around the head. I've been lucky!!!
3) So! I renamed "Dizzy.qtz" to "Normal.qtz"
4) I made a copy of Photo Booth which I called "Photo Booth my" and replaced the "Normal.qtz" file contained in Photo Boot me.app/Contents/Resources/Normal.qtz with the "Normal.qtz" file created by me.
5) Now my "Photo Booth my" opens showing normally my image taken normally and without overlay effects. Enjoy!

For those who want, I am attaching my "Normal.qtz" file. and if you don't want to create a copy of Photo Booth and use the file as explained above, put the file in the You_Home/Library/Compositions/ folder or in Macintosh HD/Library/Compositions/ (for all Mac users) and logout and log-in or restart your Mac.
In this case, starting the official Photo Booth app the black window will continue to appear; however, by clicking on Effects and scrolling through the pages, you will see the Normal filter with the image taken by the Facetime HD Camera (internal) without any effect on you. You can then select this normal effect and use it until a better solution than mine is found.

I hope there may be a more effective and radical solution that ALLOWS Photo Booth and therefore Big Sur to activate ALL other Quartz effects, as if it were an original iMac supported by Big Sur.

Kronokernel, Ausdauersportler and other talented friends, please help us, kindly :)
Long story short:

I do not own your system and so we have to rely on other users either confirming or denying your observation.

Please add just a signature to your account with the hardware, patcher revision, macOS software revision. You will not have to repeat this all the time, then.

Some questions:

You have really installed on a clean empty partition? (no update of a micropatched version)
You have a single OCLP (OpenCore) version installed on your internal EFI?
You have generated this for the right system (it should print the 14,2 when using OCLP on the top four lines)?

Photo Booth on 11.2.3 iMac 12,2 AMD WX4170 is working smoothly. And this is a machine/ssd never had a micropatched installation seen.
 
Last edited:
  • Like
Reactions: OKonnel
Long story short:

I do not own your system and so we have to rely on other users either conforming or denying your observation.

Please add just a signature to your account with the hardware, patcher revision, macOS software revision. You will not have to repeat this all the time, then.

Some questions:

You have really installed on a clean empty partition? (no update of a micropatched version)
You have a single OCLP (OpenCore) version installed on your internal EFI?
You have generated this for the right system (it should print the 14,2 when using OCLP on the top four lines)?

Photo Booth on 11.2.3 iMac 12,2 AMD WX4170 is working smoothly. And this is a machine/ssd never had a micropatched installation seen.
Photo Booth also works in my iMac 2010 booting from OCLP on SD to chain-boot an unpatched Big Sur 11.2.3 (that has installed over a Big Sur 11.2.3 patched by iMac Micropatcher previously).
 
I have exactly the same problem with "photo booth" as @OKonnel.
So we have two NVIDIA GPU systems from two users installed with Big Sur using two different patcher methods, i.e. OCLP and iMac micopatcher.

Hmm, I doubt this will be an SMBIOS problem. iMac micropatcher uses iMacPro1,1 while OCLP the iMac15,1.
 
A) Please add just a signature to your account with the hardware, patcher revision, macOS software revision. You will not have to repeat this all the time, then.
B) You have really installed on a clean empty partition? (no update of a micropatched version)
C) You have a single OCLP (OpenCore) version installed on your internal EFI? You have generated this for the right system (it should print the 14,2 when using OCLP on the top four lines)?
A) Thank you for your suggestion, @Ausdauersportler, I did it :)

B) Uhm... You make me think... Initially I created a single APFS partition on external SSD, named "MacIntosh HD" and installed Big Sur with Micropatcher 0.5.1. After verifying that Big Sur was working fine, I disassembled the iMac, inserted the SSD with Big Sur in place of Fusion Drive's mechanical HD and, of course, I doesn't recreated the Fusion Drive again. After mounting the SSD and rebuilding the iMac, so, Big Sur booted-up fast on the first power-on. [Of course, I see also the internal 128GB Apple SSD now on Desktop, which used to belong to Fusion Drive and I use it to store the Windows VM and other files.]

Later, if you remember, since I was missing Recovery Boot, Safe Boot, etc., thanks to you ;) I found the courage to switch from Micropatcher to OpenCore Legacy Patcher. So! I created an installation USB key (original and unpatched), I reinstalled Big Sur with OpenCore Legacy Patcher EFI (I believe 0.0.12) and since then I have replaced the EFI partition with latest OCLP Main Build, almost every day. Do you think that doing so did not overwrite all the Big Sur installed with Micropatcher and so I should reformat the SSD newly, then redo a new installation with OCLP, from scratch?

The mystery is that Photo Booth sees and uses only two Effects (Quartz) while does'nt sees all the other Quartz effects. Friends who have replied to my post so far have the NVIDIA 775M card while mine is the 780M. Could it be that Big Sur's KEXT does not enable something on my 780M card and therefore there is incompatibility with many Quartz effects? Do you thinks I can try to activate OpenCore Legacy Patcher option 5: "Force iMac Metal Patch" or I could try other options? (e.g.: non-minimal SMBIOS, etc.). Obviously I tried to copy all the files *.qtz of the Quartz effects from the System/Library/Compositions/ folder to the Compositions folder of MY_HOME/Library/Compositions or to /Library/Compositions/; I also tried to create a new User, I tried to reset SMC and PRAM, etc.

C) I have a single OCLP (OpenCore) version installed in the EFI partition of internal SSD, totally dedicated to Big Sur as an original Mac. However I mounted all EFI partitions and found that in EFI partition of the 128GB Apple SSD (empty, without OS) there was an EFI folder and a file called "BOOTLOG" of which I copy the text here. I am also attach a clip of this EFI Folder. I obviously deleted both (EFI and BOOTLOG) and restarted the Mac, but Photo Booth always behaves the same way. What do you see from this BOOTLOG? We hope to solve this the Quartz's mystery :)

Code:
SlingShot: Starting Local and Network Diags/Recovery Session at 03/12/2021  14:36.
SlingShotL8LocalBootSetup: Didnt find a recovery partition for startup disk, startup disk may not be set, (Not Found)
NetworkFinishOSRSHostInfoLookup: Resolved OSRS Hostname [osrecovery.apple.com] to 17.164.1.12, Port 80
GetStationAddressViaIpAgent: Client IP Address: 192.168.1.33
GetStationAddressViaIpAgent: Client Subnet Mask: 255.255.255.0
GetStationAddressViaIpAgent: Router IP Address: 192.168.1.1
GetStationAddressViaIpAgent: DnsServer 0 Address: 192.168.1.1
NetworkFinishOSRSHostInfoLookup: Resolved DNS Address on interface with address 192.168.1.33
NetworkFinishOSRSHostInfoLookup: Got 2 Network Interfaces.
NetworkFinishOSRSHostInfoLookup: Handle 0 was used for successful DNS resolution of OSRS.
SlingShot: Got OSRS Info: Hostname osrecovery.apple.com, Host IP 17.164.1.12, Port: 80
SlingShotSetupAuthParams: Got MLB SN 'C02412601ABCD3EFG' (Note that I modified SN for privacy)
SlingShotGetRecoveryType: Error getting RecoveryType (Not Found),
NetworkResolveDomainName: Resolved IP Address for 'oscdn.apple.com': 104.77.185.58
DownloadChunkedAsset: Downloading 48 chunks.
NetworkResolveDomainName: Resolved IP Address for 'oscdn.apple.com': 104.77.185.58
SlingShotUpdateProgressUI: 30 sec avg 24 KBps, 6625 KBps new total, last total 0 KBps, now 3312 KBps
SlingShotUpdateProgressUI: 30 sec avg 1495 KBps, 8342 KBps new total, last total 8488 KBps, now 8415 KBps
 

Attachments

  • EFI_Clip.jpg
    EFI_Clip.jpg
    104.2 KB · Views: 92
Last edited:
I have exactly the same problem with "photo booth" as @OKonnel.
Hi @traser! I see that you too have an Nvidia GTX 780M graphics card and an i7 CPU.
At this point I would say that my doubts about the incompatibility of many Quartz effects with the Nvidia GTX 780M are well founded and perhaps it could also depend on the i7 CPU that you and me have.

What do you think, @khronokernel and @Ausdauersportler ? Did we find a bug where your need to do some extra work? ;) Or could the problem be solved by varying the OCLP's options when creating the EFI build? Thanks for your help.

Note:
I specify that the graphics acceleration of the GTX 780M is recognized by Photoshop and also by the automatic setup of the VideoProc app and other video applications. Also, as I have already written, two Photo Booth effects work well and the effects become three if we consider the file "Normal.qtz" I created (by modifying "Dizzy.qtz") and attached before. It allows a copy of Photo Booth to function normally, following my instructions.
By the way, Traser! You can try my "Normal.qtz" and tell us if it works. I recommend that you use both methods that I explained to you in my first post and have fun.
 
Last edited:
  • Like
Reactions: traser
Hi @traser! I see that you too have an Nvidia GTX 780M graphics card and an i7 CPU.
At this point I would say that my doubts about the incompatibility of many Quartz effects with the Nvidia GTX 780M are well founded and perhaps it could also depend on the i7 CPU that you and me have.

What do you think, @khronokernel and @Ausdauersportler ? Did we find a bug where your need to do some extra work? ;) Or could the problem be solved by varying the OCLP's options when creating the EFI build? Thanks for your help.

Note:
I specify that the graphics acceleration of the GTX 780M is recognized by Photoshop and also by the automatic setup of the VideoProc app and other video applications. Also, as I have already written, two Photo Booth effects work well and the effects become three if we consider the file "Normal.qtz" I created (by modifying "Dizzy.qtz") and attached before. It allows a copy of Photo Booth to function normally, following my instructions.
By the way, Traser! You can try my "Normal.qtz" and tell us if it works. I recommend that you use both methods that I explained to you in my first post and have fun.
Sorry but I will surely not dig into this!

It is the third NVIDIA glitch reported here by different users. We have GUI problems, green and black blocks in the webkit Safari and now the Photo Booth. I owned two GTX780M my own and sold them because of the green black blocks visible with Safari on Catalina (the K2100M had the same problem) with or without OpenCore on @dosdude1 patched Mojave and Catalina systems.

The only common part in your systems it the NVIDIA GPU, your have different generation Intel CPUs. IMHO it is with 99.9% certainty no OpenCore problem. There is simply no evidence for this.

You may go back and create a micropatcher based Big Sur installation into a separate partition or onto an external USB connected disk and check Photo Booth on your system. This will give us more information for upcoming research.
 
Last edited:
  • Love
  • Like
Reactions: traser and OKonnel
Successfully OTA updated 11.2.3 to 11.3b7 on MBP5,2.

Was using 0.0.21 first for b6 and b7. Installation seemed fine both cases, but couldn't boot into updated BS. Did boot fine now with 0.0.22 (without repeating OTA installation).
Although already successful, exercised OCLP release 0.0.22 a bit further on MBP5,2.

All involved media on USB (stick with OCLP 0.0.22, 11.2.3 installer, SSD with two separate partitions for BS).

1) installed 11.2.3 with OCLP, over an existing 11.2.3 made a while ago with jackluke's BigSurFixes (option 3 of other patcher options in 1st post). That worked well, subsequent OTA update to 11.3b7 did install, but couldn't boot; as also suggested in the README of 0.0.22. But maybe I just wasn't patient enough.
Could not install 11.2.3 over it, neither with OCLP nor with BigSurFixes. Then erased this partition.

2) clean install of 11.2.3 with OCLP with full migration of data/apps from Catalina 10.15.7. Worked well, afterwards OTA update to 11.3b7. Installed well, subsequent booting apparently hang for >1hr. Rebooted via OCLP, came a bit further according to progress bar, but hang again. Proceeded to login the third time.
Internal audio working OK.

3) clean install of 11.2.3 with OCLP to the other partition without migration, works well, subsequent OTA to 11.3b7 installs well, hangs once during booting, proceeds to config screens 2nd time.

No graphics acceleration of course, and Monitor Panel of system settings incomplete.
Good that OCLP works so well nonetheless with the MBP5,2. THANKS!
 

Attachments

  • Bildschirmfoto 2021-04-12 um 16.38.54.png
    Bildschirmfoto 2021-04-12 um 16.38.54.png
    125.9 KB · Views: 160
  • Bildschirmfoto 2021-04-11 um 09.25.35.png
    Bildschirmfoto 2021-04-11 um 09.25.35.png
    88.3 KB · Views: 118
  • Bildschirmfoto 2021-04-12 um 16.37.51.png
    Bildschirmfoto 2021-04-12 um 16.37.51.png
    79.3 KB · Views: 114
  • Bildschirmfoto 2021-04-12 um 20.51.07.png
    Bildschirmfoto 2021-04-12 um 20.51.07.png
    62.8 KB · Views: 116
  • Bildschirmfoto 2021-04-11 um 09.31.08.png
    Bildschirmfoto 2021-04-11 um 09.31.08.png
    65.6 KB · Views: 120
  • Bildschirmfoto 2021-04-12 um 20.56.56.png
    Bildschirmfoto 2021-04-12 um 20.56.56.png
    51 KB · Views: 135
Last edited:
Updated to 11.3 beta (latest) using OCLP (0.0.22) without issue (I had issues with not writing the EFI update to internal drive thus needing the external USB, but once updated the OCLP config to the internal drive, all was well).

Has anyone else noticed that XProtect is disabled by chance?
~ ❯❯❯ spctl --status​
assessments disabled​

Even though SIP is still enabled?
~ ❯❯❯ csrutil status​
System Integrity Protection status: enabled.​

Not sure when XProtect went to disabled (I hadn't checked before upgrading with OCLP). If anyone has a way to enable this or build it into OCLP settings, that would be great.

I also checked if my volume was sealed which applies to the snapshot and that showed that it was.

Thank you in advance...
 
Updated to 11.3 beta (latest) using OCLP (0.0.22) without issue (I had issues with not writing the EFI update to internal drive thus needing the external USB, but once updated the OCLP config to the internal drive, all was well).

Has anyone else noticed that XProtect is disabled by chance?
~ ❯❯❯ spctl --status​
assessments disabled​

Even though SIP is still enabled?
~ ❯❯❯ csrutil status​
System Integrity Protection status: enabled.​

Not sure when XProtect went to disabled (I hadn't checked before upgrading with OCLP). If anyone has a way to enable this or build it into OCLP settings, that would be great.

I also checked if my volume was sealed which applies to the snapshot and that showed that it was.

Thank you in advance...
OCLP doesn't touch Gatekeeper in any way. If you have it disabled, you must have done it on your own.
SIP is completely independent of Gatekeeper and snapshotting is also independent of Gatekeeper.

You can reenable it fully with
Code:
spctl --master-enable
Or check Security & Privacy in System Preferences.
 
OCLP doesn't touch Gatekeeper in any way. If you have it disabled, you must have done it on your own.
SIP is completely independent of Gatekeeper and snapshotting is also independent of Gatekeeper.

You can reenable it fully with
Code:
spctl --master-enable
Or check Security & Privacy in System Preferences.
Even though I have install from anywhere, is this why?
1618264286575.png


Using SilentNight (https://eclecticlight.co/lockrattler-systhist/), KEXT is reported as being not in compliance -
1618265188643.png


Is this normal due to OCLP?
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.