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

[BillLee]

您在“：”和“ opencore-version”之间留有一个空格。删除空间，它应该可以工作。

Haha ,cuz no space in MacRumors will become a emoji. I type in Terminal is right.

 

[PeterHolbrook]

On a Mac Pro 5,1 currently running Catalina and with updated BT hardware, has anyone actually installed the latest release of Big Sur, either from scratch or on top of Catalina, just using OC 0.6.3 with VMM, spoofing et cetera? I mean WITHOUT patching the installer in any way? If so, would this be the recommended way to update, or are there better options (for instance, in order to have Night Shift)? If patching the installer is deemed unnecessary, are there any post-install patches or processes one can run in order to solve minor issues like Night Shift?

 

[toke lahti]

Which is better with MP5,1(was4,1) to use win10 with separate drive:

#1
Install win10 in legacy mode
(And how to do that?)

#2
Install OpenCore and then install win10 in EFI mode

Why? What are the benefits of EFI mode compared to legacy mode?

 

[cdf]

On a Mac Pro 5,1 currently running Catalina and with updated BT hardware, has anyone actually installed the latest release of Big Sur, either from scratch or on top of Catalina, just using OC 0.6.3 with VMM, spoofing et cetera? I mean WITHOUT patching the installer in any way? If so, would this be the recommended way to update, or are there better options (for instance, in order to have Night Shift)? If patching the installer is deemed unnecessary, are there any post-install patches or processes one can run in order to solve minor issues like Night Shift?

I can confirm doing a clean install of 11.0.1 beta by adding the necessary firmware features bit. See post #4,399. No VMM flag necessary. The installer was not patched in any way. I later updated to RC 1 through Software Update. Again, without VMM. I expected the same approach will work for today's release of Big Sur.

Getting Night Shift and DRM to work in Big Sur is another story: I will be looking into full MacPro7,1 spoofing for that.

 

[cdf]

Just wondering since I don't think I ever saw an answer, but I have OC 0.6.3 and have been running OC with a base config for some time now on a native Mojave install. To update the machine to Catalina, is it necessary to have a whole other drive configured for the purpose as stated or can Mojave be upgraded by toggling the respective flags in OC? Seems a little basic, but Id rather not go about restoring backups from one drive to another since Catalina would be the daily driver anyway. Thanks in advance and if this has been answered, feel free to point it out.

You can update Mojave. However, it is strongly recommended to have a Mojave installation on hand as a fall back when booting outside of OpenCore.

 

[cdf]

Big Sur will be officially released on Nov 12, what do we need to do to upgrade? @cdf if possible please provide also instructions for an USB stick Big Sur clean install. I will want to start everything fresh, with such major OS change.

I would recommend getting the full installer using installinstallmacos (or gibMacOS) and doing a clean install from Mojave or Catalina to a freshly formatted drive. If you've already enabled hybridization, the only OpenCore configuration step should be adding the firmware features bit. See post #4,399.

 

[toke lahti]

Should it be included in the #1 (wiki) post, that OpenCore only supports EFI installation of windows...?

 

[PeterHolbrook]

Should it be included in the #1 (wiki) post, that OpenCore only supports EFI installation of windows...?

It already says so, doesn't it?

 

[205Maxi]

256GB runs at 800mhz?

I assume it would. I had 16GB modules of 800MHz and the system was showing 800MHz.

 

[ScrumpyDaniel]

I assume it would. I had 16GB modules of 800MHz and the system was showing 800MHz.

Could you show what settings you've put in the memory spoofing to get the 32GB modules to work?

 

[JeDiGM]

I will do that, ASAP but I can tell you that it ran the 128GB 4x32GB. Guarantied!

I only use SK Hynix R10600 but I am pretty sure that we could have a higher speed like 1867MHz or above... I will test that and report here...

Hey 205Maxi. Do you have the model number of the RAM you tested? Also, did you hit a wall at 1333MHz?

 

[Paolo-Sp]

In PART I Basic Installation - 3 First Boot, terminal command to reboot into recovery "sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery", not work with OC 0.63 and Big Sur.
For reboot into recovery, need restar Mac and in OC start display, bust space-bar and select recovery partition from menu.

 

[205Maxi]

Hey 205Maxi. Do you have the model number of the RAM you tested? Also, did you hit a wall at 1333MHz?

Here is what you guys need.. PC3-10600R DDR3 4Rx4 Server Memory. I went with SK Hynix brand.

 

[205Maxi]

Hey 205Maxi. Do you have the model number of the RAM you tested? Also, did you hit a wall at 1333MHz?

DDR3 at 1333MHz is as far as you can go on these due to FSB limitations.

 

[JeDiGM]

Here is what you guys need.. PC3-10600R DDR3 4Rx4 Server Memory. I went with SK Hynix brand.

Do you have the model number? Shopping.

 

[205Maxi]

This is what I run in my MacPro have a look here too #4,648

For the memory config I followed the Apple MacPro 2019 scheme -> https://support.apple.com/en-us/HT210103

8 DIMMs is the one we need, note still shows 12 slots. I have configured it on 12 slots scheme because I did not want to see the notification, which as no incidence whatsoever. You would put 1.5TB memory config that it would not change anything.

However when I tried the set the 8 slots according to the supported configuration I would get the error notification. So I reverted back to 12 slots configuration even though we only have 8 slots and the error's gone.

I guess that in the near future if IOIIIO works on the kext notification disabler, that we can properly set the memory config to reflect the true memory configuration of our MacPro5,1.

I preferred to set it that way so 1 less .kext in the driver folder.


I would love to have it configured this way which reflect the true config but then you get error and orange check, which I don't like

 

[abaxworld]

On a Mac Pro 5,1 currently running Catalina and with updated BT hardware, has anyone actually installed the latest release of Big Sur, either from scratch or on top of Catalina, just using OC 0.6.3 with VMM, spoofing et cetera? I mean WITHOUT patching the installer in any way? If so, would this be the recommended way to update, or are there better options (for instance, in order to have Night Shift)? If patching the installer is deemed unnecessary, are there any post-install patches or processes one can run in order to solve minor issues like Night Shift?

Hi, I did it just installing OC 0.6.3 replacing a previous 0.6.1 version I had. Both upgrading from Catalina and doing a fresh install. So it works "out of the box" without patching ( at least for me, in my MacPro 4.1 with 5.1 firmware updated years ago ).

 

[mike.101]

I successfully installed the beta of macOS Big Sur 11.0.1 by spoofing only the board product and changing only a single bit of the firmware features:

<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
</dict>

By default, the firmware features of the Mac Pro 5,1 are set to A1QMwA==. For some reason, the changed bit fixes the "Your Mac needs a firmware update in order to install to this volume..." issue. (Interestingly, this bit has been documented as the one for enabling proper UEFI bootability for Windows...)

Unfortunately, Lilu userspace patching is broken in Big Sur, so no Night Shift or DRM without more spoofing. If Lilu patching is not fixed, we'll have to seriously consider properly changing model and generating serials to regain proper functionality...

Where in your config.plist does this bit go?

 

[h9826790]

As per cdf's expectation, we can get / install / update to Big Sur (official release) "natively" with that firmware feature mask

 

[johnwillsey]

extra confirmation... I just did a fresh install (not upgrade) just a few min ago.. worked flawlessly.

 

[naerct]

As per cdf's expectation, we can get / install / update to Big Sur (official release) "natively" with that firmware feature mask
View attachment 1661394
View attachment 1661395

Something looks wrong there. It says you are going to get 12+GB downloaded in less than 2 minutes??? Here's what I got:

Sad to say my connection is that much slower. ???

 

[watkipet]

It already says so, doesn't it?

If it does, I can't find it. It says to use the GUID partition scheme--but that doesn't necessarily imply GPT with a protective MBR instead of the hybrid GPT MBR that the Bootcamp Assistant creates (that was why I couldn't boot Windows 10--I had to convert to pure GPT).

 

[watkipet]

I'm having trouble installing Windows 10 according to these instructions. I've installed OpenCore--and it works fine. Since I have a Nehalem processor, I haven't enabled VMM:

Machine:~ username$ sudo gpt -r show /dev/disk0
Password:
gpt show: /dev/disk0: Suspicious MBR at sector 0
       start        size  index  contents
           0           1         MBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6     
          40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      409640  1374945080      2  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
  1375354720         160     
  1375354880   499767296      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  1875122176      262799     
  1875384975          32         Sec GPT table
  1875385007           1         Sec GPT header

"Suspicious MBR at sector 0" was the smoking gun. I had created my Windows partition with Bootcamp Assistant and it had made my drive use a hybrid MBR GPT partition scheme. Once I changed the partition scheme to GPT with a protective MBR, Windows would attempt to boot. I had to run the bcdboot command in the appendix again and copy the Microsoft EFI directory since the first bcdboot I ran probably made a bad BCD file due to it thinking it was on an MBR partition.

To convert from Hybrid MBR / GPT to pure GPT, I installed gdisk via MacPorts, launched it against my disk, went to the extras menu (x), issued the (n) command, then the (w) command, and then rebooted immediately.

 

[Enricote]

Something looks wrong there. It says you are going to get 12+GB downloaded in less than 2 minutes??? Here's what I got:

Sad to say my connection is that much slower. ???

Servers seem to be super busy to download Big Sur at the moment:

 

[h9826790]

Something looks wrong there. It says you are going to get 12+GB downloaded in less than 2 minutes??? Here's what I got:

Sad to say my connection is that much slower. ???

I have 1Gbps internet connection. And Apple server can provide 100MB/s download when not busy. So, 12000/100 = 120s, which is 2 minutes.

Anyway, most likely there are millions of people downloading at the same time. It's expected to be very slow now.