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

[OneyedK]

About the wiki, in the maintenance section:
"To update OpenCore, simply repeat steps 2 and 5 of Part I"

I just did that and I also had to include step 3 (blessing the EFI volume).
Is this a step missing in the sentence above? Or did I goof up somewhere

Redid part II afterwards, everything running fine and dandy again...

 

[PowerPaw]

I've been experimenting with 0.6.3 and Big Sur over the weekend and generally pretty happy with what I'm seeing so far as we step closer to GA on this release however I just can't get NightShiftEnabler.kext to work or perhaps it just doesn't work for certain configurations. I was wondering if anyone could help.

1. I've placed the kernel dictionary entry after Lilu in the array in my config.plist
2. Tried this with Mojave
3. Tried this with Big Sur
4. Checked my config and I do actually have NightShiftEnabler.kext in my Kexts folder
5. Followed the documentation at the beginning of this thread
6. Read the readme.md in GitHub which suggests there are parameters unless these refer to the unmaintained version this replaces
7. Looked at any timezone settings that may not have been correctly set

Thanks

 

[cdf]

About the wiki, in the maintenance section:
"To update OpenCore, simply repeat steps 2 and 5 of Part I"

I just did that and I also had to include step 3 (blessing the EFI volume).
Is this a step missing in the sentence above? Or did I goof up somewhere

Redid part II afterwards, everything running fine and dandy again...

It shouldn't be necessary to rebless the EFI volume if you're just overwriting the old files. Did you reboot as indicated in step 5?

Moving forward, I plan on including better integration with @TECK's script to facilitate updates, especially for users with advanced configurations.

I've been experimenting with 0.6.3 and Big Sur over the weekend and generally pretty happy with what I'm seeing so far as we step closer to GA on this release however I just can't get NightShiftEnabler.kext to work or perhaps it just doesn't work for certain configurations. I was wondering if anyone could help.

Unfortunately, NightShiftEnabler does not currently work in Big Sur because Lilu userspace patching is broken.

 

[OneyedK]

Did you reboot as indicated in step 5?

Moving forward, I plan on including better integration with @TECK's script to facilitate updates, especially for users with advanced configurations.

Yep, sure did.

I have to look into the possibilities of that script. Upgrading the manual way is not hard, but it is time consuming.

 

[205Maxi]

All credit goes to cdf, he found the critical firmware feature ma

I can today confirm that we can have 256GB of ram 8x32GB. Running it in my Mac Pro ( see my signature )
Tomorrow I will try 512GB with 8x64GB. It should not be a problem though.
I have also ECC Registered sticks, and ECC shows enabled in the System Information.
I will tomorrow post pictures.

Y'all have a great Sunday.

 

[OneyedK]

Moving forward, I plan on including better integration with @TECK's script to facilitate updates, especially for users with advanced configurations.

I compared the result of the manual installation / config.plist following the wiki
and the one generated by @TECK's script.

Other than the fact that the script includes the ExFatDxeLegacy.efi, result is identical.

Personally, I'd keep the wiki as is, so people get a bit insight of what is happening.
Adapting the script to fit your own configuration, is another topic, imho...

This said, @TECK's script is awesome!

 

[joevt]

It shouldn't be necessary to rebless the EFI volume if you're just overwriting the old files.

True except if the file is on HFS+ or APFS partition and overwriting the old file gives a new file id. You can see the file id with the bless --volume --info command (finderinfo[1])
Maybe overwriting the old file uses the old file id - depends on the code for the overwrite.

bless --info /Volumes/rEFInd

finderinfo[0]:   9428 => Blessed System Folder is /Volumes/rEFInd/System/Library/CoreServices
finderinfo[1]:  11861 => Blessed System File is /Volumes/rEFInd/System/Library/CoreServices/boot.efi
finderinfo[2]:      0 => Open-folder linked list empty
finderinfo[3]:      0 => No alternate OS blessed file/folder
finderinfo[4]:      0 => Unused field unset
finderinfo[5]:   9428 => OS X blessed folder is /Volumes/rEFInd/System/Library/CoreServices
64-bit VSDB volume id:  0xDCC9E934FCEBB1D1

 

[PowerPaw]

It shouldn't be necessary to rebless the EFI volume if you're just overwriting the old files. Did you reboot as indicated in step 5?

Moving forward, I plan on including better integration with @TECK's script to facilitate updates, especially for users with advanced configurations.


Unfortunately, NightShiftEnabler does not currently work in Big Sur because Lilu userspace patching is broken.

Thanks for the feedback on Big Sur I suspected something might be up there but was puzzled over why I didn't see this with Mojave either. Maybe I need to recheck my Mojave setup with that in mind though I'm pretty sure the configurations are the same.

 

[naerct]

Now that 11.0 is imminent, I am curious about how this will work. I'm assuming Big Sur will need its own physical drive, and work, similar to the Catalina setup. I hardly ever use Mojave, except with certain expensive software, but I think Mojave must stay. ???

If I want to keep only two OS drives in the cMP, will one need to be Mojave?

If I can use 3 boot drives, can I use Mojave, Catalina, and Big Sur?

