Actually, with the files in place, BOOTx64.efi will appear as "EFI Boot" in the boot picker. However, as just pointed out, a Mac Pro does not generally have a native boot picker.
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
Is not the first OS, my first OS on boot picker is Windows, second Big Sur and third Mojave. Yet OC always picks the second choice because that is the selected startup disk. Pick a different startup disk in macOS and OC will use that one to boot by default. You can have OC boot picker remember always what disk to pick (regardless your startup disk) by setting MISC/Security/AllowSetDefault to True. Then you use Ctrl+Enter to pick and save your disk. Is all explained into OC documentation.
Hi @secondhandnews:
I was just going to post asking if anyone knows a fix for this issue without having to play around with the Ubuntu
/EFI/ folder files, but I see you've already posted and unless I missed a later answer been referred to the longer Ubuntu install instructions on p.1.So, I'll at least post the fix that worked for me by playing around with the
/EFI/ files, to avoid anyone else having to go through a full reinstall if they get this problem and might prefer to try this first (or perhaps even having to use a different Linux version as you did).So, I got the exact same issue of
Failed to set MokListRT followed by Could not read \EFI\ when trying to boot Ubuntu via OC - this was with a pre-existing install of Ubuntu from before I installed OC, which did (and still does) boot fine from the Apple bootpicker.I actually fixed it more or less as you were mentioning:
- Copy
/EFI/ubuntu/grubx64.efi into /EFI/BOOT- Remove (or just rename)
/EFI/BOOT/mmx64.efi and /EFI/BOOT/fbx64.efiAfter this, Ubuntu boots fine in both OC and in the Apple bootpicker. It also has the added advantage (as I see it!) of Ubuntu not putting up that message during boot about adding a
BOOT0000 nvram entry, and generally not taking over as the default boot OS.I have no idea why this is working and got to it by only slightly informed experimentation, so I am willing to be told exactly why it is horrible and wrong! (I do know that
Failed to set MokListRT is a red herring - it happens anyway, on a successful boot - Could not read \EFI\ is the real issue.)
Last edited:
@TECK: That is very helpful information, thank you!
As a minor point I noticed that even with
AllowSetDefault=true the OC bootpicker does not change the arrow icon as you hold CTRL (unlike the Apple bootpicker), so it is less obvious that the feature is there, but yes, indeed, it works fine - thank you!As a perhaps more interesting observation, and having only just now experimented with this, after getting your info: on my system at least (which is latest OC), then OC only uses the same default OS as the Apple bootpicker when
RequestBootVarRouting=false. If it is true then the OC and Apple bootpicker have separate defaults. (And also, in that case, until you change the OC default within OC it of course always stays on the first OS, which is what I was seeing.) (I have just tried and seen this: my Apple default OS was Ubuntu, but my OC default OS was Windows - as a quick test!)I have no idea whether that just-mentioned behaviour is per OC spec or not! I find it very hard to understand the OC docs at first, as they assume a huge amount of background knowledge about each relevant part of the OS and firmware!! You have to first learn that (which of course you can; often by playing around with OC settings which you do not quite understand, I am afraid to say!) and then you start to see what it all really means - at least in the part you have been learning! 😅
Open a suggestion on Acidanthera bugtracker, you're pretty good at it making it happen.
That is the intended failsafe value, if you change it, it will not behave that way. Also, people tend to say these are default OC settings, there is no such thing as
default property values in OC, read this.I personally read the documentation but I don't experiment often, as I only have one Mac. However, there are many users here who are helping by testing things, which is amazing.
Last edited:
I actually pointed this out to Vit a while ago, suggesting that a text version could be implemented first in Builtin mode, but it never panned out...Open a suggestion on Acidanthera bugtracker, you're pretty good at it making it happen.
@TECK Firstable, thank you so much for all the time you spend helping another people. I read you have windows as first OS. Is it very difficult to install Windows with OpenCore. I can see I can boot now from an external installation Windows 10 DVD. Never could do it before. But I remember @tsialex talking about problems with certificates on the ROM. Right?
Last edited:
From my perspective, is very easy to install Windows, following the @cdf guide listed into first post. Myself, I'm experiencing random freeze issues, which so far only another user does. Follow cdf's steps to create the USB image and also look at my detailed screenshots to install Windows and validate the EFI structure (see #32 and #33). Make sure the Microsoft directory is properly created inside EFI partition.
@cdf, maybe you can add a command to display the EFI structure, as on my install the files were not copied into right directory. The safest way is to create the Microsoft directory like I did and copy the files inside with an
archive switch.
Last edited:
I forgot to mention it, DO NOT install Windows from your bootable disk, follow cdf's guide. Also, make sure
ProtectSecureBoot=True, default in OC is False, which will write Windows certificates into your Mac firmware and damage the BootROM. cdf's config has that property value set to True, I switched also to this value into Plistlib Generator for safety reasons. @tsialex if you want to chime-in it will be appreciated, since you know much more on this subject.
Fortunately @******* already have a never booted image, he can install UEFI Windows, enable
ProtectSecureBoot=True then flash back the reconstructed image/disable SIP/bless OC/etc.Btw, SecureBoot is not the problem. It was seriously misunderstood when found back in High Sierra firmware betas. The whole problem is space inside the NVRAM, MP5,1 NVRAM is ridiculously tiny for today standards and SecureBoot der/pks/dbs are huge. If you don't have space available inside the NVRAM your are fast tracked to a brick. If you have, it's completely innocuous.
once i got Windows installed i downloaded the drivers for my new wireless card (FV-T919), shutdown, installed the card itself, rebooted and things were running smoothly for a while. at some point after idling for a bit in a browser window my system blue-screened again with the same driver error i've been getting.
does it make sense to just remove
bcmwl63a.sys entirely?
If I remember correctly, Microsoft and Broadcom had to correct an enormous security fail with Broadcom BCM controllers last year and the drivers had several updates. The problem is that these drivers are sent to OEMs directly and not to end users and are a pain to update.
Installing the 2012ish era drivers from BootCamp is not the best idea right now.
unless you're talking about bcmwl63a.sys, i'm not installing any drivers from BootCamp. i'd like to use my own wireless drivers.
EDIT: i was able to delete this driver all over the place and reinstall my Fenvi drivers. so far everything's running fine again. still working on audio...
Last edited:
I've talked specifically about Broadcom drivers, you have no other way to get Apple mice/keyboards support without BootCamp drivers.
For audio you can even install current Realtek drivers directly.
Speaking of bootcamp, the last time I installed Win10 was through BC on Sierra (MP3,1). This was via an actual OEM Windows 10 DVD so install was classic rather than UEFI.
Can I do the same on my 5,1 via Mojave and if so, is there anything I need to change in the config.plist file?
Can I do the same on my 5,1 via Mojave and if so, is there anything I need to change in the config.plist file?
Yes, you can and there is nothing to configure in OpenCore.
Long time lurker for admittedly (and embarrassingly) for decades now.
cMP 5,1 DP 3.46, Sapphire Radeon RX 580 has been running stably with Martin Lo's OC for a few months now. Have been running Big Sur 11.0 and I think MLo's OC 0.6.3.
As I use it as my work machine, I've avoided doing updates. However, seeing that MLo's OC 0.6.6 now apparently handles updates just fine without doing the whole flag thing, I figured I'd give it a shot this morning.
That broke it. Won't finish booting and it restarts -- going back to the OC boot picker screen. Also a black-screen warning message that reminded me of a kernel panic...
It will boot into the 11.2.1 recovery drive just fine, though -- which is interesting. Also tried reinstalling a copy over the original failed installation. No dice. Trying a fresh install from recovery to an external drive for now to see what happens.
This is with the macOS 11.2.1 2nd release that was likely released within the past 24 hours.
Any help appreciated, again -- especially as I need this for work and my backup is 150 miles away right now. Cheers and thanks.
cMP 5,1 DP 3.46, Sapphire Radeon RX 580 has been running stably with Martin Lo's OC for a few months now. Have been running Big Sur 11.0 and I think MLo's OC 0.6.3.
As I use it as my work machine, I've avoided doing updates. However, seeing that MLo's OC 0.6.6 now apparently handles updates just fine without doing the whole flag thing, I figured I'd give it a shot this morning.
That broke it. Won't finish booting and it restarts -- going back to the OC boot picker screen. Also a black-screen warning message that reminded me of a kernel panic...
It will boot into the 11.2.1 recovery drive just fine, though -- which is interesting. Also tried reinstalling a copy over the original failed installation. No dice. Trying a fresh install from recovery to an external drive for now to see what happens.
This is with the macOS 11.2.1 2nd release that was likely released within the past 24 hours.
Any help appreciated, again -- especially as I need this for work and my backup is 150 miles away right now. Cheers and thanks.
We have found that hybridization with firmware features is enough for updates in Big Sur. However, Big Sur has been flip-flopping on how it checks the system before installation and updates.
I wonder if this isn't the reason. Maybe something changed here. Most users have probably updated with the first version. Perhaps other users that have done this update with the second version could chime in.
So, I tried to install Linux Ubuntu 20.10. I followed the instructions exactly. I get a Linux disk in OpenCanopy, but when I try to boot this disk I just get a black screen and I get moved back to OpenCanopy automatically. I am using OpenCore 0.6.6. What am I doing wrong?