I updated through Software Update after manually enrolling my machine to the beta program. (Unfortunately, being away from my machine, I don't have the terminal commands at hand.)
Got a tip for us?
Let us know
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
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I updated through Software Update after manually enrolling my machine to the beta program. (Unfortunately, being away from my machine, I don't have the terminal commands at hand.)
My cMP has several partitions with various OSes. It also has a RX 580. I installed OC with the help of h9826790 and his work on HW acceleration. Problem is, one of my partition has High Sierra and won't boot if I disable Lilu/WhateverGreen for this OS in my config. If I don't disable it, then High Sierra boots but HW is activated and if an app uses it, it crashes the system.
I read that WhateverGreen has a "don't activate HW acceleration" boot argument. Which could be a solution to my problem. Is there a way to add this boot argument only for when I boot High Sierra? Can that be done in the config.plist?
I read that WhateverGreen has a "don't activate HW acceleration" boot argument. Which could be a solution to my problem. Is there a way to add this boot argument only for when I boot High Sierra? Can that be done in the config.plist?
Thanks. Weirdly enough, that was the case - as that's how h9826790 did it in his OC package, but when doing so, neither Sierra nor High Sierra will boot. If I let Lilu/WEG load, then fine. Hence the idea of just disabling HW acceleration.
But apart from using minkernel, there are no other ways of setting a behaviour individually and depending on the OS that will load then?
I played a little with open core and it worked for me with my GPUs with Bootscreen, I have seen the OS Chooser.
Now I want to do some tests with no-mac-bootscreen-but-uefi GPUs.
Excuse me for my ignorancebut I cannot get a boot screen with the settings of post 1 on some of my old UEFI GPUs like GT640 and Quadro K600.
I checked the Firmware and for example my K600 should have UEFI support
also I fired up nvflash and it gave me info:
UEFI Version 0x10015 (Oct 26 2012)
UEFI Signers Microsoft 2011
is that UEFI GOP or am I wrong ?
As an all time Mac User I have no clue about this UEFI GOP stuff.
I know that those GPUs are weak, but at least they are silent and affordable Kepler cards.
Must self reply:
I got hands on another low end Quadro GPU what seems to have uefi gop.
It worked with the un-edited settings file from post 1 (3-13-2020), no graphical issues, clean grey screen since the open core boot menu and further boot looked exactly like if I had an efi GPU.
Now I have another challenge, flashing PC GPUs for UEFI GOP.
Fiddling now with knowledge and a tool to add / correct GOP from here:
AMD and Nvidia GOP update (No requests, DIY)
I’m not really the guy to run on unlimited supply of patience, so this will be more a mix of tutorial, tool to do the job for you, assistance (“as long as you don’t insist with unlimited/unrelated questions” kind) and ABSOLUTELY NO GUARANTEES. Users should read this again, I am not offering any...
www.win-raid.com
But I still dont get it when and why a GPU Firmware is UEFI and what is the difference of UEFI GOP and how to determine if a PC GPU is GOP or not.
Someone jumps in and teach an ole dog new tricks ,-)
Well you have a GT640 and Quadro EFI firmwares. Get the corresponding original ROM's from the techpower database and compare the differences. Pay particular attention to fixing the checksums as it will brake the boot screen even in OC.
yes, but as simple as this:
Is, when nvflash reports a GPU has UEFI and certs from Microsoft, a PC GPU an uefi gop GPU ?
Or are uefi and uefi gop two different things ?
see:
NVIDIA Kepler GPUs had an update very later in life to be GOP compatible, around Maxwell time. You had to ask eVGA for a firmware update, without it, pre-boot configuration support don't work.
Did you read my reply?
Activate AMD hardware acceleration
Use this guide, this for Windows and this manual. The guide missed sudo. Use this command: sudo VBoxManage internalcommands createrawvmdk -filename ".vmdk" -rawdisk /dev/disk# Where /dev/disk# is the disk number where you will be installing Windows revealed by diskutil list. First, make sure the...
forums.macrumors.com
You never need to run Bootcamp (in MacOS) on cMP to install Windows. It’s just an apps for making partition and download the driver package.
OpenCore on the Mac Pro
Here's a quick write-up of the process I took to get OpenCore (OC) booting macOS and Windows in UEFI mode on the MacPro5,1. I don't recommend doing this right now. There's something flakey in either OC, my configuration of OC, or Windows itself which will eventually result in your Windows...
forums.macrumors.com
This might be it! The boot args i just enter into the terminal, right? Or can i integrate it into the OpenCore somewhere?
Edit: when i enter it in the terminal, i get a response like this:
nvram: Error setting variable - 'boot-args': (iokit/common) general error
get the message that this version of Mac OS X is not supported on this platform.
Last edited:
i entered it in recovery mode, rebooted, tried to install Caralina, nothing happend. Just the blocked sign appears, then the computer turns off. I tried to integrate it as boot-args into the config.plist, but this also does nothing.
I suggest you re-read post #1 and start everything again. It's very hard for us to know what you've done wrong. Rather than try to find out what's the problem. Start from scratch again should be easier and quicker.
Or if that still doesn't work, may be you can try my 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
N.B. This package is NOT designed for Catalina installation. However, after you install that package, you can follow my video guide at here to activate the ability for installing Catalina.
Doing a fresh and clean install of Mojave, instead of migrating my old High Sierra installation, fixed the problem.
This did the trick! I just integrated the TB3 support and now Catalina is running fine! ?
Thanks a lot!Thanks for a very nice guide!
However, I have a couple of questions.
i) Regarding step 8. - What does the VMM flag really do, and why does it give a performance loss?
ii) Regarding step 9. - Is this just something I would do if I would want to stop using Catalina on my 5.1, or if I have difficulty booting back to Mojave?
The VMM flag basically just makes Catalina think its running in a virtual machine, so it bypasses the hardware checks that prevent Catalina from being updated. MacOS probably has optimizations for certain architectures that also probably don't work because it just runs with whatever is probably best for virtualized hardware.
You don't have to uninstall OC to boot directly into the OS. Its actually really easy to do if you have a video card you can get to the apple boot picker with (hold down option key, then select the macOS install directly, not EFI boot). You don't even need to use it to run Catalina once its installed if you use:
nvram boot-args="-no_compat_check"
Avoiding? OC is not something which will install on its own on your system so you should avoid it. If you don't know what it is then you most probably don't need it. All your questions will find their answers by reading the OC manual. Spend some time and read the manual.
You asked about uninstalling OC and if it was necessary if you wanted to boot back to Mojave. I answered it. No, you don't need to uninstall it to run Mojave OR Catalina.
As far as reasons you might want to? Who knows, but I can think of a few:
1) If you were trouble shooting to see if a problem was being caused by OpenCore.
2) You have a BootCamp installation that uses legacy boot.
3) You have multiple OC configurations and switch between them... for example one to update Catalina and one for daily use.
Last edited by a moderator:
OC developers are working on their own GUI Bootliquor.efi.
It is still in development and it is not in the manual from what I understand. Those of you who already tested NdkBootPicker.efi may test easily BootLiquor.efi. All you have to do is:
Of course you need to put BootLiquor.efi in the drivers folder and the "Resources" folder inside the OC folder. Generate the "Resources" folder with Pavo's OC builder
If you want to compile it from master you may need to issue this command (if you have errors compiling):
After pressing spacebar I got some icons getting out of the screen. There is no secondary raw like in NDK's bootlicker:
It is still in development and it is not in the manual from what I understand. Those of you who already tested NdkBootPicker.efi may test easily BootLiquor.efi. All you have to do is:
Code:
<key>UEFI</key>
<dict>
<key>ConnectDrivers</key>
<true/>
<key>Drivers</key>
<array>
<string>FwRuntimeServices.efi</string>
<string>NTFS.efi</string>
<string>#NdkBootPicker.efi</string>
<string>BootLiquor.efi</string>If you want to compile it from master you may need to issue this command (if you have errors compiling):
Code:
# Change the path if you installed Xcode somewhere else.
sudo xcode-select -s /Applications/Xcode.app/Contents/DeveloperAfter pressing spacebar I got some icons getting out of the screen. There is no secondary raw like in NDK's bootlicker:
