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

[nos1609]

What NVMe M.2 blade? This firmware update message is usually a signal that the NVMe blade is incompatible with macOS, several incompatible blades do that like WD Blue SN550.

Have a 10.15.3 running on SN550 my xps 3360 just fine and catalina install passed with no issues. By the way first thing done was 4k lba switch. The xserve 5.1 is running with no issues from both SN750 and SN500. No issues during install and no issues with operation.
So nothing more than 4k format and configuration issue there, no reason to blame the ssd for mulfunction.

 

[tsialex]

Have a 10.15.3 running on SN550 my xps 3360 just fine and catalina install passed with no issues. By the way first thing done was 4k lba switch. The xserve 5.1 is running with no issues from both SN750 and SN500. No issues during install and no issues with operation.
So nothing more than 4k format and configuration issue there, no reason to blame the ssd for mulfunction.

Changing a blade sectorization from 512 bytes per sector to 4K is a non standard operation that no user is expected to do.

If WD Blue SN550 just need this for correctly working with a Mac running macOS, nice to know - thx, but the non-compatible blade still stands until a firmware update resolves the issue.

 

[Sharky II]

Hi guys,

When I try to run 'Bless OpenCore', after I put in my password, I get the following error.

Any ideas? Specs and SIP status shown in the picture too. I'm running an AHCI SM951 Samsung boot drive.

So far I've just unmounted the EFI partition to try to 'put everything back' before proceeding any further

Thanks,

Ed

 

[h9826790]

Hi guys,

When I try to run 'Bless OpenCore', after I put in my password, I get the following error.

Any ideas? Specs and SIP status shown in the picture too. I'm running an AHCI SM951 Samsung boot drive.

So far I've just unmounted the EFI partition to try to 'put everything back' before proceeding any further

Thanks,

Ed

Are you sure the OC folder is inside the EFI "folder", but not the EFI partition's root?

 

[Earl Urley]

I ran into this exact error.. if the volume /EFI has nothing in it, as was the case with my Mojave SSD, you have to create a new folder at the root of /EFI called "EFI" and then drag the OC folder into that folder. The script won't work if there's nothing at:

/Volumes/EFI/EFI/OC

That means you have to mount it again with Clover Configurator if you unmounted it.

Creating the folder with the New Folder command in Finder seems to work just fine.

Using h9826790's prepackaged config file mentioned in the acceleration thread was a breeze and delivered everything promised.

I was able to get a boot screen for an unflashed Nvidia GTX 770!

 

[Sharky II]

Thank you guys! I just needed to create the EFI folder. It was very late for me

@h9826790 - thank you so much for your continued hard work on this. Showing the PCIe drives as internal, the hardware decode and the boot screens are incredible to have. Thank you!

I currently have all the updates for 10.14.6 but will be sure to check in here before installing any more!

 

[joot]

Anybody know why I can select anything on the bootpicker screen? I see the menu screen and an asterisk in front of the default boot drive but I can't make a selection at all. Arrow keys don't work, pressing the numbers don't work either. This is a wired keyboard.

 

[JeDiGM]

Anyone have handoff and continuity working in Catalina?

Tried:
sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

No joy. Was working in Mojave.

I have HWAccel enabled from h9826790 https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/

 

[h9826790]

Anyone have handoff and continuity working in Catalina?

Tried:
sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

No joy. Was working in Mojave.

I have HWAccel enabled from h9826790 https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/

Try CAT

 

[JeDiGM]

Try CAT

Nothing here. You?
[automerge]1583361790[/automerge]
Diagnostics show:
Verifying Mac board-id... NOT OK. Board id length is not compatible. Expected 12 or 20 characters. Board id:Mac-7BA5B2D9E42DDD94
board-id

Is there a way to make hardware acceleration work without

<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
</dict>

? This injection seems to be causing issues.

 

[Itconnects]

Is it still not recommended for EFI windows install?

OC is mysteriously disabled after using Windows (legacy) bootcamp control panel to boot back into Mac (which didn’t work). I had to shut down. After restarting OC menu no longer there. Drives are displaying “external” in MacOs

 

[Sharky II]

Also noticed that my X5690 CPUs now show as 3.5GHz... which is a nice psychological boost

 

[startergo]

OC is mysteriously disabled after using Windows (legacy)

OC does not support Windows in legacy mode only UEFI.

 

[Itconnects]

OC does not support Windows in legacy mode only UEFI.

That is understood, but I didn’t read anything where simply booting into Windows legacy disables OC indefinitely

On another note. I have my Rom Dump. I don’t know how to read a bin file. If this is the case I would like to see if windows EFI solves this, and also looking for a little more clarity

 

[Objectivist-C]

My current config is Catalina on an NVMe blade, Mojave on a hard drive, and legacy-mode Windows 10 on a SATA SSD. Would the recent developments in bootscreen support let me set up FileVault on the NVMe? I’m guessing I’d have to convert the Windows install to EFI, but doesn’t that come with bootrom risks?

Also, does OpenCore work for installing Catalina on other old Mac models, e.g. a 2010 MBP?

 

[startergo]

I didn’t read anything where simply booting into Windows legacy disables OC indefinitely

How did you get to Windows?

I have my Rom Dump. I don’t know how to read a bin file

