Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
startergo said:
You can try loading from rEFInd. Place these EFI Drivers in the drivers directory and modify the attached nsh startup script to your needs and place it next to your shell.efi tool. Start shell.efi (if your text mode does not work use the attached rEFInd version) and it should load whatever is requested in the startup.nsh script.
Click to expand...

Your RefindGOP worked, nsh and also using a patched boot.efi 0xfff on CoreServices worked, but I need that it could work from OpenCore too, and I guess only a modification on the source of OpenCore.efi could fix that.
 
  • Like
Reactions: startergo
startergo said:
That would be up to @vit9696 to decide or if you are skilled you can modify the OC source code. Glad it worked for you with rEFInd.
edit:
@jackluke you can try the same procedure in OC's context's shell.
Click to expand...

Your modified Refind allowed correctly to set 3 digit custom SIP value , but if @vit9696 could decide to allow an option for custom DMG also for OpenCore, because I made this script to allow booting USB BigSur Installer from Penryn non-APFS or legacy USB Mac: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28726070

also after using a stock createinstallmedia to install BigSur (or update a previous installation) on unsupported Mac is suffice this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28729919

From my other tests, I can use also a previous BaseSystem.dmg (patched) to boot a recent "Install macOS.app".
 
@vit9696 on the new release of OpenCore 0.6.0 , I just noticed:
  • Added preview version of KernelCollection injection code
it means that can inject kext on the BootKernelExtensions.kc ?
 
ч
cdf said:
The guide has been updated to OpenCore version 0.6.0.
Click to expand...
:rolleyes:
Снимок экрана 2020-08-03 в 20.17.22.png
 
Hi guys,
My X5690 is shown as 3,5 instead of 3,46 in system properties. Not sure what I’m supposed to tweak in OC config.
A helping hand would be highly appreciated.

thanks
 
phoenix.factory said:
My X5690 is shown as 3,5 instead of 3,46 in system properties. Not sure what I’m supposed to tweak in OC config.
Click to expand...

There is nothing to tweak. This is a feature of applying the hybridization and reflects how modern Macs display their processor information.
 
  • Like
Reactions: tommy chen
PeterHolbrook said:
HDMI used to work for me in Mojave. It doesn't work at all after updating to Catalina.
Click to expand...

What video card do you have? Did you use a patched install (or obtain the installer in any way related to such installs)?
 
cdf said:
The guide has been updated to OpenCore version 0.6.0.
Click to expand...
What is new in 0.6.0?

Is it worth to update from a stable 0.5.9 and doing all the processes of the advanced configurations?

I have tried to understand how to use the script by @TECK to simplify the configurations but I don't see it easy for simple users. Where can I learn to use it?

Thank you for your job and all the people here!
 
Ludacrisvp said:
github.com

Release 0.6.0 · acidanthera/OpenCorePkg

v0.6.0 Fixed sound corruption with AudioDxe Fixed icon choice for Apple FW update in OpenCanopy Fixed APFS driver loading on Fusion Drive Added Comet Lake HDA device code Fixed audio stream positi...
github.com github.com
Click to expand...
Thank you !
I see the list. Then. Is it worth to update from my stable 0.5.9 in my cMP 5.0 with no issues? Sorry for my question
 
Just looking through the new config file for 0.6 release, I noticed that the Wiki instructions on cleaning up the NVRAM don't reference the presence of the "RunEFIupdater" string.

This string is present in both of the NVRAM instructions in the 0.6 config file which are highlighted for deleting.
 
cdf said:
For updates, you can keep hybridization enabled; you just need to turn on the VMM flag.



Without enabling hardware acceleration (hybridization and WEG), you will not have DRM for Netflix in Safari. Things may be different for other apps and services. I would enable hardware acceleration and check. Make sure to let us know if it works.
Click to expand...

Thanks for taking the time to comment. That's good to know about needing to change the VMM flag only.

I enabled the hardware acceleration last night. Even though it appeared daunting in the Wiki, it was straightforward in the end. The TV app in Catalina functioned perfectly afterwards. Thank you every much.
 
  • Like
Reactions: cdf
Angelus said:
Just looking through the new config file for 0.6 release, I noticed that the Wiki instructions on cleaning up the NVRAM don't reference the presence of the "RunEFIupdater" string.

This string is present in both of the NVRAM instructions in the 0.6 config file which are highlighted for deleting.
Click to expand...

Good catch. I adjusted the wiki. The string should be kept in the unlikely case of undesired firmware updates.

Angelus said:
Even though it appeared daunting in the Wiki, it was straightforward in the end.
Click to expand...

Indeed. Because of the guide's explicitness, simple things look complicated.
 
startergo said:
I am forcing Orinoco frame buffer:
Code: 
AMD Radeon RX 580:

  Name:    ATY,Orinoco
  Type:    Display Controller
  Driver Installed:    Yes
  MSI:    Yes
  Bus:    PCI
  Slot:    Slot-1
  Vendor ID:    0x1002
  Device ID:    0x67df
  Subsystem Vendor ID:    0x1028
  Subsystem ID:    0x1701
  Revision ID:    0x00c7
  Link Width:    x16
  Link Speed:    5.0 GT/s
Click to expand...

Do you know what framebuffer would work with Vega 64? Mine is currently using RadeonFramebuffer and I wonder if its possible or worth it to force a compatible framebuffer.
 
lukesturr said:
Do you know what framebuffer would work with Vega 64? Mine is currently using RadeonFramebuffer and I wonder if its possible or worth it to force a compatible framebuffer.
Click to expand...
What's stopping you from using WhateverGreen.kext and Lilu.kext for Vega 64?
 
cdf said:
There is nothing to tweak. This is a feature of applying the hybridization and reflects how modern Macs display their processor information.
Click to expand...
Thanks for your answer. I just wanted OC to be as invisible as possible and the cMP to show the informations as close as possible to the original.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back