Since my clones of past OSs show up in the picker, once I get all the drives back in the drive bays, will a Catalina clone show up in the macOS 11 Opencore picker, and boot?

Thanks in advance for any help.

 

[h9826790]

Now that 11.0 is imminent, I am curious about how this will work. I'm assuming Big Sur will need its own physical drive, and work, similar to the Catalina setup. I hardly ever use Mojave, except with certain expensive software, but I think Mojave must stay. ???

If I want to keep only two OS drives in the cMP, will one need to be Mojave?

If I can use 3 boot drives, can I use Mojave, Catalina, and Big Sur?

Since my clones of past OSs show up in the picker, once I get all the drives back in the drive bays, will a Catalina clone show up in the macOS 11 Opencore picker, and boot?

Thanks in advance for any help.

You can keep whatever OS you want. However, at least on natively supported OS is preferable. But there is no need to keep that inside the cMP. You can keep that in your drawer, and only install that on the day you really need it.

Regardless clone or not, old or new. The boot picker always shows whatever OS it detects at that moment. And that’s OpenCore boot picker, not MacOS 11 boot picker.

 

[The Spirit]

i can not see the big sur release candidate while enabling vmm.
is there something else i have to do?
thanks

 

[RottenCotton]

Hi Everyone,

Sorry to bother you all again, last time for this project I promise. I am on the last step of the Windows install part of this guide and I just need one small bit of clarification to get this done.

I am on the very last section "Copy Boot Files"

You may need to authorize this. The volume should mount as /Volumes/EFI and appear as EFI in Finder. This EFI volume should be empty.

• Copy /USB/EFI/Microsoft to /Volumes/EFI/EFI
• Delete /USB/EFI and rename efi.bak to efi
• Eject the USB

As you can see in the screenshot below I have the EFI for Disk C mounted, it is completely empty, I also have in the screenshot the USB open and there you can see all the files.

My reading of the instructions are to copy over just the "Microsoft" folder from /USB/EFI to the EFI volume on Disk C if that's the case would I need to first create an EFI folder on the Disk C because right now I would be copying over the Microsoft folder to /volumes/EFI and not /Volumes/EFI/EFI as instructed.

The next item on the unordered list is to delete /USB/EFI and rename efi.bak to efi .... So I should delete the EFI folder on USB and rename the efi.bak folder to efi

then according to the instructions I should eject the USB

I think this section is to move over all the needed files/instructions that were on the USB to the Disk C EFI so I can complete Windows Install/Configure without needing USB.

I know I should follow the instructions as listed but it feels like I have misunderstood them since if I followed them the way I'm interpreting them I am just copying over the "Microsoft" folder only to the Disk C EFI volume. making a bunch of changes to the USB volume but then ejecting it and not using it to complete the windows configuration.

Would one of you that knows what is needed be able to give me this last bit of assistance?

 

[cdf]

My reading of the instructions are to copy over just the "Microsoft" folder from /USB/EFI to the EFI volume on Disk C if that's the case would I need to first create an EFI folder on the Disk C because right now I would be copying over the Microsoft folder to /volumes/EFI and not /Volumes/EFI/EFI as instructed.

Yes, you should create the EFI folder first.

The next item on the unordered list is to delete /USB/EFI and rename efi.bak to efi .... So I should delete the EFI folder on USB and rename the efi.bak folder to efi