Depends. Hex Fiend (Insert, delete, rearrange) watch out for CRC32 checksums if you change anything with it , UEFI tool (for parsing, extracting and modifying UEFI firmware images).

 

[Itconnects]

How did you get to Windows?

Depends. Hex Fiend (Insert, delete, rearrange) watch out for CRC32 checksums if you change anything with it , UEFI tool (for parsing, extracting and modifying UEFI firmware images).

I booted into windows via Option key, from shut down and triggered restart in windows control panel with windows option, which I reverted back to MacOS in startup disk control panel. Before OC, windows control panel never obeyed restart in MacOS command anyway. Rebless would probably bring back OC, but I want to have a little more clarity of what’s happening

Okay I just want to read dump to see if any cert has been written and if it’s possible to do an EFI install which OC supports

 

[jameslmoser]

I booted into windows via Option key, from shut down and triggered restart in windows control panel with windows option, which I reverted back to MacOS in startup disk control panel. Before OC, windows control panel never obeyed restart in MacOS command anyway. Rebless would probably bring back OC, but I want to have a little more clarity of what’s happening

Okay I just want to read dump to see if any cert has been written and if it’s possible to do an EFI install which OC supports

In the windows control panel did you see an option for "EFI Boot"? I can't test this right now as I'm not in front of my mac.

If you hold down the option key to boot into windows, you should see your macos installations and there should be an "EFI Boot" option (unless you changed the label when you originally blessed it), if you choose "EFI Boot" it should start up with OpenCore enabled.... from there it will show you the bootpicker if you have it enabled or just boot into macos.

 

[Itconnects]

In the windows control panel did you see an option for "EFI Boot"? I can't test this right now as I'm not in front of my mac.

If you hold down the option key to boot into windows, you should see your macos installations and there should be an "EFI Boot" option (unless you changed the label when you originally blessed it), if you choose "EFI Boot" it should start up with OpenCore enabled.... from there it will show you the bootpicker if you have it enabled or just boot into macos.

No, EFI boot is only available at Boot (Option key), not in MacOS start up disk or Windows Bootcamp control panel. Even if it was in Windows Bootcamp control panel, i don’t expect it to obey because it doesn’t obey Any change except windows boot

 

[jameslmoser]

No, EFI boot is only available at Boot (Option key), not in MacOS start up disk or Windows Bootcamp control panel. Even if it was in Windows Bootcamp control panel, i don’t expect it to obey because it doesn’t obey Any change except windows boot

Does it work if you disable SIP nvram? In recovery:

csrutil enable --without nvram

Anyways, choosing "EFI Boot" at boot should startup with OpenCore. You shouldn't have to rebless the partition (like you initially do per the instructions in recovery mode anyways).

 

[Itconnects]

Ya, I won’t type reboot until you respond

Does it work if you disable SIP nvram? In recovery:

csrutil enable --without nvram

Anyways, choosing "EFI Boot" at boot should startup with OpenCore. You shouldn't have to rebless the partition (like you initially do per the instructions in recovery mode anyways).

 

[jameslmoser]

Ya, I won’t type reboot until you respond

Yeah, that is the expected reponse... Does the windows control panel let you select MacOS now? I'm assuming its showing the APFS partitions already.

I don't really use the control panel because I had to hack it to get it to work with APFS and even then it seemed flakey.

 

[Itconnects]

Yeah, that is the expected reponse... Does the windows control panel let you select MacOS now? I'm assuming its showing the APFS partitions already.

I don't really use the control panel because I had to hack it to get it to work with APFS and even then it seemed flakey.

Fans were blowing at super high speed while booting in windows for some reason, never before. No EFI boot option in windows control panel or Mac. Only when option key is held down. I’m going to rebless the system now and confirm the same behavior

How do I revert back to enable with nvram for future references ?

Yes, MacOs boot is APFS

 

[Itconnects]

Same behavior. Holding down option and selecting windows boot hangs the boot. I need to shut down now, but this time while I’m in Windows I won’t touch the Bootcamp control panel. I think choosing Windows there shuts down OC for some reason.

Issue 1: OC prevents manually warm boot into windows, unless starting from complete shutdown

Issue 2: OC has to be reblessed after warmbooting into MacOs (Not confirmed)

 

[jameslmoser]

Fans were blowing at super high speed while booting in windows for some reason, never before. No EFI boot option in windows control panel or Mac. Only when option key is held down. I’m going to rebless the system now and confirm the same behavior

How do I revert back to enable with nvram for future references ?

Yes, MacOs boot is APFS

Just run the same command in recovery without the --without option.

crsutil enable
[automerge]1583374461[/automerge]

Same behavior. Holding down option and selecting windows boot hangs the boot. I need to shut down now, but this time while I’m in Windows I won’t touch the Bootcamp control panel. I think choosing Windows there shuts down OC for some reason

It does. If you are booting into anything other than the "EFI Boot" partition where OC is by holding down the option key, OpenCore is no longer active. That includes if you select MacOS directly by holding down the option key. To reactivate it, just choose "EFI Boot". You boot into opencore just like you would if its any other os entry.

Its possible to have multiple EFI Boot partitions show up there, so if thats the case you just need to know which one has it.