Do you have RX-580 for testing just to confirm whether the OC does not work with Radeon VII only or at all for you as @h9826790 I believe has the same card as you and cannot get it to work either.
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
You are still using 140.0.0.0.0? Apple did several changes with GOP support with 142.0.0.0.0, use 144.0.0.0.0.
Btw, @cdf besides Westmere, 144.0.0.0.0 should be a pre-requirement too.
Good catch! I actually have 144.0.0.0 so this must be a typo, corrected.
Just booted with my RX580 and exactly the same config.plist and it works. I get the boot selector and apple logo boot screen.
[automerge]1580685044[/automerge]
The "2" boot selection didn't work because my bluetooth keyboard apparently isn't alive yet at that point of boot. (SATECHI aluminium bluetooth)
But as stated in my previous post, RX580 just works so we probably still need a little tweak for the Radeon VII. If I can do anything to get log info let me know.
For now we are on our own as no more changes in the near future will be implemented for the OC bootpicker. Those settings with the MAX value or Graphics/Text are not firm so you will need to test around there with different values and the UI values as well. Something should work.
Isn't this Blessoverride :
" Designed to be filled with plist string entries containing absolute UEFI paths to customised bootloaders, for example, \EFI\Microsoft\Boot\bootmgfw.efi for Microsoft bootloader. This allows unusual boot paths to be automaticlly discovered by the boot picker. Designwise they are equivalent to predefined blessed path, such as \System\Library\CoreServices\boot.efi, but unlike predefined bless paths they have highest priority."
"3. Bless override option is not about specifying the default operating system. Bless override is about specifying a vendor extension to bless protocol. I.e. it lets you make OpenCore see specially named Windows or Linux bootloaders (e.g. something like \EFI\grub2\grub64.efi). "
The path to that boot loader should appear in the log file.
Last edited:
With this config and the newly released version 5.5 I can get a Bootscreen but with some weird graphics issues (pictures attached).
At first the screen turns red, then there is the boot menu, but Im not able to select an entry, not with the bluetooth keyboard nor with a usb one.
After the timeout it selects the Catalina bootdrive (first entry) and boots it in verbose mode.
After that it starts up normal.
(Sorry, for the bad quality of the first picture, but you are only able to see it for a second maybe, so it confuses the autofocus of my phone)
At first the screen turns red, then there is the boot menu, but Im not able to select an entry, not with the bluetooth keyboard nor with a usb one.
After the timeout it selects the Catalina bootdrive (first entry) and boots it in verbose mode.
After that it starts up normal.
(Sorry, for the bad quality of the first picture, but you are only able to see it for a second maybe, so it confuses the autofocus of my phone)
Can you provide boot log? You need the debug version of OpenCore.efi.
[automerge]1580728055[/automerge]
Also try another video output
Try setting one of these resolutions instead of MAX:
Code:
Mode 0 - 1920x1200:1
00:408 00:002 OCC: Mode 1 - 640x480:1
00:410 00:002 OCC: Mode 2 - 800x600:1
00:413 00:002 OCC: Mode 3 - 1024x768:1
00:417 00:004 OCC: Mode 4 - 1280x1024:1
00:423 00:005 OCC: Mode 5 - 1400x1050:1
00:425 00:002 OCC: Mode 6 - 1600x1200:1
00:427 00:002 OCC: Mode 7 - 1280x960:11920x1200 that is an odd resolution. What display it is?
Did you try enabling ConsoleControl and setting ConsoleBehaviourOs and ConsoleBehaviourUi to ForceGraphics?
I have that too. Remember this is not a perfect boot screen solution and it was not intended to be by design. It was just a way to provide us with a boot screen for the OC boot picker. As long as you can select the boot drive during boot and there is no KP during boot it is working as designed.
Most importantly it is an open code. Anybody with the right knowledge can fork the repository and enhance the drivers.
Last edited:
Im fully okay with that. If the behaviour doesn't harm my system everything is perfect.
I just wasn't sure because of these graphics issues.
Everything that gives me a boot picker is better than a black screen
I agree. Getting any kind of GOP support is significant.
The OpenCore documentation is very comprehensive. With some careful trial and error, you might be able to find the right settings for your system.
FYI I get "system halted" after the boot picker menu expires if I have both RX-480 (MVC and non -MVC) cards connected to the machine but not any display connected to the MVC card. If the displays are connected to both cards I can boot without a problem. The OC boot picker appears on the non-flashed card (weird) and the MVC EFI is suppressed up until the final boot stage.
16:10 displays are commonly used by Apple
Apple Cinema Display - Wikipedia
Apple didn't start using 16:9 until later. MacBook Pros still use 16:10 displays.
You can add refind to its own partition and add the appropriate core services folder and get refind showing in the system preferences prefpane. In theory that should tell refind to boot by default after OC. I had started down that path with my 3,1 but simply hadn’t the time to finish. I think the “connectdrivers” thing was killing me. As I could chainload sometimes I just didn’t realize why The behavior changed.
the install for refind calls this “ownhfs” but it does also work with apfs formatted drives. I didnt use the refind installer I simply manually placed the files in the right path and they showed up in the prefpane boot selector automatically.