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

[h9826790]

Please this Icon Pack give for me. Like this! Thank!

This?
[automerge]1588689325[/automerge]

@h9826790,
Thanks for the response. What I meant was the actual set of icons from where those two specific ones came from originally.

The TimeMachine and Windows icons look different from the others in your image and I presume they came from a specific set.

Oh, sorry, I forget that the public package only contain the standard disk icons.

I just post the zip file in post #2101, is that what you want?

 

[lbuisson]

@h9826790,
Thanks for the response. What I meant was the actual set of icons from where those two specific ones came from originally.

The TimeMachine and Windows icons look different from the others in your image and I presume they came from a specific set.

That's depending of each user want to have or create icons
for example what I created for my OC :

 

[Dayo]

I just post the zip file in post #2101, is that what you want?

os_recovery.icns seems to be from one family of icons and os_win.icns seems to be from another family.
Trying to get either one or both of the rest of those families if you have the source.

for example what I created for my OC

Thanks but I don't use NDK or any OC bootpicker and my purpose is totally different.

 

[leoaf79]

You will find in my original post (bottom)

https://forums.macrumors.com/thread...80.2231649/page-2?post=28399065#post-28399065

Thanks, mate. Funny thing is that you posted originally at my birthday date (April 24). So, thanks for this awesome gift.

 

[h9826790]

os_recovery.icns seems to be from one family of icons and os_win.icns seems to be from another family.
Trying to get either one or both of the rest of those families if you have the source.


Thanks but I don't use NDK or any OC bootpicker and my purpose is totally different.

Sorry, I really don't have the source. I have my own icons collections. I keep those for many years already. Some of them are extracted from the macOS itself, and some of them are downloaded from the internet. I can't remember which one is from which source.

 

[Dayo]

Sorry, I really don't have the source.

No Problem. Thanks

 

[TECK]

@cdf is there a Quirk I can use to make the NVMes external show as internal? So the icons do not show on desktop.
Or do I set a DeviceProperty? I saw:

OpenCore on the Mac Pro

DeviceProperties Add PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0) built-in AA== Block You will have to find the path of your drives with GFXUTIL.

forums.macrumors.com

I installed GFXUTIL but I have no idea how to find the drive path.

 

[cdf]

@cdf is there a Quirk I can use to make the NVMes external show as internal? So the icons do not show on desktop.
Or do I set a DeviceProperty? I saw:

OpenCore on the Mac Pro

DeviceProperties Add PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0) built-in AA== Block You will have to find the path of your drives with GFXUTIL.

forums.macrumors.com

Yes, adding a device property is the right way to do it.

 

[Dayo]

I can't remember which one is from which source.

Found that ithe Windows one is from an icon set known as "Minimum-2" and the time machine one is from "ive-drives"

 

[vit9696]

OpenCanopy now properly supports HiDPI and arbitrary background colour mode (including grey). I guess that was mostly demanded by legacy MacPro users =)

 

[Draeconis]

The correct base64 value to disable SIP under OC for real macs is

dwAAAA==

In addition: To disable SIP and Hyper-threading using OC I used

<key>boot-args</key>
                <string>-no_compat_check cwae=2</string>
                <key>csr-active-config</key>
                <data>dwAAAA==</data>
                <key>SMTDisable</key>
                <data>AQ==</data>

The above survives NVRAM/PRAM resets under OC if you wish to always have SIP and Hyper-Threading disabled on cMP 5,1

Hey, was just reading about setting SMTDisable as apparently I'd missed the notification on that.

added the SMTDisable entry above in the right place, shows up when reading nvram back, but hyper threading is still enabled?

 

[w1z]

Hey, was just reading about setting SMTDisable as apparently I'd missed the notification on that.

added the SMTDisable entry above in the right place, shows up when reading nvram back, but hyper threading is still enabled?

Works for me.

You need to power off after adding the entry and rebooting the first time. I also have not added entries to Block/boot-args.

 

[h9826790]

OpenCanopy now properly supports HiDPI and arbitrary background colour mode (including grey). I guess that was mostly demanded by legacy MacPro users =)

You mean the latest 0.5.9 beta, right?

 

[w1z]

You mean the latest 0.5.9 beta, right?

Yes. Just tried it, worked nicely.

 

[Grumply]

Hi guys, I've run into a bit of pickle. I had a nice, stable build with OC 0.5.7 with OSX Mojave on an NVME and Windows 10 on a SATA SSD.

I moved on to OC 0.5.8 on the OSX drive which finally gave me a 100% correct bootpicker (OSX, Recovery, Windows), where before I had (Non-working Windows, OSX, Working Windows, no Recovery icon).

However I ran out of space on both OS Drives, so picked up two new 1TB SATA SSDs to migrate both OSs on to. That caused me a whole bunch of grief, now (thankfully) resolved (seemingly).

However, now, having finally got clean, working OS clones on both 1TB SATA SSDs. I've lost bootpicker functionality when both SSDs are installed.

If I unplug the Windows SSD, I load into bootpicker on the OSX SSD (showing just OSX and Recovery Icons). And if I unplug the OSX SSD, I load up cleanly into Windows 10. But with both SSDs plugged in, I never see Bootpicker, and it just loads me up directly into Windows.

Is there anything I can do here to force the 5,1 to prioritise the OSX SSD, so that I load into the bootpicker first (so that I can choose which OS to boot into)? That functionality was working fine before I migrated to the new SSDs.

 

[lbuisson]

@cdf and @h9826790
I compared your 2 config files
- one's on 1st post from cdf
- one's on cMP post from h9826790

and they are a lot different.

Which one I need to use for update in OC 0.5.8?

1. keep mine from 0.5.7
2. replace by the new one 0.5.8
3. merge between twice?

thank you

 

[h9826790]

@cdf and @h9826790
I compared your 2 config files
- one's on 1st post from cdf
- one's on cMP post from h9826790

and they are a lot different.

Which one I need to use for update in OC 0.5.8?

1. keep mine from 0.5.7
2. replace by the new one 0.5.8
3. merge between twice?

thank you

Of course, my config is mainly for providing full HWAccel, and I activated few more functions that some people may want (e.g. able to "run" Catalina).

cdf's config is mainly for providing the ability to run Catalina on cMP. It's the cleanest solution. My config can't even "install" Catalina (because of the SMBIOS spoofing), and it contain Lilu / WhateverGreen etc that some people don't want.

IMO, the best way of course to learn how to config OC properly, and make your own config.

Merge isn't a good idea if you don't know what you are doing. This can cause lots of issues.

If you only want OpenCore for Catalina, please stick with cdf's config.
[automerge]1588756494[/automerge]

Yes. Just tried it, worked nicely.

Just want to make sure that's for 0.5.9 beta. Otherwise, some people may confused that post / comment is for the latest 0.5.8 official release.

 

[startergo]

Hi guys, I've run into a bit of pickle. I had a nice, stable build with OC 0.5.7 with OSX Mojave on an NVME and Windows 10 on a SATA SSD.

I moved on to OC 0.5.8 on the OSX drive which finally gave me a 100% correct bootpicker (OSX, Recovery, Windows), where before I had (Non-working Windows, OSX, Working Windows, no Recovery icon).

However I ran out of space on both OS Drives, so picked up two new 1TB SATA SSDs to migrate both OSs on to. That caused me a whole bunch of grief, now (thankfully) resolved (seemingly).

However, now, having finally got clean, working OS clones on both 1TB SATA SSDs. I've lost bootpicker functionality when both SSDs are installed.

If I unplug the Windows SSD, I load into bootpicker on the OSX SSD (showing just OSX and Recovery Icons). And if I unplug the OSX SSD, I load up cleanly into Windows 10. But with both SSDs plugged in, I never see Bootpicker, and it just loads me up directly into Windows.

Is there anything I can do here to force the 5,1 to prioritise the OSX SSD, so that I load into the bootpicker first (so that I can choose which OS to boot into)? That functionality was working fine before I migrated to the new SSDs.

Where is the OC installed? On Both drives? The easiest way to find out is to plug in all drives and use an EFI video card, boot with option key pressed and see what is selected by default. Scroll to the OC option and hit cntrl+enter. This will save OC as the default start drive. On the next reboot (replacing the EFI card with the regular AMD card it should boot to the OC boot picker menu. Also normally when you clone the drives the EFI partition does not get cloned.

 

[Grumply]

Where is the OC installed? On Both drives? The easiest way to find out is to plug in all drives and use an EFI video card, boot with option key pressed and see what is selected by default. Scroll to the OC option and hit cntrl+enter. This will save OC as the default start drive. On the next reboot (replacing the EFI card with the regular AMD card it should boot to the OC boot picker menu. Also normally when you clone the drives the EFI partition does not get cloned.

OC is only on the OSX drive. Can I put it on the EFI Partition of the Windows drive as well?

 

[h9826790]

OC is only on the OSX drive. Can I put it on the EFI Partition of the Windows drive as well?

Can but better not to. This often create more trouble than benefit.

IMO, having two OC copies on two macOS / data drive's EFI partition should be good enough. In case the primary drive failed, or you accidentally break the config etc, you can simply pull out the primary drive, and let the cMP boot from the backup copy of OC.

 

[Grumply]

Can but better not to. This often create more trouble than benefit.

IMO, having two OC copies on two macOS / data drive's EFI partition should be good enough. In case the primary drive failed, or you accidentally break the config etc, you can simply pull out the primary drive, and let the cMP boot from the backup copy of OC.

Yep, I've already got a backup drive on-hand. It's just getting back to setup I had before (where the computer would load to bootpicker every time), and then I could pick from there, whether to load OSX or Windows.

Currently, I have to physically unplug the SSD with the OS I'm not using, before I can start the computer.

 

[lbuisson]

Of course, my config is mainly for providing full HWAccel, and I activated few more functions that some people may want (e.g. able to "run" Catalina).

cdf's config is mainly for providing the ability to run Catalina on cMP. It's the cleanest solution. My config can't even "install" Catalina (because of the SMBIOS spoofing), and it contain Lilu / WhateverGreen etc that some people don't want.

IMO, the best way of course to learn how to config OC properly, and make your own config.

Merge isn't a good idea if you don't know what you are doing. This can cause lots of issues.

If you only want OpenCore for Catalina, please stick with cdf's config.

Thank you
in my case OC is used for Mojave and Win10 only
no Catalina
then I need to keep your config from 0.5.7?

 

[h9826790]

Thank you
in my case OC is used for Mojave and Win10 only
no Catalina
then I need to keep your config from 0.5.7?

If the 0.5.7 package works for you, there is no need to update.

But if you want to, you can go 0.5.8 by replacing the whole package.

Activate AMD hardware acceleration

I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...

forums.macrumors.com

 

[lbuisson]

If the 0.5.7 package works for you, there is no need to update.

But if you want to, you can go 0.5.8 by replacing the whole package.

There is no improvement between 0.5.7 and 8 for cMP?

 

[vrds]

There is no improvement between 0.5.7 and 8 for cMP?

Take a look at the changelog. Have any related problems? Update. No? Then why touch things that just work?