MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[gradyg22]

How far did you get?
1. Use OpenCore boot picker to select Linux installer from USB [which variant of Linux?]
2. Linux installer starts okay
3. Install Linux using Linux installer [as recommended, just leave GRUB - or whatever your Linux's default bootloader is - do not unselect or disable it]
4. Reboot system
5. Newly installed Linux appears in OC picker
6. On selecting newly installed Linux, it starts and runs [I know it was not as far as this one]

Thanks for your response. It depends on the Distro. On PopOS, I could go through the installer, but it would freeze at the finishing up your machine stage. Force shutting down the machine and starting back up, I could see the new drive, but selecting it would bring just a grey screen. For Manjaro, the installer would finish all the way, and the machine would restart, I would see the new drive, but same grey screen.

 

[Gustav Holdoff]

Hi All, I started testing OC 0.7.7 with Monterey. AppleMCEReporterDisabler, which should be responsible for the correct operation of two processors, did not affect anything at all, the cMP works the same way with and without it
my question is: can anyone explain AppleMCEReporterDisabler kext at all works for monterey? maybe this one is outdated?
why do my cpu renders in CoronaRender benchmark take the same time as with and without it? although, when testing versions 0.5.9 with catalina a year and a half ago, there seemed to be a difference, if I remember correctly...
I follow the instructions very carefully and strictly, I turn everything on, as it is written, csrutil is disable, etc. MacPro 4.1/5.1, dual Xeon 5680, 96Gb samsung RAM, 1Tb nvme 970EvoPlus, USB3 pcie card, OC 0.7.7, MacOS Monterey

 

[startergo]

Hi All, I started testing OC 0.7.7 with Monterey. AppleMCEReporterDisabler, which should be responsible for the correct operation of two processors, did not affect anything at all, the cMP works the same way with and without it
my question is: can anyone explain AppleMCEReporterDisabler kext at all works for monterey? maybe this one is outdated?
why do my cpu renders in CoronaRender benchmark take the same time as with and without it? although, when testing versions 0.5.9 with catalina a year and a half ago, there seemed to be a difference, if I remember correctly...
I follow the instructions very carefully and strictly, I turn everything on, as it is written, csrutil is disable, etc. MacPro 4.1/5.1, dual Xeon 5680, 96Gb samsung RAM, 1Tb nvme 970EvoPlus, USB3 pcie card, OC 0.7.7, MacOS Monterey

It used to Kernel panicked without it at boot on dual CPU's. Maybe it has changed in Monterey?
I wonder if AppleMCEReporter.kext is still loaded?

 

[Gustav Holdoff]

It used to Kernel panicked without it at boot on dual CPU's. Maybe it has changed in Monterey?
I wonder if AppleMCEReporter.kext is still loaded?

it is strange that in my case there is no difference at all, there are no kernel panics, despite the fact that I tested with empty OC without kexts, and with kexts, but without HVAC, and a full one with hybridization. if you look at the github, then the kext was written in 2019, there is not even a discussion there except for 2019

 

[startergo]

it is strange that in my case there is no difference at all, there are no kernel panics, despite the fact that I tested with empty OC without kexts, and with kexts, but without HVAC, and a full one with hybridization. if you look at the github, then the kext was written in 2019, there is not even a discussion there except for 2019

It is a codeless kext. All it does is to disable AppleMCEReporter.kext at boot.
Check if AppleMCEReporter.kext is loaded.

 

[cdf]

can anyone explain AppleMCEReporterDisabler kext at all works for monterey? maybe this one is outdated?

It used to Kernel panicked without it at boot on dual CPU's. Maybe it has changed in Monterey?
I wonder if AppleMCEReporter.kext is still loaded?

It seems that AppleMCEReporterDisabler is no longer needed, at least for booting in macOS 12.1.

 

[paalb]

It is a codeless kext. All it does is to disable AppleMCEReporter.kext at boot.
Check if AppleMCEReporter.kext is loaded.

I did my upgrade to BigSur without AppleMCEReporter.kext All seemed well, but I discovered that it had rebooted some hours later. Maybe 5 hours, I do not remember exactly. After some more crashes, I guessed it was sleep that provoked it. I added AppleMCEReporter.kext and config code and the mac has been stable since.

 

[cdf]

I guessed it was sleep that provoked it.

You're right. It seems that while AppleMCEReporter no longer prevents a dual-socket machine from booting, it provokes a panic when entering sleep...

 

[prefuse07]

Man.... the more I keep seeing these posts about 12.1 and OC, the more I am inclined to try it... I generally like to wait for OS builds to be around the .3 or .4 stage (meaning more stability), but if Monterey is running that good on our machines already?

Also want to try 0.7.7, but I am afraid, as I was not able to get 0.7.6 working, even with Martin's package. Just kept getting black screens instead of the OC boot picker.

 

[splifingate]

Bootable volume renaming issue
I apologize if this has been addressed before, but I've been unable to locate the specific instruction to rename an EFI volume. As soon as it was released, I installed Big Sur on top of a secondary disk that used to have a vanilla version of Catalina, and the disk name or label was Catalina. After successfully upgrading it to Big Sur, I changed its name to "Big Sur", and that's the way the disk appears when Apple's Startup Manager kicks in. However, if I choose Boot EFI as the the startup disk (when I press Option at the chime), the Boot Picker displays that Big Sur disk as "Catalina". How can I remedy this?

Don't know if you have fixed your naming discrepancy (or if an approach similar to what I used has since been posited), but I was faced with almost the same (cosmetic?) issue.

Tried to use the items that @joevt has graciously shared to no success, thus have just left it alone.

After seeing a similar query on the '-monterey-on-unsupported-' thread--and searching for clues--I was successfully able to resolve the naming issue by directly refreshing the Preboot Volume with 'diskutil apfs' in my admin account (native tools; SIP Active; no need to enter Recovery).

% diskutil apfs updatePreboot /dev/diskXsY

See: https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-30777911

I have no idea if this holds parity with others' installations, but it definitely worked for me.

 

[Bmju]

Thanks for your response. It depends on the Distro. On PopOS, I could go through the installer, but it would freeze at the finishing up your machine stage. Force shutting down the machine and starting back up, I could see the new drive, but selecting it would bring just a grey screen. For Manjaro, the installer would finish all the way, and the machine would restart, I would see the new drive, but same grey screen.

Okay, next q, are you doing all of this via OpenCore? i.e. for Linux it is always possible to install booting not via OpenCore (although it's certainly harder on machine without a native bootpicker).

 

[Scansterz]

Is this in your browser - or are you using VLC or......
What file types?
If you right click on a file that won't play and then go GET INFO what is the Open with?

View attachment 1941337

Here's the update on this issue. I found out when choosing my audio interface - Firewire Safire Pro 40 - NOTHING plays, it's all stuck. Choose internal spkr, or hdmi to monitor files play. So it's the Firewire interface that is not working and stops Big Sur from even starting playback.

Can we solve that?
It is recognized, it show up on System Report and Control panel sees it so we can choose it as our audio out/in...
So if we could solve the prob with BigSure, cool.
It all runs fine in Catalina.

I've also tested Thunderbolt interface; Presonus Quantum in Catalina it runs just fine - in Big Sure it stutters but it is recognized and you can choose it in the sound control panel.

Solve that and I'd buy beers!

kerbs

 

[Fastsavage]

Solve that and I'd buy beers!

Some stuff here about firewire audio devices

Check out the posts

OpenCore on the Mac Pro

What interface do you have, FireWire or USB? I have the same problem in BigSur connected via the FireWire port (I did not test yet via USB connection). In Catalina it was fine above 48kHz with my RME Fireface UFX audio interface. Using samplerate beyond 48kHz playing audio thru system or via...

forums.macrumors.com

 

[kkinto]

I was reading (on facebook I think) that latest OCLP enable BT and Wifi in Moneterey 12.1 on cMP 5,1 with factory broadcom card. If this is in fact true, surely this can be done with the config and OC install as per this thread and Martin Lo's (which I mainly use). Does anyone know any more about this - and how to achieve?
Thanks

 

[Gustav Holdoff]

Man.... the more I keep seeing these posts about 12.1 and OC, the more I am inclined to try it... I generally like to wait for OS builds to be around the .3 or .4 stage (meaning more stability), but if Monterey is running that good on our machines already?

Also want to try 0.7.7, but I am afraid, as I was not able to get 0.7.6 working, even with Martin's package. Just kept getting black screens instead of the OC boot picker.

About the work of AMD 5700-5700XT with MacOs there are a lot of negative reviews in the community. I can tell what problems I encountered and how I solved them
1. I noticed that on my card only one port shows the bootscreen, the rest of the ports are enabled only after the system boots. I often work on multiple monitors, so I set up my main and extended monitors. now I always see OС bootscreen
2. on my second cMP I use a rather old Sony TV as a display, it only supports 720p at a frequency of 50Hz - (any other settings cause a black screen). On one of the outputs of the video card, I see a boot option and a boot logo, but how Monterey 12.1 is loaded - there is a black screen on all outputs - I found out that Monterey for some reason sets it to 25 or 30 Hz and it is clear that the monitor does not work in this mode - this problem was not on bigsur) I solved this problem: I connect the display via simple HDMI switch 3 to 1- it gives correct settings for SONY - 720p 50Hz
3. there are many posts about the black screen with Martin Lo's config, but Martin gave a treatment for this problem
Martin posted:
"Once you upgraded to Big Sur, you may find that some of the ports are disabled on your graphic card.
If that happens, you may follow the steps in this video to re-gain multi monitors support.
For your reference, the number you need to search in the config plist is 7BA5B2D9E42DDD94, you should replace that by 27AD2F918AE68F61
N.B. Once you perform this mod. HWAccel will be disabled in Mojave.
If you want to install my OpenCore package (for Mac Pro 5,1), please click the following link, read that post, and follow the instruction at there."
MY COMMENTS: I only encountered this problem on some later versions - I don’t remember exactly, but probably 7.4 or 7.5 - and Martin’s recommendation worked for me on BigSur, but when I tried to do this trick on Monterey - cMP did not load - it means: on Monterey can't do this trick
MacPro 4.1/5.1, dual xeon 5680, 96Gb samsung RAM, 1Tb nvme 970EvoPlus, USB3 pcie card, OC 0.7.7, MacOS Monterey- MacPro 4.1/5.1, single xeon 5680, 32Gb samsung RAM, 1Tb nvme 970EvoPlus, USB3 pcie card, OC 0.7.7, MacOS Monterey

 

[DigitaLife]

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

View attachment 1899553

How can I upgrade to Windows 11 from Windows 10 (already installed according to the guide in post #1 - OC 0.7.6 Martin Lo package)?
I tried to upgrade from Win 10 settings but I get the message that the hardware is not compatible! Thanks a lot in advance for any suggestions!

 

[PeterHolbrook]

How can I upgrade to Windows 11 from Windows 10 (already installed according to the guide in post #1 - OC 0.7.6 Martin Lo package)?
I tried to upgrade from Win 10 settings but I get the message that the hardware is not compatible!

You need to download Windows 10 AND Windows 11 installers from Microsoft. Prepare an exFAT USB bootable pen drive with the Windows 11 installer. Rename the file appraisers.dll in the Windows 11 /sources folder to something like _appraisers.dll. Copy the file appraisers.dll in the Windows 10 /sources folder and paste it in the same folder of the Windows 11 installer. Now, follow @cdf's tutorial. Everything should work.

 

[DigitaLife]

You need to download Windows 10 AND Windows 11 installers from Microsoft. Prepare an exFAT USB bootable pen drive with the Windows 11 installer. Rename the file appraisers.dll in the Windows 11 /sources folder to something like _appraisers.dll. Copy the file appraisers.dll in the Windows 10 /sources folder and paste it in the same folder of the Windows 11 installer. Now, follow @cdf's tutorial. Everything should work.

Thanks!
So does this mean that it is not possible to do an update but a new installation is required?

 

[PeterHolbrook]

You can easily update a 64-bit version of Windows 10 to its Windows 11 counterpart. If you follow @cdf’s tutorial and respond coherently to all relevant prompts, the installer will carry out the update for you.

 

[Bmju]

For anyone who remembers back to the discussion about the value for csr-active-config that OpenCore was using when requested to disable SIP, and in particular to the confusion about whether bit 0x10 (CSR_ALLOW_APPLE_INTERNAL) did or did not break updates, there is some news: thanks to the persistence @startergo, a bug in OpenCore has finally been tracked down, which was actually the cause of the 0x10 bit behaving differently on most hacks to most Macs. It is fixed in: https://github.com/acidanthera/OpenCorePkg/commit/d51442406cb738a8db904ccfbfa0ef78569b03bc

This now means that 0x7F will behave the same on Macs and hacks (as in fact it should have done all along), and also that csrutil disable (with its standard value of 0x7F) and csrutil enable (with its standard value of 0x10) behave as expected on all systems (and in particular, do not break updates). csrutil clear may still be used as an alternative to csrutil enable, but it is not required. (This is info for anyone who was following this back then, as much as anything, since on Mac Pros and on any Macs there was no problem and things behaved fine with either 0x6F or 0x7F anyway.)

Also a reminder, if you want to enable or disable SIP much more quickly than entering Recovery (disabling SIP is for occasional use only, if/when you understand what you are doing and really need it - it is NOT recommended to run with SIP disabled normally) as of version 0.7.0 you can use OpenCore's AllowToggleSip config option, and/or the OpenCore CsrUtil.efi tool - see documentation.

 

[prefuse07]

About the work of AMD 5700-5700XT with MacOs there are a lot of negative reviews in the community. I can tell what problems I encountered and how I solved them
1. I noticed that on my card only one port shows the bootscreen, the rest of the ports are enabled only after the system boots. I often work on multiple monitors, so I set up my main and extended monitors. now I always see OС bootscreen
2. on my second cMP I use a rather old Sony TV as a display, it only supports 720p at a frequency of 50Hz - (any other settings cause a black screen). On one of the outputs of the video card, I see a boot option and a boot logo, but how Monterey 12.1 is loaded - there is a black screen on all outputs - I found out that Monterey for some reason sets it to 25 or 30 Hz and it is clear that the monitor does not work in this mode - this problem was not on bigsur) I solved this problem: I connect the display via simple HDMI switch 3 to 1- it gives correct settings for SONY - 720p 50Hz
3. there are many posts about the black screen with Martin Lo's config, but Martin gave a treatment for this problem
Martin posted:
"Once you upgraded to Big Sur, you may find that some of the ports are disabled on your graphic card.
If that happens, you may follow the steps in this video to re-gain multi monitors support.
For your reference, the number you need to search in the config plist is 7BA5B2D9E42DDD94, you should replace that by 27AD2F918AE68F61
N.B. Once you perform this mod. HWAccel will be disabled in Mojave.
If you want to install my OpenCore package (for Mac Pro 5,1), please click the following link, read that post, and follow the instruction at there."
MY COMMENTS: I only encountered this problem on some later versions - I don’t remember exactly, but probably 7.4 or 7.5 - and Martin’s recommendation worked for me on BigSur, but when I tried to do this trick on Monterey - cMP did not load - it means: on Monterey can't do this trick
MacPro 4.1/5.1, dual xeon 5680, 96Gb samsung RAM, 1Tb nvme 970EvoPlus, USB3 pcie card, OC 0.7.7, MacOS Monterey- MacPro 4.1/5.1, single xeon 5680, 32Gb samsung RAM, 1Tb nvme 970EvoPlus, USB3 pcie card, OC 0.7.7, MacOS Monterey

Unfortunately, I am already using the Mac Pro 7,1's Board ID (Mac-27AD2F918AE68F61), and I also tried spoofing the iMac Pro's (Mac-7BA5B2D9E42DDD94) to see if it fixed anything, but it doesn't make a difference. Still get a total black screen with 0.7.6 -- but since 0.7.7 is out, I am working on a config for that. I see that there are already some differences between 0.7.7 and 0.7.6, so hopefully 0.7.7 works fine! *fingers crossed

I'm also suffering from the sleep bug. No KPs yet (thankfully), but my cMP does come back from sleep after a few minutes randomly, and it's really irritating -- so seeing some posts that Monterey fixes that is great news!

How can I upgrade to Windows 11 from Windows 10 (already installed according to the guide in post #1 - OC 0.7.6 Martin Lo package)?
I tried to upgrade from Win 10 settings but I get the message that the hardware is not compatible! Thanks a lot in advance for any suggestions!

@DigitaLife Check this out

 

[Bmju]

Thanks for your response. It depends on the Distro. On PopOS, I could go through the installer, but it would freeze at the finishing up your machine stage. Force shutting down the machine and starting back up, I could see the new drive, but selecting it would bring just a grey screen. For Manjaro, the installer would finish all the way, and the machine would restart, I would see the new drive, but same grey screen.

Also, just to check, did you try leaving PopOS for a long time - like say overnight - just to make sure that it would not eventually finish finishing up?

 

[kkinto]

Hi. I seem to be unable to boot without having the VMM set to on (the 'C' added instead of A). I was under the impression that after installing it can be switched off again, and should be. But that lands me in a "boot loop" which is only cleared by putting that C back in the config. Other than haveing "UIscale" = 2 there are no other changes in the config. Is this normal?

 

[cdf]

Hi. I seem to be unable to boot without having the VMM set to on (the 'C' added instead of A). I was under the impression that after installing it can be switched off again, and should be. But that lands me in a "boot loop" which is only cleared by putting that C back in the config. Other than haveing "UIscale" = 2 there are no other changes in the config. Is this normal?

If you want, post your config, so that we can take a look. With the proper settings, VMM is now only really necessary for macOS Catalina, which more aggressively blocks MacPro5,1.

 

[quiff]

I've followed the original guide and I now have a working system. both Big Sur and Windows 11.
What I would like to do now is enable HDMI Audio for the GTX 680.
I had previously used the example on post 1314 this did work. But I don't know how to apply it to my new config.

Also has anyone found a way to enable the DP port on this card?
Thanks Matt