Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Very interesting. OC already includes a version of XhciDxe.efi. Do you think you could verify if that version can be used instead (in addition to UsbBusDxe.efi and UsbMassStorageDxe.efi)?
Sorry for the late reply
The OC version of XhciDxe does not work with the Mac Pro's Legacy EFI, it will cause OC to hang
Edit: https://github.com/dortania/OpenCore-Legacy-Patcher/issues/254 has a decent explanation, though a MacBook Pro is used
 
External USB3.1 booting

I hope the following is not considered to be entirely off-topic. If someone believes it is, let me know and I'll erase it and move it somewhere else.

I followed with great interest last week's discussion regarding USB3 PCI cards with a specific chip and booting from USB devices attached to said cards. The only thing partially similar to such cards at my disposal is a Mac-flashed Titan-Ridge Thunderbolt 3 card, which has two USB-C connectors at the rear. All my previous attempts at booting via this card had been unsuccessful. That has just changed. I've just booted from an ExFat-formatted USB 3.1 thumb drive with a Windows 11 installer connected to a USB 3.1 hub attached to one of the USB-C ports of my Thunderbolt 3 card. Naturally, this is possible thanks to OpenCore (0.7.6 in my case) and the UsbBusDxe.efi and XhciDxe.efi drivers shared last week by one of our forum members (I don't remember his/her name right now, apologies) (I must stress that the XhciDxe.efi driver that comes with OC didn't work for me).

For what it's worth, this is the relevant portion of config.plist that did the trick for me:
Code:
    <dict>
    <key>Arguments</key>
    <string></string>
    <key>Comment</key>
    <string></string>
    <key>Enabled</key>
    <true/>
    <key>Path</key>
    <string>UsbBusDxe.efi</string>
    </dict>
    <dict>
    <key>Arguments</key>
    <string></string>
    <key>Comment</key>
    <string></string>
    <key>Enabled</key>
    <true/>
    <key>Path</key>
    <string>XhciDxe.efi</string>
    </dict>

EDIT: You'll also need to set UEFI/Quirks/ForgeUefiSupport to TRUE.

EDIT2: Although it is now possible to boot an operating system from an external USB device via the OpenCore Picker, macOS itself won't let you select any external USB devices as startup disks on a Mac Pro 5,1. As a matter of fact, it won't even see them.
 
Last edited:
External USB3.1 booting

I hope the following is not considered to be entirely off-topic. If someone believes it is, let me know and I'll erase it and move it somewhere else.

I followed with great interest last week's discussion regarding USB3 PCI cards with a specific chip and booting from USB devices attached to said cards. The only thing partially similar to such cards at my disposal is a Mac-flashed Titan-Ridge Thunderbolt 3 card, which has two USB-C connectors at the rear. All my previous attempts at booting via this card had been unsuccessful. That has just changed. I've just booted from an ExFat-formatted USB 3.1 thumb drive with a Windows 11 installer connected to a USB 3.1 hub attached to one of the USB-C ports of my Thunderbolt 3 card. Naturally, this is possible thanks to OpenCore (0.7.6 in my case) and the UsbBusDxe.efi and XhciDxe.efi drivers shared last week by one of our forum members (I don't remember his/her name right now, apologies) (I must stress that the XhciDxe.efi driver that comes with OC didn't work for me).

For what it's worth, this is the relevant portion of config.plist that did the trick for me:
Code:
    <dict>
    <key>Arguments</key>
    <string></string>
    <key>Comment</key>
    <string></string>
    <key>Enabled</key>
    <true/>
    <key>Path</key>
    <string>UsbBusDxe.efi</string>
    </dict>
    <dict>
    <key>Arguments</key>
    <string></string>
    <key>Comment</key>
    <string></string>
    <key>Enabled</key>
    <true/>
    <key>Path</key>
    <string>XhciDxe.efi</string>
    </dict>

EDIT: You'll also need to set UEFI/Quirks/ForgeUefiSupport to TRUE.
So you dropped the drivers in the fold and added the relevant code? I tried this last week and I got black screen on boot. I don't think the ForgeUefiSupport was set to true but I may do a test shortly.
 
You might want to try this Lilu plugin to disable the error:

I'm sorry that I'm going back several months with a request for help on this post. (Post #7,297 on Mar 1, 2021
)
I can't find anywhere that I've searched (this forum and many others) on how to add this plugin to Lilu in order to disable the 'incompatible disk' error in Mojave on one of my OpenCore configured Macs. (it will be the Monterey disk on this Mac that's triggering it no doubt).
Where do I put the DiskArbitrationFixup folder (or part of it's content) ?
and
What do I need to edit in my Config.plist? (I'm using the format at post 1 with the recommended edits) to enable it?

Thanks
 
Last edited:
I can't find anywhere that I've searched (this forum and many others) on how to add this plugin to Lilu in order to disable the 'incompatible disk' error in Mojave on one of my OpenCore configured Macs.
You'll need the actual kext file. But unfortunately, it seems that builds are not (no longer?) readily available. Another obstacle is that Lilu has changed quite a bit since the code was last maintained. Probably best to just ignore that pesky message.
 
Hi. Again. I'm back because I'm unable to upgrade OpenCore from 0.72 to 0.76 and let Catalina boot correctly. As I wrote above, I replaced my nvme SSD copying ESP and boot partition: now with new nvme all works as with previous. But I'd like to update OpenCore too. As I jump from 0.72 to 0.76, I guess it should be simpler go as with a new installation, following the steps in the first page. Ad it's what I did. More times, until now. I found even I made an error editing the sample config file posted monday, not editing all parts of Hybridization section, but even I corrected this error, Catalina won't boot with OC 0.76. Today I started again from scratch, following step by step the guide in first page, downloading OC0.76 and all kext again, and editing newly the sample config downloaded from first page, adding even SurPlus, cleaning up the NVRAM, enabling Monterey firmware features, etc. But no luck.
I compared this new config file with the one I created monday, finding the error I wrote above, and all known difference between the two config (SurPlus, etc.), so if all the rest is identical, I can't figure there are any other errors. All config files are tested with plutil and ocvalidate. But with none of them I can't boot Catalina. Does here someone use Catalina anymore? Could someone post a OC 0.76 config file that works correctly with Catalina (so I try to understand if and which are th differences)? I'll bundle my last edited Config, in case someone has the time and desire to try it.
 

Attachments

  • config 076.plist.zip
    3.9 KB · Views: 66
But with none of them I can't boot Catalina.
It looks like you're spoofing the iMacPro board-id. In that case, to avoid a black screen on boot, you'll need the agdpmod=pikera device property or boot argument.
 
You'll need the actual kext file. But unfortunately, it seems that builds are not (no longer?) readily available. Another obstacle is that Lilu has changed quite a bit since the code was last maintained. Probably best to just ignore that pesky message.
Thanks for the swift reply.
 
Hi guys, just installed OC 0.7.6 following amazing guide on first post. I'm on mojave 10.14.6 a Mac Pro 2x3.46 with rx 580 pulse, everything seems working perfectly (eg. finally i see as internal my sm951... ) except for boot screen, i have same black screen until login as before.. is there something i can check to solve it? if you need some log, how can i get it? thanks in advance

in attach my config
 

Attachments

  • config.plist.zip
    3.7 KB · Views: 60
EDIT2: Although it is now possible to boot an operating system from an external USB device via the OpenCore Picker, macOS itself won't let you select any external USB devices as startup disks on a Mac Pro 5,1. As a matter of fact, it won't even see them.

Same procedure allows my el cheapo USB3 PCIe controller to boot. Some data for those who google:

Host Controller Driver: AppleASMediaUSBXHCI
PCI Device ID: 0x1242
PCI Revision ID: 0x0000
PCI Vendor ID: 0x1b21
 
i have same black screen until login as before.. is there something i can check to solve it?
This is likely caused by the firmware of your video card. Search for "techpowerup" and "tiny switch" in this thread.
 
This is likely caused by the firmware of your video card. Search for "techpowerup" and "tiny switch" in this thread.
Do i need a PC to check it?
Another thing, i just checked with my gtx 680 mac edition, at the boot holding alt, i see my macintosh hd and efi, going on efi i enter in the OC picker... maybe is there a problem here? I thought with OC booting was directly to OC picker

thanks
 
Do i need a PC to check it?
No, your Mac Pro is enough. Windows may be useful for flashing the VBIOS, though.

I thought with OC booting was directly to OC picker
Yes, if OC is blessed, then booting will be directly to the OC boot menu. However, with an EFI graphics card, holding Option (Alt), will always bring up the native boot menu. No problem here.
 
  • Like
Reactions: JeDiGM
No, your Mac Pro is enough. Windows may be useful for flashing the VBIOS, though.


Yes, if OC is blessed, then booting will be directly to the OC boot menu. However, with an EFI graphics card, holding Option (Alt), will always bring up the native boot menu. No problem here.
Ok, got it my second question, thank you.

About first one, how can I check my Radeon bios on my Mac?
 
About first one, how can I check my Radeon bios on my Mac?
I don't know if there is a way to check it, but if you bought your card second hand, then it is likely that the VBIOS has been modified. In this case, finding the stock firmware in the Techpowerup library and simply flashing it using Windows is the best solution. You can also use FreeDOS or the EFI Shell. Your GTX 680 will be useful here.

There are many good resources available in this forum for solving this issue:

 
  • Like
Reactions: spideyrsf
I don't know if there is a way to check it, but if you bought your card second hand, then it is likely that the VBIOS has been modified. In this case, finding the stock firmware in the Techpowerup library and simply flashing it using Windows is the best solution. You can also use FreeDOS or the EFI Shell. Your GTX 680 will be useful here.

There are many good resources available in this forum for solving this issue:

Ok thanks you, I will give a look and a try ✌???
 
Given the new OpenLinuxBoot driver (thanks to @Bmju), those instructions had become outdated. An improved method will be included in due time.
Hi @cdf, any updates on this? I have not been able to boot linux on my machine, only faced with a grey screen unfortunately.
 
Greetings - hope to get some help...

I am trying to update OC from 0.6.7 to 0.7.6, but I am getting stuck in boot with progress bar hanging when booting into any of my two existing Big Sur installations.

Booting into the Mojave installation works, where I am able to revert back to my previous OC 0.6.7 version, and be able to boot the Big Sur installations again.

This happens even with the standard config for 0.7.6 per the initial post in this thread.
I had initially enabled SurPlus and Hybridization with the same effect, which is why I tried the unmodified comfig.plist, but this did not behave any different.

My setup:
970 EVO: macOS 11.6.2
SM951: macOS 11.6.2
840 EVO: macOS 10.14.6 (Mojave)

Any help would be appreciated - thanks!
 
Greetings - hope to get some help...

I am trying to update OC from 0.6.7 to 0.7.6, but I am getting stuck in boot with progress bar hanging when booting into any of my two existing Big Sur installations.

Booting into the Mojave installation works, where I am able to revert back to my previous OC 0.6.7 version, and be able to boot the Big Sur installations again.

This happens even with the standard config for 0.7.6 per the initial post in this thread.
I had initially enabled SurPlus and Hybridization with the same effect, which is why I tried the unmodified comfig.plist, but this did not behave any different.

My setup:
970 EVO: macOS 11.6.2
SM951: macOS 11.6.2
840 EVO: macOS 10.14.6 (Mojave)

Any help would be appreciated - thanks!
Have you updated your config.plist with the new version for .76? If not try using the basic one at the bottom of the 1st post in this thread and see if you can boot with that. First guess would be some issue in your config.plist.
 
Have you updated your config.plist with the new version for .76? If not try using the basic one at the bottom of the 1st post in this thread and see if you can boot with that. First guess would be some issue in your config.plist.
Yes, I downloaded the new basic config.plist for .76 along with the new packages, and I am building up the configuration from that file. So even with the unmodified freshly downloaded config file, Big Sur does not boot (whereas Mojave does).
 
Yes, I downloaded the new basic config.plist for .76 along with the new packages, and I am building up the configuration from that file. So even with the unmodified freshly downloaded config file, Big Sur does not boot (whereas Mojave does).
Have you carefully looked through the "Basic Setup" section of the first post? Some settings are different depending on what version of macOS you are trying to boot.

If nothing is obvious then post your config.plist here. members like @cdf are excellent in spotting settings that would (for example) allow Mojave to boot but not Big Sur.

Also for Big Sur make sure you have added the "Surplus" patch. See the "Complete your setup" section of the first post.
 
It looks like you're spoofing the iMacPro board-id. In that case, to avoid a black screen on boot, you'll need the agdpmod=pikera device property or boot argument.
In which config file? As I wrote, I started editing OC 0.76 sample config file, following step by step the instructions in first page... but I can't boot Catalina (lately also Mojave) with OC 0.76. I tried even using unmodified sample file, and today I tried to add "agdpmod=pikera" in the configuration that most closely follows the instructions (config 076.plist). I tried even to pick some other parts from my working OC 0.72 config file (config AB.plist), but with none of them, I'm able to boot using OC 0.76
 

Attachments

  • OC 0.76 Config files.zip
    7.8 KB · Views: 61
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.