The idea here is to restore the functionality of the USB installer (otherwise the USB will boot the installation rather than the installer; you don't want that).

 

[RottenCotton]

Yes, you should create the EFI folder first.


The idea here is to restore the functionality of the USB installer (otherwise the USB will boot the installation rather than the installer; you don't want that).

ok so I should just follow the instructions then and stop overthinking it LOL:

• create a EFI folder on Voumes/EFI so its Volumes/EFI/EFI and then copy just the Microsoft folder from USB/EFI/ to the Disk C EFI
• Make all the changes EFI.bak to just EFI and delete the prior EFI folder on the USB volume (that makes sense btw)
• But when I reboot to complete windows config I leave the USB ejected, so now its back to just being the installer right?

 

[RottenCotton]

Ohhh and Big Thanks BTW

 

[cdf]

But when I reboot to complete windows config I leave the USB ejected, so now its back to just being the installer right?

Correct. The USB, which is now back to being an installer for later use, should be removed from the computer. When you reboot, OpenCore will see the new files on the EFI volume, and you can complete the configuration.

 

[RottenCotton]

Ok so Good News, Bad News

Good News:

• I got Windows installed and up and running, so thanks for the guide and all the help

Bad News:

• The Weird Colour Vomit I reported in the Pre Boot and Boot Picker screens that went away once in Mac OS is always there for using Windows. I have an RX 580 and heard that if you switch modes it can fix the issue so I was planning on using the install disk that came with the VCard (which is windows only) to make that switch to see if I could fix the issue.
• Wifi and Bluetooth do not work in Windows. When I got this CMP I replaced the 10 year old Wifi and Bluetooth with a solution from OSXWifi. So I installed 802.11 AC and Bluetooth 4.2 and it works like a charm in Mac OS but I guess I need to purchase a new solution if I want Wifi and Bluetooth when in Windows?
  • Is that the case and if so any suggestions on what I should get to give me Wifi at least.... Ethernet hook up is difficult.

My plan is to get Wifi on Windows working, get the RX580 drivers and setup/mode switch completed which will hopefully take care of the colour vomit issue pre boot and everywhere in windows issues.

Anyway if any of you can confirm that I should expect my Apple Broadcom Wifi and Bluetooth cards to not work in Windows and suggest a wifi (and bluetooth although not as vital) solution that would be awesome.

 

[johnwillsey]

You should just need the drivers.. I did something similar months ago.. try this.. https://www.tonymacx86.com/threads/broadcom-wifi-bt-from-osxwifi-under-windows.208470/#post-1760298

 

[D34db33f]

Hi, I've been running OC 0.6.0 for some time successfully, booting a MacPro5,1 with a Radeon RX580 and dual X5960s into Mojave off a 500GB WD Black SN750 NVMe and a Sonnet USB-C 3.1 PCIe Card - everything works pretty much perfectly.

However, I installed Catalina successfully onto a second partition, and now whenever the system is put to sleep, the light at the front will pulse like it's going to sleep and _sometimes_ it'll actually 'click' and the fans will stop, but when it is woken up, 30-50 seconds pass with a black screen and eventually it returns to the boot menu having crashed.

I can't find any incling of what's going on the syslog so any help in diagnosing this would be appreciated.

I'm just in the process of upgrading to 10.15.7 having enabled the VMM flag.

UPDATE:

Some more info:

sudo pmset -g log | grep -i fail
2020-11-09 21:33:54 +0000 Failure                 Failure during wake: 0x00000027 : Some drivers failed to handle setPowerState panic
2020-11-09 22:00:25 +0000 Failure                 Failure during wake: 0x00000027 : Some drivers failed to handle setPowerState panic

On boot I was presented with the "report to apple" box which I had a dig through and noted that something on the firewire bus was at the beginning of the panic.
The only thing on the FireWire bus is a MOTU 828mk3 audio interface.

Turning this off before setting the mac to sleep appears to fix the issue, however it's obviously quite inconvinient, especially if I leave my mac accidentally with the audio interface turned on.

Any thoughts on how I can stop it from panicking?

 

[cdf]

Good News:

• I got Windows installed and up and running, so thanks for the guide and all the help

Great!

Bad News:

• The Weird Colour Vomit I reported in the Pre Boot and Boot Picker screens that went away once in Mac OS is always there for using Windows. I have an RX 580 and heard that if you switch modes it can fix the issue so I was planning on using the install disk that came with the VCard (which is windows only) to make that switch to see if I could fix the issue.
• Wifi and Bluetooth do not work in Windows. When I got this CMP I replaced the 10 year old Wifi and Bluetooth with a solution from OSXWifi. So I installed 802.11 AC and Bluetooth 4.2 and it works like a charm in Mac OS but I guess I need to purchase a new solution if I want Wifi and Bluetooth when in Windows?
  • Is that the case and if so any suggestions on what I should get to give me Wifi at least.... Ethernet hook up is difficult.

My plan is to get Wifi on Windows working, get the RX580 drivers and setup/mode switch completed which will hopefully take care of the colour vomit issue pre boot and everywhere in windows issues.

Anyway if any of you can confirm that I should expect my Apple Broadcom Wifi and Bluetooth cards to not work in Windows and suggest a wifi (and bluetooth although not as vital) solution that would be awesome.

The weird colors are still there probably because the AMD driver isn't installed yet. As mentioned by another poster, the Wi-Fi and and Bluetooth work perfectly with the right Broadcom drivers. You will also need the Realtek driver for the internal speaker.

 

[205Maxi]

Tried and Tested 64GB Modules and it did not work. Unless I have missed something.

So 256GB 32x8 is the maximum we can have in our MacPro here is a screenshot.

 

[wnlewis]

I have done all of the steps successfully except for making a mountable USB stick with the ISO.

Should I use a Windows PC and the Download Tool, or is downloading the ISO on a Mac OK?

Thanks for your help.

 

[cdf]

Should I use a Windows PC and the Download Tool, or is downloading the ISO on a Mac OK?

Downloading the ISO on a Mac should be fine.

 

[wnlewis]

OK. Done. Double clicked on the image and it mounted, as a disk image.

Now I want to "burn" it to the 32 Gb USB stick that I have set up as exFAT MBR.

Disk Utility doesn't seem to want to do that job.

Incidentally the Windows Disc Image name is ESD-ISO, not CCCOMA_x64.

 

[JeDiGM]

Tried and Tested 64GB Modules and it did not work. Unless I have missed something.

So 256GB 32x8 is the maximum we can have in our MacPro here is a screenshot.

View attachment 1620950

Hey 205Maxi. So you got 384GB working? That's perfect. It's a triple channel CPU anyway. Personally, I was never going to use 8x64 anyway. From the screenshot you sent it looks like that's the limit you are hitting? Is that the issue you mean or is it something else? Are you saying it doesn't work because it's not reporting properly in the RAM section?